Two ports, one line.A derailment at Barking cut rail freight to Tilbury and London Gateway together

RA GB Railfreight container train travelling from London Gateway towards Hams Hall in the West Midlands derailed near Barking station in east London on Friday 23 October 2026. Reports place it at about noon or about 13:10, and describe damaged wagons dragged along the line, with track and overhead line equipment damaged.¹⁴

VGBR Anglia, which runs c2c, said about 1.2 km of track needed renewal and that the recovery was complex because of the significant damage to infrastructure. Its trains stopped calling at Dagenham Dock, Rainham and Purfleet, and the Rail Accident Investigation Branch is investigating.²

VForth Ports told customers that the line was closed and no freight rail would run to Tilbury and Tilbury2 that week. DP World said it was operating a reduced rail freight service from London Gateway, working with customers and Network Rail to minimise disruption.¹³

RBy 27 October no party had confirmed a date for normal service, and repairs were expected to last at least a week.³

AThe visible problem is a damaged stretch of track in east London. The system problem is that two separately owned container ports, which compete for the same ships, share the same few kilometres of railway inland.

RTwo ports, one outage. Tilbury lost its rail service for the week and London Gateway ran a reduced one, from a single event at a single location.¹³

RFreight and passengers on the same loop. The loop through Dagenham Dock, Rainham and Purfleet carries most of the freight trains, and the same closure shut three passenger stations.¹²

RAlternatives that were already full. The North London Line and the Great Eastern Main Line offer other paths, but both are busy with passenger services, which limits how much freight can be rerouted.¹

RA shift to the road with its own limit. Hapag-Lloyd asked merchant haulage customers to arrange road transport and said it could not accept extra haulage requests during the disruption. The Road Haulage Association said it was monitoring the situation.³

RPriorities set under pressure. Deep-sea container flows were being prioritised to prevent congestion in the Thames Estuary, while transit times to inland hubs such as Hams Hall, Birch Coppice and Daventry were extended. A second, low-speed derailment during recovery slowed the work.¹

AA port's inland service depends on its rail terminal, the network beyond the gate, the train paths it shares with passenger operators, the crews and wagons in position, the hauliers who can take the overflow, and decisions made by bodies the port does not control. Three disciplines ask distinct questions of it.

AThe requirements question (systems engineering): which stretches of network lie on every rail route out of the port, and what evidence shows that a second route can carry a useful share of the trains? The time question (system dynamics): how fast does a container backlog build when trains stop, and how long after the track reopens does it take to clear? The condition question (asset management): who owns the shared stretch, how do the ports that rely on it learn its condition, and who decides between freight and passengers when capacity is short?

VRail carries real volume for these ports. DP World said in 2021 that its trains left London Gateway every working day, and that rail across its Southampton and London Gateway terminals took 300,000 trucks off UK roads each year.⁵

ITraffic diverted to road at short notice meets a haulage market that carriers were already rationing, so the container backlog is likely to outlast the repair of the track.

AKPL calls this landside common mode: the condition in which separate ports or terminals look independent at the quay but share one inland link, so that a single fault removes their rail capacity together.

ATrace every route inland. For each port or site, list the stretches of network that every rail route uses, whoever owns them.

ACount shared stretches across owners. Where competing ports or terminals use the same stretch, record it as one dependency in each of their risk registers.¹

ATest the diversion before it is needed. Agree with the network operator how many trains an alternative route can take while passenger services are running.¹

APrice the road overflow. Know how many containers local hauliers can move in a week, and on what terms, before carriers begin to ration.³

APlan the backlog as well as the repair. Set the order in which delayed containers move once trains return, and name who decides it.¹

OUR PERSPECTIVE

Two quays can share one weak link inland.

AThe same pattern applies to airports that share one fuel pipeline, data centres that share one substation and water companies that share one chemical supplier: wherever separate owners rely on one link they do not control.

1. Which stretches of network does every one of our rail routes pass through, and who owns them?
2. Which other ports, terminals or operators depend on the same stretches?
3. How many trains a day could an alternative route take while passenger services are running, and has that been tested?
4. How many containers a week can road haulage take from us at short notice, and at what cost?
5. Once the line reopens, how long does it take to clear the backlog, and who sets the order?
6. How quickly do we learn about incidents and condition on a network we do not own?

AFollow-through on Nº 12: the government meeting in Rome on the former Ilva steelworks was scheduled for 27 October at 17:00. A KPL search on 28 October found no report of its outcome and no count of restocked stations in Puglia, so both milestones remain open.

AKPL will return to this story when the line reopens, to check how long the container backlog took to clear after the track was repaired.