Return to field — PRGDY

KMLB · 27R

2026-08-21 16:45 UTC· KMLB → KMLB· EMBRAER S.A.· E545

▶ Replay 📊 Analyse

PRGDY (Embraer S.A.) had departed KMLB on 2026-08-21. SkyMeter detected a return to field at Melbourne International Airport (KMLB) on runway 27R at 16:45 UTC. Peak cruise altitude FL454, turnaround area near Hobe Sound, US. Approach stability score: 61/100. Scores in this band occur on roughly 10-15% of approaches at this runway, with multiple gates outside the per-runway envelope. 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)
  • SPACE OPERATIONS6/5396 2026-08-21 14:57Z – 2026-08-21 19:39Z SFC–180 ft

    Cape Canaveral, FL, Friday, August 21, 2026 Local

    View FAA NOTAM →
  • SPACE OPERATIONS6/5397 2026-08-21 14:57Z – 2026-08-21 19:39Z SFC–180 ft

    Cape Canaveral, FL, Friday, August 21, 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

  • Runway 27R
  • 45405 ft AGL at event
  • 452 kt ground speed
  • 0 fpm vertical
  • Approach stability 61/100
  • 0 kt wind
  • 0 kt crosswind component
  • 16,093 m visibility
  • KMLB 160953Z 12003KT 10SM BKN017 OVC023 26/24 A3008 RMK AO2 RAE24 SLP187 P0000 T02610244

Flight context

  • PRGDY
  • Embraer S.A.
  • E545
  • KMLB → KMLB
  • 2026-08-21 16:45 UTC
  • KMLB runway 27R

All events on this flight

Return to field 16:45:07 UTC · KMLB runway 27R · 45,405 ft AGL · 452 kt GS
EmergencyDescent 18:14:21 UTC · · 42,223 ft AGL · 422 kt GS
EmergencyDescent 18:14:21 UTC · · 42,223 ft AGL · 422 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· KMLB