United Airlines Flight 169: NTSB Finds Below-Glideslope Approach Before Newark Turnpike Light Pole Strike

Updated: June 6, 2026

United Airlines Flight 169, a Boeing 767-424ER carrying 231 people from Venice, Italy, struck a 15-foot light pole on the New Jersey Turnpike during final approach to Runway 29 at Newark Liberty International Airport on May 3, 2026. Debris from the shattered pole impacted a southbound tractor-trailer and injured the driver; the aircraft sustained substantial fuselage damage but landed and taxied to the gate, where all passengers and crew deplaned without injury. Federal investigators are focused on why the aircraft descended well below the published glideslope on a runway without precision instrument approach guidance, where the approach path crosses an active interstate highway with single-digit feet of vertical clearance above the roadway.

Accident Summary

What Happened

The flight originated at Venice Marco Polo Airport as a scheduled Part 121 international passenger service. The captain served as pilot flying on the return leg, with the first officer as pilot monitoring. During descent into Newark, air traffic control changed the assigned landing runway twice — first from Runway 4R to Runway 22L, then from 22L to Runway 29 — and the crew prepared for holding that was ultimately not required. The captain briefed each new approach in sequence, describing the briefings as compressed but complete.

The crew was assigned the RNAV (GPS) W Runway 29 approach. No precision Instrument Landing System is installed on Runway 29 at Newark. The RNAV procedure provides vertical and lateral guidance to a published Visual Guidance Fix at AXELL, after which pilots transition to visual reference for the final segment to the runway. The captain disconnected the autopilot and auto-throttles at approximately 880 feet MSL, near AXELL, and flew the remainder of the approach manually in gusty conditions — wind from 290 degrees at 19 knots gusting to 30, producing what the captain described as moderate turbulence.

The captain stated he planned to fly the final segment at three red and one white on the Precision Approach Path Indicator, a profile deliberately lower than the standard two-red-two-white glidepath. The PAPIs for Runway 29 are installed on the right side of the runway rather than the standard left-side configuration. The cockpit voice recorder captured no discussion of PAPI light settings for Runway 29 prior to landing.

At the automated 500-foot callout, the captain responded with “stable,” and the first officer reported they were on speed and on profile. Below 500 feet, the airspeed began to decay. The first officer called out that the captain was slow, then moments later stated he was still slow and a little low. The first officer looked outside, recognized the aircraft appeared low, but could not process the information and verbalize a go-around callout before the aircraft was about to touch down.

Flight data recorder information shows the aircraft crossed the New Jersey Turnpike at approximately 19 feet above the roadway at 1350:04 EDT. One second later, altitude had dropped to 18 feet above ground level. By 1350:07, the aircraft was at 6 feet AGL at the position of the 15-foot light pole. The turnpike surface sits approximately 5 feet higher than the runway elevation. Touchdown occurred at 1350:12. That eight-second window — from 19 feet over the highway to wheels on the runway — defines the vertical margin that existed between this aircraft and the interstate traffic beneath it.

The captain reported hearing a thump just before touchdown. The first officer felt a mild jolt near the threshold. The relief officer, stationed in the flight deck for the international duty period, described an audible thump as the aircraft crossed the airport boundary one to two seconds before landing. After the flight parked at the gate, the purser called the flight deck to report that aft cabin crew members had heard a loud bang just prior to touchdown. The captain inspected the aircraft externally and discovered damage along the aft fuselage.

On-site examination revealed three punctures to the left lower aft fuselage, spanning fuselage stations 1219 to 1373 between stringers 27L and 31L. The largest puncture measured approximately 46 inches long and 4 inches wide. The total size of the perforations exceeded the dimensions of the outflow valve, and the damage affected all three elements of the fuselage structure — skin, stringer, and frame — meeting the regulatory threshold for substantial damage. The number-one tire on the left main landing gear exhibited slash marks. The tractor-trailer sustained windshield impact damage and punctures to its aluminum siding, and the driver was treated for minor injuries.

Aircraft and Operational Context

The Boeing 767-424ER is a wide-body, twin-engine transport category aircraft operated by United Airlines on long-haul international routes. The accident aircraft, registered N77066, was operating under Part 121 on the return leg of a transatlantic rotation.

The flight crew had been reassigned shortly before departure from their original schedule — a Boeing 757-200 rotation to Shannon, Ireland — to a Boeing 767-400 rotation to Venice. Both types share a common type rating, but the late reassignment changed the planned aircraft, route, and flight duration. The captain had logged 2,724 hours in the 757/767 type, with 378 of those hours as captain. The first officer had 1,958 hours in type. The relief officer had 853 hours in type. All figures reflect time accrued at United Airlines only and do not include prior flight experience.

Runway 29 at Newark presents a distinct operational environment. It lacks an Instrument Landing System, relying instead on an RNAV approach with a visual transition segment after the fix at AXELL. The PAPIs are installed on the right side of the runway — opposite from the standard left-side placement. The approach path crosses the New Jersey Turnpike less than 400 feet from the runway threshold, with the turnpike surface sitting approximately 5 feet above runway elevation. That geometry means the vertical margin between an aircraft on the visual segment and vehicles on the highway below is determined entirely by how precisely the crew tracks the visual glidepath.

