Go-around — AAL843
KDCA · 192026-08-30 22:21 UTC· KTPA → KDCA· AMERICAN AIRLINES INC· B738
AAL843 (American Airlines) was operating from KTPA to KDCA on 2026-08-30. SkyMeter detected a go-around at Ronald Reagan Washington National Airport (KDCA) on runway 19 at 22:21 UTC. Trace data at the event: 450 ft AGL, 145 kt GS, 0 fpm vertical. METAR at the time reported 7 kt wind, 16,093 m visibility. A go-around is a discontinued landing approach in which the pilot adds power and climbs back to a safe altitude before re-attempting the approach or proceeding to an alternate. It is a routine safety response, not an emergency, and is taught as the standard reaction to any unstable approach. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- SECURITY6/6989 2026-08-27 21:00Z – 2026-09-02 21:00Z SFC–400 ft
Asheville, NC, Thursday, August 27, 2026 through Wednesday, September 2, 2026 Local
View FAA NOTAM → - VIP6/8638 2026-08-28 20:00Z – 2026-08-30 21:00Z SFC–4,999 ft
Middleburg, VA, Friday, August 28, 2026 through Sunday, August 30, 2026 Local
View FAA NOTAM → - VIP6/8772 2026-08-30 13:00Z – 2026-08-30 23:00Z SFC–9,999 ft
Sterling, VA, Sunday, August 30, 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
- 450 ft AGL at event
- 145 kt ground speed
- 0 fpm vertical
- 7 kt wind
- 0 kt crosswind component
- 16,093 m visibility
- KDCA 161452Z 16008KT 10SM FEW250 24/17 A3039 RMK AO2 SLP290 T02390167 51008
Flight context
- AAL843
- American Airlines
- B738
- KTPA → KDCA
- 2026-08-30 22:21 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