Diversion — EJA759
KBDN · 162026-07-19 23:12 UTC· KSJC → KBDN· NETJETS SALES INC, AIR MERLINO LLC, FBMC INC, HAMPTON JOHN BETHE· CL35
EJA759 (Netjets Sales) was operating from KSJC to KSTS (Charles M. Schulz Sonoma County Airport) on 2026-07-19. SkyMeter detected a diversion to Bend Municipal Airport (KBDN) on runway 16 at 23:12 UTC. Peak cruise altitude FL454, turnaround area near Burney, US. Approach stability score: 72/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 7 kt wind, 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/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/4052 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
San Jose, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4054 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
San Jose, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4204 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
Santa Clara, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/7983 2026-07-05 14:07Z – 2026-07-21 06:59Z SFC–400 ft
San Jose, CA
View FAA NOTAM → - SECURITY6/7985 2026-07-05 14:07Z – 2026-07-21 06:59Z SFC–400 ft
San Jose, 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/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/6388 2026-07-17 02:26Z – 2026-07-31 04:00Z SFC–10,000 ft
63NM NE REDDING, CA, Friday, July 17, 2026 through Friday, July 31, 2026 UTC
View FAA NOTAM → - HAZARDS6/6393 2026-07-17 02:30Z – 2026-07-31 04:00Z SFC–10,000 ft
63NM NE REDDING, CA, Friday, July 17, 2026 through Friday, July 31, 2026 UTC
View FAA NOTAM → - HAZARDS6/6434 2026-07-17 05:07Z – 2026-08-01 04:00Z SFC–10,000 ft
63NM NE REDDING, CA, Friday, July 17, 2026 through Saturday, August 1, 2026 UTC
View FAA NOTAM → - HAZARDS6/6433 2026-07-17 05:08Z – 2026-08-01 04:00Z SFC–10,000 ft
63NM NE REDDING, CA, Friday, July 17, 2026 through Saturday, August 1, 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 16
- 3460 ft AGL at event
- 120 kt ground speed
- 0 fpm vertical
- Approach stability 72/100
- 7 kt wind
- 0 kt crosswind component
- 16,093 m visibility
- METAR KBDN 160655Z AUTO 30005KT 10SM -RA BKN060 OVC070 11/08 A3004 RMK AO2 P0002
Flight context
- EJA759
- Netjets Sales
- CL35
- KSJC → KBDN
- 2026-07-19 23:12 UTC
- KBDN runway 16
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