I attended the Manor Farm Data Centre presentation in Colnbrook on 26th August 2026. There was no reference to Reservoir Flooding – consequently I offered my worst-case scenario as follows:
Imagine a fully loaded large long-haul aircraft taking off from Heathrow in a Westerly direction. Multiple engine failures and fires (possibly due to bird strike) lead to a total loss of power. The plane rapidly loses height and misses the Data Centres, but crashes into the top of the Wraysbury Reservoir embankment – creating a channel – before skidding towards and into the water. Flaming fuel from the ruptured tanks is then carried out of the reservoir (by the uncontrolled water release through the damaged embankment) and on down the embankment slope towards the buildings’.
So who is going to stand up and say ‘this cannot possibly happen’?
I submitted my scenario to Claud AI who produced the text:
Wraysbury Reservoir Plane Crash Scenario
Impact Zone – A speculative reconstruction
This is a work of fiction. It depicts a hypothetical aviation and infrastructure disaster scenario for illustrative purposes only. It does not describe a real event, and all crew, passengers, and specific operational details are invented.
________________________________________
06:14 GMT — Heathrow Airport, Runway 27L
The aircraft is a wide-body, four-engine long-haul type, cleared for a westerly departure — a routine rotation on a foggy late-autumn morning, bound for the other side of the world. Two hundred and eighty-one souls aboard: crew and passengers, most still settling into a ten-hour flight.
Investigators will later reconstruct the next ninety seconds from flight data and cockpit voice recordings, black-box telemetry, and the testimony of people on the ground who happened to be looking up.
06:14:41 — Rotation
The aircraft lifts off cleanly. Gear retracts. Flaps begin their scheduled retraction sequence. In the cockpit, the crew calls “positive rate,” standard procedure, nothing unusual.
06:14:58 — Bird strike
A flock — later identified as Canada geese, common on this stretch of the Thames Valley at this time of year — crosses the departure path at low altitude. The strike is not survivable in engineering terms: multiple engines ingest birds within seconds of each other. Compressor stall. Flameout. Fire warnings illuminate on two engines almost simultaneously.
Cockpit voice recording (reconstructed): “Engine two, fire — engine two fire, confirmed.” “Engine three’s not responding — I’ve lost three.” “Mayday, mayday, mayday—”
06:15:04 — Total loss of thrust
Within seconds, the crew are managing a scenario few simulators fully replicate: total loss of power on departure, below a thousand feet, over one of the most densely built-up approach corridors in the world. The aircraft’s nose is still slightly up from the climb. Airspeed begins to bleed away immediately.
The captain’s only real tool is the aircraft’s glide characteristics and whatever altitude the last thirty seconds bought them. There is no runway within reach. There is barely time to choose a direction.
06:15:19 — Descent
Below, the crew has a fractured, formulaic map to work from: reservoir, data infrastructure, motorway, farmland, village rooftops. None of it is a good option. The aircraft’s shallow bank carries it fractionally clear of a cluster of low industrial buildings — data centres, among other things — that sit close under the departure path.
What’s left ahead is Wraysbury Reservoir: an artificial lake held above the surrounding land by an earthen embankment built in the late 1960s, seventeen metres high at its tallest point, holding tens of millions of cubic metres of water.
06:15:31 — Impact
The aircraft strikes the top of the embankment at a shallow angle, wheels-up, still carrying significant forward speed. The impact tears a channel through the packed earth and clay of the embankment crest — not a clean cut, but a ragged furrow gouged by an eighty-tonne mass moving faster than any vehicle the structure was ever built to withstand.
The fuselage does not stop there. It skids, breaks apart across the breach, and the largest section slides down the inner slope into the reservoir itself. Fuel tanks in the wings rupture on impact; what doesn’t burn immediately spreads across the water’s surface in a slick, catching fire from the wreckage seconds later.
06:15:40 — Breach
The channel the aircraft tore through the embankment does what breached embankments do: water finds it. What begins as a trickle through torn earth becomes, within a minute or two, an accelerating release — tonnes of water per second, forced by the head pressure of millions of cubic metres behind it, widening the gap as it goes.
The burning fuel on the surface doesn’t stay on the surface. It rides the outflow, a thin sheet of flame carried on the leading edge of the water, down the outer slope of the embankment toward the low ground and the buildings below.
06:17 — First responders
Fire crews from the airport’s own rescue service are moving before the aircraft has stopped burning — this is the one piece of the scenario that isn’t speculative; airport crash-rescue response times are measured in minutes for exactly this reason. What they’re driving into, though, is not a runway incident. It’s a breached dam, a fire on moving water, and a crash site that is actively still unfolding as the ground beneath it changes shape.
________________________________________
The scenario above is constructed from public engineering data on Wraysbury Reservoir’s embankment dimensions, published discussion of Heathrow’s departure corridor and nearby infrastructure development, and general aviation accident patterns — assembled into a fictional narrative, not a report of an actual event or a prediction of one.