EmergencyDescent — N645PM

2026-05-30 22:50 UTC· KJYO KPBI· PAG MANAGEMENT LLC· E35L

N645PM (PAG Management) was operating from KJYO to KPBI on 2026-05-30. SkyMeter detected a emergencydescent at 22:50 UTC. Trace data at the event: 31345 ft AGL, 448 kt GS. Approach stability score: 49/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 7 kt wind, 6 kt crosswind component. 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/2644 2026-05-27 11:00Z – 2026-06-12 22:00Z SFC–400 ft

    Brunswick, GA, Wednesday, May 27, 2026 through Friday, June 12, 2026 Local

    View FAA NOTAM →
  • SPACE OPERATIONS6/3356 2026-05-30 23:02Z – 2026-05-31 00:33Z SFC–180 ft

    Cape Canaveral, FL, Saturday, May 30, 2026 through Saturday, May 30, 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

  • 31345 ft AGL at event
  • 448 kt ground speed
  • 0 fpm vertical
  • Approach stability 49/100
  • 7 kt wind
  • 6 kt crosswind component

Flight context

  • N645PM
  • PAG Management
  • E35L
  • KJYO → KPBI
  • 2026-05-30 22:50 UTC

All events on this flight

EmergencyDescent 22:50:39 UTC · · 31,345 ft AGL · 448 kt GS
EmergencyDescent 22:50:39 UTC · · 31,345 ft AGL · 448 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