Diversion — EJA567
KCAD · 182026-06-21 15:53 UTC· KCLT → KCAD· NETJETS SALES INC, ARIEL INVESTMENTS LLC, BNSF RAILWAY CO, MOSZK· C68A
EJA567 (Netjets Sales) was operating from KCLT to KTVC (Cherry Capital Airport) on 2026-06-21. SkyMeter detected a diversion to Wexford County Airport (KCAD) on runway 18 at 15:53 UTC. Peak cruise altitude FL418, turnaround area near Lake Darby, US. METAR at the time reported 0 kt wind, 16,093 m visibility. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- SECURITY6/4120 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
CINNCINATI, OH, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4125 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
MILFORD, OH, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/8964 2026-06-19 21:00Z – 2026-06-21 22:00Z SFC–400 ft
Cincinati, OH, Friday, June 19, 2026 through Sunday, June 21, 2026 Local
View FAA NOTAM → - AIR SHOWS/SPORTS6/8270 2026-06-20 19:00Z – 2026-06-21 21:00Z SFC–16,000 ft
Columbus, OH, Saturday, June 20, 2026 through Sunday, June 21, 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 18
- 1295 ft AGL at event
- 120 kt ground speed
- 0 fpm vertical
- 0 kt wind
- 0 kt crosswind component
- 16,093 m visibility
- METAR KCAD 180855Z AUTO 03003KT 10SM CLR 10/10 A3031 RMK AO2
Flight context
- EJA567
- Netjets Sales
- C68A
- KCLT → KCAD
- 2026-06-21 15:53 UTC
- KCAD runway 18
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