Long landing rollout — TKR182

K6S8 · 22

2026-08-21 00:16 UTC· BANK OF UTAH TRUSTEE· DH8D

▶ Replay 📊 Analyse

TKR182 (Bank of Utah) was inbound to K6S8 on 2026-08-21. SkyMeter detected a long landing rollout at Laurel Municipal Airport (K6S8) on runway 22 at 00:16 UTC. Trace data at the event: 3500 ft AGL, 13 kt GS. METAR at the time reported 4 kt wind, 1 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)
  • AIR SHOWS/SPORTS6/4976 2026-08-20 17:30Z – 2026-08-23 22:30Z

    BILLINGS, MT, Thursday, August 20, 2026 through Sunday, August 23, 2026 UTC

    View FAA NOTAM →
  • AIR SHOWS/SPORTS6/4977 2026-08-20 17:30Z – 2026-08-23 22:30Z SFC–17,999 ft

    Billings, MT, Thursday, August 20, 2026 through Sunday, August 23, 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 22
  • 3500 ft AGL at event
  • 13 kt ground speed
  • 0 fpm vertical
  • 4 kt wind
  • 1 kt crosswind component
  • 16,093 m visibility
  • METAR K6S8 160455Z AUTO 02013KT 10SM CLR 14/03 A3004 RMK A01

Flight context

  • TKR182
  • Bank of Utah
  • DH8D
  • 2026-08-21 00:16 UTC
  • K6S8 runway 22

All events on this flight

Long landing rollout 00:16:26 UTC · K6S8 runway 22 · 3,500 ft AGL · 13 kt GS
Long landing rollout 00:16:26 UTC · K6S8 runway 22 · 3,500 ft AGL · 13 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· K6S8