Go-around — UCA4327
KDAY · 06L2026-06-08 13:30 UTC· KIAD → KDAY· UNITED AIRLINES INC· E45X
UCA4327 (United Airlines) was operating from KIAD to KDAY on 2026-06-08. SkyMeter detected a go-around at James M Cox Dayton International Airport (KDAY) on runway 06L at 13:30 UTC. Trace data at the event: 1521 ft AGL, 159 kt GS. METAR at the time reported 5 kt wind, 4 kt crosswind component, 11,265 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)- SECURITY6/4120 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
CINNCINATI, OH, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4125 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
MILFORD, OH, Monday, June 1, 2026 through Monday, July 20, 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 06L
- 1521 ft AGL at event
- 159 kt ground speed
- 0 fpm vertical
- 5 kt wind
- 4 kt crosswind component
- 11,265 m visibility
- KDAY 181256Z 03009KT 7SM OVC006 22/21 A3023 RMK AO2 SLP228 T02220211
Flight context
- UCA4327
- United Airlines
- E45X
- KIAD → KDAY
- 2026-06-08 13:30 UTC
- KDAY runway 06L
All events on this flight
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