Long landing rollout — ENY4292
KFTW · 352026-05-27 21:03 UTC· KCOS → KFTW· AMERICAN AIRLINES INC· E75L
ENY4292 (American Airlines) was operating from KCOS to KFTW on 2026-05-27. SkyMeter detected a long landing rollout at Fort Worth Meacham International Airport (KFTW) on runway 35 at 21:03 UTC. Trace data at the event: 623 ft AGL, 22 kt GS. Approach stability score: 52/100. Scores in this band occur on roughly 10-15% of approaches at this runway, with multiple gates outside the per-runway envelope. METAR at the time reported 6 kt wind, 16,093 m visibility. A long landing rollout is detected when ground deceleration after touchdown is below the per-runway P10 envelope. It is an observational measure of rollout efficiency, not a runway-exit incident. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- HAZARDS6/0887 2026-05-16 18:37Z – 2026-05-30 04:00Z SFC–10,500 ft
19NM SW TUCUMCARI, NM, Saturday, May 16, 2026 through Saturday, May 30, 2026 UTC
View FAA NOTAM → - HAZARDS6/1358 2026-05-19 00:52Z – 2026-06-02 02:00Z SFC–10,000 ft
5NM S CAMPO, CO, Tuesday, May 19, 2026 through Tuesday, June 2, 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 35
- 623 ft AGL at event
- 22 kt ground speed
- 0 fpm vertical
- Approach stability 52/100
- 6 kt wind
- 0 kt crosswind component
- 16,093 m visibility
- KFTW 200953Z 17007KT 10SM CLR 27/18 A2991 RMK AO2 SLP118 T02670183
Flight context
- ENY4292
- American Airlines
- E75L
- KCOS → KFTW
- 2026-05-27 21:03 UTC
- KFTW runway 35
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