767 Clips the Turnpike at Newark
On May 3, 2026, United Airlines Flight 169, a Boeing 767-400ER arriving from Venice, Italy, was on short final to Runway 29 at Newark Liberty International Airport when its landing gear and underside struck a light pole and then a bakery delivery truck on the New Jersey Turnpike. The aircraft landed safely with 231 souls on board unharmed; the truck driver sustained only minor injuries. Dashcam video and airport security footage captured the moment, and the NTSB has opened an investigation. As a retired airline captain who has flown the Stadium Visual approach to Runway 29 many times in the Boeing 727 and twice in the much larger MD-11, I watched the reports with a mixture of professional curiosity and familiarity.
Runway 29 at EWR is the airport's shortest runway at just 6,725 feet. It is used primarily when winds favor an east-west operation, as they did that afternoon with gusts reported up to 35 mph. The Stadium Visual is the published procedure for this runway. After crossing the Teterboro VOR at 3,000 feet, you proceed to GIMEE at or above 2,500 feet, then turn left on a 190° heading along the east side of the Hackensack River. You cross HILOK between 2,000 and 1,500 feet, continue to SLIMR, and then make the final right turn onto the extended centerline for Runway 29. The last few miles take you low over Newark Bay and directly across the New Jersey Turnpike.
On a stabilized 3° visual approach with a standard 50-foot threshold crossing height, the aircraft should be approximately 100–120 feet above ground level when crossing the western lanes of the Turnpike — roughly 700–800 feet prior to the threshold. Regardless of which published approach the crew was flying — the Stadium Visual or the RNAV (GPS) W — the importance of rigorously cross-checking crossing altitudes cannot be overstated, especially at the final two fixes. On the Stadium Visual, COPKO is at 700 feet, and CHUMR is at 500 feet. On the RNAV (GPS) W, they are AXEL and NOWAY, which serve as additional visual guidance fixes with recommended crossing altitudes. These points are mandatory cross-checks that every crew must verify against the aircraft's altimeter and the PAPI.
Before going further, it is worth acknowledging what this crew was dealing with. The final right turn onto Runway 29 centerline is made close-in, in gusty crosswind conditions that day — gusts to 35 mph — demanding precise roll-out timing and immediate re-stabilization. In a wide-body aircraft like the 767, the captain in the left seat faces a genuine visibility challenge during that right turn: the runway is off to the right, the nose is swinging through the turn, and the geometry of a large cockpit means the runway environment may not be fully in view until the aircraft is nearly wings-level. That is precisely the moment when the first officer's callouts, cross-checks, and situational awareness are not merely helpful — they are operationally essential. A gusty wind environment compounds everything: power corrections, attitude adjustments, and altitude deviations can stack up quickly in the final mile. None of this is an excuse, but it is context, and it deserves honest acknowledgment.
That said, a deviation below the published altitude gates at COPKO or CHUMR is a clear indication that the approach has become unstable and must trigger an immediate correction or a go-around. There is no acceptable alternative. These fixes exist precisely because the terrain and obstacle environment below the glidepath on this approach — the Turnpike among them — is unforgiving. The PAPI is there for a reason. The published gates are there for a reason. The stabilized approach criteria that every airline crew briefs before departure are there for a reason. None of them are bureaucratic formality.
I have flown this exact approach in aircraft larger and heavier than the 767 involved. In the 727, with its relatively short wingspan and responsive handling, the maneuver felt manageable once you were familiar with the landmarks. The MD-11, with its long body and higher cockpit, demanded even more precise speed and altitude control because any deviation became magnified in the last mile. In both types, the key was the same: stay on the proper glidepath, keep the aircraft stabilized at approach speed with configuration complete, and rigorously cross-check the published fixes. Landing long on a short runway is a real concern, but being dangerously low on short final is never an acceptable trade-off — regardless of what pressures, workload, or visual illusions contributed to getting there.
The weather on May 3 was reported as good VMC with daylight conditions. There was no fog, no low visibility, no ceiling pressing the crew down. That the crew was able to continue to a safe landing after the contact speaks to the inherent robustness of the Boeing 767 and to their composure in a moment that could easily have gone much worse. Runway 29's proximity to the Turnpike has long been a known characteristic of operations at Newark; it is not new, nor is it inherently unsafe when flown as designed. The NTSB will sort out the precise sequence of events, and this analysis should not presume to render a verdict on what the crew did or did not do. That is the Board's job.
Every approach to a major airport carries risk, but the Stadiums discipline, crew coordination, and situationally in gusty conditions, when Visual to 29 is one that rewards awareness — especially the workload spikes at exactly the wrong moment. As the NTSB gathers data from the flight recorders and interviews the crew, the rest of us who fly these procedures are reminded once again that visual approaches are not "relaxed" approaches. They demand the same precision we apply to any instrument procedure, and in gusty conditions on a short runway over a busy highway, the crew must function as a single integrated unit — captain and first officer cross-checking, calling deviations, and making the call to go around without hesitation if the gates are not met.
Safe flying is never the result of luck. It is the product of rigorous adherence to stabilized approach criteria, effective crew resource management, and honest situational awareness — especially when conditions conspire to make a familiar procedure unexpectedly demanding. The United 169 incident is a reminder that those standards exist for good reason, even on a clear afternoon at one of the world's busiest airports.
