LIVE · BRIEFING WIRE
FlightLogic Brief Daily aviation wire
← YouTube
● YT VIDEO ·blancolirio ·June 4, 2026 ·22:47Z

NTSB Prelim United 767 vs Bread Truck Newark NJ

The NTSB preliminary report is just out here at the Blanco Global World Headquarters on the United 767 that hit the bread truck in Newark, New Jersey back on the 3rd of May. My name's Juan Brown. You're watching the Blanco channel. And it looks to me like
Detailed analysis

A United Airlines Boeing 767 on an inbound international flight struck a light pole on approach to runway 29 at Newark Liberty International Airport on May 3rd, with the displaced pole subsequently making contact with a bread truck operating near the runway environment. The NTSB preliminary report reveals that the left main landing gear clipped the pole, severing the tire and cutting a significant gash into the aircraft's fuselage. The crew did not become aware of the structural damage until conducting a post-flight inspection after an otherwise completed landing. No fatalities or serious injuries resulted from the incident, though CCTV footage confirms the margin between a controlled outcome and a catastrophic one was extraordinarily narrow.

The operational picture emerging from the preliminary report centers heavily on crew workload saturation produced by a rapid sequence of runway reassignments during the arrival phase. The crew was originally planned for runway 4R, was switched to 22L during the descent, then assigned runway 29 — the shortest and operationally most demanding runway in the Newark complex — while simultaneously being set up for a potential holding clearance that ultimately was not needed. That cancellation of the expected hold further compressed the available time for crew preparation. The captain reported briefing the approach after each runway change, stating all required items were addressed, but the compounding effect of three distinct reconfigurations in short succession — each requiring full FMS reprogramming, approach plate review, weather and performance reassessment, and crew coordination — represents exactly the kind of incremental workload accumulation that erodes decision quality and situational awareness even among experienced crews. The captain brought meaningful type experience to the flight, having accumulated 2,724 total hours in the 757/767 prior to upgrading, though his time in command in the type stood at 378 hours at the time of the incident.

Runway 29 at Newark presents a specific set of challenges that distinguish it from the airport's primary runways. At roughly 6,800 feet, it is substantially shorter than the nearly 10,000-foot 4R/22L pairing, and the RNAV Whiskey 29 procedure transitions to a visual approach segment from the AXLE fix, requiring hand-flown visual maneuvering from a right base entry. Notably, the PAPI system for runway 29 is positioned on the right side of the runway rather than the conventional left, an atypical configuration that demands deliberate crew awareness. The captain acknowledged planning to fly a slightly below-standard glidepath — targeting three red and one white on the PAPI rather than the standard two-and-two — as a deliberate technique to avoid landing long on a short runway. That technique is a recognized practice among experienced line crews, but the CVR reportedly captured no pre-approach discussion of this PAPI strategy between the captain and first officer prior to the event, a gap that investigators will likely examine in the context of crew coordination and shared mental model verification on a non-standard visual approach.

For working airline and business aviation crews, this incident encapsulates several recurring themes in high-workload arrival management. Late runway changes, particularly those substituting a more demanding runway for the originally planned one, have featured in numerous incidents and accidents. The combination of a late reassignment, compressed time, a non-standard visual segment, and environmental pressure — gusty winds were reported — creates a scenario where even experienced, professional crews can find themselves slightly behind the aircraft. The fact that the captain had prior exposure to the runway 29 approach at Newark and considered it familiar terrain underscores that familiarity itself can function as a subtle hazard, potentially reducing the sense of urgency that drives thorough pre-approach crew coordination. Part 121 operators and their training departments will likely review this event in the context of stabilized approach criteria, go-around decision authority, and the protocols governing how crews should manage and communicate when multiple late changes compound during a single arrival sequence.

The broader significance of this event extends to the ongoing regulatory and industry conversation about airport surface safety, obstacle clearance on tight approaches, and the coordination between airport operations and air traffic control when vehicles are authorized on or near active runways during visual approach conditions. The presence of a commercial vehicle sufficiently close to the runway environment to be struck by a low-flying heavy widebody on short final raises questions that go beyond the flightcrew's performance alone. As the NTSB investigation moves toward a final report, findings are likely to address not only crew workload and approach management but also airport vehicle control procedures and the adequacy of obstacle clearance surfaces on non-precision visual approaches to constrained runways at major metropolitan airports.

Read original article