EmergencyDescent — N558LM

2026-06-25 13:41 UTC· PAFA → PAED· CORSAIR TWO LLC· LJ45

▶ Replay 📊 Analyse

N558LM (Corsair TWO) was operating from PAFA to PAED on 2026-06-25. SkyMeter detected a emergencydescent at 13:41 UTC. Trace data at the event: 29180 ft AGL, 446 kt GS. Approach stability score: 35/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 2 kt wind, 2 kt crosswind component. Detection algorithm and known limitations: see SkyMeter methodology.

Active FAA TFR during this flight

Source: FAA TFR archive (hourly snapshot)
  • SECURITY6/4925 2026-03-08 10:00Z – 2026-11-01 09:59Z SFC–360 ft

    CLEAR, AK, Sunday, March 8, 2026 through Sunday, November 1, 2026 Local

    View FAA NOTAM →
  • SECURITY6/4926 2026-03-08 10:00Z – 2026-11-01 12:00Z SFC–2,600 ft

    CLEAR, AK, Sunday, March 8, 2026 through Sunday, November 1, 2026 Local

    View FAA NOTAM →
  • HAZARDS6/0243 2026-06-23 23:00Z – 2026-07-04 04:00Z SFC–4,000 ft

    47NM SW FAIRBANKS, AK, Tuesday, June 23, 2026 through Saturday, July 4, 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

  • 29180 ft AGL at event
  • 446 kt ground speed
  • 0 fpm vertical
  • Approach stability 35/100
  • 2 kt wind
  • 2 kt crosswind component

Flight context

  • N558LM
  • Corsair TWO
  • LJ45
  • PAFA → PAED
  • 2026-06-25 13:41 UTC

All events on this flight

EmergencyDescent 13:41:04 UTC · · 29,180 ft AGL · 446 kt GS
Unstable approach 13:54:58 UTC · PAED runway 06 · 1,185 ft AGL · 150 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