Long landing rollout — N605CE
KJYO · 172026-05-21 20:47 UTC· KAPF → KJYO· EXPEDIENT VOYAGES LLC· CL60
N605CE (Expedient Voyages) was operating from KAPF to KJYO on 2026-05-21. SkyMeter detected a long landing rollout at Leesburg Executive Airport (KJYO) on runway 17 at 20:47 UTC. Trace data at the event: 380 ft AGL, 11 kt GS, 0 fpm vertical. METAR at the time reported 5 kt wind, 4 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/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 → - HAZARDS6/9916 2026-05-13 12:00Z – 2026-05-22 01:30Z SFC–2,000 ft
27NM E OF WAYCROSS, GA, Wednesday, May 13, 2026 through Friday, May 22, 2026 UTC
View FAA NOTAM → - SECURITY6/1014 2026-05-19 13:00Z – 2026-05-23 06:00Z SFC–2,500 ft
MAYPORT, FL, Tuesday, May 19, 2026 through Saturday, May 23, 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 17
- 380 ft AGL at event
- 11 kt ground speed
- 0 fpm vertical
- 5 kt wind
- 4 kt crosswind component
- 16,093 m visibility
- METAR KJYO 200555Z AUTO 16007KT 10SM OVC034 22/20 A3005 RMK AO2
Flight context
- N605CE
- Expedient Voyages
- CL60
- KAPF → KJYO
- 2026-05-21 20:47 UTC
- KJYO runway 17
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