United Boeing 767 Strikes Truck & Pole on Final Newark Approach

A United Airlines Boeing 767-400ER operating as Flight UA169 struck a light pole and a commercial truck on the New Jersey Turnpike during its final approach to Newark Liberty International Airport (EWR) on May 3, 2026. The aircraft, arriving from Venice Marco Polo Airport (VCE), landed safely on Runway 29 moments after the collision. All 221 passengers and 10 crew members aboard were uninjured.

The incident has triggered parallel investigations by the National Transportation Safety Board (NTSB) and the Federal Aviation Administration (FAA) to determine the cause of the unusually low approach. The NTSB, citing its authority under 49 CFR Part 831, has taken the lead in the accident investigation and directed United to preserve the cockpit voice and flight data recorders for analysis. The FAA is conducting a separate review of flight safety procedures related to the event.

Incident Details and Immediate Response

According to preliminary information from the New Jersey State Police, the collision occurred at approximately 1:50 PM local time. The aircraft’s landing gear or a low-hanging portion of the fuselage made contact with an H&S Bakery truck and a highway light pole adjacent to the airport boundary. The driver of the truck sustained minor injuries. Despite the impact, the flight crew continued the approach and executed a safe landing.

The approach was to Runway 29, which at 6,725 feet is the shortest runway at EWR. Its proximity to the New Jersey Turnpike and its relatively short length present unique challenges for pilots, particularly those operating widebody aircraft. Former NTSB Chair Robert Sumwalt characterized the landing as a "difficult approach," noting that the required circling maneuver can incentivize pilots to fly lower to ensure they do not land long on the constrained runway surface.

For United Airlines, the immediate impact involves the removal of the flight crew from duty pending the outcome of the safety review, a standard procedure. The Port Authority of New York and New Jersey, which operates EWR, faces increased pressure to evaluate approach procedures and safety buffers for Runway 29. The incident also caused a minor disruption for H&S Bakery, which lost a vehicle in the collision.

Regulatory Scrutiny and Historical Context

The investigation will focus on why the Boeing 767-400ER (Extended Range) descended below a safe altitude over public infrastructure. This event draws comparisons to previous landing incidents where aircraft struck objects short of the runway.

In July 2013, Asiana Airlines Flight 214 struck a seawall during a visual approach to San Francisco International Airport. The NTSB ultimately cited pilot error and an over-reliance on automation, leading to significant changes in pilot training protocols. Similarly, the United 169 incident raises questions about crew procedures during a visual approach phase of flight.

Another relevant precedent is Southwest Airlines Flight 1248 in December 2005, which overran a runway at Chicago Midway and struck a vehicle on an adjacent road, resulting in a fatality in the car. That accident spurred the mandatory installation of runway safety areas (EMAS) at many U.S. airports and underscored the risks of airport operations near public roadways.

Technical Analysis

This incident highlights the operational pressures at capacity-constrained airports like Newark, where shorter runways remain in active use for large aircraft. The investigation's findings could have broad implications for approach path design and air traffic control vectoring, particularly for aging widebody fleets. The involved aircraft is part of United's fleet of 16 Boeing 767-400ERs, which have an average age of over 23 years. United has already announced plans to replace its 767s with more modern Boeing 787 Dreamliners by 2030.

The NTSB's analysis will almost certainly scrutinize the decision to assign a heavy, widebody aircraft to the airport's shortest runway, especially if weather or wind conditions were factors. The data from the flight recorders will be critical in reconstructing the flight path and understanding the crew's actions and the aircraft's performance in the final moments of the approach. This event follows a pattern where near-misses or minor accidents expose latent risks in established procedures, often leading to system-wide safety enhancements.

What Comes Next

The NTSB is expected to release its preliminary report on the incident within 30 days, likely by early June 2026. This initial report will outline the basic facts gathered but will not state a probable cause.

A comprehensive final accident report, which will include a probable cause and any formal safety recommendations, is expected to take between 12 and 24 months to complete. The final report is anticipated between May 2027 and May 2028. In the interim, the FAA may issue safety alerts or procedural changes if its investigation uncovers immediate risks.

Why This Matters

This event serves as a critical reminder of the thin safety margins in commercial aviation, especially at airports embedded within dense urban environments. The outcome of the federal investigation will likely influence approach procedures, air traffic control protocols, and pilot training for challenging runways, with potential impacts on operations at similar airports across the United States. For airlines, it reinforces the need for rigorous training and crew resource management during all phases of flight, particularly complex visual approaches.