Unstable approach — C102

KDCA · 19

2026-07-25 15:32 UTC· KDAL KDCA· GLF5

C102 was operating from KDAL to KDCA on 2026-07-25. SkyMeter detected a low approach-stability score at Ronald Reagan Washington National Airport (KDCA) on runway 19 at 15:32 UTC. Trace data at the event: 1127 ft AGL, 127 kt GS. Approach stability score: 40/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 2 kt wind, 1 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)
  • HAZARDS6/6848 2026-07-20 00:32Z – 2026-08-03 23:45Z SFC–3,000 ft

    2NM W SHULERVILLE, SC, Monday, July 20, 2026 through Monday, August 3, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/7051 2026-07-21 04:00Z – 2026-07-29 04:00Z SFC–4,200 ft

    18NM SW WAYNESBORO, VA, Tuesday, July 21, 2026 through Wednesday, July 29, 2026 UTC

    View FAA NOTAM →
  • VIP6/8360 2026-07-24 19:00Z – 2026-07-26 23:00Z SFC–4,999 ft

    Middleburg, VA, Friday, July 24, 2026 through Sunday, July 26, 2026 Local

    View FAA NOTAM →
  • VIP6/8424 2026-07-25 11:30Z – 2026-07-25 22:30Z SFC–9,999 ft

    Sterling, VA, Saturday, July 25, 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 19
  • 1127 ft AGL at event
  • 127 kt ground speed
  • 0 fpm vertical
  • Approach stability 40/100
  • 2 kt wind
  • 1 kt crosswind component
  • 16,093 m visibility
  • KDCA 282152Z 22016G25KT 10SM SCT047 BKN080 BKN250 29/19 A2953 RMK AO2 PK WND 20029/2111 SLP001 CB DSNT NW-NE AND SW MOV E T02940194

Flight context

  • C102
  • GLF5
  • KDAL → KDCA
  • 2026-07-25 15:32 UTC
  • KDCA runway 19

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· KDCA