Go-around — UAL2394

KEWR · 4R

2026-04-17 15:03 UTC· KBOS KEWR· UMB BANK NA TRUSTEE· A319

UAL2394 (UMB Bank NA) was operating from KBOS to KEWR on 2026-04-17. SkyMeter detected a go-around at Newark Liberty International Airport (KEWR) on runway 4R at 15:03 UTC. Trace data at the event: 674 ft AGL, 143 kt GS. METAR at the time reported 5 kt wind, 5 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/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 →

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 4R
  • 674 ft AGL at event
  • 143 kt ground speed
  • 0 fpm vertical
  • 5 kt wind
  • 5 kt crosswind component
  • 16,093 m visibility
  • KEWR 210451Z 01010KT 10SM -RA FEW009 SCT021 OVC070 19/18 A2994 RMK AO2 SLP139 P0001 T01940178 402170183 $

Flight context

  • UAL2394
  • UMB Bank NA
  • A319
  • KBOS → KEWR
  • 2026-04-17 15:03 UTC
  • KEWR runway 4R

All events on this flight

Go-around 15:03:11 UTC · KEWR runway 4R · 674 ft AGL · 143 kt GS
Go-around 15:03:11 UTC · KEWR runway 4R · 674 ft AGL · 143 kt GS
Go-around 15:03:11 UTC · KEWR runway 04R · 674 ft AGL · 143 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· KEWR