Major fire shut the Hillhouse chemical plant for three months. What was public at the time, and what AGC's own reports to the Environment Agency now say.

AGC's own 2024 accounts record a fire in October 2024 that stopped production at its Hillhouse plant for three months. The fire service logged a 'commercial building fire' on Fleetwood Road North, naming no chemical plant and no hazard. This piece sets out what the accounts say, what the major-hazard regulations require, what AGC has since answered, and what it has not. Updated 18 October 2026: AGC's notification and investigation report, disclosed by the Environment Agency on 2 September 2026, describe a lagging fire on the Steam Pyrolysis section and, on AGC's estimate, about 275 cubic metres of process gas released, a significant portion combusted.

Primary sources used in this post:
  • AGC Chemicals Europe Ltd accounts, Companies House 03825057 (2024 filing): going-concern note and Note 25 (contingent asset), fire on 19 October 2024, three-month outage, ongoing insurance claim.
  • Control of Major Accident Hazards Regulations 2015, regulations 17 and 18 (legislation.gov.uk). HSE’s COMAH 2015 public information register, checked 14 October 2026, lists AGC Chemicals Europe, Limited (Thornton Cleveleys, Hillhouse International, FY5 4PF) as “Lower Tier”. FOI 202602243 to HSE is unanswered.
  • HSE guidance on RIDDOR dangerous occurrences: a fire suspending normal work for more than 24 hours is reportable to HSE.
  • Published safety literature on tetrafluoroethylene (TFE) manufacture by high-temperature steam pyrolysis of chlorodifluoromethane; byproducts include hydrogen fluoride and perfluoroisobutene.

We found this fire in the company’s own accounts. The only public trace of it we can find is a fire-service log entry that names no chemical plant and no hazard. What follows is drawn from AGC’s own filings, from public safety regulations, from the published chemistry of the process involved, and from AGC’s own answers to us.

Updated 5 August 2026. AGC Chemicals Europe has responded. Its statement is published in full, with a full timeline and a note of what it answered and what it declined, in Updates and responses at the foot of this article. This article also carries a correction, marked in place below.

What the accounts record

In its 2024 accounts, filed at Companies House, AGC Chemicals Europe records that “the business experienced a fire in October 2024 within the Steam Pyrolysis section of the plant,” and that this “caused an outage of 3 months.” A separate note confirms the date, “an incident on 19 October 2024 where a fire occurred at the Company premises,” and that the company is claiming on its insurers for “income lost directly attributable to this incident.”

So there was a fire, at a chemical plant on a residential fenceline, that stopped part of the works for three months. It was written down for shareholders in plain terms. What reached the public was considerably less specific.

What was published, and what it did not say

Lancashire Fire and Rescue Service did publish a record of the incident. Its entry for 19 October 2024 (incident 2410007359) describes a “commercial building fire” on Fleetwood Road North. It does not name AGC. It does not identify the premises as a chemical works. It does not mention any hazardous material, and it carries no advice to residents.

Beyond that entry we could find, when this was written in July 2026, no local news report naming the site in connection with this fire. The fire and the three-month outage were on the public record in one other place: AGC’s accounts for 2024, filed at Companies House in September 2025, which is where we found them. What burned, what was released and why became public, on AGC’s account, when the Environment Agency disclosed AGC’s notification and investigation report on 2 September 2026 (see the update below).

So a record exists. What it does not do is tell anyone living on the boundary that the fire was at a chemical plant, or that it would stop production there for three months. A reader of that entry would learn that a commercial building on Fleetwood Road North had caught fire. They would learn nothing about what the building was.

Correction, 5 August 2026. An earlier version of this article said there was “no fire-service statement.” That was wrong: the Lancashire Fire and Rescue Service record described above was published, and AGC pointed to it in correspondence. We have rewritten the passage and left this note rather than quietly amending it. The substance is unchanged, and in our view sharpened: the question was never whether anything was published, but whether what was published identified the site or the hazard.

Correction, 30 September 2026. The headline said “the community was never told what had burned”, and the article said “the regulators knew what had burned” and listed the reporting to regulators and the absence of enforcement action as answered facts. We can only say what the public record we have found shows. The headline and those passages now say so. The questions we sent AGC are quoted as sent.

