Sidcup Waste to Energy Facility
Clinical Waste Incinerator operated by Stericycle (SRCL) and located adjacent to Queen Mary's Hospital, Sidcup, Kent.
| Sidcup Waste to Energy Facility | |
 See HT & Clin → page for a larger UK Wide map. | |
| Waste Licence | JP3133XP |
| Operator | SRCL |
| Operational Capacity | 8,500tpa |
| Number of Lines | 1 |
| Region | London |
Annual Report Data
| Year | Total In | Total Clinical | IBA Out | ACP Out | Op Hours
|
|---|---|---|---|---|---|
| 2019 | 7984 | 7933 | 1448 | 306 | 7984 |
| 2018 | |||||
| 2017 | |||||
| 2020 | 6305 | 6305 | 1250 | 261 | 7292 |
| 2021 | 6720 | 6720 | 1194 | 334 | 7424 |
| 2022 | 5250 | 5175 | 694 | 255 | 6161 |
Summary
Clinical Waste Incinerator operated by Stericycle (SRCL) and located adjacent to Queen Mary's Hospital, Sidcup, Kent.
The Sidcup Waste to Energy Facility incinerates clinical waste, including clinical wastes classed as hazardous under the Hazardous Waste (England and Wales) Regulations 2005. The bulk of the waste is produced at hospitals, but also includes smaller quantities from doctors’ surgeries, dentists, health clinics, residential and nursing homes, and from medical research facilities. The hazardous wastes incinerated include infectious waste and waste containing cytotoxic or cytostatic medicines.
The plant also incinerates small amounts of specialised wastes.
Plant[1]
Text to follow
The query SELECT "updated" FROM "db_ea"."ea_ew_in" WHERE epr='JP3133XP' LIMIT 1 is invalid (Error : SSL SYSCALL error: EOF detected
Function: EDConnectorRdbms::fetch Query: SELECT "updated" FROM "db_ea"."ea_ew_in" WHERE epr='JP3133XP' LIMIT 1 ).Error: Could not connect to database (Cannot access the database: Unable to connect to PostgreSQL server: connection to server at "10.106.0.2", port 5432 failed: FATAL: the database system is in recovery mode).Error: Could not connect to database (Cannot access the database: Unable to connect to PostgreSQL server: connection to server at "10.106.0.2", port 5432 failed: FATAL: the database system is in recovery mode).
Waste Tonnage, By Origin
The table shows a list of the Waste for the Permit JP3133XP, that has arrived into sites as reported to the Regulator and then publicised in their reported statistics. The Data used is from the most recent returns. The total reported tonnage arriving at the site was: Expression error: Unexpected < operator.t.
Where this tonnage exceeds that reported in year of the corresponding annual report, this may be due to the following reasons:
- Tonnage may have been received but not incinerated, i.e. the material is held pending incineration (the operator return to the EA reports as received whereas the annual report focuses on when the waste is incinerated.)
- Material may have been received into the site but treated in some other way than incineration.
- Material may have been received on the but transferred out of site for disposal/treatment at another site rather than incineration on the site.
| EWC Code | Origin of Waste | Tonnes In |
|---|
References
- ↑ Annual Performance Report 2020