Go-around — UAL752
KTUL · 18L2026-07-18 20:48 UTC· KORD → KTUL· UNITED AIRLINES INC· A319
UAL752 (United Airlines) was operating from KORD to KTUL on 2026-07-18. SkyMeter detected a go-around at Tulsa International Airport (KTUL) on runway 18L at 20:48 UTC. Trace data at the event: 1075 ft AGL, 147 kt GS. METAR at the time reported 25 kt wind, 23 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/4134 2026-06-01 00:00Z – 2026-07-20 23:59Z
TULSA, OK, Monday, June 1, 2026 through Monday, July 20, 2026 UTC
View FAA NOTAM → - SECURITY6/4135 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
CLAYTON, MO, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4141 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
Tulsa, OK, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4146 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
Lawrence, KS, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4149 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
Lawrence, KS, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4151 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
Kansas City, MO, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4154 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
Kansas City, KS, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4155 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
Riverside, MO, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4157 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
PRAIRIE VILLAGE, KS, 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/4162 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
Kansas City, MO, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4206 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
Kansas City, MO, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/7652 2026-07-01 16:07Z – 2026-07-21 04:59Z SFC–400 ft
Riverside, MO
View FAA NOTAM → - SECURITY6/7650 2026-07-01 16:07Z – 2026-07-21 04:59Z SFC–400 ft
Kansas City, MO
View FAA NOTAM → - SECURITY6/7646 2026-07-03 16:07Z – 2026-07-21 04:59Z SFC–400 ft
Lawrence, KS
View FAA NOTAM → - SECURITY6/7647 2026-07-03 16:07Z – 2026-07-21 04:59Z SFC–400 ft
Lawrence, KS
View FAA NOTAM → - SECURITY6/7651 2026-07-09 11:07Z – 2026-07-21 04:59Z SFC–400 ft
Prairie Village, KS
View FAA NOTAM → - SECURITY6/7817 2026-07-09 11:07Z – 2026-07-21 04:59Z SFC–400 ft
St Louis, MO
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 18L
- 1075 ft AGL at event
- 147 kt ground speed
- 0 fpm vertical
- 25 kt wind
- 23 kt crosswind component
- 16,093 m visibility
- KTUL 162053Z 17014G22KT 10SM TS SCT065CB BKN110 BKN250 37/21 A3012 RMK AO2 TSB51 SLP188 OCNL LTGIC S TS S MOV N T03670206 56015
Flight context
- UAL752
- United Airlines
- A319
- KORD → KTUL
- 2026-07-18 20:48 UTC
- KTUL runway 18L
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