Long landing rollout — LXJ602
KCDW · 042026-05-02 16:27 UTC· KBCT → KCDW· FLEXJET LLC, NAFTA TOOLS INC, STERN ZACHARY, GILLIKIN J DAVID, P· E550
LXJ602 (Flexjet) was operating from KBCT to KCDW on 2026-05-02. SkyMeter detected a long landing rollout at Essex County Airport (KCDW) on runway 04 at 16:27 UTC. Trace data at the event: 0 ft AGL, 4 kt GS, 0 fpm vertical. Approach stability score: 37/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 5 kt wind, 5 kt crosswind component, 3,219 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/2809 2025-10-20 12:00Z – 2026-10-20 12:00Z SFC–2,000 ft
Palm Beach, FL, Monday, October 20, 2025 through Tuesday, October 20, 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 04
- 0 ft AGL at event
- 4 kt ground speed
- 0 fpm vertical
- Approach stability 37/100
- 5 kt wind
- 5 kt crosswind component
- 3,219 m visibility
- SPECI KCDW 201714Z 17006KT 2SM -RA BR BKN009 OVC024 19/18 A2996 RMK AO2 P0001 T01890178
Flight context
- LXJ602
- Flexjet
- E550
- KBCT → KCDW
- 2026-05-02 16:27 UTC
- KCDW runway 04
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