EmergencyDescent — LXJ593

2026-07-18 14:04 UTC· KDAY → KMDW· FLEXJET LLC· CL35

▶ Replay 📊 Analyse

LXJ593 (Flexjet) was operating from KDAY to KMDW on 2026-07-18. SkyMeter detected a emergencydescent at 14:04 UTC. Trace data at the event: 43320 ft AGL, 413 kt GS. Approach stability score: 90/100. Scores in this band are observed on roughly 50% of approaches at this runway and represent the centerline of normal operations. METAR at the time reported 10 kt wind, 9 kt crosswind component. Detection algorithm and known limitations: see SkyMeter methodology.

Active FAA TFR during this flight

Source: FAA TFR archive (hourly snapshot)
  • SECURITY6/4118 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

    CARMEL, IN, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/4128 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

    WESTFIELD, IN, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/7205 2026-06-23 21:07Z – 2026-07-21 03:59Z SFC–400 ft

    Carmel, IN

    View FAA NOTAM →
  • SECURITY6/7208 2026-06-23 21:07Z – 2026-07-21 03:59Z SFC–400 ft

    Westfield, IN

    View FAA NOTAM →
  • SECURITY6/5591 2026-07-15 17:00Z – 2026-07-20 04:59Z SFC–400 ft

    Hammond, IN, Wednesday, July 15, 2026 through Sunday, July 19, 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

  • 43320 ft AGL at event
  • 413 kt ground speed
  • 0 fpm vertical
  • Approach stability 90/100
  • 10 kt wind
  • 9 kt crosswind component

Flight context

  • LXJ593
  • Flexjet
  • CL35
  • KDAY → KMDW
  • 2026-07-18 14:04 UTC

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