Long landing rollout — FDX97
K2R2 · 362026-09-03 15:22 UTC· EBLG → K2R2· FEDERAL EXPRESS CORP· B77L
FDX97 (Federal Express) was operating from EBLG to K2R2 on 2026-09-03. SkyMeter detected a long landing rollout at Hendricks County Gordon Graham Field (K2R2) on runway 36 at 15:22 UTC. Trace data at the event: 790 ft AGL, 6 kt GS. METAR at the time reported 6 kt wind, 5 kt crosswind component. 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)- 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 → - SECURITY6/2790 2026-07-02 22:30Z – 2026-09-15 03:59Z SFC–400 ft
St. George, ME, Thursday, July 2, 2026 through Monday, September 14, 2026 Local
View FAA NOTAM → - SECURITY6/7002 2026-08-24 13:00Z – 2026-09-13 07:00Z SFC–1,000 ft
Flushing, NY, Monday, August 24, 2026 through Sunday, September 13, 2026 Local
View FAA NOTAM → - UAS PUBLIC GATHERING6/6427 2026-08-26 13:00Z – 2026-09-08 03:59Z SFC–400 ft
Syracuse, NY, Wednesday, August 26, 2026 through Tuesday, September 8, 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 36
- 790 ft AGL at event
- 6 kt ground speed
- 0 fpm vertical
- 6 kt wind
- 5 kt crosswind component
Flight context
- FDX97
- Federal Express
- B77L
- EBLG → K2R2
- 2026-09-03 15:22 UTC
- K2R2 runway 36
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