Unstable approach — AAL667
KDCA · 192026-07-09 02:16 UTC· KMIA → KDCA· BANK OF UTAH TRUSTEE· A321
AAL667 (Bank of Utah) was operating from KMIA to KDCA on 2026-07-09. SkyMeter detected a low approach-stability score at Ronald Reagan Washington National Airport (KDCA) on runway 19 at 02:16 UTC. Trace data at the event: 1132 ft AGL, 141 kt GS. Approach stability score: 57/100. Scores in this band occur on roughly 10-15% of approaches at this runway, with multiple gates outside the per-runway envelope. METAR at the time reported 7 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/2809 2025-10-20 12:00Z – 2026-10-20 12:00Z SFC–2,000 ft
Palm Beach, FL, Monday, October 20, 2025 through Tuesday, October 20, 2026 Local
View FAA NOTAM → - SECURITY6/3968 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Winston Salem, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/3971 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Winston Salem, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4001 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
GREENSBORO, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4005 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Greensboro, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4129 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
BOCA RATON, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4131 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
MYRTLE BEACH, SC, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4144 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
FORT LAUDERDALE, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4150 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Palm Beach Gardens, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/0777 2026-06-26 04:01Z – 2026-07-21 03:59Z SFC–400 ft
Fort Lauderdale, FL, Friday, June 26, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/0782 2026-06-26 04:01Z – 2026-07-21 03:59Z SFC–400 ft
Fort Lauderdale, FL, Friday, June 26, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/7906 2026-06-29 15:07Z – 2026-07-21 03:59Z SFC–400 ft
Boca Raton, FL
View FAA NOTAM → - SECURITY6/7889 2026-07-07 13:07Z – 2026-07-21 03:59Z SFC–400 ft
Palm Beach Gardens, FL
View FAA NOTAM → - SECURITY6/7899 2026-07-07 13:07Z – 2026-07-21 03:59Z SFC–400 ft
Palm Beach Gardens, FL
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
- 1132 ft AGL at event
- 141 kt ground speed
- 0 fpm vertical
- Approach stability 57/100
- 7 kt wind
- 3 kt crosswind component
- 16,093 m visibility
- KDCA 010152Z 19006KT 10SM BKN250 20/18 A3010 RMK AO2 SLP193 T02000178
Flight context
- AAL667
- Bank of Utah
- A321
- KMIA → KDCA
- 2026-07-09 02:16 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