Unstable approach — UAL1499

KEWR · 29

2026-08-28 18:42 UTC· KAUS KEWR· UNITED AIRLINES INC· B38M

UAL1499 (United Airlines) was operating from KAUS to KEWR on 2026-08-28. SkyMeter detected a low approach-stability score at Newark Liberty International Airport (KEWR) on runway 29 at 18:42 UTC. Trace data at the event: 1127 ft AGL, 165 kt GS. Approach stability score: 42/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 8 kt wind, 1 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)
  • SECURITY6/0708 2026-08-01 00:01Z – 2027-08-01 23:59Z SFC–400 ft

    Goodlettsville, TN, Saturday, August 1, 2026 through Sunday, August 1, 2027 UTC

    View FAA NOTAM →
  • SECURITY6/7271 2026-08-24 12:30Z – 2026-08-29 06:00Z SFC–2,500 ft

    MAYPORT, FL, Monday, August 24, 2026 through Saturday, August 29, 2026 Local

    View FAA NOTAM →
  • HAZARDS6/8103 2026-08-26 12:00Z – 2026-09-09 02:00Z SFC–4,000 ft

    21NM NW BROKEN BOW, OK, Wednesday, August 26, 2026 through Wednesday, September 9, 2026 UTC

    View FAA NOTAM →
  • UAS PUBLIC GATHERING6/7351 2026-08-27 12:00Z – 2026-10-13 03:00Z SFC–400 ft

    Timonium, MD, Thursday, August 27, 2026 through Tuesday, October 13, 2026 UTC

    View FAA NOTAM →
  • SECURITY6/6989 2026-08-27 21:00Z – 2026-09-02 21:00Z SFC–400 ft

    Asheville, NC, Thursday, August 27, 2026 through Wednesday, September 2, 2026 Local

    View FAA NOTAM →
  • VIP6/7592 2026-08-27 21:30Z – 2026-08-28 19:00Z SFC–17,999 ft

    Houston, TX, Thursday, August 27, 2026 through Friday, August 28, 2026 Local

    View FAA NOTAM →
  • VIP6/8307 2026-08-27 21:30Z – 2026-08-28 19:00Z SFC–17,999 ft

    Houston, TX, Thursday, August 27, 2026 through Friday, August 28, 2026 Local

    View FAA NOTAM →
  • VIP6/8531 2026-08-27 21:30Z – 2026-08-28 19:00Z SFC–17,999 ft

    Houston, TX, Thursday, August 27, 2026 through Friday, August 28, 2026 Local

    View FAA NOTAM →
  • AIR SHOWS/SPORTS6/8224 2026-08-28 14:00Z – 2026-08-30 23:00Z SFC–16,000 ft

    Bunker Hill, IN, Friday, August 28, 2026 through Sunday, August 30, 2026 UTC

    View FAA NOTAM →
  • AIR SHOWS/SPORTS6/7028 2026-08-28 18:00Z – 2026-08-30 22:00Z SFC–15,000 ft

    Lake Charles, LA, Friday, August 28, 2026 through Sunday, August 30, 2026 UTC

    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
  • 1127 ft AGL at event
  • 165 kt ground speed
  • 0 fpm vertical
  • Approach stability 42/100
  • 8 kt wind
  • 1 kt crosswind component
  • 16,093 m visibility
  • KEWR 161651Z 22007KT 10SM FEW090 SCT160 25/15 A3033 RMK AO2 SLP271 T02500150

Flight context

  • UAL1499
  • United Airlines
  • B38M
  • KAUS → KEWR
  • 2026-08-28 18:42 UTC
  • KEWR runway 29

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