Go-around — UAL768
KORD · 10C2026-06-03 00:46 UTC· KSEA → KORD· UNITED AIRLINES INC· B738
UAL768 (United Airlines) was operating from KSEA to KORD on 2026-06-03. SkyMeter detected a go-around at Chicago O'Hare International Airport (KORD) on runway 10C at 00:46 UTC. Trace data at the event: 2092 ft AGL, 161 kt GS. METAR at the time reported 6 kt wind, 5 kt crosswind component, 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)- HAZARDS6/2318 2026-05-22 14:00Z – 2026-06-05 04:00Z SFC–9,000 ft
17NM SW HELENA, MT, Friday, May 22, 2026 through Friday, June 5, 2026 UTC
View FAA NOTAM → - HAZARDS6/2646 2026-05-25 15:00Z – 2026-06-08 04:00Z SFC–11,000 ft
22NM SE JACKSON, WY, Monday, May 25, 2026 through Monday, June 8, 2026 UTC
View FAA NOTAM → - HAZARDS6/3585 2026-05-28 14:00Z – 2026-06-11 03:00Z SFC–9,000 ft
74NM S MILES CITY, MT, Thursday, May 28, 2026 through Thursday, June 11, 2026 UTC
View FAA NOTAM → - HAZARDS6/3649 2026-05-28 14:00Z – 2026-06-11 03:00Z SFC–9,000 ft
74NM S MILES CITY, MT, Thursday, May 28, 2026 through Thursday, June 11, 2026 UTC
View FAA NOTAM → - HAZARDS6/3574 2026-05-29 14:00Z – 2026-06-10 02:00Z SFC–13,000 ft
38NM SE TWIN FALLS, ID, Friday, May 29, 2026 through Wednesday, June 10, 2026 UTC
View FAA NOTAM → - HAZARDS6/3888 2026-05-29 14:00Z – 2026-06-10 04:00Z SFC–13,000 ft
38NM SE TWIN FALLS, ID, Friday, May 29, 2026 through Wednesday, June 10, 2026 UTC
View FAA NOTAM → - HAZARDS6/3908 2026-05-29 14:00Z – 2026-06-12 04:00Z SFC–9,000 ft
23NM SE GLENDIVE, MT, Friday, May 29, 2026 through Friday, June 12, 2026 UTC
View FAA NOTAM → - SECURITY6/4158 2026-06-01 06:00Z – 2026-07-21 05:59Z SFC–400 ft
MERIDIAN, ID, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4159 2026-06-01 06:00Z – 2026-07-21 05:59Z SFC–400 ft
Boise, ID, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4011 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
BELLEVUE, WA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4033 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
RENTON, WA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4034 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
Renton, WA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - HAZARDS6/4637 2026-06-02 13:00Z – 2026-06-05 03:00Z SFC–10,000 ft
62NM NW GREEN RIVER, WY, Tuesday, June 2, 2026 through Friday, June 5, 2026 UTC
View FAA NOTAM → - HAZARDS6/4736 2026-06-02 13:00Z – 2026-06-04 02:00Z SFC–7,500 ft
3NM NW GARDEN VALLEY, ID, Tuesday, June 2, 2026 through Thursday, June 4, 2026 UTC
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 10C
- 2092 ft AGL at event
- 161 kt ground speed
- 0 fpm vertical
- 6 kt wind
- 5 kt crosswind component
- 16,093 m visibility
- KORD 181751Z 07011KT 10SM -RA FEW025 FEW050 SCT090 BKN130 21/13 A3026 RMK AO2 RAB49 SLP242 P0000 60000 T02060133 10222 20183 58009
Flight context
- UAL768
- United Airlines
- B738
- KSEA → KORD
- 2026-06-03 00:46 UTC
- KORD runway 10C
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