Return to field — AVA030

KMIA · 08R

2026-05-18 11:50 UTC· KMIA → KMIA· WILMINGTON TRUST CO TRUSTEE· A320

▶ Replay 📊 Analyse

AVA030 (Wilmington Trust) had departed KMIA on 2026-05-18. SkyMeter detected a return to field at Miami International Airport (KMIA) on runway 08R at 11:50 UTC. Peak cruise altitude FL372, turnaround area near Negril, JM. Approach stability score: 91/100. Scores in this band are observed on roughly 50% of approaches at this runway and represent the centerline of normal operations. METAR at the time reported 0 kt wind, 16,093 m visibility. Detection algorithm and known limitations: see SkyMeter methodology.

Active FAA TFR during this flight

Source: FAA TFR archive (hourly snapshot)
  • AIR SHOWS/SPORTS6/9510 2026-05-18 19:00Z – 2026-05-19 21:30Z SFC–10,000 ft

    Miami Beach, FL, Monday, May 18, 2026 through Tuesday, May 19, 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

  • Runway 08R
  • 37267 ft AGL at event
  • 506 kt ground speed
  • 0 fpm vertical
  • Approach stability 91/100
  • 0 kt wind
  • 0 kt crosswind component
  • 16,093 m visibility
  • KMIA 171653Z VRB04KT 10SM -RA SCT026CB SCT045 BKN180 OVC210 25/23 A3007 RMK AO2 RAB36 PRESFR SLP183 CB VC SE-S MOV W CB DSNT NE P0000 T02500228

Flight context

  • AVA030
  • Wilmington Trust
  • A320
  • KMIA → KMIA
  • 2026-05-18 11:50 UTC
  • KMIA runway 08R

All events on this flight

Return to field 11:50:44 UTC · KMIA runway 08R · 37,267 ft AGL · 506 kt GS
EmergencyDescent 18:50:09 UTC · · 32,678 ft AGL · 437 kt GS
EmergencyDescent 18:50:09 UTC · · 32,678 ft AGL · 437 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· KMIA