Unstable approach — N5379F
KCAK · 142026-08-21 00:06 UTC· KPDK → KCAK· N5379F LLC· F2TH
N5379F (N5379f) was operating from KPDK to KCAK on 2026-08-21. SkyMeter detected a low approach-stability score at Akron Canton Regional Airport (KCAK) on runway 14 at 00:06 UTC. Trace data at the event: 2341 ft AGL, 165 kt GS. METAR at the time reported 5 kt wind, 5 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)- VIP6/5889 2026-08-20 21:15Z – 2026-08-23 21:15Z SFC–4,999 ft
Cincinnati, OH, Thursday, August 20, 2026 through Sunday, August 23, 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 14
- 2341 ft AGL at event
- 165 kt ground speed
- 0 fpm vertical
- 5 kt wind
- 5 kt crosswind component
- 16,093 m visibility
- KCAK 161051Z 20004KT 10SM SCT050 BKN080 19/18 A3027 RMK AO2 SLP244 T01940183
Flight context
- N5379F
- N5379f
- F2TH
- KPDK → KCAK
- 2026-08-21 00:06 UTC
- KCAK runway 14
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