Corrected again, 1 October 2026. The 30 September correction described the reporting to regulators as unconfirmed. That was wrong: the Environment Agency’s own record, disclosed on 2 September 2026 and set out on Open questions, confirms it was notified on the evening of the fire. Only the HSE’s confirmation is outstanding.

Update, 18 October 2026: what AGC’s own documents say

The Environment Agency’s disclosure of 2 September 2026 (EIR2026/37608) included two AGC documents, quoted in full on AGC in its own words. AGC’s Schedule 5 Part A notification, dated 20 October 2024, describes the release as “Smoke emitted and process gas release from AGCCE Steam Pyrolysis section”, the substances potentially released as “Smoke, AGCCE process gas (TFE, Hexafluoropropene, Chlorodifluoromethane)”, and the quantity as “TBC”. AGC’s investigation report (investigation period 19 October to 13 November 2024) says “a fire started within lagging of SP1”, that “approximately 275 m3 of process gas was released of which a significant portion was combusted”, that there were no injuries, and that the main cause was a lagging repair “not undertaken in accordance with specification (incorrect material used)” with “no independent inspection of the lagging utilised by the contractor”. These are AGC’s own account and estimates; we have seen no independent measurement of what was released. Neither document mentions ambient air monitoring, and the Agency’s reply did not include any; whether any was done remains an open question on Open questions. The paragraphs below are as written in July 2026, with the dated corrections that followed.

Corrected 18 October 2026: this section gave a pyrolysis temperature (650 to 800 °C), said the chemistry “is associated with” hydrogen fluoride and perfluoroisobutene, and called the unit “arguably the most hazardous process on the site”, without a source for any of these; the temperature and the hydrogen fluoride clause are removed and the ranking withdrawn. The pyrolysis route is now cited to Dalmijn et al. (2025), the naming of perfluoroisobutene to the fire-service log, and its toxicity to the OPCW schedule and Wingfors et al. (2022). See the changelog.

What the “Steam Pyrolysis section” is, and why it matters

At a fluoropolymer plant, steam pyrolysis is not a minor process. It is how the raw material is made. The monomer that Fluon and similar products are built from, tetrafluoroethylene, is made at Hillhouse by pyrolysis: Dalmijn et al. (2025) record that the “monomer tetrafluoroethylene (TFE) is also produced on-site through the pyrolysis of chlorodifluoromethane (HCFC-22)” (Environmental Science & Technology). In other words, this is very likely the chemical heart of the plant, the unit that makes the building block everything else depends on. That the whole works stopped for three months points to exactly that.

One substance named in the record of this fire is perfluoroisobutene (PFIB): the fire-service log records a caller naming it (the fire trains post). PFIB is listed as a toxic chemical in Schedule 2 of the Chemical Weapons Convention (OPCW, Annex on Chemicals), and Wingfors et al. (2022) describe PFIB and carbonyl fluoride as “reactive gases” that “are highly toxic and difficult to analyze in air” (Journal of Separation Science). We have not cited a source for how PFIB forms in fluoropolymer manufacture, and we are not saying any of it was released. We are saying this is the part of the plant that makes the monomer, and it is the part that caught fire.

(We have identified the unit from its name and from the standard chemistry of fluoropolymer manufacture. AGC can confirm or correct what the Steam Pyrolysis section does.)

What the rules require, and what they do not

The Health and Safety Executive’s public register under the Control of Major Accident Hazards Regulations 2015 (COMAH), checked on 14 October 2026, lists AGC Chemicals Europe, Limited at Hillhouse International, Fleetwood Road North, as an establishment subject to COMAH and as a “Lower Tier” establishment. It gives 17 January 2024 as the date of the last planned COMAH site visit by the competent authority. Our FOI request 202602243 to the HSE on the site’s COMAH status has not been answered. Under separate safety law, RIDDOR, a fire that suspends normal work for more than 24 hours is a reportable “dangerous occurrence.” This fire suspended work for about three months. On the face of it, then, it should have been reported to the HSE. AGC has since confirmed to us that it was, and that the Environment Agency was told as well.

