Go-around — UAL2219
KEWR · 22L2026-01-18 09:46 UTC· TJSJ → KEWR· WILMINGTON TRUST CO TRUSTEE· B39M
UAL2219 (Wilmington Trust) was operating from TJSJ to KEWR on 2026-01-18. SkyMeter detected a go-around at Newark Liberty International Airport (KEWR) on runway 22L at 09:46 UTC. Trace data at the event: 175 ft AGL, 154 kt GS, 0 fpm vertical. Approach stability score: 79/100. Scores in this band are observed on roughly 25% of approaches at this runway: one or more gates outside the per-runway tightest envelope, but still inside the typical operating range. METAR at the time reported 0 kt wind, 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 22L
- 175 ft AGL at event
- 154 kt ground speed
- 0 fpm vertical
- Approach stability 79/100
- 0 kt wind
- 0 kt crosswind component
- 16,093 m visibility
- SPECI KEWR 241506Z 06015G23KT 10SM FEW024 BKN030 BKN250 17/08 A3042 RMK AO2 PK WND 03027/1455 T01670078 $
Flight context
- UAL2219
- Wilmington Trust
- B39M
- TJSJ → KEWR
- 2026-01-18 09:46 UTC
- KEWR runway 22L
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