Long landing rollout — TCN774

KAWO · 29

2026-06-19 19:18 UTC· KBFI KAWO· BANK OF UTAH TRUSTEE· C750

TCN774 (Bank of Utah) was operating from KBFI to KAWO on 2026-06-19. SkyMeter detected a long landing rollout at Arlington Municipal Airport (KAWO) on runway 29 at 19:18 UTC. Trace data at the event: 564 ft AGL, 6 kt GS. METAR at the time reported 6 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)
  • SECURITY6/4013 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft

    Seattle, WA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/8846 2026-06-19 16:00Z – 2026-06-20 01:00Z SFC–3,000 ft

    Seattle, WA, Friday, June 19, 2026 through Friday, June 19, 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 29
  • 564 ft AGL at event
  • 6 kt ground speed
  • 0 fpm vertical
  • 6 kt wind
  • 1 kt crosswind component
  • 16,093 m visibility
  • METAR KAWO 172256Z AUTO 30004KT 10SM CLR 24/12 A3002 RMK AO2 SLP170 T02390117 $

Flight context

  • TCN774
  • Bank of Utah
  • C750
  • KBFI → KAWO
  • 2026-06-19 19:18 UTC
  • KAWO runway 29

All events on this flight

Long landing rollout 19:18:17 UTC · KAWO runway 29 · 564 ft AGL · 6 kt GS
Long landing rollout 19:18:17 UTC · KAWO runway 29 · 564 ft AGL · 6 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· KAWO