EmergencyDescent — N229LJ

2026-08-23 02:30 UTC· KAEJ → KVBT· LJRSW LLC· LJ31

▶ Replay 📊 Analyse

N229LJ (Ljrsw) was operating from KAEJ to KVBT on 2026-08-23. SkyMeter detected a emergencydescent at 02:30 UTC. Trace data at the event: 30039 ft AGL, 473 kt GS. Approach stability score: 73/100. Scores in this band are observed on roughly 25% of approaches at this runway: one or more gates outside the per-runway tightest envelope, but still inside the typical operating range. METAR at the time reported 6 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)
  • HAZARDS6/1462 2026-08-04 13:00Z – 2026-09-01 04:00Z SFC–15,000 ft

    20NM SW PUEBLO, CO, Tuesday, August 4, 2026 through Tuesday, September 1, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/3101 2026-08-09 13:00Z – 2026-08-24 03:00Z SFC–15,000 ft

    24NM SW PUEBLO, CO, Sunday, August 9, 2026 through Monday, August 24, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/4894 2026-08-13 13:00Z – 2026-08-28 04:00Z SFC–15,000 ft

    8NM SE TRINIDAD, CO, Thursday, August 13, 2026 through Friday, August 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

  • 30039 ft AGL at event
  • 473 kt ground speed
  • 0 fpm vertical
  • Approach stability 73/100
  • 6 kt wind
  • 4 kt crosswind component

Flight context

  • N229LJ
  • Ljrsw
  • LJ31
  • KAEJ → KVBT
  • 2026-08-23 02:30 UTC

All events on this flight

EmergencyDescent 02:30:49 UTC · · 30,039 ft AGL · 473 kt GS
EmergencyDescent 02:30:49 UTC · · 30,039 ft AGL · 473 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