The warning came first. Before the light pole, before the impact report, before the NTSB — there was a voice in the right seat telling the captain the Boeing 767 was low and slow on approach to Newark.
The airplane kept descending.
This is not a story about a crew that didn't communicate. It's a story about what happens in the seconds between a warning being spoken and a correction being flown — and how much ground a 767 covers inside that gap.
At Vref, a 767 on final approach is moving at roughly 145 knots. That translates to approximately 245 feet per second. Not per minute. Per second. The moment the copilot issued that callout, the aircraft was already a quarter-mile closer to the New Jersey Turnpike than when the thought to speak first formed.
CRM protocol is a three-step sequence under time pressure. The callout must be made. It must be acknowledged. Then corrective action follows. Each step is necessary. Each step costs time. At low altitude with degraded energy state, that sequence — designed to prevent miscommunication — creates a structural lag between recognition and recovery.
The crew wasn't skipping steps. They were following the protocol exactly as trained. And the protocol, functioning correctly, still couldn't compress physics.
When the NTSB flags "crew communication" as a central issue, it isn't assigning blame to a conversation. It's identifying a design tension baked into how cockpits work: the same structure that prevents impulsive, uncoordinated inputs also slows the response to urgent, time-critical ones.
The protocol worked. The margin didn't.