Diversion — EJA467
KDAY · 06L2026-07-26 18:33 UTC· KMKC → KDAY· NETJETS SALES INC, 507 AVIATION LLC, BANK OF UTAH TRUSTEE, BAREL· E55P
EJA467 (Netjets Sales) was operating from KMKC to KBWI (Baltimore/Washington International Thurgood Marshall Airport) on 2026-07-26. SkyMeter detected a diversion to James M Cox Dayton International Airport (KDAY) on runway 06L at 18:33 UTC. Peak cruise altitude FL435, turnaround area near Logan County, US. Approach stability score: 84/100. Scores in this band are observed on roughly 25% of approaches at this runway: one or more gates outside the per-runway tightest envelope, but still inside the typical operating range. METAR at the time reported 6 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/7851 2026-07-23 17:00Z – 2026-07-27 04:59Z SFC–400 ft
Westfield, IN, Thursday, July 23, 2026 through Sunday, July 26, 2026 Local
View FAA NOTAM → - SECURITY6/8361 2026-07-24 13:00Z – 2026-07-27 04:59Z SFC–400 ft
Westfield, IN, Friday, July 24, 2026 through Sunday, July 26, 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 06L
- 996 ft AGL at event
- 120 kt ground speed
- 0 fpm vertical
- Approach stability 84/100
- 6 kt wind
- 0 kt crosswind component
- 16,093 m visibility
- KDAY 162156Z 01013G20KT 10SM TS SCT048CB BKN070 BKN250 27/19 A3027 RMK AO2 TSB30 SLP241 FRQ LTGICCG NW-NE TS NW-NE MOV E T02670194
Flight context
- EJA467
- Netjets Sales
- E55P
- KMKC → KDAY
- 2026-07-26 18:33 UTC
- KDAY runway 06L
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