EJA561 (Walker & Dunlop) was operating from KMIA to KADS on 2026-06-14. SkyMeter detected a emergencydescent at 20:22 UTC. Trace data at the event: 36985 ft AGL, 429 kt GS. Approach stability score: 78/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 2 kt wind, 1 kt crosswind component. Detection algorithm and known limitations: see SkyMeter methodology.

Active FAA TFR during this flight

Source: FAA TFR archive (hourly snapshot)
  • SECURITY5/2858 2025-12-26 04:59Z – 2026-07-02 03:59Z SFC–1,000 ft

    OCHOPPEE, FL, Thursday, December 25, 2025 through Wednesday, July 1, 2026 Local

    View FAA NOTAM →
  • SECURITY6/3705 2026-05-29 05:00Z – 2026-07-20 08:00Z SFC–400 ft

    DALLAS, TX, Friday, May 29, 2026 through Monday, July 20, 2026 Local

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

    BOCA RATON, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    MIAMI, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    Miami, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    FORT LAUDERDALE, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    Palm Beach Gardens, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    Tampa, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    TAMPA, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    HOUSTON, TX, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    HOUSTON, TX, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • HAZARDS6/5656 2026-06-04 16:19Z – 2026-06-18 00:15Z SFC–2,000 ft

    22NM SW TALLAHASSEE, FL, Thursday, June 4, 2026 through Thursday, June 18, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/5771 2026-06-04 21:47Z – 2026-06-18 00:15Z SFC–3,500 ft

    22NM SW TALLAHASSEE, FL, Thursday, June 4, 2026 through Thursday, June 18, 2026 UTC

    View FAA NOTAM →
  • SECURITY6/6447 2026-06-09 05:01Z – 2026-07-20 04:59Z SFC–1,000 ft

    Houston, TX, Tuesday, June 9, 2026 through Sunday, July 19, 2026 Local

    View FAA NOTAM →
  • SECURITY6/7228 2026-06-13 04:01Z – 2026-07-06 03:59Z SFC–1,000 ft

    Miami, FL, Saturday, June 13, 2026 through Sunday, July 5, 2026 Local

    View FAA NOTAM →
  • SECURITY6/7620 2026-06-14 14:00Z – 2026-06-14 23:00Z SFC–3,000 ft

    Houston, TX, Sunday, June 14, 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

  • 36985 ft AGL at event
  • 429 kt ground speed
  • 0 fpm vertical
  • Approach stability 78/100
  • 2 kt wind
  • 1 kt crosswind component

Flight context

  • EJA561
  • Walker & Dunlop
  • C68A
  • KMIA → KADS
  • 2026-06-14 20:22 UTC

All events on this flight

EmergencyDescent 20:22:43 UTC · · 36,985 ft AGL · 429 kt GS
EmergencyDescent 20:22:43 UTC · · 36,985 ft AGL · 429 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