Go-around — UCA4925

UCA4925 (United Airlines) was operating from KMHT to KIAD on 2026-06-08. SkyMeter detected a go-around at Washington Dulles International Airport (KIAD) on runway 19L at 19:58 UTC. Trace data at the event: 549 ft AGL, 145 kt GS. METAR at the time reported 6 kt wind, 6 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.

• SECURITY5/2811 2025-10-20 12:00Z – 2026-10-20 12:00Z SFC–1,000 ft

  NEW YORK, NY, Monday, October 20, 2025 through Tuesday, October 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/3955 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

  Smithfield, RI, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/3956 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

  Atlantic City, NJ, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/3959 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

  Boston, MA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/3961 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

  Chester, PA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/3963 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

  FOXBOROUGH, MA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/3965 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

  Galloway, NJ, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/3967 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

  PHILADELPHIA, PA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/3969 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

  Waltham, MA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/3973 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

  WILMINGTON, DE, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/4105 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

  JERSEY CITY, NJ, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/4106 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

  New Brunswick, NJ, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/4115 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

  BASKING RIDGE, NJ, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/4117 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

  Warren, NJ, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/3949 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft

  Providence, RI, Monday, June 1, 2026 through Tuesday, July 21, 2026 Local

  View FAA NOTAM →
• SECURITY6/5236 2026-06-03 14:00Z – 2026-06-09 21:00Z SFC–2,000 ft

  Jamaica, NY, Wednesday, June 3, 2026 through Tuesday, June 9, 2026 Local

  View FAA NOTAM →
• VIP6/5158 2026-06-05 23:30Z – 2026-06-08 23:30Z SFC–17,999 ft

  Bedminster, NJ, Friday, June 5, 2026 through Monday, June 8, 2026 Local

  View FAA NOTAM →
• VIP6/5160 2026-06-05 23:30Z – 2026-06-08 23:30Z SFC–17,999 ft

  Bedminster, NJ, Friday, June 5, 2026 through Monday, June 8, 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.

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