Nineteen feet. That's about the height of a two-story house, or a giraffe if it stretches its neck. It's also exactly how close a United Airlines Boeing 767 came to the asphalt of the New Jersey Turnpike while still flying at over 160 miles per hour.
When United Flight 169 cleared the highway on its way into Newark Liberty International Airport, it didn't just give drivers a scare. It clipped a highway light pole, sending metal debris smashing through the windshield of a passing tractor-trailer. The National Transportation Safety Board just dropped its preliminary report on the May 3 accident, and the details reveal a chilling breakdown in the cockpit during the final moments of an international flight.
The most alarming part? The co-pilot saw the danger building. He warned the captain. But in the high-stakes environment of a last-second landing, realizing you're too low doesn't mean you have time to fix it.
The Runway Shuffle That Set the Trap
Flying into Newark is rarely a walk in the park, but this particular approach turned into a shell game. The flight crew, fresh off a long haul from Venice, Italy, originally planned to land on Runway 4R. Then air traffic control changed it. Then they changed it again. By the time the plane was on final approach, they were clearing the jet for Runway 29.
The captain later told investigators the sudden runway swaps didn't bother him. But shifting planes between runways forces pilots to quickly recalculate headings, glide paths, and visual cues while dropping out of the sky.
The captain turned off the autopilot to fly the visual approach manually. That's when things started sliding sideways. He later admitted to the NTSB that he "got fast" while maneuvering through gusty headwinds. To compensate, he pulled back on the power.
He pulled back too much.
Slow and A Little Low
As the heavy Boeing 767 dropped below 500 feet, the airspeed started to decay. The plane was losing the energy it needed to stay flying properly.
In a two-pilot cockpit, the pilot monitoring the instruments is your safety net. The first officer realized the jet was dragging. According to the NTSB report, the first officer called out, "Hey, you are slow."
The captain heard the warning but didn't push the throttles forward enough. He thought the plane was in a safe position. Seconds later, the situation grew worse. The co-pilot looked out the window, looked back at his screens, and issued a sharper warning: "You are still slow and a little low."
At that exact moment, the captain finally realized they were in trouble. He looked out and thought, We are low. But it was too late. The plane was already crossing the airport perimeter, hovering just 19 feet above the busy lanes of the New Jersey Turnpike. The crew heard a dull thump. The first officer felt a mild jolt.
Cleared the Highway, Clipped the Pole
Initial reports from the scene suggested the plane's massive landing gear actually struck the roof of a Bakery Express delivery truck. The NTSB report corrects that rumor. Investigators found absolutely no tire marks or impact dents on the tractor or the trailer.
Instead, the plane's fuselage and landing gear sliced directly through a metal highway light pole. The impact shattered the pole, sending heavy metal fragments raining down onto the highway below.
The debris smashed into the truck's windshield, leaving the driver with cuts from the shattered glass. The falling pole also crushed a nearby Jeep.
Inside the cockpit, the pilots knew they hit something, but the plane remained controllable. The captain brought the jet down on Runway 29, taxied to the gate, and shut down the engines. None of the 220 passengers or 11 crew members were hurt. But a post-flight inspection revealed severe structural damage: three distinct punctures ripped into the Boeing's belly and deep slashes cut across one of the main landing gear tires.
The Fatal Flaw in Visual Approaches
This accident highlights a dangerous phenomenon in aviation known as a stabilized approach violation. When a plane gets too low and too slow close to the ground, the standard procedure is simple: abort the landing, push the throttles to full power, climb away, and try again. This is called a go-around.
So why didn't they go around?
The captain explained that by the time he processed the co-pilot's warnings and looked outside to confirm the low altitude, they were literally fractions of a second from touchdown. The human brain requires time to recognize a threat, decide on an action, and physically move the controls. When you're flying at 160 miles per hour at the height of a billboard, you don't have those seconds.
Following the incident, United Airlines issued a blunt reminder to its pilot network. The airline instructed all crews landing at Newark to strictly utilize the visual glideslope indicators next to the runway. These light systems, known as PAPI or VASI, give pilots immediate color-coded feedback if they drop below a safe angle. If you see too many red lights, you're too low.
The NTSB investigation is still active. Over the coming months, investigators will analyze data from the cockpit voice recorder, the flight data recorder, and the plane's ground proximity warning computer to find out why the crew let the airspeed drop so drastically before the highway crossing.
If you are a frequent flyer, don't let this spook you out of booking flights. Visual approach incidents are rare, and modern safety systems usually catch these errors long before a plane clips a pole. But next time your flight executes a sudden, loud climb right before landing, don't complain about the delay. Your pilots just noticed they were a little low, and they actually did something about it.
