Long landing rollout — DAL2458
K8T8 · 17L2026-07-24 20:38 UTC· KDTW → K8T8· DELTA AIR LINES INC· A319
DAL2458 (Delta AIR Lines) was operating from KDTW to K8T8 on 2026-07-24. SkyMeter detected a long landing rollout at San Geronimo Airpark (K8T8) on runway 17L at 20:38 UTC. Trace data at the event: 816 ft AGL, 4 kt GS. METAR at the time reported 9 kt wind, 1 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)- SECURITY6/7851 2026-07-23 17:00Z – 2026-07-27 04:59Z SFC–400 ft
Westfield, IN, Thursday, July 23, 2026 through Sunday, July 26, 2026 Local
View FAA NOTAM → - UAS PUBLIC GATHERING6/6521 2026-07-23 21:30Z – 2026-07-26 04:00Z SFC–400 ft
cincinnati, OH, Thursday, July 23, 2026 through Sunday, July 26, 2026 UTC
View FAA NOTAM → - SECURITY6/8361 2026-07-24 13:00Z – 2026-07-27 04:59Z SFC–400 ft
Westfield, IN, Friday, July 24, 2026 through Sunday, July 26, 2026 Local
View FAA NOTAM → - UAS PUBLIC GATHERING6/6522 2026-07-24 17:30Z – 2026-07-27 04:00Z SFC–400 ft
chicago, IL, Friday, July 24, 2026 through Monday, July 27, 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 17L
- 816 ft AGL at event
- 4 kt ground speed
- 0 fpm vertical
- 9 kt wind
- 1 kt crosswind component
Flight context
- DAL2458
- Delta AIR Lines
- A319
- KDTW → K8T8
- 2026-07-24 20:38 UTC
- K8T8 runway 17L
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