Every enclosed parking garage needs CO detection — that part isn’t really a design decision, it’s a code requirement in most jurisdictions. Whether it also needs NO₂ detection is where the actual engineering judgment comes in, and getting it wrong in either direction has real consequences: skip NO₂ where it’s needed and you leave a genuine exposure risk uncovered even while the CO system reads clean; add it where it isn’t needed and you’ve added sensor cost and maintenance burden without a corresponding safety benefit. This guide walks through how to actually make that call.
Note up front: this article uses commonly cited setpoints and code references as working examples, not a substitute for checking the specific code edition and any local amendments your authority having jurisdiction (AHJ) has adopted. Verify actual design values against the adopted code before finalizing a system.
Two Gases From Two Different Fuel Sources
Carbon monoxide (CO) is a byproduct of incomplete combustion, and in a parking garage context it’s overwhelmingly associated with gasoline engine exhaust. It’s colorless and odorless, which is exactly why detection matters — there’s no sensory warning before concentrations become dangerous.
Nitrogen dioxide (NO₂) is a byproduct specifically associated with diesel engine exhaust. Diesel combustion produces meaningfully more NO₂ relative to CO than gasoline combustion does, which is the whole reason NO₂ detection exists as a separate design question rather than being automatically bundled with CO detection everywhere.
The practical consequence: a garage with a CO-only detection system is only watching half the picture if diesel vehicles are a regular part of its traffic. A CO sensor doesn’t reliably indicate NO₂ concentration, and vice versa — they’re independent measurements of independent contaminants.
When NO₂ Detection Is Actually Needed
NO₂ detection is specifically relevant anywhere a meaningful volume of diesel-powered vehicles will be present, which in practice means:
- Bus and truck maintenance garages
- Rapid transit and rail facility parking and service areas
- Loading docks and shipping/receiving areas with truck traffic
- Ambulance bays and other emergency-vehicle facilities
- Car dealership service areas where diesel vehicles are tested or serviced
- Any mixed-fuel parking structure with a regular diesel presence, not just occasional delivery trucks
A standard residential or light-commercial parking garage serving passenger cars is overwhelmingly a gasoline-exhaust environment, which is why CO-only detection is the typical baseline there. The moment diesel vehicles become a regular rather than incidental part of a garage’s traffic, that assumption stops holding.
The Code Basis
In the US, enclosed parking garage ventilation requirements are primarily governed by the International Mechanical Code (IMC) — commonly cited as Section 404.1 in recent editions — which requires mechanical ventilation for enclosed garages, either running continuously or automatically controlled by gas detection. The International Fire Code (IFC) works alongside it, and both are typically adopted (sometimes with local amendments) rather than applied nationally as written. Whether NO₂ detection is explicitly required, merely recommended, or left to engineering judgment varies by jurisdiction and by the specific occupancy — this is one of the places a local AHJ conversation early in design saves rework later.
One distinction worth confirming early: mechanical ventilation requirements generally apply to enclosed garages specifically — a garage with large permanent openings that qualifies as “open” under the adopted code is often treated differently and may not trigger the same mechanical ventilation and detection requirements at all. Confirm which category a given structure falls into before assuming detection is required.
Typical Setpoints — Illustrative, Not a Design Standard
Gas detection controllers generally use a multi-stage setpoint structure rather than a single on/off threshold: a rising trip point that engages ventilation, a falling trip point that disengages it once concentration drops, a second-stage rising point for higher demand, and a separate alarm level for occupant notification. Commonly cited example values (they vary by manufacturer guidance and adopted code, so treat these as illustrative rather than a value to design directly against):
| Stage | CO (example) | NO₂ (example) |
|---|---|---|
| Rising trip point (ventilation on) | ~25–35 ppm | ~2.5 ppm |
| Falling trip point (ventilation off) | ~15 ppm | ~1.2 ppm |
| Alarm level | ~100–200 ppm | ~5 ppm |
The gap between CO and NO₂ setpoints looks large in raw ppm terms, and that’s expected — NO₂ is a more potent irritant at lower concentrations than CO, so its thresholds are set proportionally lower. Don’t read the smaller NO₂ numbers as “less serious”; they’re calibrated to a different exposure curve, not a lower priority.
Sensor Placement
Both CO and NO₂ sensors are typically installed at breathing-zone height — commonly cited as roughly 4 to 6 feet above finished floor — since occupant exposure is the actual concern, not just contaminant presence somewhere in the space. Sensor placement should also account for airflow patterns and known concentration sources: near ramps, entry/exit points, and anywhere vehicles idle or queue, rather than spread purely on a uniform grid regardless of how the garage is actually used.
Reasoning Through a Selection
- Establish the actual vehicle mix, not just the occupancy type on paper — a “residential parking garage” that also serves a loading dock or ambulance bay isn’t a pure gasoline-exhaust environment anymore.
- Confirm the applicable code edition and any local amendments with the AHJ before finalizing whether NO₂ detection is required, recommended, or a judgment call for this specific project.
- Determine whether the garage is “open” or “enclosed” under the adopted code definition, since that classification changes whether mechanical ventilation and detection requirements apply at all.
- Select detection technology and setpoints against the confirmed code requirement, not a generic example table — the specific numbers your AHJ has adopted are the ones that matter for compliance.
- Plan sensor placement around actual traffic and airflow patterns, not just a uniform spacing grid, prioritizing breathing-zone height and known contaminant source areas.
- Confirm the ventilation control strategy is demand-controlled, tied to actual sensor readings, rather than a simple time-switch schedule — a time-switch runs the system regardless of whether contaminant levels actually warrant it, defeating much of the energy-saving benefit of installing sensors in the first place. (This garage-ventilation logic is itself a form of demand-controlled ventilation — see our demand-controlled ventilation guide for how the same strategy applies to CO2-based occupancy control elsewhere in a building.)
Common Mistakes
- Assuming CO detection alone covers all exhaust-related risk. CO and NO₂ are independent contaminants from different combustion processes; a CO-only system provides no reliable information about NO₂ levels.
- Treating NO₂ detection as automatically required everywhere, adding cost and maintenance burden to a pure-gasoline garage that doesn’t need it, when the actual trigger is diesel vehicle presence, not garage size or type alone.
- Overriding a demand-controlled system with a time switch, which runs the ventilation system on a fixed schedule regardless of actual gas concentration and undermines the point of installing sensors.
- Designing to a generic setpoint table instead of the adopted code. Example setpoints vary between sources and manufacturers; the AHJ’s adopted code edition is the actual design requirement.
- Placing sensors on a uniform grid without regard to airflow or traffic patterns, missing localized concentration buildup near ramps, entries, or idling areas.
Frequently Asked Questions
Does every parking garage need NO₂ detection?
No. The determining factor is diesel vehicle presence, not garage size or general occupancy classification. A passenger-car-only garage is typically a CO-only design; a garage with regular bus, truck, or diesel service traffic typically needs both.
Can one sensor detect both CO and NO₂?
Combination CO/NO₂ detectors exist and are common in parking garage applications specifically because both gases are frequently relevant together in mixed-traffic facilities — check the specific product’s sensing technology and calibration requirements for each gas rather than assuming a combination unit performs identically to two dedicated single-gas sensors.
How does this connect to overall CO safety thresholds?
For the general exposure and action-level chart for CO specifically (not garage-ventilation setpoints), see our carbon monoxide levels chart. For product-level sensor selection guidance, see our best CO sensors for parking garages guide.
What communication protocol do modern gas detection controllers typically use?
Many current parking garage gas detection controllers support BACnet for integration with the building’s BMS, alongside traditional relay outputs for direct fan control. See our BMS control signals guide for how BACnet fits into the broader control-signal picture.
