EmergencyDescent — N619RJ
2026-05-16 18:22 UTC· KMYF → KMDS· ECLIPSE 231 LLC· EA50
N619RJ (Eclipse 231) was operating from KMYF to KMDS on 2026-05-16. SkyMeter detected a emergencydescent at 18:22 UTC. Trace data at the event: 29124 ft AGL, 411 kt GS. Approach stability score: 20/100. Scores below 50 occur on under 10% of approaches at this runway and indicate the v2 scorer flagged the approach as highly anomalous (three or more gates exceeded the runway's P90 envelope simultaneously). METAR at the time reported 7 kt wind, 5 kt crosswind component. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- HAZARDS6/9663 2026-05-12 13:00Z – 2026-05-26 03:00Z SFC–10,500 ft
38NM NW SILVER CITY, NM, Tuesday, May 12, 2026 through Tuesday, May 26, 2026 UTC
View FAA NOTAM → - HAZARDS6/0618 2026-05-15 13:00Z – 2026-05-28 04:00Z SFC–13,500 ft
22NM NE RUIDOSO, NM, Friday, May 15, 2026 through Thursday, May 28, 2026 UTC
View FAA NOTAM → - HAZARDS6/0607 2026-05-15 14:00Z – 2026-05-28 04:00Z SFC–12,000 ft
30NM SW NEPHI, UT, Friday, May 15, 2026 through Thursday, May 28, 2026 UTC
View FAA NOTAM → - HAZARDS6/0835 2026-05-16 12:00Z – 2026-05-28 05:00Z SFC–12,500 ft
JACKSON, WY, Saturday, May 16, 2026 through Thursday, May 28, 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
- 29124 ft AGL at event
- 411 kt ground speed
- 0 fpm vertical
- Approach stability 20/100
- 7 kt wind
- 5 kt crosswind component
Flight context
- N619RJ
- Eclipse 231
- EA50
- KMYF → KMDS
- 2026-05-16 18:22 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