Long landing rollout — EJA426
KCRQ · 242026-03-30 00:53 UTC· NETJETS SALES INC, CAROLINE MARKFIELD, CAWM LLC, MFJ ENTERPRISES· E55P
EJA426 (Netjets Sales) was inbound to KCRQ on 2026-03-30. SkyMeter detected a long landing rollout at Mc Clellan-Palomar Airport (KCRQ) on runway 24 at 00:53 UTC. Trace data at the event: 321 ft AGL, 1 kt GS, 0 fpm vertical. Approach stability score: 65/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 4 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)- SECURITY5/0601 2025-11-30 19:00Z – 2026-05-31 18:59Z SFC–400 ft
Los Angeles, CA, Sunday, November 30, 2025 through Sunday, May 31, 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 24
- 321 ft AGL at event
- 1 kt ground speed
- 0 fpm vertical
- Approach stability 65/100
- 4 kt wind
- 1 kt crosswind component
- 16,093 m visibility
- KCRQ 162353Z AUTO 26007KT 10SM CLR 23/16 A2995 RMK AO2 SLP138 T02280156 10244 20222 56009
Flight context
- EJA426
- Netjets Sales
- E55P
- 2026-03-30 00:53 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