Unstable approach — UAL2650
KEWR · 292026-08-18 23:21 UTC· KBZN → KEWR· UNITED AIRLINES INC· B38M
UAL2650 (United Airlines) was operating from KBZN to KEWR on 2026-08-18. SkyMeter detected a low approach-stability score at Newark Liberty International Airport (KEWR) on runway 29 at 23:21 UTC. Trace data at the event: 1113 ft AGL, 154 kt GS. Approach stability score: 39/100. Scores below 50 occur on under 10% of approaches at this runway and indicate the v2 scorer flagged the approach as highly anomalous (three or more gates exceeded the runway's P90 envelope simultaneously). METAR at the time reported 9 kt wind, 4 kt crosswind component, 16,093 m visibility. The approach-stability score rates the final approach against stabilized-approach gates (glideslope, lateral deviation, descent rate, and IAS) at defined altitudes. A low score means one or more of those were outside the normal envelope for how the approach was flown. The score is graded by guidance type, so instrument approaches (ILS or an aligned straight-in) are held to the full gate set, while visual and pattern arrivals are surfaced only when the score is clearly low. The score is advisory and observational, a deviation measure, not an assertion of an accident. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- HAZARDS6/1471 2026-08-04 14:00Z – 2026-08-19 04:00Z SFC–9,500 ft
33NM SW BROADUS, MT, Tuesday, August 4, 2026 through Wednesday, August 19, 2026 UTC
View FAA NOTAM → - HAZARDS6/2488 2026-08-06 14:00Z – 2026-08-20 05:00Z SFC–13,500 ft
28NM W AFTON, WY, Thursday, August 6, 2026 through Thursday, August 20, 2026 UTC
View FAA NOTAM → - HAZARDS6/2761 2026-08-07 14:00Z – 2026-08-22 03:30Z SFC–12,000 ft
10NM SE LIVINGSTON, MT, Friday, August 7, 2026 through Saturday, August 22, 2026 UTC
View FAA NOTAM → - HAZARDS6/2829 2026-08-07 14:00Z – 2026-08-22 03:30Z SFC–12,000 ft
10NM SE LIVINGSTON, MT, Friday, August 7, 2026 through Saturday, August 22, 2026 UTC
View FAA NOTAM → - HAZARDS6/2917 2026-08-08 14:00Z – 2026-08-22 05:00Z SFC–13,500 ft
20NM E AFTON, WY, Saturday, August 8, 2026 through Saturday, August 22, 2026 UTC
View FAA NOTAM → - HAZARDS6/3161 2026-08-10 12:00Z – 2026-08-25 03:30Z SFC–16,000 ft
13NM SE LANDER, WY, Monday, August 10, 2026 through Tuesday, August 25, 2026 UTC
View FAA NOTAM → - HAZARDS6/4089 2026-08-12 12:00Z – 2026-08-27 03:30Z SFC–15,000 ft
2NM SE LANDER, WY, Wednesday, August 12, 2026 through Thursday, August 27, 2026 UTC
View FAA NOTAM → - UAS PUBLIC GATHERING6/2574 2026-08-13 12:00Z – 2026-08-24 05:00Z SFC–400 ft
des moines, IA, Thursday, August 13, 2026 through Monday, August 24, 2026 UTC
View FAA NOTAM → - HAZARDS6/4893 2026-08-13 13:00Z – 2026-08-28 03:00Z SFC–9,000 ft
43NM E HOT SPRINGS, SD, Thursday, August 13, 2026 through Friday, August 28, 2026 UTC
View FAA NOTAM → - SECURITY6/5108 2026-08-18 16:30Z – 2026-08-20 16:00Z SFC–17,999 ft
Des Moines, IA, Tuesday, August 18, 2026 through Thursday, August 20, 2026 Local
View FAA NOTAM → - SECURITY6/5077 2026-08-18 20:00Z – 2026-08-19 01:00Z SFC–1,000 ft
Williamsport, PA, Tuesday, August 18, 2026 through Tuesday, August 18, 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 29
- 1113 ft AGL at event
- 154 kt ground speed
- 0 fpm vertical
- Approach stability 39/100
- 9 kt wind
- 4 kt crosswind component
- 16,093 m visibility
- KEWR 162151Z 08006KT 10SM FEW085 BKN170 BKN250 25/18 A3028 RMK AO2 SLP252 T02500183
Flight context
- UAL2650
- United Airlines
- B38M
- KBZN → KEWR
- 2026-08-18 23:21 UTC
- KEWR runway 29
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