Brake fault on empty train sparks Clapham Junction fire scare, lines reopen

A fire alert on an empty train at Clapham Junction caused several hours of disruption on Thursday afternoon, before engineers traced the problem to a brake fault and reopened all lines, according to [1]. The incident began with reports of smoke coming from an empty Southeastern train that was travelling to a depot, according to [1]. Firefighters were called to the scene at Clapham Junction, and lines were blocked between Balham and London Victoria, National Rail said, according to [1]. Gatwick Express, an affected operator, told passengers at the time that "a train is on fire between Balham and London Victoria" and that some lines were closed "until further notice", according to [1]. Southern, working alongside London Fire Brigade to deal with the incident, later confirmed the cause in a statement: "Following reports of smoke from an empty Southeastern train travelling to a depot, engineers attended and identified the cause as a brake fault. The issue has been resolved, the train has moved safely and all lines have reopened," according to [1]. While the fault was being dealt with, trains were diverted onto an alternative track, meaning services were unable to stop at Battersea Park and Wandsworth Common, according to [1]. National Rail warned that the disruption was expected to continue until 3pm, with Southern services facing delays of up to 15 minutes or being revised, according to [1]. By the end of the live coverage cited in [1], National Rail confirmed lines had reopened and trains were running as normal. Separately, live departure and arrival information for the Chelmsford to Clapham Junction route was unavailable on Thursday, with South Western Railway's website citing "technical issues" with its live feed, according to [2]. The material at [2] gives no indication of whether this outage was linked to the Clapham Junction brake fault or to the wider strain reported across the network; it is described purely as a technical fault with the live-departures feature, and no cause is given for it. Wayne's monitoring systems flagged Thursday's episode as part of a recurring congestion signature — the same pattern of high-load strain across Clapham Junction, Waterloo and Chelmsford rail links, compounded by a Blackwall Tunnel breakdown and an Oxford Street collision, that has now been logged 47 times. None of the material supplied for this story establishes a fresh causal event tying those separate incidents together; the Clapham Junction fire scare, the Chelmsford departures outage and the other reported congestion points sit in the same geographic and temporal window without any confirmed link between them. A salmonella outbreak note that surfaced alongside this batch of reports appears to have been bundled in purely by geography rather than by any demonstrated connection to the rail disruption, and nothing in the sourced material ties the two together. In short: a brake fault, not a fire, caused Thursday's Clapham Junction disruption, and it was resolved within hours, according to [1]. The broader "high-strain" pattern flagged by Wayne's instruments reflects a familiar recurring signature of London/South East congestion rather than a new, connected incident, based on what the material here actually shows. What to watch next: whether South Western Railway's Chelmsford live-departures outage noted in [2] is resolved, and whether any operator publishes a root-cause note connecting Thursday's cluster of incidents — so far, none has.