EmergencyDescent — VIV0617

2026-05-18 05:07 UTC· KIAH MMMY· A320

VIV0617 was operating from KIAH to MMMY on 2026-05-18. SkyMeter detected a emergencydescent at 05:07 UTC. Trace data at the event: 30284 ft AGL, 421 kt GS. METAR at the time reported 16 kt wind, 9 kt crosswind component. Detection algorithm and known limitations: see SkyMeter methodology.

Active FAA TFR during this flight

Source: FAA TFR archive (hourly snapshot)
  • SECURITY5/6914 2025-05-06 23:30Z – 2027-10-18 11:03Z SFC–6,000 ft

    South Padre Island, TX, Tuesday, May 6, 2025 Local

    View FAA NOTAM →
  • SECURITY5/3678 2026-01-01 05:00Z – 2027-01-01 05:59Z SFC–2,000 ft

    Brownsville, TX, Thursday, January 1, 2026 through Friday, January 1, 2027 Local

    View FAA NOTAM →
  • SECURITY5/3679 2026-01-01 05:00Z – 2027-01-01 05:59Z SFC–5,000 ft

    Brownsville, TX, Thursday, January 1, 2026 through Friday, January 1, 2027 Local

    View FAA NOTAM →
  • HAZARDS6/9795 2026-05-12 17:22Z – 2026-05-25 23:59Z SFC–10,000 ft

    BROWNSVILLE, TX, Tuesday, May 12, 2026 through Monday, May 25, 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

  • 30284 ft AGL at event
  • 421 kt ground speed
  • 0 fpm vertical
  • 16 kt wind
  • 9 kt crosswind component

Flight context

  • VIV0617
  • A320
  • KIAH → MMMY
  • 2026-05-18 05:07 UTC

All events on this flight

EmergencyDescent 05:07:51 UTC · · 30,284 ft AGL · 421 kt GS
EmergencyDescent 05:07:51 UTC · · 30,284 ft AGL · 421 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