EmergencyDescent — RAX220

2026-04-22 08:37 UTC· KPAE → KAWM· ROYAL AIR FREIGHT INC· LJ35

▶ Replay 📊 Analyse

RAX220 (Royal AIR Freight) was operating from KPAE to KAWM on 2026-04-22. SkyMeter detected a emergencydescent at 08:37 UTC. Trace data at the event: 33728 ft AGL, 453 kt GS. Approach stability score: 54/100. Scores in this band occur on roughly 10-15% of approaches at this runway, with multiple gates outside the per-runway envelope. METAR at the time reported 4 kt wind, 4 kt crosswind component. Detection algorithm and known limitations: see SkyMeter methodology.

Active FAA TFR during this flight

Source: FAA TFR archive (hourly snapshot)
  • 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 →

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

  • 33728 ft AGL at event
  • 453 kt ground speed
  • 0 fpm vertical
  • Approach stability 54/100
  • 4 kt wind
  • 4 kt crosswind component

Flight context

  • RAX220
  • Royal AIR Freight
  • LJ35
  • KPAE → KAWM
  • 2026-04-22 08:37 UTC

All events on this flight

EmergencyDescent 08:37:45 UTC · · 33,728 ft AGL · 453 kt GS
EmergencyDescent 08:37:45 UTC · · 33,728 ft AGL · 453 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