But here is the gap. Under COMAH 2015, the duty to send safety information to those likely to be affected, without being asked, falls on the operator of an upper tier establishment (regulation 18: “An operator of an upper tier establishment must ensure that…”). The register lists this site as lower tier. Under regulation 17(1) the competent authority must make baseline information about every establishment available to the public. So the regulators were informed, and the shareholders were informed. The people living against the fence were told a commercial building on their road had caught fire.

The question that leaves

AGC says it informed the regulators at the time; the Environment Agency’s record confirms it was notified, and the HSE has not yet confirmed. The shareholders were told it had cost three months of production. Until September 2026 the public record consisted of the accounts’ note and a fire-service line about a commercial building fire; what burned and what was released became public through the Agency’s disclosure of AGC’s own reports. That raises a fair question: what does this site’s duty to warn the community actually amount to, when the process that makes its monomer runs next door to homes?

“The community and the environment”

AGC’s own 2024 accounts state that its directors weigh “the community and the environment,” and the company’s reputation for high standards, in how they run the business. A fire that shut the plant for three months, whose cause and release were, so far as we have found, first described publicly in the Agency’s disclosure of September 2026, is that stated commitment set against what was said to residents at the time.

The questions we asked

We put these to AGC on 15 July 2026 and again on 23 July:

  • What burned, and what came off it? Was the surrounding air monitored during the fire and its aftermath?
  • Was the fire reported to the HSE and the Environment Agency, as the rules appear to require?
  • Did the fire service issue any advice to nearby residents at the time?
  • Why was the public not informed of a fire that shut a major-hazard chemical plant on a residential boundary for three months?
  • And is a warning regime that requires nothing to be said to the neighbours adequate for a plant on a fenceline?

The company answered the second. It declined the rest. Its full response, and a timeline, are in Updates and responses at the foot of this article.

How we know what we know

The fire: AGC Chemicals Europe Ltd accounts, Companies House company 03825057 (the going-concern note and the contingent-asset note in the 2024 filing). The site’s COMAH tier: HSE’s COMAH 2015 public information register (notifications.hse.gov.uk/COMAH2015), establishment “Thornton Cleveleys”, operator AGC Chemicals Europe, Limited, “Upper or Lower tier Establishment? Lower Tier”, checked 14 October 2026; regulations 17 and 18 as published on legislation.gov.uk. HSE has not answered FOI 202602243. The reporting rule: HSE guidance on RIDDOR dangerous occurrences. The chemistry: the published safety literature on tetrafluoroethylene manufacture. Every one of these is public, and we will point you to it.


Updates and responses

Timeline

Date What happened
19 October 2024 Fire in the Steam Pyrolysis section. Lancashire Fire and Rescue logs incident 2410007359 as a “commercial building fire” on Fleetwood Road North
September 2025 AGC’s 2024 accounts filed at Companies House, recording the fire and a three-month outage
14 July 2026 This article published
15 July 2026 Hillhouse Watch puts questions to AGC Chemicals Europe and invites comment
22 July 2026 AGC responds
23 July 2026 Hillhouse Watch puts three further questions, reply requested by 6 August
4 August 2026 AGC responds again, declining the three further questions
5 August 2026 AGC’s response published here in full. Article corrected on the fire-service record

AGC’s response, in full

AGC Chemicals Europe replied on 22 July 2026 and again on 4 August. The company asked that its response be attributed to “an AGC Chemicals Europe, Ltd. spokesperson,” noting that it “has been developed by an internal team and approved by our Directors.” It confirmed it had no objection to publication. On the fire, the statement reads:

“On the fire, this was reported at the time, in line with regulatory obligations, we informed the Health and Safety Executive (HSE) and the Environment Agency (EA) of the incident. The Lancashire Fire and Rescue Service also published details here [the company’s link was to the Lancashire Fire and Rescue Service page ‘Commercial building fire in Thornton Cleveleys’].

The fire was relatively short lived but the reason why work was suspended for three months was because the fire damaged equipment and pipework critical to the manufacturing process, and the replacement equipment had long delivery times. We also implemented a thorough investigation before restarting operations. No enforcement action was taken by the relevant authorities.”

Asked on 23 July to answer three further points, the company replied on 4 August:

