Diversion — EJA797

EJA797 (Netjets Sales) was operating from KOAK to KSJC (Norman Y. Mineta San Jose International Airport) on 2026-07-13. SkyMeter detected a diversion to Salt Lake City International Airport (KSLC) on runway 17 at 05:01 UTC. Peak cruise altitude FL435, turnaround area near Lander, US. Approach stability score: 85/100. Scores in this band are observed on roughly 50% of approaches at this runway and represent the centerline of normal operations. METAR at the time reported 3 kt wind, 3 kt crosswind component, 16,093 m visibility. Detection algorithm and known limitations: see SkyMeter methodology.

• SECURITY6/3475 2026-03-08 09:00Z – 2026-11-01 09:59Z SFC–180 ft

  BEALE AFB, CA, Sunday, March 8, 2026 through Sunday, November 1, 2026 Local

  View FAA NOTAM →
• SECURITY6/5797 2026-04-03 00:01Z – 2026-09-28 23:59Z SFC–400 ft

  SACRAMENTO, CA, Thursday, April 2, 2026 through Monday, September 28, 2026 Local

  View FAA NOTAM →
• SECURITY6/4060 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft

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

  View FAA NOTAM →
• SECURITY6/4061 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft

  BERKLEY, CA, Monday, June 1, 2026 through Tuesday, July 21, 2026 Local

  View FAA NOTAM →
• HAZARDS6/1335 2026-06-29 01:32Z – 2026-07-13 04:00Z SFC–12,000 ft

  6NM S SCIPIO, UT, Monday, June 29, 2026 through Monday, July 13, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/2593 2026-07-02 14:00Z – 2026-07-13 05:00Z SFC–12,000 ft

  12NM N PIOCHE, NV, Thursday, July 2, 2026 through Monday, July 13, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/2595 2026-07-02 14:00Z – 2026-07-13 05:00Z SFC–12,000 ft

  12NM N PIOCHE, NV, Thursday, July 2, 2026 through Monday, July 13, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/2845 2026-07-04 00:10Z – 2026-07-17 04:00Z SFC–12,500 ft

  6NM S SCIPIO, UT, Saturday, July 4, 2026 through Friday, July 17, 2026 UTC

  View FAA NOTAM →
• SECURITY6/7984 2026-07-05 14:07Z – 2026-07-21 06:59Z SFC–400 ft

  Oakland, CA

  View FAA NOTAM →
• HAZARDS6/3807 2026-07-08 15:00Z – 2026-07-22 15:00Z SFC–9,000 ft

  10NM SE FALL RIVER MILLS, CA, Wednesday, July 8, 2026 through Wednesday, July 22, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4014 2026-07-08 16:17Z – 2026-07-22 15:00Z SFC–9,000 ft

  10NM SE FALL RIVER MILLS, CA, Wednesday, July 8, 2026 through Wednesday, July 22, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4268 2026-07-09 14:00Z – 2026-07-16 04:00Z SFC–12,000 ft

  24NM S ELKO, NV, Thursday, July 9, 2026 through Thursday, July 16, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4554 2026-07-10 02:28Z – 2026-07-17 04:00Z SFC–15,500 ft

  8NM E BEAVER, UT, Friday, July 10, 2026 through Friday, July 17, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4558 2026-07-10 04:00Z – 2026-07-21 15:00Z SFC–9,000 ft

  10NM SE FALL RIVER MILLS, CA, Friday, July 10, 2026 through Tuesday, July 21, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4559 2026-07-10 04:00Z – 2026-07-21 15:00Z SFC–9,000 ft

  10NM SE FALL RIVER MILLS, CA, Friday, July 10, 2026 through Tuesday, July 21, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4964 2026-07-12 00:13Z – 2026-07-26 03:00Z SFC–10,500 ft

  3NM N LOYALTON, CA, Sunday, July 12, 2026 through Sunday, July 26, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4975 2026-07-12 13:00Z – 2026-07-26 04:00Z SFC–12,000 ft

  9NM SE DUGWAY, UT, Sunday, July 12, 2026 through Sunday, July 26, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4978 2026-07-12 13:00Z – 2026-07-26 13:00Z SFC–10,500 ft

  3NM N LOYALTON, CA, Sunday, July 12, 2026 through Sunday, July 26, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/5054 2026-07-12 14:45Z – 2026-07-26 13:00Z SFC–12,500 ft

  3NM N LOYALTON, CA, Sunday, July 12, 2026 through Sunday, July 26, 2026 UTC

  View FAA NOTAM →
• SPACE OPERATIONS6/3531 2026-07-12 15:00Z – 2026-07-13 06:00Z SFC–350 ft

  31 ZLC AIRSPACE BLACK ROCK, NV, Sunday, July 12, 2026 through Monday, July 13, 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.

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