Unstable approach — N4269T

KVGT · 30L

2026-05-17 02:37 UTC· FUNK DANIEL M· P28A

N4269T (Funk Daniel M) was inbound to KVGT on 2026-05-17. SkyMeter detected a low approach-stability score at North Las Vegas Airport (KVGT) on runway 30L at 02:37 UTC. Trace data at the event: 2797 ft AGL, 82 kt GS. Approach stability score: 31/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 6 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.

Pilot review data

  • Runway 30L
  • 2797 ft AGL at event
  • 82 kt ground speed
  • 0 fpm vertical
  • Approach stability 31/100
  • 6 kt wind
  • 4 kt crosswind component
  • 16,093 m visibility
  • KVGT 131153Z AUTO 06005KT 10SM CLR 25/17 A2987 RMK AO2 SLP106 T02500167 10283 20250 53003

Flight context

  • N4269T
  • Funk Daniel M
  • P28A
  • 2026-05-17 02:37 UTC
  • KVGT runway 30L

All events on this flight

Unstable approach 02:37:29 UTC · KVGT runway 30L · 2,797 ft AGL · 82 kt GS
Unstable approach 02:37:29 UTC · KVGT runway 30L · 2,797 ft AGL · 82 kt GS
Unstable approach 02:37:29 UTC · KVGT runway 30L · 2,797 ft AGL · 82 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· KVGT