Clapham Common: 'Panicking' passengers smashed windows to flee TfL Tube due to staff failings, says report

Watch more of our videos on Shots! 
and live on Freeview channel 276
Visit Shots! now
On May 5 2023 passengers smashed windows to flee a TfL Tube train at Clapham Common after smoke began to appear and the doors remained closed.

A passenger-led evacuation of a Tube train that could have had “serious consequences” was caused in part by London Underground’s failure to learn from a previous incident, according to a new report.

At just before 5.45pm on Sunday May 5 last year, a Tube leaving Clapham Common was halted by a passenger emergency alarm after smoke and a smell of burning entered the train. It stopped partly in the tunnel and partly at the platform and the doors remained closed.

Hide Ad
Hide Ad

Around 100 of an estimated 500 passengers self-evacuated onto the platform through doors between the train’s cars and smashed windows. Station staff began opening the train’s doors around four and a half minutes after the train stopped.

Minor injuries were sustained but a new report by the Rail Accident Investigation Branch (RAIB) says the incident could have had more serious consequences due to the narrow island platform, increasing the risk of passengers falling onto the track and touching the conductor rails or being hit by a train coming the other way.

The RAIB’s investigation found that passengers perceived a significant risk from fire, and that they became increasingly alarmed when the train’s doors remained closed. It found they did not receive suitable information or see any effective action from London Underground staff. The report suggests the smoke came from a substance on the brake resistor grid.

It said an underlying factor was a lack of training or procedures for incidents where passenger behaviour can rapidly escalate, and that London Underground did not fully apply learning from a previous similar incident at Holland Park station.

Hide Ad
Hide Ad

Andrew Hall, chief inspector of rail accidents, said: “Out-of-course events can rapidly escalate into emergencies if not responded to promptly and effectively.

“During this incident staff didn’t fully appreciate the emerging safety risk when passengers’ behaviour began to escalate as they became increasingly anxious. When passengers did not receive suitable information about the nature of the incident and the actions they should take, nor see action they would have expected to be taken, they turned to desperate measures to self-evacuate.

“RAIB investigated a similar incident at Holland Park in 2013 and for a number of years that incident was used as an example to train staff about how to respond to such out-of-course events. However, it was subsequently removed from the training syllabus and since then knowledge of the lessons learnt may well have begun to fade. This incident again demonstrates that learning from past operational incidents needs to be retained by organisations.”

Hide Ad
Hide Ad

RAIB has made three recommendations to London Underground relating to procedures and training for “out-of-course events”, learning from previous incidents and risk assessments.

Nick Dent, London Underground’s director of customer operations, said: “I would like to apologise again for the distress this incident caused to customers at Clapham Common and would like to reassure Londoners that we are continuing to do all we can to ensure the safety of everyone on the Tube.

“Our commitment to safety is at the heart of everything we do, and our staff work hard to keep our customers safe in sometimes challenging circumstances. We welcome any opportunities to learn lessons from incidents on our network and, following our own investigation last year, we are already making good progress on the recommendations from the RAIB. This includes changes to our training, which will be in place in the coming weeks.”

Comment Guidelines

National World encourages reader discussion on our stories. User feedback, insights and back-and-forth exchanges add a rich layer of context to reporting. Please review our Community Guidelines before commenting.