By Fire Alarm BT, Founder, Fire Alarm Blueprint Trainer · Creator of the FireAlarmBT YouTube channel · reviewed against NFPA 72 & NFPA 70 principles
Duct Smoke Detector Supervisory and HVAC Shutdown Troubleshooting
Duct smoke detectors exist to stop an air handler from spreading smoke — so a detector that activates while the fan keeps running has failed at its one job. This case study follows that exact call and shows how programming, relay wiring and the HVAC interface are traced and corrected.
The setting
Medical office building, addressable FACP. AHU-2 (12,000 CFM) has a return-air duct smoke detector programmed as a supervisory that must shut the unit down. Annual test, occupied building.
SUPERVISORY: DUCT DETECTOR
AHU-2 RETURN · ADDR 044 · FAN STILL RUNNING
What the technician found on arrival
You introduce test smoke at the AHU-2 duct detector. The panel posts SUPERVISORY — DUCT DETECTOR AHU-2 as expected, but the air handler keeps running. The building engineer says it 'always shut down before.'
The question
The detector works, the signal is right, but the emergency control function did not happen. What do you do?
Step-by-step: what the technician did and why
- 1
Confirm the sequence of operation in the panel program
The duct detector's supervisory must be mapped to an output (control relay) that opens the fan starter's control circuit. If the mapping was lost or changed, the detector still reports but nothing happens.
FindingPanel program shows ADDR 044 mapped to relay module R-07 'AHU-2 SHUTDOWN'. The mapping is intact.
- 2
Verify the relay module actually operated
Follow the chain: input → program → output. Check the relay's LED or read its status while the supervisory is active, then meter the contacts.
FindingR-07 LED shows active and the contacts change state — the panel side is doing its job.
- 3
Trace the shutdown circuit to the fan starter / BAS
Between the relay and the fan is the field interlock: wiring to the starter's holding circuit or a BAS input. A jumper, a bypassed interlock, or a BAS 'override' will keep the fan running.
FindingAt the starter, the fire alarm interlock terminals are jumpered with a red wire. A controls contractor added it during a BAS upgrade last spring.
- 4
Check the detector's sampling tubes and location
While you're there, confirm the sampling tube spans the duct width, holes face the airflow, and the exhaust tube is installed — an unreliable sample gives intermittent shutdowns.
FindingSampling tube correct; airflow status LED normal. Detector installed 8 duct diameters downstream of the bend — fine.
- 5
Remove the jumper with the controls contractor and retest end to end
Coordinate with the BAS/mechanical contractor so the interlock is restored the way the design intended (hardwired shutdown, not software). Then retest from smoke to fan stop.
FindingJumper removed; interlock rewired to the hardwired shutdown. Test smoke → supervisory → R-07 → AHU-2 stops within 10 s. Fan restarts only on panel reset.
- 6
Document the impairment and the correction
The interlock was defeated for months. Record it, notify the owner in writing, and recommend the BAS contractor coordinate future work with the fire alarm contractor.
FindingOwner notified; recommendation added. Duct detector marked 'passed' with the shutdown verified.
Key takeaways
- •A duct detector test is not complete until the fan actually stops.
- •Follow the chain: input → program → relay → field interlock → starter.
- •Jumpers from 'other trades' are the #1 cause of defeated emergency control functions.
- •Hardwired shutdown per design — never rely on a software override.
Code references
NFPA 72 · 21.7 — HVAC Systems (Emergency Control Functions)
Duct smoke detectors must shut down the fan per NFPA 90A; the shutdown interface is an emergency control function that must be tested.
NFPA 72 · 17.7.5.5 — Duct Smoke Detectors
Location and installation of duct detectors, including sampling tube placement and access.
NFPA 72 · 14.4 / Table 14.4.3.2 — Emergency Control Functions
Verify that the control function (fan shutdown) actually operates — not just that the signal is received.
Section numbers vary between editions. Always verify against the edition adopted by your Authority Having Jurisdiction (AHJ).
Sample service report
Found
Annual test 10:40. AHU-2 return duct detector (ADDR 044) produced SUPERVISORY at FACP with test smoke, but AHU-2 did not shut down. Relay R-07 operated correctly.
Cause
Fire alarm shutdown interlock at AHU-2 starter jumpered (red wire) during BAS upgrade by controls contractor; hardwired shutdown defeated.
Action taken
Jumper removed with controls contractor present; interlock rewired to hardwired shutdown per design. Sampling tubes verified.
Verification
Retest: test smoke → SUPERVISORY → R-07 → AHU-2 stopped within 10 s; restart only on reset. Owner notified in writing of the period the shutdown was defeated. Recommend trade coordination for future BAS work.
Practice this call in the Troubleshooting Lab
Work through the same scenario step by step, with wrong-move feedback and a downloadable completion certificate. Free, no account required.
Frequently asked questions
Should a duct smoke detector cause an alarm or a supervisory signal?
NFPA 72 permits duct detectors used for HVAC shutdown to initiate a supervisory signal instead of an alarm, provided they are not relied on for occupant notification. The design documents and AHJ determine which is used on a given project.
How is fan shutdown tested during an annual inspection?
Activate the duct detector (per the manufacturer's method), confirm the panel receives the correct signal type, and verify the air handler actually stops. The relay path and HVAC control interface must be tested end to end, not just the detector.
Related guide: Fire Alarm System Design Basics
This case study is educational. It does not replace the manufacturer's instructions, the currently adopted codes and standards, a licensed designer or engineer, or review by the Authority Having Jurisdiction.