EmergencyDescent — N763MT

2026-08-11 14:45 UTC· KSDL KU42· PACIFIC CHALLENGER AIRCRAFT SERVICES LLC· CL30

N763MT (Pacific Challenger Aircraft Services) was operating from KSDL to KU42 on 2026-08-11. SkyMeter detected a emergencydescent at 14:45 UTC. Trace data at the event: 32491 ft AGL, 485 kt GS. METAR at the time reported 5 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/1461 2026-08-04 12:00Z – 2026-08-18 04:00Z SFC–13,000 ft

    4NM W RICHFIELD, UT, Tuesday, August 4, 2026 through Tuesday, August 18, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/1464 2026-08-04 12:00Z – 2026-08-18 04:00Z SFC–13,000 ft

    4NM W RICHFIELD, UT, Tuesday, August 4, 2026 through Tuesday, August 18, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/2889 2026-08-07 19:58Z – 2026-08-21 04:00Z SFC–13,000 ft

    4NM W RICHFIELD, UT, Friday, August 7, 2026 through Friday, August 21, 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

  • 32491 ft AGL at event
  • 485 kt ground speed
  • 0 fpm vertical
  • 5 kt wind
  • 1 kt crosswind component

Flight context

  • N763MT
  • Pacific Challenger Aircraft Services
  • CL30
  • KSDL → KU42
  • 2026-08-11 14:45 UTC

All events on this flight

EmergencyDescent 14:45:24 UTC · · 32,491 ft AGL · 485 kt GS
EmergencyDescent 14:45:24 UTC · · 32,491 ft AGL · 485 kt GS

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

SkyMeter · trace data observed via ADS-B