Unstable approach — N784LA

KDYL · 05

2026-06-02 16:58 UTC· KPNE KDYL· N784LA LLC· P28A

N784LA (N784la) was operating from KPNE to KDYL on 2026-06-02. SkyMeter detected a low approach-stability score at Doylestown Airport (KDYL) on runway 05 at 16:58 UTC. Trace data at the event: 1004 ft AGL, 79 kt GS. Approach stability score: 30/100. Scores below 50 occur on under 10% of approaches at this runway and indicate the v2 scorer flagged the approach as highly anomalous (three or more gates exceeded the runway's P90 envelope simultaneously). METAR at the time reported 11 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.

Pilot review data

  • Runway 05
  • 1004 ft AGL at event
  • 79 kt ground speed
  • 0 fpm vertical
  • Approach stability 30/100
  • 11 kt wind
  • 3 kt crosswind component
  • 16,093 m visibility
  • METAR KDYL 130654Z AUTO VRB03KT 10SM CLR 23/18 A2982 RMK AO2 RAB18E30 SLP092 P0000 T02280183

Flight context

  • N784LA
  • N784la
  • P28A
  • KPNE → KDYL
  • 2026-06-02 16:58 UTC
  • KDYL runway 05

All events on this flight

Unstable approach 16:58:40 UTC · KDYL runway 05 · 1,004 ft AGL · 79 kt GS
Unstable approach 16:58:40 UTC · KDYL runway 05 · 1,004 ft AGL · 79 kt GS
Unstable approach 16:58:40 UTC · KDYL runway 05 · 1,004 ft AGL · 79 kt GS

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

SkyMeter · trace data observed via ADS-B· KDYL