Go-around — UAL2179
KORD · 27C2026-07-15 21:12 UTC· KMSY → KORD· UNITED AIRLINES INC· B739
UAL2179 (United Airlines) was operating from KMSY to KORD on 2026-07-15. SkyMeter detected a go-around at Chicago O'Hare International Airport (KORD) on runway 27C at 21:12 UTC. Trace data at the event: 1088 ft AGL, 163 kt GS. METAR at the time reported 5 kt wind, 2 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)- SECURITY6/4114 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
LOUISVILLE, KY, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4116 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
LOUISVILLE, KY, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4118 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
CARMEL, IN, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4128 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
WESTFIELD, IN, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4119 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
NASHVILLE, TN, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4121 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
Nashville, TN, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4161 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
St, Louis, MO, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/7205 2026-06-23 21:07Z – 2026-07-21 03:59Z SFC–400 ft
Carmel, IN
View FAA NOTAM → - SECURITY6/7208 2026-06-23 21:07Z – 2026-07-21 03:59Z SFC–400 ft
Westfield, IN
View FAA NOTAM → - SECURITY6/7972 2026-07-01 16:07Z – 2026-07-21 04:59Z SFC–400 ft
Nashville, TN
View FAA NOTAM → - SECURITY6/7967 2026-07-01 16:07Z – 2026-07-21 04:59Z SFC–400 ft
Nashville, TN
View FAA NOTAM → - SECURITY6/7197 2026-07-09 11:07Z – 2026-07-21 03:59Z SFC–400 ft
Louisville, KY
View FAA NOTAM → - SECURITY6/7817 2026-07-09 11:07Z – 2026-07-21 04:59Z SFC–400 ft
St Louis, MO
View FAA NOTAM → - SECURITY6/4909 2026-07-11 12:00Z – 2026-07-16 23:59Z SFC–400 ft
Pell City, AL, Saturday, July 11, 2026 through Thursday, July 16, 2026 Local
View FAA NOTAM → - UAS PUBLIC GATHERING6/4323 2026-07-14 22:30Z – 2026-07-16 04:30Z SFC–400 ft
chicago, IL, Tuesday, July 14, 2026 through Thursday, July 16, 2026 UTC
View FAA NOTAM → - AIR SHOWS/SPORTS6/4051 2026-07-15 12:30Z – 2026-07-18 21:00Z SFC–15,000 ft
Pensacola Beach, FL, Wednesday, July 15, 2026 through Saturday, July 18, 2026 UTC
View FAA NOTAM → - SECURITY6/5591 2026-07-15 17:00Z – 2026-07-20 04:59Z SFC–400 ft
Hammond, IN, Wednesday, July 15, 2026 through Sunday, July 19, 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 27C
- 1088 ft AGL at event
- 163 kt ground speed
- 0 fpm vertical
- 5 kt wind
- 2 kt crosswind component
- 16,093 m visibility
- KORD 161851Z 02008KT 10SM BKN025 BKN034 OVC120 23/18 A3030 RMK AO2 SLP256 T02330178 $
Flight context
- UAL2179
- United Airlines
- B739
- KMSY → KORD
- 2026-07-15 21:12 UTC
- KORD runway 27C
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