The Warning That Stayed Quiet

On September 29, 2006, Gol Flight 1907, a Boeing 737-800, collided with an Embraer Legacy 600 business jet over Brazil. All 154 people aboard the Boeing died. The Legacy landed at Cachimbo Air Base; its two crew members and five passengers were uninjured.

Looking back through a US National Transportation Safety Board recommendation issued on May 2, 2007, one particular vulnerability comes into focus. A system designed to warn of approaching aircraft could lose its protective function without reliably drawing the pilots’ attention to that loss.

That document was written while the Brazilian-led investigation was still underway. It is evidence for a specific safety concern, not a final allocation of responsibility for the collision.

Two aircraft, one missing conversation

Both aircraft carried TCAS II, a traffic alert and collision avoidance system capable of directing pilots to climb or descend to avoid a collision. But TCAS does not simply look out into the sky. It interrogates transponders aboard nearby aircraft.

A transponder that is off, or powered but set to standby, does not answer. The NTSB explained that this deprives the affected aircraft of its own TCAS protection and makes it undetectable to another aircraft’s TCAS. Two equipped aircraft are therefore not necessarily two independent layers of protection. Their equipment depends on a working exchange.

According to the board’s preliminary account, the Legacy’s transponder return disappeared from air traffic control radar at about 16:02 and remained absent until shortly after the collision, around 16:57. Flight recorder evidence showed no indication of a TCAS alert aboard either aircraft, no evidence that either crew saw the other aircraft before impact, and no evasive action.

The board said the Legacy’s collision avoidance system had not been functioning, for reasons then still undetermined. Its cockpit voice recording also indicated that the crew did not realize this until after the accident.

The narrow finding matters without requiring a speculative answer to who touched which control. The protective exchange was missing, and the crew apparently did not know it.

A warning must arrive, not merely exist

The NTSB said the only notification the Legacy pilots likely received of lost TCAS functionality was a small, static message in white lettering: “TCAS OFF.” It required no acknowledgment.

There is a consequential distinction between a display containing correct information and a person receiving a warning. The board argued that static text can be overlooked when pilots’ attention is elsewhere. Its preliminary survey found similar failure indications on other transport-category aircraft, widening the concern beyond this cockpit.

The recommendation was correspondingly concrete: require enhanced audible and visual warnings, with pilot acknowledgment, when airborne collision avoidance functionality is lost. That was a recommendation to the Federal Aviation Administration—not proof that a change had already been implemented, or that this change alone would have prevented the accident.

This is where the coherenceist lesson becomes an engineering question rather than an appeal to greater harmony. Does a system give people a practical chance to notice when its protections have stopped working? A safety function and the communication of its failure belong in the same design.

That does not erase individual responsibility or settle the wider inquiry. It refuses to mistake the existence of a message for the completion of a warning.

The people aboard Flight 1907 cannot be restored by a better interface. Their deaths deserve more than a tidy moral about technology. But examining how a crucial silence became possible is one concrete way to direct care toward the people who will depend on those systems next.