Go-around — AAL2236
KONT · 26R2026-06-10 02:38 UTC· KDFW → KONT· AMERICAN AIRLINES INC· A321
AAL2236 (American Airlines) was operating from KDFW to KONT on 2026-06-10. SkyMeter detected a go-around at Ontario International Airport (KONT) on runway 26R at 02:38 UTC. Trace data at the event: 1771 ft AGL, 142 kt GS. METAR at the time reported 10 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/0091 2026-01-04 00:01Z – 2026-07-04 23:59Z SFC–500 ft
Coyote Wells, CA, Saturday, January 3, 2026 through Saturday, July 4, 2026 Local
View FAA NOTAM → - SECURITY6/0092 2026-01-04 00:01Z – 2026-07-04 23:59Z SFC–500 ft
CALEXICO, CA, Saturday, January 3, 2026 through Saturday, July 4, 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 → - HAZARDS6/4313 2026-05-31 14:00Z – 2026-06-14 03:00Z SFC–8,000 ft
13NM NW CARLSBAD, NM, Sunday, May 31, 2026 through Sunday, June 14, 2026 UTC
View FAA NOTAM → - HAZARDS6/4403 2026-05-31 14:00Z – 2026-06-14 04:00Z SFC–11,000 ft
18NM NE TUCSON, AZ, Sunday, May 31, 2026 through Sunday, June 14, 2026 UTC
View FAA NOTAM → - SECURITY6/3999 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
ARLINGTON, TX, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4000 2026-06-01 05:00Z – 2026-07-21 04:59Z
MANSFIELD, TX, Monday, June 1, 2026 through Tuesday, July 21, 2026 UTC
View FAA NOTAM → - SECURITY6/4002 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
FORT WORTH, TX, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4025 2026-06-01 05:00Z – 2026-07-21 04:59Z
DENTON, TX, Monday, June 1, 2026 through Tuesday, July 21, 2026 UTC
View FAA NOTAM → - SECURITY6/3948 2026-06-01 07:00Z – 2026-07-21 06:59Z
MESA, AZ, Monday, June 1, 2026 through Tuesday, July 21, 2026 UTC
View FAA NOTAM → - SECURITY6/3966 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
Mesa, AZ, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4182 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
Irvine, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4183 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
San Diego, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4201 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
Dana Point, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4202 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
San Diego, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4203 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
San Diego, CA, Monday, June 1, 2026 through Monday, July 20, 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 26R
- 1771 ft AGL at event
- 142 kt ground speed
- 0 fpm vertical
- 10 kt wind
- 2 kt crosswind component
- 16,093 m visibility
- KONT 181153Z 00000KT 10SM FEW022 17/14 A3007 RMK AO2 SLP168 T01720144 10194 20172 55000
Flight context
- AAL2236
- American Airlines
- A321
- KDFW → KONT
- 2026-06-10 02:38 UTC
- KONT runway 26R
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