Long landing rollout — N422MP
KCRQ · 242026-08-07 00:25 UTC· KCRQ → KVNY· TVPX AIRCRAFT SOLUTIONS INC TRUSTEE· CL30
N422MP (Tvpx Aircraft Solutions) was operating from KCRQ to KVNY on 2026-08-07. SkyMeter detected a long landing rollout at Mc Clellan-Palomar Airport (KCRQ) on runway 24 at 00:25 UTC. Trace data at the event: 321 ft AGL, 0 kt GS, 0 fpm vertical. Approach stability score: 54/100. Scores in this band occur on roughly 10-15% of approaches at this runway, with multiple gates outside the per-runway envelope. METAR at the time reported 9 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)- HAZARDS6/0715 2026-08-01 02:12Z – 2026-08-08 04:00Z SFC–7,000 ft
YUCAIPA, CA, Saturday, August 1, 2026 through Saturday, August 8, 2026 UTC
View FAA NOTAM → - HAZARDS6/0745 2026-08-01 14:00Z – 2026-08-14 04:00Z SFC–9,000 ft
15NM N RAMONA, CA, Saturday, August 1, 2026 through Friday, August 14, 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 24
- 321 ft AGL at event
- 0 kt ground speed
- 0 fpm vertical
- Approach stability 54/100
- 9 kt wind
- 1 kt crosswind component
- 16,093 m visibility
- KCRQ 161553Z 20003KT 10SM OVC034 21/16 A2999 RMK AO2 SLP153 T02110156
Flight context
- N422MP
- Tvpx Aircraft Solutions
- CL30
- KCRQ → KVNY
- 2026-08-07 00:25 UTC
- KCRQ runway 24
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