Unstable approach — N916VD

KLAS · 19R

2026-08-22 17:29 UTC· KTLH KLAS· GLF5

N916VD was operating from KTLH to KLAS on 2026-08-22. SkyMeter detected a low approach-stability score at McCarran International Airport (KLAS) on runway 19R at 17:29 UTC. Trace data at the event: 3269 ft AGL, 139 kt GS. Approach stability score: 44/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, 6 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/4240 2026-03-08 08:00Z – 2026-11-01 07:00Z SFC–180 ft

    SAN ANGELO, TX, Sunday, March 8, 2026 through Sunday, November 1, 2026 Local

    View FAA NOTAM →
  • SECURITY6/2656 2026-07-05 00:01Z – 2027-01-02 23:59Z SFC–500 ft

    Coyote Wells, CA, Saturday, July 4, 2026 through Saturday, January 2, 2027 Local

    View FAA NOTAM →
  • SECURITY6/2657 2026-07-05 00:01Z – 2027-01-02 23:59Z SFC–500 ft

    Calexico, CA, Saturday, July 4, 2026 through Saturday, January 2, 2027 Local

    View FAA NOTAM →
  • SECURITY6/0708 2026-08-01 00:01Z – 2027-08-01 23:59Z SFC–400 ft

    Goodlettsville, TN, Saturday, August 1, 2026 through Sunday, August 1, 2027 UTC

    View FAA NOTAM →
  • HAZARDS6/3712 2026-08-11 14:00Z – 2026-08-25 04:00Z SFC–8,000 ft

    18NM SW PRESCOTT, AZ, Tuesday, August 11, 2026 through Tuesday, August 25, 2026 UTC

    View FAA NOTAM →
  • UAS PUBLIC GATHERING6/3173 2026-08-13 21:00Z – 2026-08-23 07:00Z SFC–400 ft

    Lebanon, TN, Thursday, August 13, 2026 through Sunday, August 23, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/5409 2026-08-17 04:00Z – 2026-08-30 04:00Z SFC–13,500 ft

    13NM N SANTA FE, NM, Monday, August 17, 2026 through Sunday, August 30, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/6216 2026-08-19 03:00Z – 2026-09-02 03:00Z SFC–13,500 ft

    13NM N SANTA FE, NM, Wednesday, August 19, 2026 through Wednesday, September 2, 2026 UTC

    View FAA NOTAM →
  • SECURITY6/6976 2026-08-22 06:00Z – 2026-08-23 13:00Z SFC–17,999 ft

    Libby AAF, AZ, Friday, August 21, 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 19R
  • 3269 ft AGL at event
  • 139 kt ground speed
  • 0 fpm vertical
  • Approach stability 44/100
  • 6 kt wind
  • 6 kt crosswind component
  • 16,093 m visibility
  • KLAS 100256Z 12003KT 10SM FEW180 38/07 A2997 RMK AO2 SLP117 T03780072 55008

Flight context

  • N916VD
  • GLF5
  • KTLH → KLAS
  • 2026-08-22 17:29 UTC
  • KLAS runway 19R

All events on this flight

Unstable approach 17:29:22 UTC · KLAS runway 19R · 3,269 ft AGL · 139 kt GS
Unstable approach 17:29:22 UTC · KLAS runway 19R · 3,269 ft AGL · 139 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· KLAS