Diversion — EJA757

KHHR · 07

2026-06-28 21:16 UTC· KSNA → KHHR· NETJETS SALES INC, ALC ENTERPRISES LLC, BICE LLC, FLYFULFROG LLC· CL35

▶ Replay 📊 Analyse

EJA757 (Netjets Sales) was operating from KSNA to KSNA (John Wayne Airport-Orange County Airport) on 2026-06-28. SkyMeter detected a diversion to Jack Northrop Field Hawthorne Municipal Airport (KHHR) on runway 07 at 21:16 UTC. Peak altitude 6,188 ft, turnaround area near Seal Beach, US. Approach stability score: 75/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, 3 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)
  • SECURITY6/4198 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft

    IRVINE, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/0306 2026-06-28 16:00Z – 2026-06-29 01:00Z SFC–3,000 ft

    Los Angeles, CA, Sunday, June 28, 2026 through Sunday, June 28, 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 07
  • 61 ft AGL at event
  • 120 kt ground speed
  • 0 fpm vertical
  • Approach stability 75/100
  • 6 kt wind
  • 3 kt crosswind component
  • 16,093 m visibility
  • KHHR 181053Z AUTO 00000KT 10SM CLR 19/16 A3005 RMK AO2 SLP175 T01940156

Flight context

  • EJA757
  • Netjets Sales
  • CL35
  • KSNA → KHHR
  • 2026-06-28 21:16 UTC
  • KHHR runway 07

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· KHHR