EmergencyDescent — EJM675

2026-07-13 20:18 UTC· KPBI KCLL· N4DA LLC· LJ45

EJM675 (N4da) was operating from KPBI to KCLL on 2026-07-13. SkyMeter detected a emergencydescent at 20:18 UTC. Trace data at the event: 39551 ft AGL, 435 kt GS. Approach stability score: 41/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 4 kt wind. Detection algorithm and known limitations: see SkyMeter methodology.

Active FAA TFR during this flight

Source: FAA TFR archive (hourly snapshot)
  • SECURITY5/2809 2025-10-20 12:00Z – 2026-10-20 12:00Z SFC–2,000 ft

    Palm Beach, FL, Monday, October 20, 2025 through Tuesday, October 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 →
  • 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/6787 2026-07-03 15:07Z – 2026-07-21 04:59Z SFC–400 ft

    Houston, TX

    View FAA NOTAM →
  • SECURITY6/6783 2026-07-03 16:07Z – 2026-07-21 04:59Z SFC–400 ft

    Houston, TX

    View FAA NOTAM →
  • SECURITY6/7880 2026-07-05 14:07Z – 2026-07-21 03:59Z SFC–400 ft

    Tampa, FL

    View FAA NOTAM →
  • SECURITY6/7881 2026-07-05 14:07Z – 2026-07-21 03:59Z SFC–400 ft

    Tampa, FL

    View FAA NOTAM →
  • SECURITY6/7889 2026-07-07 13:07Z – 2026-07-21 03:59Z SFC–400 ft

    Palm Beach Gardens, FL

    View FAA NOTAM →
  • SECURITY6/6838 2026-07-09 11:07Z – 2026-07-21 04:59Z SFC–400 ft

    Houston, TX

    View FAA NOTAM →
  • HAZARDS6/4885 2026-07-11 11:00Z – 2026-07-20 01:00Z SFC–5,000 ft

    14NM NE LAKE CITY, FL, Saturday, July 11, 2026 through Monday, July 20, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/4910 2026-07-11 11:33Z – 2026-07-20 01:00Z SFC–5,000 ft

    14NM NE LAKE CITY, FL, Saturday, July 11, 2026 through Monday, July 20, 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

  • 39551 ft AGL at event
  • 435 kt ground speed
  • 0 fpm vertical
  • Approach stability 41/100
  • 4 kt wind
  • 0 kt crosswind component

Flight context

  • EJM675
  • N4da
  • LJ45
  • KPBI → KCLL
  • 2026-07-13 20:18 UTC

All events on this flight

EmergencyDescent 20:18:26 UTC · · 39,551 ft AGL · 435 kt GS
Unstable approach 20:31:47 UTC · KCLL runway 17 · 1,409 ft AGL · 138 kt GS
EmergencyDescent 20:18:26 UTC · · 39,551 ft AGL · 435 kt GS
Unstable approach 20:31:47 UTC · KCLL runway 17 · 1,409 ft AGL · 138 kt GS
EmergencyDescent 20:18:26 UTC · · 39,551 ft AGL · 435 kt GS
Unstable approach 20:31:47 UTC · KCLL runway 17 · 1,409 ft AGL · 138 kt GS
EmergencyDescent 20:18:26 UTC · · 39,551 ft AGL · 435 kt GS
Unstable approach 20:31:47 UTC · KCLL runway 17 · 1,409 ft AGL · 138 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