INCIDENT REPORT 14-778 — CASTLE VALE CONTAMINATION EVENT
Classification: Restricted / Environmental Concealment — Regional Office (Birmingham) Filed under: Monster Accord, Incident Reports Status: Closed. Reclassified twice. Never reopened.
Background Wartime Origins
Castle Vale was not built on empty ground. Before it was an estate, it was an aerodrome, and before that, farmland the city used to treat its sewage. Between 1940 and 1945, the site absorbed over two hundred bombs meant for the factory floor next door, where workers built the aircraft that helped win a war, twelve hours at a time. Official records list eleven deaths there. The Accord’s position, then as now, is that “recorded” is doing quite a lot of work in that sentence.
Wartime gave regional operatives something they don’t often get: cover that writes itself. A site absorbing that much ordnance, that much rubble, that many hurried night-time clearances doesn’t need an explanation for anything unusual turning up in the ground afterward. It only needs patience. Operatives contained something on the site during this period, though the file never names it. Whoever wrote the original entry never saw the thing directly, and the Accord prefers to keep it that way.
The wartime factory this site once served built more Spitfires than any other in the country, and its production record is a matter of extensive public documentation. For anyone wanting the real history behind this ground, Castle Bromwich Assembly is a useful primer. The Accord has no interest in disputing any of it. If anything, that history is exactly what makes the ground so useful: true, thoroughly documented, and an excellent place to hide something that isn’t.
First Disturbance, 1966
Builders raised the estate between 1964 and 1969, directly over the old airfield. Groundworks disturbed the containment site once, in 1966, and operatives undertook a remedial action that doesn’t appear in this file. It’s referenced here for one reason only: so whoever reads Incident Report 14-778 next understands that Castle Vale had already asked this question once, and the Accord had already answered it.
The Incident
Council contractors marked Castle Vale’s tower blocks for demolition in the 1990s, part of the estate’s wider regeneration. Demolition and groundworks reached the containment site a second time. This time, the disturbance didn’t stay contained to the ground.
Contractors working the affected zone reported three things, in order. First, unexplained structural readings that didn’t match the surveyed soil composition. Second, two minor injuries logged as “equipment failure,” though equipment records don’t support that cause. Third, a site foreman’s account — never formally taken down — of hearing something move under a slab still waiting to be lifted. Management transferred the foreman to a different site within the week. Nobody ever took his account down officially, because by the time anyone arrived to record it, there was nothing left to corroborate it against.
One incident stands apart from the others. A site surveyor — name withheld in this file at Accord discretion, referred to hereafter as D.M. — filed an internal report describing movement beneath a section of cleared ground, roughly forty minutes before contractors were due to begin work on it. D.M.’s report turned out to be accurate. It was also the last document D.M. ever filed under their own name. Personnel records show a lateral transfer to environmental monitoring duties shortly after, along with a change in reporting line and no further fieldwork of any kind. As of this filing, D.M. remains alive and employed, and has not spoken about Castle Vale since. The Accord doesn’t consider this a coincidence. It doesn’t consider it a matter for further comment, either.
Incident Log (abridged)
Day 1, 06:40 — Groundworks crew begins clearance of the affected section, previously undisturbed since the 1966 remedial action.
Day 1, 11:15 — First anomalous structural reading logged by site instrumentation. Flagged internally as instrument fault. No fault found on inspection.
Day 1, 16:50 — D.M. files internal report describing detected movement beneath cleared ground. Report is time-stamped forty minutes ahead of the following morning’s scheduled excavation.
Day 2, 05:30 — Excavation crew reassigned to a different section of the site “as a precaution,” per instruction from a site manager who does not, in later interview, recall giving that instruction.
Day 2, 09:10 — Two minor injuries reported among groundworks staff. Equipment logs do not support the stated cause.
Day 3 — D.M.’s transfer to environmental monitoring duties is processed. Regional operatives arrive on site the same day, formally attached to the council’s environmental health team as external consultants.
Day 4–11 — Soil sampling conducted. Restricted zone established. Public messaging aligned with sampling results (see below).
Day 12 — Site cleared for continued demolition. No further incidents recorded.
Containment Response
Regional operatives moved quickly, drawing on the precedent set in 1966. The approach stayed the same in principle: give the disturbance a name the public already understands, and let existing anxieties do the rest of the work.
Operatives supplied Birmingham City Council’s environmental health department with soil sample data indicating contamination consistent with historic industrial land use. This was plausible, given the site’s genuine wartime and pre-war history, and hard to challenge without specialist knowledge the council had no reason to seek out. The classification landed on exactly the kind of hazard a former aerodrome and sewage works would carry anyway: aviation fuel residue, heavy metals, asbestos from wartime structures. None of it needed inventing from nothing. It only needed misattributing, and Castle Vale’s ground handed the Accord more than enough real contamination history to make the swap convincing.
The council accepted the classification without dispute. Officials established a restricted zone around the affected section, citing asbestos and heavy-metal exposure. They informed residents accordingly, issued the standard advisories, and quietly adjusted the demolition schedule to accommodate a “remediation window” that existed for entirely different reasons than the ones printed on the noticeboard. Nobody on the council side did anything wrong. That’s precisely why it worked.
This is the mechanism the Accord depends on more than any other, and Castle Vale is one of its cleanest examples. The council never participated in the concealment — it was the instrument of it, a functioning, well-intentioned institution acting correctly on false information it had every reason to trust. Nobody at the council needed to be complicit. They only needed to do their jobs, and doing their jobs properly closed the file for everyone else.
Public Messaging Alignment
Local reporting at the time attributed the restricted zone to standard remediation ahead of regeneration works — a mundane, expected part of any 1990s council estate redevelopment, and therefore not a story anyone felt inclined to chase further. This is the outcome the Accord aims for in every incident of this kind: not a cover-up that needs defending, but a non-event that needs no defending at all. Public messaging alignment in this instance required no active press engagement, no denial, and no follow-up. The truth was simply never interesting enough to ask about.
This lines up with the operating principle in ACC-MEMO-009: the public doesn’t need a convincing lie. It just needs a reason not to ask the next question. Castle Vale’s own history supplied that reason before regional operatives had to invent one.
Cross-Reference and Current Status
Incident Report 14-778 is filed alongside the Accord’s other regional containment records. Operatives reviewing this file in connection with future Castle Vale activity should note the unresolved 1966 remedial action referenced above, which remains outside the scope of this document.
The Accord’s containment doctrine, and the reasoning behind it, sits in the cornerstone memo Why the Public Must Never Know. Field operatives who saw more than they were meant to have their own precedent in the Mutt Mallory personnel file. And for background on the kind of entity a groundworks disturbance like this is consistent with, the Field Guide to Monster Accord Feeders covers it.
The complete Accord archive, in chronological order, begins with Clause I: The Silence at Bleakmere, the Accord’s foundational 1947 document, and continues through The Mourner’s Feast, No Names in the Fog, Feed Nothing After Midnight, Kilo-Four Went Quiet, and The Dead Don’t Stay Logged.
Castle Vale’s tower blocks are gone now. The ground beneath them is not new. It has simply been asked to keep quiet twice.
Status: Closed.
The Monster Accord is a fictional found-document horror universe accompanying the novel Bad Wiring. Historical details regarding Castle Bromwich Aerodrome and the Castle Vale estate are drawn from real regional history; all named incidents, personnel, and containment actions described above are fictional.