“Regarding the fire, there is little more that I can add. As you say, this is a matter of public record. Such incidents are taken extremely seriously by the relevant authorities such as the emergency services, the Health and Safety Executive (HSE) and the Environment Agency (EA) and we would not comment on their operational decisions, actions and assessments.”

Question by question, and what we can confirm

We have set this out plainly rather than summarising, because the difference between “AGC has told us this” and “we have confirmed this” matters. Everything in the middle column is the company’s account. The right-hand column is what we have been able to establish independently.

Our question AGC’s answer What we take it to mean Have we been able to verify it?
What burned, and what came off the site? Was the air monitored? Declined twice No answer to us. AGC’s documents disclosed by the Environment Agency on 2 September 2026 say lagging on SP1 burned; the notification lists the substances “potentially released” as smoke and process gas (TFE, hexafluoropropene, chlorodifluoromethane), and the later investigation report estimates about 275 m³ of process gas released, a significant portion combusted (see the update above) Partly. What burned and what was released are AGC’s account, now on the public record. We have found no air monitoring data for 19 October 2024 in any public source and cannot say from that whether monitoring happened and is unpublished, or did not happen
Was the fire reported to the HSE and the Environment Agency? “we informed the Health and Safety Executive (HSE) and the Environment Agency (EA) of the incident” Both regulators were told at the time Partly. The Environment Agency’s own record, disclosed on 2 September 2026, confirms it was notified on the evening of the fire (Open questions). The HSE has not yet answered
Did the fire service issue any advice to residents? Declined No answer Partly. The Lancashire Fire and Rescue entry we have found carries no advice to residents. We cannot rule out advice given by some other route that leaves no public record
Why were residents not told it was a major-hazard site? Declined No answer Not applicable
Was any enforcement action taken? “No enforcement action was taken by the relevant authorities” Neither the HSE nor the EA took formal action Not yet. AGC’s account. Checkable with both regulators, and we are asking
Why was the plant down for three months? Fire “damaged equipment and pipework critical to the manufacturing process,” long replacement lead times, plus an investigation before restart The outage was caused by damage and procurement delay rather than by the length of the fire itself No. This is AGC’s account of its own plant and we have no way to test it. It is the first explanation anyone has given

What that answers, and what it does not

Answered in part. AGC says the fire was reported to the HSE and the Environment Agency and that no enforcement action followed. The Environment Agency’s record, disclosed on 2 September 2026, confirms it was notified on the evening of the fire; what that record and the Agency’s compliance reports show is set out on Open questions. The HSE has not yet answered.

Newly stated. The three-month outage was caused by fire damage to “equipment and pipework critical to the manufacturing process,” with long replacement lead times, plus an investigation before restart. That is AGC’s own account, and it is the first explanation anyone has given. It also sits oddly beside the description of the fire as “relatively short lived”: a brief fire that destroyed critical pipework and halted a chemical plant for three months.

Not answered. Three of our questions were put twice and remain unanswered:

  • What burned, and what came off the site during the fire and its aftermath. Was the surrounding air monitored?
  • Did the fire service issue any advice to nearby residents at the time?
  • Why were residents not told the fire was at a major-hazard chemical site on their boundary?

The reason the company gives for declining is that it “would not comment on their operational decisions, actions and assessments,” meaning those of the emergency services, the HSE and the EA. We would note, without inviting any inference, that this does not answer the first question. What burned on AGC’s own plant, and whether the air around it was monitored, is AGC’s own knowledge. It is not an operational decision of the emergency services.

We put the questions. The company chose not to answer them. Readers can weigh that for themselves.

The company’s statement is reproduced above in full and unedited. Where we have summarised, we have said so.

Status, 28 September 2026: the Health and Safety Executive has not answered our request of 5 August for the RIDDOR report, its response and any enforcement action. Its own stated deadline was 4 September 2026. We have reported this to the Information Commissioner’s Office. Open questions

Corrected 18 October 2026: the title, summary and several passages still said the only public record did not say what burned and that the fire’s nature “has not been made public”. AGC’s notification and investigation report, disclosed by the Environment Agency on 2 September 2026, describe the fire and the release on AGC’s account; the post now says so, dated, and keeps the record of what was public at the time. See the changelog.