You are still slow and a little low
On a May afternoon over New Jersey, a commercial airliner descended too low and too slowly toward Newark Liberty, clipping a light pole with its wing and scattering debris onto the highway below. The plane landed safely, but the National Transportation Safety Board's early findings surface a quieter concern: the warnings were there, spoken aloud in the cockpit, and the approach continued anyway. It is a story not of catastrophe but of the narrow margin between procedure and consequence — and of what happens when human judgment diverges from the instruments and the voices meant to safeguard it.
- With the plane descending through 500 feet, the first officer warned the captain twice — 'you are slow' and 'you are still slow and a little low' — yet the approach was not abandoned.
- The left wing struck a light pole near the New Jersey Turnpike, tearing a gash nearly four feet long into the fuselage and sending debris crashing into a passing tractor-trailer below.
- Crew members experienced the impact differently — a thump, a jolt, a loud bang — each account a fragment of a moment that could have ended far worse.
- The NTSB has classified the structural damage as substantial and is now probing why the captain pressed forward despite explicit crew warnings and three runway reassignments during final descent.
- The central question hanging over the investigation is whether a go-around — the standard response to an unstable approach — was ever seriously considered, and if not, why.
On the afternoon of May 3rd, United Airlines flight 169 was descending toward Newark Liberty International Airport when its left wing struck a light pole near the New Jersey Turnpike. The impact tore a gash nearly four feet long into the plane's lower fuselage and sent debris onto the roadway below, where it struck a passing tractor-trailer. The aircraft landed safely minutes later.
What the NTSB's preliminary report makes plain is that the danger had been named before it arrived. As the plane passed through 500 feet — roughly the height of a 50-story building — the first officer called out twice: first that the captain was slow, then that he was still slow and a little low. The captain acknowledged sensing they were low but believed the runway was close enough to continue. The runway assignment had been changed three times during the approach, though the captain said this did not concern him, and he reported no windshear alerts.
The crew felt and heard the impact in different ways — a thump for the captain, a mild jolt for the first officer, a loud bang for flight attendants in the rear. Once parked at the gate, investigators found three punctures in the lower left aft fuselage, one measuring nearly four feet long and four inches wide.
The investigation now centers on why the captain continued despite his first officer's explicit warnings rather than executing a go-around — the standard response when an approach becomes unstable. Whether fatigue, workload, or the pressure of repeated runway changes played a role remains an open question, one the NTSB's full inquiry will be tasked with answering.
On the afternoon of May 3rd, United Airlines flight 169 was descending toward Newark Liberty International Airport when its left wing struck a light pole standing near the New Jersey Turnpike. The impact tore a gash nearly four feet long into the plane's lower fuselage and sent debris spinning onto the roadway below, where it smashed into a passing tractor-trailer. The aircraft landed safely minutes later, but the National Transportation Safety Board's preliminary investigation reveals a troubling sequence: the first officer had warned the captain twice about dangerously slow airspeed and low altitude in the final moments before impact.
The flight was making its approach to runway 29 at 1:50 p.m. when the strike occurred. What makes the incident particularly striking is that the crew's own instruments and voices had flagged the problem. As the plane descended through 500 feet—roughly the height of a 50-story building—the first officer called out to the captain: "Hey you are slow" and then, moments later, "You are still slow and a little low." The captain acknowledged seeing the problem himself, telling investigators he thought "we were low," but believed they were close enough to the runway that landing was imminent.
The runway assignment had been changed three times during the approach, a detail the captain said did not concern him. He reported receiving no windshear alerts and felt the aircraft was in a safe position to land. Yet the first officer's repeated warnings suggest the plane was descending too steeply and moving too slowly through the air—a dangerous combination that left little margin for error. When the wing clipped the pole, crew members felt and heard the impact in different ways: the captain described hearing a thump, the first officer felt a mild jolt, another crew member heard a thump a second or two before touchdown, and flight attendants in the rear reported a loud bang.
Once the plane was parked at the gate in Newark, the damage became visible. Investigators found three punctures in the lower left aft fuselage, with one gash measuring nearly four feet long and four inches wide. The NTSB classified the structural damage as substantial. The light pole debris that fell onto the New Jersey Turnpike struck the tractor-trailer, though initial reports had mistakenly suggested the plane's landing gear had made contact with the truck.
The investigation now turns to why the captain continued the approach despite the first officer's explicit warnings about airspeed and altitude. The runway changes, the lack of windshear alerts, and the captain's own perception that they were low but close to landing all factor into the picture. What remains unclear is whether fatigue, workload, or other pressures influenced the decision to press forward rather than execute a go-around—a standard procedure when an approach becomes unstable. The NTSB's full investigation will likely examine these questions in detail.
Citas Notables
The first officer told the captain 'Hey you are slow' and 'You are still slow and a little low' as the plane descended through 500 feet— NTSB preliminary report, citing first officer's account
The captain said he thought they were low but believed they were just about to land— Captain's statement to NTSB investigators
La Conversación del Hearth Otra perspectiva de la historia
Why does it matter that the first officer warned the captain twice? Couldn't the captain have simply been managing a normal descent?
Because at 500 feet, you're out of time. If something goes wrong that low, you can't recover. The first officer wasn't making a casual observation—he was flagging a condition that violated basic approach standards. The fact that he said it twice suggests he was escalating.
The captain said he thought they were low but believed they were about to land anyway. Isn't that a reasonable judgment call?
Not really. In aviation, there's a concept called "stabilized approach." If you're slow and low at 500 feet, you're unstable. The procedure is to go around and try again. Continuing down is gambling that nothing else will go wrong.
What about the runway changes? Could that have distracted the crew?
It's possible. Three changes is unusual and creates cognitive load. But the captain said it didn't concern him, so we don't know if it was a factor. What we do know is that the first officer was paying attention to the actual flight parameters—airspeed and altitude—and raising the alarm.
The plane landed safely. Does that change how we should view what happened?
It changes nothing about the risk that was taken. The plane landed safely because the strike wasn't catastrophic. But a light pole is a fixed object. Next time it could be terrain, or another aircraft. The investigation is really asking: why did the crew accept this level of risk when they had a safe alternative?
What happens now?
The NTSB will dig into the captain's training, experience, workload that day, and decision-making process. They'll look at whether there were systemic factors—fatigue rules, crew resource management training, pressure from scheduling. The goal is to figure out what needs to change so this doesn't happen again.