Diversion — EJM22
KHND · 17R2026-08-27 20:17 UTC· KNZY → KHND· SAUVAGE MT LLC· G280
EJM22 (Sauvage MT) was operating from KNZY to KSAN (San Diego International Airport) on 2026-08-27. SkyMeter detected a diversion to Henderson Executive Airport (KHND) on runway 17R at 20:17 UTC. Peak cruise altitude FL331, turnaround area near Twentynine Palms, US. METAR at the time reported 10 kt wind, 6 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/2652 2026-07-05 00:01Z – 2027-01-02 23:59Z SFC–500 ft
Coyote Wells, CA, Saturday, July 4, 2026 through Saturday, January 2, 2027 Local
View FAA NOTAM → - SECURITY6/2656 2026-07-05 00:01Z – 2027-01-02 23:59Z SFC–500 ft
Coyote Wells, CA, Saturday, July 4, 2026 through Saturday, January 2, 2027 Local
View FAA NOTAM → - SECURITY6/2657 2026-07-05 00:01Z – 2027-01-02 23:59Z SFC–500 ft
Calexico, CA, Saturday, July 4, 2026 through Saturday, January 2, 2027 Local
View FAA NOTAM → - SECURITY6/4812 2026-07-15 07:00Z – 2027-07-14 06:59Z SFC–17,999 ft
El Centro, CA, Wednesday, July 15, 2026 through Tuesday, July 13, 2027 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 17R
- 2492 ft AGL at event
- 120 kt ground speed
- 0 fpm vertical
- 10 kt wind
- 6 kt crosswind component
- 16,093 m visibility
- METAR KHND 040756Z AUTO 21010KT 10SM CLR 26/03 A2983 RMK AO2 SLP086 T02610033 $
Flight context
- EJM22
- Sauvage MT
- G280
- KNZY → KHND
- 2026-08-27 20:17 UTC
- KHND runway 17R
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