EmergencyDescent — N585BP

2026-07-03 01:29 UTC· KMSY → KRVS· MS AIRWAYS LLC· PRM1

▶ Replay 📊 Analyse

N585BP (MS Airways) was operating from KMSY to KRVS on 2026-07-03. SkyMeter detected a emergencydescent at 01:29 UTC. Trace data at the event: 33970 ft AGL, 455 kt GS. Approach stability score: 33/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, 3 kt crosswind component. Detection algorithm and known limitations: see SkyMeter methodology.

Active FAA TFR during this flight

Source: FAA TFR archive (hourly snapshot)
  • SECURITY6/4134 2026-06-01 00:00Z – 2026-07-20 23:59Z

    TULSA, OK, Monday, June 1, 2026 through Monday, July 20, 2026 UTC

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

    Tulsa, OK, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • AIR SHOWS/SPORTS6/1386 2026-07-02 17:00Z – 2026-07-04 03:00Z SFC–17,500 ft

    athens, TX, Thursday, July 2, 2026 through Saturday, July 4, 2026 UTC

    View FAA NOTAM →
  • AIR SHOWS/SPORTS6/1387 2026-07-02 17:00Z – 2026-07-05 03:00Z SFC–17,500 ft

    malakoff, TX, Thursday, July 2, 2026 through Sunday, July 5, 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

  • 33970 ft AGL at event
  • 455 kt ground speed
  • 0 fpm vertical
  • Approach stability 33/100
  • 4 kt wind
  • 3 kt crosswind component

Flight context

  • N585BP
  • MS Airways
  • PRM1
  • KMSY → KRVS
  • 2026-07-03 01:29 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