Diversion — EJA691
KOPF · 09L2026-03-30 23:09 UTC· KJAX → KOPF· NETJETS SALES INC, BANK OF UTAH TRUSTEE, CSC DELAWARE TRUST CO T· C68A
EJA691 (Netjets Sales) was operating from KJAX to KFTW (Fort Worth Meacham International Airport) on 2026-03-30. SkyMeter detected a diversion to Miami-Opa Locka Executive Airport (KOPF) on runway 09L at 23:09 UTC. Peak cruise altitude FL313, turnaround area near Viera West, US. Approach stability score: 80/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 12 kt wind, 1 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 09L
- 8 ft AGL at event
- 120 kt ground speed
- 0 fpm vertical
- Approach stability 80/100
- 12 kt wind
- 1 kt crosswind component
- 16,093 m visibility
- METAR KOPF 241453Z 31008KT 10SM CLR 29/25 A2994 RMK AO2 RAB1357E10B26E49 SLP139 P0000 60000 T02940250 50007 $
Flight context
- EJA691
- Netjets Sales
- C68A
- KJAX → KOPF
- 2026-03-30 23:09 UTC
- KOPF runway 09L
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