There is No Fuel Gauge on Failing Culture

On the evening of December 28, 1978, United Airlines Flight 173 was on approach to Portland, Oregon. A routine flight. An experienced crew. Then a warning light flickered on the instrument panel, a possible malfunction with the landing gear indicator.

The captain circled the airport to troubleshoot. Standard procedure. He was methodical, focused, in control.

Forty-five minutes later, the plane ran out of fuel and crashed into a suburban neighborhood, killing 10 people.

Here is what the investigation revealed: the fuel gauges had been visible the entire time. The first officer noticed. The flight engineer noticed. They said something, carefully, obliquely, with the hedged language of people who understood the hierarchy they were operating in.

The captain acknowledged their hints, then he kept troubleshooting.

Nobody in that cockpit lacked skill. Nobody lacked information. What failed was something harder to measure and easier to ignore: the ability of the team to function as a unit when it mattered most.

The Black Box Tells a Different Story

For decades, aviation investigated accidents by asking what went wrong technically. Faulty equipment. Pilot error. Weather. These were legible problems with legible solutions.

Then flight data recorders and cockpit voice recorders became standard. Investigators heard something unexpected.

Many accidents didn't result from technical failure or lack of pilot skill. They were caused by the inability of crews to respond appropriately to the situation they found themselves in. Communication breakdowns. Deference to authority over evidence. A silence that everyone in the cockpit could hear except the person who needed to.

Flight 173 wasn't an outlier. It was a pattern.

The aviation industry had spent decades making planes safer. Better engines. Better instruments. Better redundancies. The technology had evolved dramatically. The culture in the cockpit, the unspoken rules about who speaks, who decides, who is allowed to be right, had barely changed at all.

The "captain is king" mentality had worked well enough when cockpits were simpler. Modern commercial aviation had become extraordinarily complex, high-stakes, time-pressured, with interlocking systems that no single person could fully monitor alone. The old hierarchy wasn't just inefficient in that environment. It was lethal.

The Answer Wasn't Training. It Was Culture.

The industry's response to Flight 173, and to a cluster of similar accidents in the same era, became known as Crew Resource Management. CRM.

The name undersells it. This wasn't a new checklist or a communications workshop. It was a fundamental restructuring of how authority, information and voice were supposed to work in a cockpit.

CRM held that safety depended not just on what each crew member knew, but on how they functioned together. It trained captains to invite challenge. It trained first officers to speak with clarity and force, not just hint. It embedded the idea that situational awareness was a collective responsibility, that the team, not the individual, was the unit of performance.

The results, measured over decades, are striking. Commercial aviation has become one of the safest operating environments humans have ever created. Not because the planes got smarter, though they did. Because the teams got better.

Now Look at Your Leadership Team

I have sat in enough executive meetings, war rooms and offsites to tell you with confidence: the cockpit dynamic is alive and well in most organizations.

The names are different. The stakes feel lower because they rarely resolve in a single catastrophic moment. The pattern, however, is the same.

Consider the project everyone on the team knows is failing. The timelines have slipped, the original assumptions no longer hold, the early results are quietly alarming. Everyone knows. Somehow, nobody has told the person who needs to hear it most. Status reports stay green. Meetings stay constructive. The problem compounds in plain sight while the team performs confidence for each other and for leadership.

Or consider the silo wars that consume so many organizations. Teams withholding information from each other because sharing it might weaken their position. Decisions that never get made because making them would require someone to lose, and nobody has the authority or appetite to force the issue. Politics filling the vacuum where clarity should be. Meanwhile the customer isn't served, the opportunity closes, and everyone privately blames everyone else.

In both cases, the people involved are often talented, experienced and genuinely committed to the organization's success. What is missing is not capability. It is the system, the norms and the safety that would allow the truth to travel upward and sideways before the damage becomes irreversible.

Think about the capable teams you have watched underperform. How often was the failure really about individual skill? How often was it about the team's inability to tell each other the truth, hold collective awareness of what was actually happening, and act together under pressure?

The Four Failures in the Cockpit and in Your Organization

When I look at Flight 173 through the lens of what I call Holistic Leadership, four distinct failures are visible. They map almost exactly to the four dimensions where organizations consistently break down.

Strategy and alignment collapsed first. The captain had a clear priority, resolve the landing gear issue, and never updated it. Situational awareness shifted around him while his focus stayed fixed. In organizations, this is the leader so committed to a plan that new information stops registering. The strategy becomes the reality, regardless of what the environment is actually signaling.

Execution consumed everything. The crew was technically executing well. The captain was methodically working the problem, coordinating with maintenance, managing the approach. Execution without broader awareness, however, is just organized motion toward the wrong outcome. Activity became a substitute for judgment.

Talent was present but couldn't perform. The first officer and flight engineer were capable people. Capability isn't the same as effectiveness. They lacked, or felt they lacked, the psychological safety and the trained habits to escalate with the force the situation required. Organizations routinely under-invest in this: the development of the skills and conditions that allow capable people to actually function at their level.

Culture made silence the safest choice. This is the one that cuts deepest. Nobody decided to stay quiet. The cockpit's authority gradient made speaking up feel riskier than the problem itself. That is a culture problem, not an individual one. Culture problems don't announce themselves. There's no fuel gauge on a failing culture.

What CRM Actually Changed

The aviation industry didn't fix this by hiring better pilots. It changed the system those pilots operated in.

CRM created explicit norms for how challenge should work. It trained captains to solicit input rather than wait for it. It gave first officers language and permission to escalate beyond a hint. It made collective situational awareness a professional responsibility, not a personality trait.

Most importantly, it treated communication and collaboration not as soft skills but as safety-critical competencies, as essential to flight operations as technical proficiency, and trained with the same rigor.

The lesson for leaders isn't "run a better meeting." It's that your team's ability to function under pressure, to share inconvenient information, to challenge without fear, to hold a shared picture of reality together, is not a cultural nicety. It is a core operational capability. Like all capabilities, it doesn't develop by accident.

The Leadership Question Worth Sitting With

Flight 173 gives us a useful thought experiment. If your organization were a cockpit, what would the voice recorder reveal?

Not the official communications. The real ones. The conversations that happen after the meeting, in the parking lot and in DMs. The things your team knows but hasn't found a way to say to you. The signals that are visible on someone's instrument panel right now, being managed with careful, oblique language because the culture makes directness feel dangerous.

Most leaders, if they're honest, already know the answer.

The captain of Flight 173 was not a bad leader. He was a skilled, experienced pilot operating in a system that had never asked him to lead differently. The system caught up with him in the worst possible way.

You have more time than he did. The question is whether you'll use it.

---

Clarity Forge is built on the conviction that organizational performance depends on four integrated capabilities: strategic alignment, disciplined execution, talent development and cultural health. When any one of these is neglected, the others eventually fail, sometimes quietly, sometimes all at once. If this resonates, we'd like to talk.