Long landing rollout — N45NS

KTRI · 27

2026-07-09 19:29 UTC· KAPF → KTRI· SEAMAN CORP· C56X

▶ Replay 📊 Analyse

N45NS (Seaman) was operating from KAPF to KTRI on 2026-07-09. SkyMeter detected a long landing rollout at Tri-Cities Regional TN/VA Airport (KTRI) on runway 27 at 19:29 UTC. Trace data at the event: 1535 ft AGL, 4 kt GS. METAR at the time reported 8 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/4153 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

    Tampa, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/4156 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

    TAMPA, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/7880 2026-07-05 14:07Z – 2026-07-21 03:59Z SFC–400 ft

    Tampa, FL

    View FAA NOTAM →
  • SECURITY6/7881 2026-07-05 14:07Z – 2026-07-21 03:59Z SFC–400 ft

    Tampa, FL

    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 27
  • 1535 ft AGL at event
  • 4 kt ground speed
  • 0 fpm vertical
  • 8 kt wind
  • 4 kt crosswind component
  • 16,093 m visibility
  • KTRI 180453Z 00000KT 10SM CLR 20/20 A3025 RMK AO2 SLP216 T02000200 403440172 $

Flight context

  • N45NS
  • Seaman
  • C56X
  • KAPF → KTRI
  • 2026-07-09 19:29 UTC
  • KTRI runway 27

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· KTRI