EJA468 (Netjets Sales) was operating from KCLT to KLUK (Cincinnati Municipal Airport Lunken Field) on 2026-08-07. SkyMeter detected a diversion to Chicago Executive Airport (KPWK) on runway 16 at 20:47 UTC. Peak cruise altitude FL452, turnaround area near Cold Spring, US. Approach stability score: 81/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 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/0708 2026-08-01 00:01Z – 2027-08-01 23:59Z SFC–400 ft

    Goodlettsville, TN, Saturday, August 1, 2026 through Sunday, August 1, 2027 UTC

    View FAA NOTAM →
  • SECURITY6/1710 2026-08-06 21:00Z – 2026-08-10 02:00Z SFC–400 ft

    West Chester, OH, Thursday, August 6, 2026 through Sunday, August 9, 2026 Local

    View FAA NOTAM →
  • UAS PUBLIC GATHERING6/2104 2026-08-07 19:30Z – 2026-08-08 00:30Z SFC–400 ft

    cincinnati, OH, Friday, August 7, 2026 through Saturday, August 8, 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 16
  • 0 ft AGL at event
  • 0 kt ground speed
  • 0 fpm vertical
  • Approach stability 81/100
  • 0 kt wind
  • 0 kt crosswind component
  • 16,093 m visibility
  • KPWK 162352Z 05004KT 10SM OVC006 19/18 A3028 RMK AO2 SLP253 60005 T01890183 10228 20189 58008 $

Flight context

  • EJA468
  • Netjets Sales
  • E55P
  • KCLT → KPWK
  • 2026-08-07 20:47 UTC
  • KPWK runway 16

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

SkyMeter · trace data observed via ADS-B· KPWK