Long landing rollout — N
2CL9 · 252026-08-30 18:09 UTC· KSJC → 2CL9· RICALICHAN LLC· E55P
N (Ricalichan) was operating from KSJC to 2CL9 on 2026-08-30. SkyMeter detected a long landing rollout at Mustang Airport (2CL9) on runway 25 at 18:09 UTC. Trace data at the event: 85 ft AGL, 0 kt GS, 0 fpm vertical. METAR at the time reported 4 kt wind, 1 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/5797 2026-04-03 00:01Z – 2026-09-28 23:59Z SFC–400 ft
SACRAMENTO, CA, Thursday, April 2, 2026 through Monday, September 28, 2026 Local
View FAA NOTAM → - UAS PUBLIC GATHERING6/7555 2026-08-29 01:00Z – 2026-09-02 06:59Z SFC–400 ft
Santa Clara, CA, Saturday, August 29, 2026 through Wednesday, September 2, 2026 UTC
View FAA NOTAM → - UAS PUBLIC GATHERING6/7569 2026-08-29 01:00Z – 2026-09-02 06:59Z SFC–400 ft
Santa Clara, CA, Saturday, August 29, 2026 through Wednesday, September 2, 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 25
- 85 ft AGL at event
- 0 kt ground speed
- 0 fpm vertical
- 4 kt wind
- 1 kt crosswind component
Flight context
- N
- Ricalichan
- E55P
- KSJC → 2CL9
- 2026-08-30 18:09 UTC
- 2CL9 runway 25
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