Rejected takeoff — AAL2030
KLGA · 132026-08-20 16:00 UTC· KLGA → KBNA· BANK OF UTAH TRUSTEE· B738
AAL2030 (Bank of Utah) was operating from KLGA to KBNA on 2026-08-20. SkyMeter detected a rejectedtakeoff at La Guardia Airport (KLGA) on runway 13 at 16:00 UTC. Trace data at the event: 9 ft AGL, 86 kt GS, 0 fpm vertical. Approach stability score: 90/100. Scores in this band are observed on roughly 50% of approaches at this runway and represent the centerline of normal operations. METAR at the time reported 8 kt wind, 7 kt crosswind component, 16,093 m visibility. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- SECURITY5/2811 2025-10-20 12:00Z – 2026-10-20 12:00Z SFC–1,000 ft
NEW YORK, NY, Monday, October 20, 2025 through Tuesday, October 20, 2026 Local
View FAA NOTAM → - UAS PUBLIC GATHERING6/3173 2026-08-13 21:00Z – 2026-08-23 07:00Z SFC–400 ft
Lebanon, TN, Thursday, August 13, 2026 through Sunday, August 23, 2026 UTC
View FAA NOTAM → - HAZARDS6/6869 2026-08-20 17:24Z – 2026-08-21 20:30Z SFC–400 ft
CARLISLE, PA, Thursday, August 20, 2026 through Friday, August 21, 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 13
- 9 ft AGL at event
- 86 kt ground speed
- 0 fpm vertical
- Approach stability 90/100
- 8 kt wind
- 7 kt crosswind component
- 16,093 m visibility
- KLGA 170351Z 18005KT 10SM FEW050 OVC060 24/19 A3028 RMK AO2 SLP252 T02390189
Flight context
- AAL2030
- Bank of Utah
- B738
- KLGA → KBNA
- 2026-08-20 16:00 UTC
- KLGA runway 13
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