Railway Accident Investigation: The Methods Engineers Use

Purpose and independence

Many countries have independent bodies that investigate serious railway accidents and incidents — for example the Rail Accident Investigation Branch (RAIB) in the UK, the National Transportation Safety Board (NTSB) in the US and national investigation bodies across the EU. Their aim is to understand what happened and why, and to recommend changes that prevent it from happening again. Their findings are kept separate from questions of legal liability.

Collecting the evidence

• Site survey: positions of vehicles, marks on rails and sleepers, damage patterns, often recorded with photogrammetry or laser scanning.
• Rolling stock: wheels, bogies, brakes and couplings are examined, sometimes in the laboratory.
• Infrastructure: track geometry, rail condition, signalling and level-crossing equipment.
• Data: on-train data recorders, signalling logs, CCTV and voice communications.
• People: interviews with drivers, signallers, maintenance staff and witnesses.

Analysing causes

Investigators distinguish between the immediate cause — a broken rail, a signal passed at danger — and the underlying factors that allowed it. Systemic methods examine how maintenance regimes, procedures, training, workload and organisational decisions contributed. Human-factors analysis looks at why actions made sense to the people involved at the time.

Engineering tools

Vehicle dynamics simulation can test derailment hypotheses. Metallurgical analysis shows whether a component failed by fatigue or overload. Data from recorders is synchronised to rebuild an accurate timeline of the final seconds.

From findings to safety

Investigations end with recommendations addressed to infrastructure managers, operators, manufacturers or regulators. Following up those recommendations is how lessons become safer railways.

To build skills in railway systems, safety and infrastructure, explore our civil, rail and smart cities programmes. Safety engineering methods are shared across sectors — see our introduction to ISO 26262.