Long landing rollout — EJA645

K6S5 · 34

2026-06-04 16:45 UTC· KLNS K6S5· NETJETS SALES INC, BANK OF UTAH TRUSTEE, B-LINE LLC, SMITH BRUCE· C68A

EJA645 (Netjets Sales) was operating from KLNS to K6S5 on 2026-06-04. SkyMeter detected a long landing rollout at Ravalli County Airport (K6S5) on runway 34 at 16:45 UTC. Trace data at the event: 3615 ft AGL, 11 kt GS. METAR at the time reported 4 kt wind, 4 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)
  • HAZARDS6/2646 2026-05-25 15:00Z – 2026-06-08 04:00Z SFC–11,000 ft

    22NM SE JACKSON, WY, Monday, May 25, 2026 through Monday, June 8, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/3585 2026-05-28 14:00Z – 2026-06-11 03:00Z SFC–9,000 ft

    74NM S MILES CITY, MT, Thursday, May 28, 2026 through Thursday, June 11, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/3649 2026-05-28 14:00Z – 2026-06-11 03:00Z SFC–9,000 ft

    74NM S MILES CITY, MT, Thursday, May 28, 2026 through Thursday, June 11, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/3574 2026-05-29 14:00Z – 2026-06-10 02:00Z SFC–13,000 ft

    38NM SE TWIN FALLS, ID, Friday, May 29, 2026 through Wednesday, June 10, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/3888 2026-05-29 14:00Z – 2026-06-10 04:00Z SFC–13,000 ft

    38NM SE TWIN FALLS, ID, Friday, May 29, 2026 through Wednesday, June 10, 2026 UTC

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

    WESTFIELD, IN, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    Sandy, UT, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    Salt Lake City, UT, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • HAZARDS6/4299 2026-06-01 13:00Z – 2026-06-04 23:00Z SFC–10,000 ft

    43NM SW GREEN RIVER, WY, Monday, June 1, 2026 through Thursday, June 4, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/4637 2026-06-02 13:00Z – 2026-06-05 03:00Z SFC–10,000 ft

    62NM NW GREEN RIVER, WY, Tuesday, June 2, 2026 through Friday, June 5, 2026 UTC

    View FAA NOTAM →
  • UAS PUBLIC GATHERING6/3661 2026-06-03 06:00Z – 2026-06-07 18:00Z

    COLUMBUS, OH, Wednesday, June 3, 2026 through Sunday, June 7, 2026 UTC

    View FAA NOTAM →
  • UAS PUBLIC GATHERING6/3706 2026-06-03 06:00Z – 2026-06-07 18:00Z

    COLUMBUS, OH, Wednesday, June 3, 2026 through Sunday, June 7, 2026 UTC

    View FAA NOTAM →
  • VIP6/4993 2026-06-04 13:45Z – 2026-06-04 16:45Z SFC–4,999 ft

    COLUMBUS, OH, Thursday, June 4, 2026 Local

    View FAA NOTAM →
  • VIP6/4995 2026-06-04 15:45Z – 2026-06-04 20:30Z SFC–4,999 ft

    CLEVELAND, OH, Thursday, June 4, 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 34
  • 3615 ft AGL at event
  • 11 kt ground speed
  • 0 fpm vertical
  • 4 kt wind
  • 4 kt crosswind component

Flight context

  • EJA645
  • Netjets Sales
  • C68A
  • KLNS → K6S5
  • 2026-06-04 16:45 UTC
  • K6S5 runway 34

All events on this flight

Long landing rollout 16:45:18 UTC · K6S5 runway 34 · 3,615 ft AGL · 11 kt GS
Long landing rollout 16:45:18 UTC · K6S5 runway 35 · 3,615 ft AGL · 11 kt GS
Long landing rollout 16:45:18 UTC · K6S5 runway 35 · 3,615 ft AGL · 11 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· K6S5