Paddington fire halts Heathrow rail services, evacuates 380 passengers

380 passengers were evacuated from a stranded Elizabeth line train due to the fire and electricity supply failure.
380 passengers evacuated from a stranded train by fire crews
A grass fire near Paddington caused an electricity failure that disabled rail lines and forced the evacuation of hundreds of travelers.
Mark

So this fire was near the tracks themselves—that's what knocked out the power?

Mimi

Yes, it was a grass fire right by Scrubs Lane, close enough to the infrastructure that it caused an electricity supply failure. That's what disabled the lines.

Luke

Do we know what started the fire, or is that still under investigation?

Mimi

The source doesn't say. We know it was a grass fire and where it was, but not the cause.

Mark

And 380 people were on that one train when it got stranded?

Mimi

That's what fire crews evacuated. They had to help get all those passengers off.

Luke

Was anyone hurt in the evacuation itself, or during the fire?

Mimi

The source doesn't mention any injuries. It's focused on the disruption and the evacuation process.

Mark

How long did it take to get things moving again?

Mimi

The reporting says disruptions were expected to continue until the end of Saturday, but it doesn't give a specific timeline for full recovery.

Luke

So we're looking at a few hours of chaos, not a days-long shutdown?

Mimi

That's what the available information suggests, yes.

Mark

The Piccadilly line was also affected—was that because of the same fire?

Luke

No, the source is clear that the Piccadilly delays were separate—there was an earlier trespasser at Hammersmith that caused those. The fire made things worse, but didn't cause them.

  • A grass fire near Scrubs Lane knocked out the electricity supply feeding Paddington's rail junction, instantly severing London's most critical airport rail corridor.
  • 380 passengers found themselves stranded aboard an Elizabeth line train, requiring fire crews to carry out a full evacuation in the middle of the disruption.
  • The chaos spread beyond one line — Great Western Railway canceled all Reading services, and the Piccadilly line, already slowed by a trespasser incident at Hammersmith, buckled further under the weight of diverted Heathrow-bound travelers.
  • Transport for London and Heathrow airport both issued advisories urging passengers to allow extra time, but the alternatives they offered were themselves compromised.
  • By late Saturday the fire was contained, yet the network's recovery lagged behind, leaving the capital's busiest corridors operating at a fraction of their capacity through the end of the day.

On a Saturday afternoon in North Kensington, a grass fire near Scrubs Lane reminded London — and perhaps all cities built on intricate, interdependent systems — how fragile the threads of modern life can be. The blaze disabled an electricity supply serving Paddington's rail junction, suspending Elizabeth line services to Heathrow, stranding 380 passengers who required evacuation, and cascading disruption across Great Western Railway and the Piccadilly line. What began as a fire in the grass became, within hours, a lesson in how a single severed node can unravel the journeys of hundreds. The city's networks held together imperfectly, as they always do, while passengers and operators alike searched for ways around the gap.

A grass fire near Scrubs Lane in North Kensington on Saturday afternoon brought significant parts of London's rail network to a halt, forcing the evacuation of 380 passengers and suspending airport services across multiple lines. London Fire Brigade arrived just after 4pm with six engines and 40 crew members, but the fire's proximity to the tracks had already done its damage — an electricity supply failure disabled all rail connections between Paddington and Heathrow.

The Elizabeth line bore the sharpest impact, suspended entirely between Paddington and Heathrow Terminals 4 and 5, and separately toward Reading. A stranded train required fire crews to evacuate all 380 passengers on board, while the Abbey Wood branch suffered severe delays as the network struggled to absorb the shock. Great Western Railway canceled its Reading services outright, warning that disruptions would last through the end of the day.

Passengers seeking Heathrow were directed to the Piccadilly line, though that route was already experiencing severe delays between Heathrow and Acton Town — partly due to an earlier trespasser incident at Hammersmith. Heathrow airport asked travelers to allow additional journey time as the system strained under the combined pressure.

The episode illustrated a familiar vulnerability: a single point of failure at a critical junction can cascade swiftly across operators, routes, and hundreds of individual journeys. The fire was contained by afternoon, but London's recovery moved more slowly, leaving travelers to navigate a diminished network across the capital's most heavily used corridors.

A grass fire that erupted near Scrubs Lane in North Kensington on Saturday afternoon brought significant portions of London's rail network to a standstill, forcing the evacuation of 380 passengers and canceling services to Heathrow airport across multiple lines.

London fire brigade arrived at the scene just after 4pm with six engines and 40 crew members to tackle the blaze. The fire's location near the tracks proved consequential: it caused an electricity supply failure that disabled all rail lines running between Paddington and the airport terminals. The disruption rippled outward across the network, affecting not only the Elizabeth line but also services operated by Great Western Railway heading toward Reading.

The Elizabeth line, which connects central London to the airport and beyond, bore the brunt of the immediate impact. The line was suspended entirely between Paddington and Heathrow Terminals 4 and 5, and separately between Paddington and Reading. A train carrying passengers became stranded in the affected zone, and fire crews were called in to assist with evacuating all 380 people aboard. The line to Abbey Wood also experienced severe delays as the network struggled to reroute traffic around the disabled infrastructure.

Passengers attempting to reach Heathrow faced a narrowed set of options. Transport for London advised travelers to use the Piccadilly line as an alternative, though that route itself was experiencing severe delays between Heathrow and Acton Town. Those delays were compounded by an earlier incident—a trespasser at Hammersmith—that had already slowed service on the rest of the line. Heathrow airport issued its own advisory, asking passengers to allow additional time for their journeys as the transport system absorbed the disruption.

Great Western Railway canceled all services to Reading on Saturday, with the operator warning that disruptions would persist through the end of the day. The scale of the disruption underscored how a single point of failure in London's rail infrastructure—in this case, an electricity supply serving a critical junction—can cascade across multiple operators and routes, affecting hundreds of travelers in a matter of hours. By Saturday afternoon, the fire had been contained, but the network's recovery remained incomplete, leaving passengers to navigate a significantly diminished service across the capital's busiest transport corridors.

The fire caused an electricity supply failure which left all lines between Paddington and the airport blocked
— National Rail, Saturday afternoon
Contattaci Domande frequenti