Accident Investigation

The National Transportation Safety Board is leading the investigation with participation from the FAA, United Airlines, the Air Line Pilots Association, and Boeing. An operations group was formed and the flight crew interviewed. The flight data recorder and cockpit voice recorder were shipped to NTSB headquarters and downloaded successfully. A vehicle performance specialist has reviewed data from the FDR, CVR, ADS-B, radar, and security video. The ground proximity warning computer was also recovered and will be downloaded at the manufacturer. A detailed overview of how this investigative process typically unfolds is available in the NTSB investigation process.

The central investigative thread is the aircraft’s vertical profile during the final approach segment. FDR data plotted against the published 3-degree glideslope shows the aircraft consistently below the altitude that would produce a standard two-red-two-white PAPI indication, and at points below the threshold that would display four red lights — the most extreme low-path warning the system provides. The captain’s stated intent to fly three red and one white placed the planned profile below the standard glidepath before any wind-induced deviations compounded the situation.

Investigators will also evaluate the first officer’s monitoring performance and the crew resource management dynamics in the final seconds of the approach. The first officer identified both the airspeed decay and the low altitude verbally, but did not initiate or complete a go-around callout. The point at which the pilot monitoring recognized the developing situation, the cockpit workload at that moment, and the time available to intervene before the aircraft crossed the turnpike will each be reconstructed from recorder data.

Operational and Regulatory Issues

This accident places direct scrutiny on the approach environment at a runway where the margin for vertical error is physically constrained by a major highway. Runway 29 at Newark does not offer ILS precision guidance. After the RNAV procedure’s Visual Guidance Fix, pilots fly visually — and the visual reference they rely on is a PAPI array installed on the opposite side of the runway from the standard configuration. That layering of non-standard elements does not by itself cause accidents, but it narrows the tolerance for technique variation and increases the consequences when deviations occur.

United Airlines took immediate safety actions following the event. Flight Operations issued an Ops Alert specific to RNAV vertical guidance for Runway 29, reminding pilots that the visual glideslope indicator provides safe obstruction clearance only within 10 degrees of the runway centerline up to 4 nautical miles. The airline’s Safety Management System identified a broader hazard: the pilot technique of shifting the aimpoint below the electronic or visual glide path indication — referred to internally as “ducking under” — as a contributor to low approach altitudes on certain runways. Pilot Bulletin 26-069 revision 1 reinforced that all approaches must result in touchdown between 1,000 and 1,500 feet from the runway threshold, in accordance with the airline’s flight manual. That the airline itself identified this technique as a systemic hazard through its own SMS process is not a minor disclosure.

The broader regulatory focus extends beyond this single crew. If the approach geometry at Runway 29 produces routine operations with single-digit feet of clearance above an active highway, the system’s tolerance for any below-glideslope deviation — from technique, wind, turbulence, or workload — is functionally zero. Attention may turn to whether the current approach design, obstruction clearance criteria, and visual guidance configuration remain adequate given the physical environment surrounding Runway 29.

Aviation Accident Litigation

The presence of a third-party ground injury distinguishes this event from approach incidents that remain contained within the airport perimeter. The truck driver struck by light pole debris sustained injuries on a public highway during the normal course of travel, creating a liability framework that extends beyond airline-passenger relationships into ground-party claims involving the carrier, the airport operator, and potentially the entities responsible for approach design and obstruction clearance certification. Experienced aviation accident attorneys recognize that ground-party injury cases often involve multiple defendants and overlapping regulatory frameworks.

Liability analysis will turn on several factual determinations the NTSB investigation is positioned to resolve: whether the crew’s vertical profile complied with published approach procedures and operator standards, whether the runway environment met all applicable FAA design and obstruction clearance criteria, and whether the airline’s operational control — including the late crew and aircraft reassignment — contributed to the conditions present on this approach.

The substantial damage classification carries independent significance. Three fuselage punctures affecting all structural elements of the pressure vessel, combined with a wide-body aircraft removed from service for structural repair, produces material financial exposure apart from personal injury claims.

Consultation Regarding Aviation Accident Investigations

Families, referring attorneys, and journalists sometimes seek legal consultation or technical insight regarding aviation accidents and investigative issues discussed in these analyses. Inquiries may be directed to Katzman, Lampert & Stoll at the link below.

Contact the Firm

PENNSYLVANIA OFFICE
Katzman Lampert & Stoll
121 N. Wayne Ave. # 205
Wayne, PA 19087

E-mail: Click to use our Contact Form
Toll-Free: (866) 309-6097
Phone: (610) 686-9686
Fax: (610) 686-9687

Copyright 1998-2026 The Law Firm of Katzman Lampert & Stoll | Privacy Notice | Disclaimer | Site by: Lucidpage