Unstable approach — N39EG
KDYL · 052026-07-23 14:40 UTC· KN14 → KDYL· INDEL SERVICES LLC· C510
N39EG (Indel Services) was operating from KN14 to KDYL on 2026-07-23. SkyMeter detected a low approach-stability score at Doylestown Airport (KDYL) on runway 05 at 14:40 UTC. Trace data at the event: 1503 ft AGL, 122 kt GS. METAR at the time reported 5 kt wind, 3 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)- SECURITY5/2811 2025-10-20 12:00Z – 2026-10-20 12:00Z SFC–1,000 ft
NEW YORK, NY, Monday, October 20, 2025 through Tuesday, October 20, 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 05
- 1503 ft AGL at event
- 122 kt ground speed
- 0 fpm vertical
- 5 kt wind
- 3 kt crosswind component
- 16,093 m visibility
- METAR KDYL 160454Z AUTO 00000KT 10SM CLR 15/12 A3035 RMK AO2 SLP276 T01500122 402280100
Flight context
- N39EG
- Indel Services
- C510
- KN14 → KDYL
- 2026-07-23 14:40 UTC
- KDYL runway 05
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