Long landing rollout — N541Z
US-1043 · 242026-05-24 21:20 UTC· KBDL → US-1043· BANK OF UTAH TRUSTEE· F2TH
N541Z (Bank of Utah) was operating from KBDL to US-1043 on 2026-05-24. SkyMeter detected a long landing rollout at Speedway Airport (US-1043) on runway 24 at 21:20 UTC. Trace data at the event: 921 ft AGL, 20 kt GS. METAR at the time reported 6 kt wind, 6 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 → - VIP6/2122 2026-05-22 20:30Z – 2026-05-24 23:00Z SFC–17,999 ft
Bedminster, NJ, Friday, May 22, 2026 through Sunday, May 24, 2026 Local
View FAA NOTAM → - VIP6/2125 2026-05-22 20:30Z – 2026-05-24 23:00Z SFC–17,999 ft
Bedminster, NJ, Friday, May 22, 2026 through Sunday, May 24, 2026 Local
View FAA NOTAM → - SECURITY6/2322 2026-05-24 20:20Z – 2026-05-24 23:00Z SFC–2,000 ft
Morristown, NJ, Sunday, May 24, 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 24
- 921 ft AGL at event
- 20 kt ground speed
- 0 fpm vertical
- 6 kt wind
- 6 kt crosswind component
Flight context
- N541Z
- Bank of Utah
- F2TH
- KBDL → US-1043
- 2026-05-24 21:20 UTC
- US-1043 runway 24
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