A Near Miss Is Not a Lucky Escape. It Is a Warning.

Some incidents do not end in injury.

No one is hurt.

No one is hospitalised.

No equipment is seriously damaged.

The work continues.

That can make a near miss feel like a close call that “turned out fine.”

But a near miss is not proof that the system worked.

Sometimes it is proof that the consequence simply missed its target.

Sologic’s example problem on falling asphalt is a strong reminder of this. A large chunk of asphalt fell from a partially demolished bridge deck and landed between a sidewalk and an existing bridge pier. Nobody was in the immediate area at the time, but crews were working nearby on an open public street.

It would be easy to describe that as a lucky escape.

But good RCA asks a better question:

What made it possible for a large, loosened chunk of asphalt to remain elevated, close to the edge, and capable of falling into an area where people could have been present?

That shift changes the investigation.

Instead of stopping at “the asphalt fell,” the team can start looking at the conditions around the work.

The bridge deck had been partially demolished. The asphalt overlay had been loosened during work the day before. End-of-shift clearing was being done using a demolition tool on an excavator arm, followed by a visual check from a manlift. Yet the next morning, inspection showed large chunks of loose asphalt still near the deck edge.

That is the part worth paying attention to.

The issue was not only that a chunk of asphalt fell.

The deeper concern was that the controls intended to identify and remove loose material did not fully work. The inspection method missed the hazard. Lighting may not have been adequate. The work environment allowed heavy material to remain elevated and exposed after demolition activity.

This is where near misses are so valuable.

They give teams a chance to learn before the consequence becomes permanent.

But that only happens if the organisation treats the near miss as evidence, not as a non-event.

A weak investigation might produce simple actions like “remind crews to inspect the area” or “be more careful at shift end.”

A stronger investigation asks:

• What could the inspection method reasonably detect?
• What could it miss?
• Was the hazard visible from the inspection position?
• Was lighting adequate for the task?
• Were there physical controls to prevent material movement after demolition?
• Was the work area controlled based on what could fall, not just where people were expected to be?

Those questions move the discussion away from hindsight and closer to risk reduction.

Because after an incident, everything looks obvious.

Before the incident, the hazard often sits inside normal work.

That is why structured RCA matters. It helps teams connect the event to the conditions that allowed it to happen, then develop corrective actions that control the actual risk.

In this example, the proposed solutions included adding end-of-shift inspections from the top side for elevated road decking demolition jobs, improving lighting for inspections, and installing protective restraints over elevated roads to prevent asphalt movement after demolition work.

That is the difference between closing a near miss and learning from one.

A near miss should not be measured by how little damage occurred.

It should be measured by how clearly it shows what could happen next time.

And if the only reason nobody was hurt was timing, then timing should not be treated as a control.

Read the Sologic example problem on Near Miss Falling Asphalt to see how a structured cause-and-effect approach can help teams move beyond “close call” thinking and focus on the conditions that need to change. Link here.