Diversion — EJA438
KJYO · 172026-08-11 17:26 UTC· KBTV → KJYO· NETJETS SALES INC, COFFIN & SHAWVER LLC, TRUAX DOUGLAS, FRED B B· E55P
EJA438 (Netjets Sales) was operating from KBTV to KCLT (Charlotte Douglas International Airport) on 2026-08-11. SkyMeter detected a diversion to Leesburg Executive Airport (KJYO) on runway 17 at 17:26 UTC. Peak cruise altitude FL395, turnaround area near Waymart, US. 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 8 kt wind, 5 kt crosswind component, 16,093 m visibility. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- SECURITY5/2811 2025-10-20 12:00Z – 2026-10-20 12:00Z SFC–1,000 ft
NEW YORK, NY, Monday, October 20, 2025 through Tuesday, October 20, 2026 Local
View FAA NOTAM → - SECURITY6/0879 2026-08-06 12:00Z – 2026-08-14 20:00Z SFC–2,000 ft
Laurel, MD, Thursday, August 6, 2026 through Friday, August 14, 2026 Local
View FAA NOTAM → - VIP6/2748 2026-08-08 14:00Z – 2026-08-16 22:00Z SFC–4,999 ft
THURMONT, MD, Saturday, August 8, 2026 through Sunday, August 16, 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
- 387 ft AGL at event
- 120 kt ground speed
- 0 fpm vertical
- Approach stability 54/100
- 8 kt wind
- 5 kt crosswind component
- 16,093 m visibility
- METAR KJYO 162135Z AUTO 17008KT 10SM CLR 30/21 A3030 RMK AO2
Flight context
- EJA438
- Netjets Sales
- E55P
- KBTV → KJYO
- 2026-08-11 17:26 UTC
- KJYO runway 17
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