None was operating from KNIP to KNIP on 2026-06-23. SkyMeter detected a low approach-stability score at Jacksonville Naval Air Station (Towers Field) (KNIP) on runway 28 at 18:40 UTC. Trace data at the event: 1114 ft AGL, 179 kt GS. METAR at the time reported 9 kt wind, 4 kt crosswind component, 16,093 m visibility. The approach-stability score rates the final approach against stabilized-approach gates (glideslope, lateral deviation, descent rate, and IAS) at defined altitudes. A low score means one or more of those were outside the normal envelope for how the approach was flown. The score is graded by guidance type, so instrument approaches (ILS or an aligned straight-in) are held to the full gate set, while visual and pattern arrivals are surfaced only when the score is clearly low. The score is advisory and observational, a deviation measure, not an assertion of an accident. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- SECURITY6/9513 2026-06-22 12:30Z – 2026-06-26 06:00Z SFC–2,500 ft
MAYPORT, FL, Monday, June 22, 2026 through Friday, June 26, 2026 Local
View FAA NOTAM →
SkyMeter cross-referenced this flight against FAA-published TFRs that were active during its window and within its geographic bounding box. Overlap doesn't necessarily mean violation — the aircraft may have been outside the TFR’s precise polygon or flying under air-traffic-control coordination.
Pilot review data
- Runway 28
- 1114 ft AGL at event
- 179 kt ground speed
- 0 fpm vertical
- 9 kt wind
- 4 kt crosswind component
- 16,093 m visibility
- KNIP 091753Z 07015G27KT 10SM SCT015 BKN035 OVC055 26/22 A2998 RMK AO2 PK WND 06028/1717 SLP147 60005 T02560222 10261 20244 58005
Flight context
- None
- P8
- KNIP → KNIP
- 2026-06-23 18:40 UTC
- KNIP runway 28
All events on this flight
Automated analysis. Events shown on this page (such as go-around, unstable approach, or runway events) are heuristic classifications produced by algorithms from publicly broadcast ADS-B data. They are intended to surface flights of interest for further review — they are not findings of fact, and they do not determine pilot fault, regulatory compliance, or the cause of any occurrence. Coverage gaps and sensor noise can affect accuracy. Only the relevant civil aviation authority or accident investigation body can make official determinations. How we detect events · Dispute or correct this data