EmergencyDescent — RAX220

RAX220 (Royal AIR Freight) was inbound to KPAE on 2026-05-29. SkyMeter detected a emergencydescent at 05:14 UTC. Trace data at the event: 25419 ft AGL, 455 kt GS. METAR at the time reported 3 kt wind, 2 kt crosswind component. Detection algorithm and known limitations: see SkyMeter methodology.

• SECURITY5/0601 2025-11-30 19:00Z – 2026-05-31 18:59Z SFC–400 ft

  Los Angeles, CA, Sunday, November 30, 2025 through Sunday, May 31, 2026 Local

  View FAA NOTAM →
• SECURITY6/4348 2026-03-08 07:00Z – 2026-11-01 06:59Z SFC–2,400 ft

  GRAND FORKS AFB, ND, Sunday, March 8, 2026 through Sunday, November 1, 2026 Local

  View FAA NOTAM →
• 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 →
• HAZARDS6/0887 2026-05-16 18:37Z – 2026-05-30 04:00Z SFC–10,500 ft

  19NM SW TUCUMCARI, NM, Saturday, May 16, 2026 through Saturday, May 30, 2026 UTC

  View FAA NOTAM →
• SECURITY6/0758 2026-05-18 07:01Z – 2026-05-31 06:59Z SFC–1,499 ft

  Concord, CA, Monday, May 18, 2026 through Saturday, May 30, 2026 Local

  View FAA NOTAM →
• HAZARDS6/1359 2026-05-18 20:54Z – 2026-05-31 16:00Z SFC–6,000 ft

  3NM S SIMI VALLEY, CA, Monday, May 18, 2026 through Sunday, May 31, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1358 2026-05-19 00:52Z – 2026-06-02 02:00Z SFC–10,000 ft

  5NM S CAMPO, CO, Tuesday, May 19, 2026 through Tuesday, June 2, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1376 2026-05-19 02:58Z – 2026-05-31 15:00Z SFC–6,000 ft

  3NM S SIMI VALLEY, CA, Tuesday, May 19, 2026 through Sunday, May 31, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/2366 2026-05-22 06:00Z – 2026-06-05 04:00Z SFC–10,000 ft

  12NM S PRESCOTT, AZ, Friday, May 22, 2026 through Friday, June 5, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/2318 2026-05-22 14:00Z – 2026-06-05 04:00Z SFC–9,000 ft

  17NM SW HELENA, MT, Friday, May 22, 2026 through Friday, June 5, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/2580 2026-05-24 14:00Z – 2026-05-30 04:00Z SFC–10,000 ft

  30NM SW WINNEMUCCA, NV, Sunday, May 24, 2026 through Saturday, May 30, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/2645 2026-05-25 14:00Z – 2026-05-30 04:00Z SFC–10,000 ft

  30NM SW WINNEMUCCA, NV, Monday, May 25, 2026 through Saturday, May 30, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/2573 2026-05-25 15:00Z – 2026-06-06 03:00Z SFC–8,000 ft

  32NM SW SANTA BARBARA, CA, Monday, May 25, 2026 through Saturday, June 6, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/2646 2026-05-25 15:00Z – 2026-06-08 04:00Z SFC–11,000 ft

  22NM SE JACKSON, WY, Monday, May 25, 2026 through Monday, June 8, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/2830 2026-05-25 15:45Z – 2026-06-11 16:00Z SFC–5,000 ft

  GARDEN GROVE, CA, Monday, May 25, 2026 through Thursday, June 11, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/3585 2026-05-28 14:00Z – 2026-06-11 03:00Z SFC–9,000 ft

  74NM S MILES CITY, MT, Thursday, May 28, 2026 through Thursday, June 11, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/3649 2026-05-28 14:00Z – 2026-06-11 03:00Z SFC–9,000 ft

  74NM S MILES CITY, MT, Thursday, May 28, 2026 through Thursday, June 11, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/3703 2026-05-28 15:12Z – 2026-05-29 04:00Z SFC–13,000 ft

  38NM SE TWIN FALLS, ID, Thursday, May 28, 2026 through Friday, May 29, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/3699 2026-05-28 16:00Z – 2026-05-29 00:15Z SFC–2,800 ft

  23NM W GRAND MARAIS, MN, Thursday, May 28, 2026 through Friday, May 29, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/3887 2026-05-28 22:43Z – 2026-05-29 04:00Z SFC–9,000 ft

  23NM SE GLENDIVE, MT, Thursday, May 28, 2026 through Friday, May 29, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/3889 2026-05-28 22:59Z – 2026-06-10 04:00Z SFC–10,500 ft

  11NM SE SPANISH FORK, UT, Thursday, May 28, 2026 through Wednesday, June 10, 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.

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