Go-around — UAL1138
KLAX · 25L2026-08-04 12:55 UTC· UNITED AIRLINES INC· B38M
UAL1138 (United Airlines) was inbound to KLAX on 2026-08-04. SkyMeter detected a go-around at Los Angeles International Airport (KLAX) on runway 25L at 12:55 UTC. Trace data at the event: 276 ft AGL, 157 kt GS, 0 fpm vertical. METAR at the time reported 2 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)- SECURITY5/6914 2025-05-06 23:30Z – 2027-10-18 11:03Z SFC–6,000 ft
South Padre Island, TX, Tuesday, May 6, 2025 Local
View FAA NOTAM → - SECURITY5/3678 2026-01-01 05:00Z – 2027-01-01 05:59Z SFC–2,000 ft
Brownsville, TX, Thursday, January 1, 2026 through Friday, January 1, 2027 Local
View FAA NOTAM → - SECURITY5/3679 2026-01-01 05:00Z – 2027-01-01 05:59Z SFC–5,000 ft
Brownsville, TX, Thursday, January 1, 2026 through Friday, January 1, 2027 Local
View FAA NOTAM → - SECURITY6/4165 2026-02-14 07:00Z – 2026-08-15 06:59Z SFC–400 ft
Nogales, AZ, Saturday, February 14, 2026 through Friday, August 14, 2026 Local
View FAA NOTAM → - SECURITY6/4160 2026-02-14 08:00Z – 2026-08-15 06:59Z SFC–400 ft
Chula Vista, CA, Saturday, February 14, 2026 through Friday, August 14, 2026 Local
View FAA NOTAM → - SECURITY6/4240 2026-03-08 08:00Z – 2026-11-01 07:00Z SFC–180 ft
SAN ANGELO, TX, Sunday, March 8, 2026 through Sunday, November 1, 2026 Local
View FAA NOTAM → - SECURITY6/2652 2026-07-05 00:01Z – 2027-01-02 23:59Z SFC–500 ft
Coyote Wells, CA, Saturday, July 4, 2026 through Saturday, January 2, 2027 Local
View FAA NOTAM → - SECURITY6/2656 2026-07-05 00:01Z – 2027-01-02 23:59Z SFC–500 ft
Coyote Wells, CA, Saturday, July 4, 2026 through Saturday, January 2, 2027 Local
View FAA NOTAM → - SECURITY6/2657 2026-07-05 00:01Z – 2027-01-02 23:59Z SFC–500 ft
Calexico, CA, Saturday, July 4, 2026 through Saturday, January 2, 2027 Local
View FAA NOTAM → - SECURITY6/4812 2026-07-15 07:00Z – 2027-07-14 06:59Z SFC–17,999 ft
El Centro, CA, Wednesday, July 15, 2026 through Tuesday, July 13, 2027 Local
View FAA NOTAM → - HAZARDS6/0712 2026-08-01 02:09Z – 2026-08-05 04:00Z SFC–9,000 ft
15NM N RAMONA, CA, Saturday, August 1, 2026 through Wednesday, August 5, 2026 UTC
View FAA NOTAM → - HAZARDS6/0745 2026-08-01 14:00Z – 2026-08-14 04:00Z SFC–9,000 ft
15NM N RAMONA, CA, Saturday, August 1, 2026 through Friday, August 14, 2026 UTC
View FAA NOTAM → - HAZARDS6/0749 2026-08-01 15:00Z – 2026-08-14 03:00Z SFC–13,000 ft
13NM S SAFFORD, AZ, Saturday, August 1, 2026 through Friday, August 14, 2026 UTC
View FAA NOTAM → - HAZARDS6/1456 2026-08-03 23:57Z – 2026-08-04 13:00Z
109 ELZABETH LN, TX, Monday, August 3, 2026 through Tuesday, August 4, 2026 UTC
View FAA NOTAM → - HAZARDS6/1463 2026-08-04 02:02Z – 2026-08-04 13:00Z SFC–5,000 ft
NM 109 ELZABETH LN, TX, Tuesday, August 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 25L
- 276 ft AGL at event
- 157 kt ground speed
- 0 fpm vertical
- 2 kt wind
- 2 kt crosswind component
- 16,093 m visibility
- KLAX 162153Z COR 23012KT 10SM FEW020 25/14 A2996 RMK AO2 SLP142 T02500144 $
Flight context
- UAL1138
- United Airlines
- B38M
- 2026-08-04 12:55 UTC
- KLAX runway 25L
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