Long landing rollout — N1860

KU42 · 16

2026-05-02 23:05 UTC· KLHM KU42· N1860 LLC· SF50

N1860 (N1860) was operating from KLHM to KU42 on 2026-05-02. SkyMeter detected a long landing rollout at South Valley Regional Airport (KU42) on runway 16 at 23:05 UTC. Trace data at the event: 4625 ft AGL, 4 kt GS. Approach stability score: 46/100. Scores below 50 occur on under 10% of approaches at this runway and indicate the v2 scorer flagged the approach as highly anomalous (three or more gates exceeded the runway's P90 envelope simultaneously). METAR at the time reported 2 kt wind, 2 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/3475 2026-03-08 09:00Z – 2026-11-01 09:59Z SFC–180 ft

    BEALE AFB, CA, Sunday, March 8, 2026 through Sunday, November 1, 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 16
  • 4625 ft AGL at event
  • 4 kt ground speed
  • 0 fpm vertical
  • Approach stability 46/100
  • 2 kt wind
  • 2 kt crosswind component

Flight context

  • N1860
  • N1860
  • SF50
  • KLHM → KU42
  • 2026-05-02 23:05 UTC
  • KU42 runway 16

All events on this flight

Long landing rollout 23:05:31 UTC · KU42 runway 16 · 4,625 ft AGL · 4 kt GS
Long landing rollout 23:05:31 UTC · KU42 runway 16 · 4,625 ft AGL · 4 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· KU42