Long landing rollout — SUB8922
KDTW · 03L2026-06-24 00:17 UTC· 0MI7 → KDTW· SUBURBAN AIR FREIGHT INC· B190
SUB8922 (Suburban AIR Freight) was operating from 0MI7 to KDTW on 2026-06-24. SkyMeter detected a long landing rollout at Detroit Metropolitan Wayne County Airport (KDTW) on runway 03L at 00:17 UTC. Trace data at the event: 670 ft AGL, 9 kt GS. METAR at the time reported 9 kt wind, 4 kt crosswind component, 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)- SECURITY6/4116 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
LOUISVILLE, KY, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4120 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
CINNCINATI, OH, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4125 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
MILFORD, OH, 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 03L
- 670 ft AGL at event
- 9 kt ground speed
- 0 fpm vertical
- 9 kt wind
- 4 kt crosswind component
- 16,093 m visibility
- KDTW 170153Z 05006KT 10SM BKN028 BKN065 OVC160 19/16 A3031 RMK AO2 SLP261 T01890161
Flight context
- SUB8922
- Suburban AIR Freight
- B190
- 0MI7 → KDTW
- 2026-06-24 00:17 UTC
- KDTW runway 03L
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