DWI5863 was operating from CYYZ to KMIA on 2026-08-31. SkyMeter detected a go-around at Miami International Airport (KMIA) on runway 09 at 20:57 UTC. Trace data at the event: 499 ft AGL, 167 kt GS, 0 fpm vertical. METAR at the time reported 6 kt wind, 1 kt crosswind component, 16,093 m visibility. A go-around is a discontinued landing approach in which the pilot adds power and climbs back to a safe altitude before re-attempting the approach or proceeding to an alternate. It is a routine safety response, not an emergency, and is taught as the standard reaction to any unstable approach. 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 → - SPACE OPERATIONS6/8542 2026-08-31 11:00Z – 2026-08-31 12:16Z SFC–180 ft
Cape Canaveral, FL, Monday, August 31, 2026 Local
View FAA NOTAM → - SPACE OPERATIONS6/8544 2026-08-31 11:00Z – 2026-08-31 12:16Z SFC–180 ft
Cape Canaveral, FL, Monday, August 31, 2026 Local
View FAA NOTAM → - SECURITY6/8897 2026-08-31 12:00Z – 2026-08-31 20:30Z SFC–400 ft
STOYSTOWN, PA, Monday, August 31, 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 09
- 499 ft AGL at event
- 167 kt ground speed
- 0 fpm vertical
- 6 kt wind
- 1 kt crosswind component
- 16,093 m visibility
- KMIA 131753Z COR 27012G24KT 10SM SCT020CB BKN035 BKN250 30/22 A3003 RMK AO2 SLP168 CB S-W-N MOV E T03000222 10333 20261 58019 $
Flight context
- DWI5863
- B38M
- CYYZ → KMIA
- 2026-08-31 20:57 UTC
- KMIA runway 09
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