United Kingdom · guide · 5 October 2026
Reading stack emission limit findings on a CAR
Combustion plant, crematoria, industrial dryers and energy-from-waste units often carry permit emission limit values (ELVs) with stack testing or continuous monitoring conditions. CAR non-compliance rows may cite exceedances, broken abatement, missing MCERTS monitoring, or incomplete emissions reports. Operators read those lines to map actions and permit tables — not to redesign abatement from a guide.
Free CAR check · £19.99 Full CARBrief · £49.99 Permit + CAR Review
Where emission rows sit on the form
- Emissions monitoring — emissions monitoring findings.
- Monitoring data — monitoring data findings.
- Abatement / plant maintenance — may overlap competence and training findings.
- Odour and amenity — distinct from ELV rows — odour, dust and noise findings.
Common breach descriptions
| CAR wording pattern | Plain-English reading |
|---|---|
| ELV exceeded for [pollutant] | Emission limit breach — note stack and averaging period in CAR text |
| Abatement plant not operational | Plant availability finding — may be separate condition |
| Stack test not undertaken | Monitoring schedule breach |
| CEMS / MCERTS monitoring failure | Continuous monitoring infrastructure row |
| Emissions report not submitted | Documentation / management system theme |
Permit conditions and improvement schedules
Match cited conditions — linking findings to permit conditions, improvement conditions on permits, standard rules vs bespoke permits.
Scores and escalation
Read category and points per row — CCS scores, what C1 means on a CAR, site warning explained.
Response deadlines
Officer actions may require retesting, plant repair or revised monitoring plans by a date — CAR response deadlines, what happens after a CAR, enforcement notice vs CAR.
Worked example — ELV vs reporting rows
A combustion site CAR might include:
- Row 1: “Stack test showed NOx exceedance against ELV on Stack A.”
- Row 2: “Annual emissions report not submitted by due date.”
Row 1 is an emissions performance finding; Row 2 is documentation — actions and deadlines may differ. Pull Stack A limits from the permit table — how to read a permit.
Common misreadings
- Worst pollutant name assumed to mean C1. Always read printed category on the row.
- Abatement offline rolled into ELV exceedance without reading text. Separate remedial tracks.
- Odour complaints merged with ELV breaches. Amenity rows differ — odour and dust guide.
- Improvement plan conditions ignored after repeat test failures. See improvement conditions on permits.
CAR row triage checklist
| Capture | Notes |
|---|---|
| Stack / plant reference | Permit schedule alignment |
| Pollutant and ELV cited | Averaging period in CAR text |
| Test vs CEMS vs report miss | Three different breach types |
| Category and points | Per row on tracker |
| Officer action date | Response deadlines guide |
Why ELV rows are not interchangeable
Permits often set different averaging periods, reference conditions and stack identifiers for each pollutant. A CAR line citing NOx on Stack A does not automatically describe SO2 performance on Stack B. Compliance teams build spreadsheets per stack and pollutant because the EA publishes findings the same way — CARBrief mirrors that granularity in sourced readings rather than collapsing rows into a single “emissions fail” summary.
After an exceedance, follow-up assessments may be scheduled — track what happens after a CAR for process literacy only.
Batch vs continuous monitoring
Permits may require annual stack tests while continuous monitors cover daily variability — a CAR row about missed stack testing is not automatically an ELV exceedance row. Read how to read a CAR section headings to see which assessed area the officer marked non-compliant. When both appear, list separate actions and deadlines.
Trade effluent and energy recovery overlap
Sites with co-located processes may carry trade effluent findings on the same visit — do not merge remedial tasks without reading each cited condition. Energy-from-waste lines may reference ammonia or HCl limits distinct from greenhouse gas reporting.
Management system overlap
Missing emissions reports may be classified under management system findings rather than emissions monitoring — search the whole CAR PDF before assuming the row lives in one section only.
Keep stack test certificates with the CAR row citation so responders can match pollutant, stack ID and test date to the officer wording.
Reading checklist
- List each emission-related non-compliance with cited condition and stack reference if printed.
- Separate ELV exceedances from monitoring/reporting failures.
- Pull permit ELV tables and monitoring frequency for that stack.
- Record category/points per row.
- Note whether abatement plant availability is cited separately from test results.
Questions
Where do stack emission findings appear on a CAR?
Under emissions monitoring, abatement plant, or monitoring data rows when the CAR cites permit ELVs, stack testing or continuous monitoring conditions.
Are emission exceedances always high category scores?
Category and points depend on the printed CAR line — read C1–C4 labels per row; do not assume from pollutant name alone.
Will CARBrief calibrate stack testing equipment?
No. CARBrief reads published CAR wording. Stack testing and abatement engineering are for your environmental consultant.
Is abatement plant offline treated the same as an ELV exceedance on a CAR?
Often separate rows with different cited conditions. Read plant availability and test result lines independently.
Do missing MCERTS reports always appear under monitoring data?
Usually monitoring or management system sections — but the CAR headings vary by site. Search the PDF for MCERTS, CEMS and reporting phrases.
All guides: /guides/. Related: emissions monitoring findings, competence and training findings.