SPAR537 was operating from KVBG to KAMA on 2026-08-12. SkyMeter detected a emergencydescent at 03:42 UTC. Trace data at the event: 28667 ft AGL, 444 kt GS. METAR at the time reported 9 kt wind, 1 kt crosswind component. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- 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 → - HAZARDS6/2435 2026-08-06 13:00Z – 2026-08-20 04:00Z SFC–13,500 ft
13NM N SANTA FE, NM, Thursday, August 6, 2026 through Thursday, August 20, 2026 UTC
View FAA NOTAM → - HAZARDS6/2747 2026-08-07 12:00Z – 2026-08-14 03:00Z SFC–14,000 ft
24NM SE ALBUQUERQUE, NM, Friday, August 7, 2026 through Friday, August 14, 2026 UTC
View FAA NOTAM → - HAZARDS6/2842 2026-08-07 14:30Z – 2026-08-21 04:00Z SFC–13,500 ft
13NM N SANTA FE, NM, Friday, August 7, 2026 through Friday, August 21, 2026 UTC
View FAA NOTAM → - HAZARDS6/2916 2026-08-08 01:45Z – 2026-08-15 05:00Z SFC–6,000 ft
25NM S BAKERSFIELD, CA, Saturday, August 8, 2026 through Saturday, August 15, 2026 UTC
View FAA NOTAM → - HAZARDS6/3075 2026-08-08 19:30Z – 2026-08-22 04:00Z SFC–12,000 ft
28NM NE LAS VEGAS, NM, Saturday, August 8, 2026 through Saturday, August 22, 2026 UTC
View FAA NOTAM → - HAZARDS6/3130 2026-08-09 15:00Z – 2026-08-12 03:00Z SFC–6,000 ft
5NM SW SEDONA, AZ, Sunday, August 9, 2026 through Wednesday, August 12, 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
- 28667 ft AGL at event
- 444 kt ground speed
- 0 fpm vertical
- 9 kt wind
- 1 kt crosswind component
Flight context
- SPAR537
- LJ35
- KVBG → KAMA
- 2026-08-12 03:42 UTC
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