Diversion — EJA627
KCPS · 052026-04-02 23:52 UTC· KPBI → KCPS· NETJETS SALES INC, ACC FINANCE CO OF ARKANSAS INC, BERKSHIRE HAT· C68A
EJA627 (Netjets Sales) was operating from KPBI to KMDW (Chicago Midway International Airport) on 2026-04-02. SkyMeter detected a diversion to St Louis Downtown Airport (KCPS) on runway 05 at 23:52 UTC. Peak cruise altitude FL415, turnaround area near Smiths Station, US. Approach stability score: 40/100. Scores below 50 occur on under 10% of approaches at this runway and indicate the v2 scorer flagged the approach as highly anomalous (three or more gates exceeded the runway's P90 envelope simultaneously). METAR at the time reported 14 kt wind, 8 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/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/4875 2026-03-30 13:00Z – 2026-04-04 06:00Z SFC–2,500 ft
20NM NW MEDFORD, OR, Friday, July 10, 2026 through Saturday, July 25, 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 05
- 409 ft AGL at event
- 120 kt ground speed
- 0 fpm vertical
- Approach stability 40/100
- 14 kt wind
- 8 kt crosswind component
- 16,093 m visibility
- METAR KCPS 231653Z 01010KT 10SM BKN024 OVC031 20/14 A3029 RMK AO2 SLP256 T02000144 $
Flight context
- EJA627
- Netjets Sales
- C68A
- KPBI → KCPS
- 2026-04-02 23:52 UTC
- KCPS runway 05
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