Long landing rollout — N331US
KSLE · 312026-07-10 21:46 UTC· KBDN → KHIO· N331US LLC· LJ31
N331US (N331us) was operating from KBDN to KHIO on 2026-07-10. SkyMeter detected a long landing rollout at Salem Municipal Airport/McNary Field (KSLE) on runway 31 at 21:46 UTC. Trace data at the event: 219 ft AGL, 0 kt GS, 0 fpm vertical. Approach stability score: 83/100. Scores in this band are observed on roughly 25% of approaches at this runway: one or more gates outside the per-runway tightest envelope, but still inside the typical operating range. METAR at the time reported 3 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/4041 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
PORTLAND, OR, Monday, June 1, 2026 through Monday, July 20, 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 31
- 219 ft AGL at event
- 0 kt ground speed
- 0 fpm vertical
- Approach stability 83/100
- 3 kt wind
- 1 kt crosswind component
- 16,093 m visibility
- KSLE 180456Z AUTO 18005KT 10SM CLR 18/11 A3008 RMK AO2 SLP183 T01780106 $
Flight context
- N331US
- N331us
- LJ31
- KBDN → KHIO
- 2026-07-10 21:46 UTC
- KSLE runway 31
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