Diversion — MXY650
KACV · 322026-08-06 17:01 UTC· KBUR → KACV· BANK OF UTAH TRUSTEE· BCS3
MXY650 (Bank of Utah) was operating from KBUR to KACV (California Redwood Coast-Humboldt County Airport) on 2026-08-06. SkyMeter detected a diversion to California Redwood Coast-Humboldt County Airport (KACV) on runway 32 at 17:01 UTC. Peak cruise altitude FL320, turnaround area near Patterson, US. Approach stability score: 94/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 0 kt wind, 14,484 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/6491 2026-07-20 07:01Z – 2026-09-16 06:59Z SFC–1,499 ft
Concord, CA, Monday, July 20, 2026 through Tuesday, September 15, 2026 Local
View FAA NOTAM → - HAZARDS6/7246 2026-07-21 05:00Z – 2026-08-21 03:00Z SFC–10,500 ft
20NM N INDEPENDENCE, CA, Tuesday, July 21, 2026 through Friday, August 21, 2026 UTC
View FAA NOTAM → - HAZARDS6/7372 2026-07-21 13:38Z – 2026-08-22 03:00Z SFC–10,500 ft
20NM N INDEPENDENCE, CA, Tuesday, July 21, 2026 through Saturday, August 22, 2026 UTC
View FAA NOTAM → - HAZARDS6/7909 2026-07-22 18:11Z – 2026-08-08 04:00Z SFC–12,500 ft
20NM N INDEPENDENCE, CA, Wednesday, July 22, 2026 through Saturday, August 8, 2026 UTC
View FAA NOTAM → - HAZARDS6/8487 2026-07-25 01:02Z – 2026-08-08 04:00Z SFC–10,500 ft
12NM NE SUSANVILLE, CA, Saturday, July 25, 2026 through Saturday, August 8, 2026 UTC
View FAA NOTAM → - HAZARDS6/8945 2026-07-27 14:57Z – 2026-08-09 04:00Z SFC–5,500 ft
SONORA, CA, Monday, July 27, 2026 through Sunday, August 9, 2026 UTC
View FAA NOTAM → - HAZARDS6/9397 2026-07-28 01:03Z – 2026-08-11 04:00Z SFC–5,000 ft
9NM NW GRASS VALLEY, CA, Tuesday, July 28, 2026 through Tuesday, August 11, 2026 UTC
View FAA NOTAM → - HAZARDS6/9881 2026-07-29 02:10Z – 2026-08-12 04:00Z SFC–13,500 ft
25NM S BISHOP, CA, Wednesday, July 29, 2026 through Wednesday, August 12, 2026 UTC
View FAA NOTAM → - HAZARDS6/0938 2026-08-02 15:28Z – 2026-08-16 04:00Z SFC–6,000 ft
11NM SE UKIAH, CA, Sunday, August 2, 2026 through Sunday, August 16, 2026 UTC
View FAA NOTAM → - HAZARDS6/1795 2026-08-04 20:57Z – 2026-08-18 04:00Z SFC–6,000 ft
27NM NE STOCKTON, CA, Tuesday, August 4, 2026 through Tuesday, August 18, 2026 UTC
View FAA NOTAM → - HAZARDS6/2267 2026-08-05 18:05Z – 2026-08-08 04:00Z SFC–9,000 ft
27NM S BAKERSFIELD, CA, Wednesday, August 5, 2026 through Saturday, August 8, 2026 UTC
View FAA NOTAM → - HAZARDS6/2274 2026-08-05 19:25Z – 2026-08-15 04:00Z SFC–13,500 ft
25NM S BISHOP, CA, Wednesday, August 5, 2026 through Saturday, August 15, 2026 UTC
View FAA NOTAM → - HAZARDS6/2433 2026-08-05 21:49Z – 2026-08-15 04:00Z SFC–6,000 ft
27NM NE STOCKTON, CA, Wednesday, August 5, 2026 through Saturday, August 15, 2026 UTC
View FAA NOTAM → - HAZARDS6/2489 2026-08-06 02:15Z – 2026-08-19 04:00Z SFC–9,000 ft
27NM S BAKERSFIELD, CA, Thursday, August 6, 2026 through Wednesday, August 19, 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 32
- 0 ft AGL at event
- 0 kt ground speed
- 0 fpm vertical
- Approach stability 94/100
- 0 kt wind
- 0 kt crosswind component
- 14,484 m visibility
- KACV 170653Z AUTO 15007KT 9SM OVC006 13/12 A2994 RMK AO2 SLP144 T01330122
Flight context
- MXY650
- Bank of Utah
- BCS3
- KBUR → KACV
- 2026-08-06 17:01 UTC
- KACV runway 32
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