Why We Wait for Catastrophe Before We Change

Most organizations do not change when the warning light first comes on. They change when the smoke fills the room.

That is what makes the UPS MD-11 accident such a painful and useful case study. The point is not to turn a tragedy into a slogan. The point is to look honestly at a pattern that shows up in aviation, manufacturing, leadership, culture, safety, relationships, and business: we often know enough to act before disaster, but we wait until disaster gives us permission.

On November 4, 2025, UPS Flight 2976, a Boeing/McDonnell Douglas MD-11F, crashed shortly after takeoff from Louisville Muhammad Ali International Airport. The NTSB reported that the aircraft was destroyed after impacting buildings and the ground, killing the three crewmembers and people on the ground. The FAA later issued an emergency airworthiness directive for MD-11 and MD-11F aircraft after the accident, prohibiting further flight until inspections and corrective actions were completed.

The emerging focus was the left engine and pylon. The FAA’s directive said the accident involved the left-hand engine and pylon detaching from the airplane during takeoff. NTSB investigative updates identified fatigue cracking in areas connected to the pylon structure and spherical bearing assembly. Afterward, the response was immediate: grounding, inspections, emergency directives, operational disruption, and ultimately UPS retiring its MD-11 fleet.

And that is the uncomfortable leadership lesson. The risk did not become serious only after the crash. It became impossible to dismiss after the crash.

The dangerous gap between “known” and “mandatory”

In most organizations, there is a large and dangerous space between these two statements:

“We know this could become a problem.”

“We are required to fix it now.”

That gap is where risk learns to hide.

Before catastrophe, the language usually sounds careful and reasonable. Monitor it. Review it. Inspect it at the next interval. Wait for more data. Study the trend. See if the condition repeats. Avoid unnecessary disruption. Do not overreact.

Sometimes that caution is wise. Not every risk deserves a five-alarm response. But caution becomes cowardice when repeated warnings are treated as background noise simply because the worst-case outcome has not happened yet.

That is the trap. Leaders and regulators can become more comfortable managing the paperwork around risk than eliminating the risk itself.

Why organizations wait

Waiting rarely feels reckless in the moment. It often feels responsible, disciplined, and financially mature. Fixes cost money. Mandatory action disrupts operations. Grounding assets creates pressure. Pulling equipment out of service affects customers. Replacing parts too early can look wasteful. Raising the alarm can make the person raising it look dramatic.

So the organization learns to live with the warning.

That same pattern shows up far beyond aviation. A toxic supervisor stays because the numbers are good. A failing process remains because employees have learned workarounds. A safety hazard sits unresolved because no one has been badly hurt yet. A training gap is ignored because mistakes have been recoverable. A culture problem gets minimized because turnover has not exploded.

Then something breaks. Someone gets hurt. A customer leaves. A lawsuit lands. A key employee quits. A machine fails. A public incident exposes what insiders already knew.

Suddenly, the fix that was “too expensive” becomes non-negotiable.

The false comfort of “no catastrophe yet”

One of the most dangerous sentences in leadership is, “It has not happened yet.”

That sentence feels like evidence. It is not. It is a temporary condition.

“It has not happened yet” does not mean the system is safe. It may only mean the system has been lucky. It may mean the failure mode is rare, hidden, intermittent, slow-moving, or waiting for the right combination of age, fatigue, pressure, temperature, workload, schedule, and human decision-making.

Luck can make weak systems look strong for a long time.

That is why strong leadership has to ask a harder question: Are we safe because the system is healthy, or are we safe because nothing has exposed the weakness yet?

Catastrophe as a forcing function

After a catastrophe, urgency appears instantly. Meetings get scheduled. Budgets open. Decisions accelerate. Policies change. Leaders who once asked for more data suddenly ask why no one acted sooner.

But that urgency is not leadership. It is consequence.

Real leadership acts before consequence removes all other choices. It does not need a death, lawsuit, scandal, shutdown, or customer revolt to do the obvious thing. It respects weak signals before they become breaking news.

This is not about panic. It is about moral seriousness. When the stakes involve people, safety, trust, or long-term organizational health, waiting for catastrophe is not patience. It is gambling with someone else’s future.

The lesson for leaders

The UPS MD-11 case is still subject to formal investigation, and aviation professionals should rely on the NTSB and FAA for final technical conclusions. But as a leadership case study, the lesson is already clear enough to use.

Known risk without action is not wisdom. It is delayed responsibility.

Every organization has its own version of the pylon bearing. A part, a process, a person, a culture issue, a training gap, a maintenance shortcut, a staffing weakness, a leadership habit. Something that people know is not right but have learned to tolerate.

The challenge is simple, but not easy: find it before it fails.

Because the most expensive change is the change you make after people are already hurt.