Long landing rollout — EJA829
K6S5 · 342026-06-22 22:21 UTC· KSDL → K6S5· NETJETS SALES INC, B14T LLC, ELEMENT SOLUTIONS INC, ELTRICH MART· C700
EJA829 (Netjets Sales) was operating from KSDL to K6S5 on 2026-06-22. SkyMeter detected a long landing rollout at Ravalli County Airport (K6S5) on runway 34 at 22:21 UTC. Trace data at the event: 3615 ft AGL, 9 kt GS. METAR at the time reported 5 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)- 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/8795 2026-06-17 15:00Z – 2026-06-29 04:00Z SFC–11,000 ft
58NM S ST. GEORGE, UT, Wednesday, June 17, 2026 through Monday, June 29, 2026 UTC
View FAA NOTAM → - HAZARDS6/8796 2026-06-17 15:00Z – 2026-06-29 04:00Z SFC–11,500 ft
65NM SE CEDAR CITY, UT, Wednesday, June 17, 2026 through Monday, June 29, 2026 UTC
View FAA NOTAM → - HAZARDS6/9269 2026-06-18 19:00Z – 2026-06-30 04:00Z SFC–11,000 ft
39NM NW MESQUITE, NV, Thursday, June 18, 2026 through Tuesday, June 30, 2026 UTC
View FAA NOTAM → - HAZARDS6/9359 2026-06-20 13:00Z – 2026-07-03 04:00Z SFC–11,000 ft
39 NM NW MESQUITE, NV, Saturday, June 20, 2026 through Friday, July 3, 2026 UTC
View FAA NOTAM → - HAZARDS6/9412 2026-06-20 17:53Z – 2026-07-03 04:00Z SFC–11,000 ft
27NM SW PROVO, UT, Saturday, June 20, 2026 through Friday, July 3, 2026 UTC
View FAA NOTAM → - HAZARDS6/9461 2026-06-21 12:00Z – 2026-07-04 04:00Z SFC–10,500 ft
3.5NM SW SALT LAKE CITY, UT, Sunday, June 21, 2026 through Saturday, July 4, 2026 UTC
View FAA NOTAM → - HAZARDS6/9457 2026-06-21 13:00Z – 2026-07-04 04:00Z SFC–12,000 ft
39 NM NW MESQUITE, NV, Sunday, June 21, 2026 through Saturday, July 4, 2026 UTC
View FAA NOTAM → - HAZARDS6/9460 2026-06-21 14:00Z – 2026-07-04 04:00Z SFC–11,000 ft
27NM SW PROVO, UT, Sunday, June 21, 2026 through Saturday, July 4, 2026 UTC
View FAA NOTAM → - HAZARDS6/9504 2026-06-21 14:14Z – 2026-07-05 15:00Z SFC–10,500 ft
10NM NE OGDEN, UT, Sunday, June 21, 2026 through Sunday, July 5, 2026 UTC
View FAA NOTAM → - HAZARDS6/9555 2026-06-22 12:00Z – 2026-07-04 04:00Z SFC–10,500 ft
3.5NM SW SALT LAKE CITY, UT, Monday, June 22, 2026 through Saturday, July 4, 2026 UTC
View FAA NOTAM → - HAZARDS6/9562 2026-06-22 12:00Z – 2026-07-04 04:00Z SFC–10,500 ft
29NM NW TOOELE, UT, Monday, June 22, 2026 through Saturday, July 4, 2026 UTC
View FAA NOTAM → - HAZARDS6/9582 2026-06-22 13:04Z – 2026-07-05 15:00Z SFC–10,500 ft
29NM NW TOOELE, UT, Monday, June 22, 2026 through Sunday, July 5, 2026 UTC
View FAA NOTAM → - HAZARDS6/9592 2026-06-22 13:29Z – 2026-07-05 15:00Z SFC–10,500 ft
3.5NM SW SALT LAKE CITY, UT, Monday, June 22, 2026 through Sunday, July 5, 2026 UTC
View FAA NOTAM → - HAZARDS6/9834 2026-06-22 19:21Z – 2026-07-05 15:00Z SFC–10,500 ft
4NM SW SALT LAKE CITY, UT, Monday, June 22, 2026 through Sunday, July 5, 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 34
- 3615 ft AGL at event
- 9 kt ground speed
- 0 fpm vertical
- 5 kt wind
- 4 kt crosswind component
Flight context
- EJA829
- Netjets Sales
- C700
- KSDL → K6S5
- 2026-06-22 22:21 UTC
- K6S5 runway 34
All events on this flight
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