Go-around — UAL8220
KORD · 28C2026-04-23 11:02 UTC· KHAF → KORD· UNITED AIRLINES INC· A21N
UAL8220 (United Airlines) was operating from KHAF to KORD on 2026-04-23. SkyMeter detected a go-around at Chicago O'Hare International Airport (KORD) on runway 28C at 11:02 UTC. Trace data at the event: 974 ft AGL, 131 kt GS. METAR at the time reported 6 kt wind, 6 kt crosswind component, 9,656 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/3475 2026-03-08 09:00Z – 2026-11-01 09:59Z SFC–180 ft
BEALE AFB, CA, Sunday, March 8, 2026 through Sunday, November 1, 2026 Local
View FAA NOTAM → - SECURITY6/5797 2026-04-03 00:01Z – 2026-09-28 23:59Z SFC–400 ft
SACRAMENTO, CA, Thursday, April 2, 2026 through Monday, September 28, 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 28C
- 974 ft AGL at event
- 131 kt ground speed
- 0 fpm vertical
- 6 kt wind
- 6 kt crosswind component
- 9,656 m visibility
- KORD 210051Z 04013G18KT 6SM -RA BR SCT015 BKN022 OVC027 17/15 A3004 RMK AO2 PK WND 06026/0014 DZE01RAB01 SLP171 P0000 T01670150 $
Flight context
- UAL8220
- United Airlines
- A21N
- KHAF → KORD
- 2026-04-23 11:02 UTC
- KORD runway 28C
All events on this flight
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