RAIB report: Audenshaw freight derailment (Sept 2024)

On 6 September 2024 at about 11:25, nine wagons of a 24‑wagon freight train derailed on a small bridge over a public footpath in Audenshaw, Greater Manchester. No one was hurt, but the line was shut for around eight weeks for repairs, according to the RAIB report published 24 December 2025.

To follow what happened, start with two ideas: track gauge-the fixed distance between the rails-and the way the rails sit on the bridge. This bridge used a longitudinal bearer system, where rails sit on long timber beams via steel baseplates and screws, rather than on sleepers and ballast.

Investigators say the gauge spread because several screws holding the baseplates to the timber bearers had already failed through fatigue. As the train rolled over, right‑hand wheels dropped into the widened gap and nine wagons were pulled off the line.

Fatigue is the slow bruising of metal under repeated loads. Each pass of a train is a tiny stress; over thousands of cycles, small cracks grow. In a joint like a screw in timber, those stresses concentrate at the threads and at the plate‑to‑bearer interface.

RAIB’s calculations show the screws, in this bridge’s configuration, were never likely to last indefinitely, even though measured train forces were within Network Rail limits. Installed in 2007, the system then saw busier traffic from about 2015, accelerating fatigue. Routine geometry measurements and inspections did not flag the problem.

Why didn’t the numbers warn anyone? Geometry checks look at how the rails sit and move, not the hidden strength of the bolts and screws underneath. You can have an apparently smooth ride while a critical fastener is quietly losing its grip.

There’s also a paperwork lesson. When maintenance teams record small failures and share them promptly, patterns emerge. Miss a few entries and you miss the trend; a component that looks like a one‑off can actually be telling you a story about design limits.

RAIB makes eight recommendations for Network Rail, covering better assurance of LBS components, clearer design and maintenance guidance, stronger staff competence, closer working between track and structures teams, attention to supporting structures, traffic‑change assessment, complete asset records, and tougher assurance of local record‑keeping.

If you’re studying engineering or transport operations, read this case in layers. Start with the system (bridge plus track), move to the component (screws and baseplates), then to the data (traffic levels and inspection outputs). That way, you see how ordinary numbers hide unusual risk.

One subtle detail is who owns the problem. Bridges are ‘structures’ and track is ‘track’, often with different teams. Failures that sit on the boundary can fall between responsibilities, which is why the report calls for tighter interfaces between those teams.

Try a simple exercise: take a photo of a footbridge or fence at your school, mark every fixing point, and imagine half of them loosening over time. Which measurements would spot the change? Which would not? That’s the difference between checking geometry and checking fixings.

RAIB investigates to prevent future accidents and improve safety, not to assign blame.