Long landing rollout — N460RM
KSNS · 312026-08-21 16:57 UTC· KSNA → KSNS· MUSTANG TWO LLC· C525
N460RM (Mustang TWO) was operating from KSNA to KSNS on 2026-08-21. SkyMeter detected a long landing rollout at Salinas Municipal Airport (KSNS) on runway 31 at 16:57 UTC. Trace data at the event: 55 ft AGL, 14 kt GS, 0 fpm vertical. METAR at the time reported 3 kt wind, 3 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)- HAZARDS6/3157 2026-08-10 01:18Z – 2026-08-23 15:00Z SFC–7,500 ft
8NM SE BIG SUR, CA, Monday, August 10, 2026 through Sunday, August 23, 2026 UTC
View FAA NOTAM → - HAZARDS6/3480 2026-08-10 18:36Z – 2026-08-23 15:00Z SFC–7,500 ft
8NM SE BIG SUR, CA, Monday, August 10, 2026 through Sunday, August 23, 2026 UTC
View FAA NOTAM → - HAZARDS6/5070 2026-08-14 13:00Z – 2026-08-27 03:00Z SFC–8,500 ft
8NM SE BIG SUR, CA, Friday, August 14, 2026 through Thursday, August 27, 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 31
- 55 ft AGL at event
- 14 kt ground speed
- 0 fpm vertical
- 3 kt wind
- 3 kt crosswind component
- 16,093 m visibility
- KSNS 162153Z 30012KT 10SM CLR 20/12 A3000 RMK AO2 SLP166 T02000117
Flight context
- N460RM
- Mustang TWO
- C525
- KSNA → KSNS
- 2026-08-21 16:57 UTC
- KSNS runway 31
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