Go-around — UAL273

UAL273 (United Airlines) was operating from LFMN to KEWR on 2026-06-21. SkyMeter detected a go-around at Newark Liberty International Airport (KEWR) on runway 22L at 19:07 UTC. Trace data at the event: 336 ft AGL, 170 kt GS, 0 fpm vertical. METAR at the time reported 10 kt wind, 7 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/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/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/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/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/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/6449 2026-06-11 04:01Z – 2026-06-28 03:59Z SFC–400 ft

  New York, NY, Thursday, June 11, 2026 through Saturday, June 27, 2026 Local

  View FAA NOTAM →
• SECURITY6/6850 2026-06-12 04:01Z – 2026-06-28 03:59Z SFC–1,000 ft

  Boston, MA, Friday, June 12, 2026 through Saturday, June 27, 2026 Local

  View FAA NOTAM →
• SECURITY6/6851 2026-06-13 04:01Z – 2026-07-12 03:59Z SFC–1,000 ft

  Harrison, NJ, Saturday, June 13, 2026 through Saturday, July 11, 2026 Local

  View FAA NOTAM →
• SECURITY6/7230 2026-06-13 04:01Z – 2026-07-20 03:59Z SFC–1,000 ft

  New York, NY, Saturday, June 13, 2026 through Sunday, July 19, 2026 Local

  View FAA NOTAM →
• SECURITY6/7801 2026-06-15 04:00Z – 2026-07-07 03:29Z SFC–400 ft

  Whippany, NJ, Monday, June 15, 2026 through Monday, July 6, 2026 Local

  View FAA NOTAM →
• SECURITY6/7815 2026-06-15 10:00Z – 2026-06-22 02:00Z SFC–400 ft

  Southampton, NY, Monday, June 15, 2026 through Sunday, June 21, 2026 Local

  View FAA NOTAM →
• AIR SHOWS/SPORTS6/8255 2026-06-19 15:00Z – 2026-06-22 02:00Z SFC–3,000 ft

  West Milford, NJ, Friday, June 19, 2026 through Monday, June 22, 2026 UTC

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

  Jersey City, NJ, Sunday, June 21, 2026 through Wednesday, July 1, 2026 Local

  View FAA NOTAM →
• SECURITY6/9266 2026-06-21 15:00Z – 2026-06-21 21:00Z SFC–400 ft

  Secaucus, NJ, Sunday, June 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.

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