Long landing rollout — TCN753

US-11001 · 14

2026-08-12 02:43 UTC· KLNK → ?· BANK OF UTAH TRUSTEE· C750

▶ Replay 📊 Analyse

TCN753 (Bank of Utah) had departed KLNK on 2026-08-12. SkyMeter detected a long landing rollout at US-11001 (US-11001) on runway 14 at 02:43 UTC. Trace data at the event: 121 ft AGL, 15 kt GS, 0 fpm vertical. METAR at the time reported 3 kt wind, 2 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)
  • VIP6/3135 2026-08-11 20:30Z – 2026-08-12 02:00Z SFC–17,999 ft

    Cleveland/Geneva, OH, Tuesday, August 11, 2026 through Tuesday, August 11, 2026 Local

    View FAA NOTAM →
  • SECURITY6/3696 2026-08-11 22:30Z – 2026-08-13 05:00Z SFC–400 ft

    Dyersville, IA, Tuesday, August 11, 2026 through Thursday, August 13, 2026 Local

    View FAA NOTAM →
  • VIP6/4081 2026-08-12 00:07Z – 2026-08-12 00:30Z SFC–17,999 ft

    Cleveland, OH

    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 14
  • 121 ft AGL at event
  • 15 kt ground speed
  • 0 fpm vertical
  • 3 kt wind
  • 2 kt crosswind component

Flight context

  • TCN753
  • Bank of Utah
  • C750
  • 2026-08-12 02:43 UTC
  • US-11001 runway 14

All events on this flight

Long landing rollout 02:43:04 UTC · US-11001 runway 14 · 121 ft AGL · 15 kt GS
Long landing rollout 02:43:04 UTC · US-11001 runway 14 · 121 ft AGL · 15 kt GS

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

SkyMeter · trace data observed via ADS-B· US-11001