Diversion — EJA434
KOPF · 122026-07-22 21:19 UTC· KMCO → KOPF· NETJETS SALES INC, FORDYOUNG LLC, HIGHER LLC, CLEARY JOSEPH, CLE· E55P
EJA434 (Netjets Sales) was operating from KMCO to KPDK (DeKalb Peachtree Airport) on 2026-07-22. SkyMeter detected a diversion to Miami-Opa Locka Executive Airport (KOPF) on runway 12 at 21:19 UTC. Peak cruise altitude FL224, turnaround area near Indian River, US. Approach stability score: 77/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 11 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/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 → - SPACE OPERATIONS6/6690 2026-07-22 21:05Z – 2026-07-23 01:47Z SFC–180 ft
Cape Canaveral, FL, Wednesday, July 22, 2026 through Wednesday, July 22, 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 12
- 8 ft AGL at event
- 120 kt ground speed
- 0 fpm vertical
- Approach stability 77/100
- 11 kt wind
- 5 kt crosswind component
- 16,093 m visibility
- KOPF 170353Z AUTO 03006KT 10SM FEW110 25/24 A3011 RMK AO2 LTG DSNT S RAE0258 SLP196 T02500244 PNO $
Flight context
- EJA434
- Netjets Sales
- E55P
- KMCO → KOPF
- 2026-07-22 21:19 UTC
- KOPF runway 12
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