.png)
A VAV box can run out of design tolerance for months without ever generating a building automation alarm, because most BAS alarm thresholds trigger on hard failures while missing the gradual drift that actually wastes the most energy. Periodic testing and balancing, run against a measured reference rather than the BAS's own reported values, is what catches a box that looks fine on the graphics screen but is quietly costing the building money.
Why Do These Faults Stay Hidden?
The BAS trusts its own sensors. If a VAV box's airflow sensor has drifted 12 percent below calibration, the controller still reports a number, adjusts the damper to chase that number, and closes the loop successfully by its own logic. That sequence satisfies every check the controller runs on itself, so it operates alarm-free, because the system is doing exactly what it was told to do with the (wrong) information it has. The same holds for a damper that sticks at 65 percent open while the zone calls for minimum airflow during unoccupied hours: the position looks plausible on a trend graph unless someone compares it against what the control sequence actually commanded.
Industry estimates suggest that around 30 percent of VAV boxes in a typical commercial building are operating with some degree of fault at any given time, with waste from these hidden faults running an estimated 5 to 30 percent of that zone's HVAC energy use. That estimate deserves a grain of salt on any individual building, but the underlying mechanism is well established: a fault that stays below the alarm threshold can run indefinitely, because the system lacks any mechanism built to notice it.
What Are the Most Common VAV Fault Types?
| Fault | Typical Cause | Why the BAS Misses It |
|---|---|---|
| Damper position mistracking the control signal | Actuator gear wear, shaft binding, feedback sensor drift | Position holds steady even as commanded signal changes, and steady looks stable rather than stuck |
| Airflow sensor drift | Dirty sensing ports, pitot tube blockage, uncalibrated transducer | Reported flow still moves in the right direction, so the loop looks like it's working |
| Incorrect minimum airflow setpoint | Programming error, outdated occupancy assumption, box resized after a tenant change | The box hits its programmed setpoint every time, which is a pass on its own terms even when that setpoint is wrong |
| Simultaneous heating and cooling | Stuck reheat valve, failed actuator that fails to close | Zone temperature can still land near setpoint through brute-force energy use, masking the underlying conflict |
What Tolerance Does TAB Testing Actually Check Against?
ASHRAE and NEBB testing and balancing standards set the commissioning tolerance for VAV airflow verification at within 10 percent of design value, measured with a flow hood or traverse, compared against the design schedule rather than the BAS readout. Minimum airflow setpoints get checked against ASHRAE 62.1 ventilation minimums for current occupancy, with a target window of roughly 5 percent above that minimum, capped at 15 percent above it, since overshooting the ventilation minimum by too wide a margin wastes conditioning energy even though it clears the code requirement.
How Is a VAV Box Actually Tested?
A functional VAV test commands the box to its minimum and maximum airflow setpoints through the BMS, then measures actual delivered airflow at the diffuser with a flow hood or pitot traverse rather than reading the number the BAS reports. The two numbers get compared: agreement within 10 percent at both ends of the range is a pass, and disagreement points to sensor drift, a leak between the box and the diffuser, or a k-factor that was entered incorrectly during original setup. Actuator stroke gets checked at full travel in both directions, damper position feedback gets verified against physical position within 5 percent, and reheat coil operation gets confirmed where fitted.
ASHRAE Guideline 36 fault detection and diagnostics sequences extend this idea into continuous monitoring between TAB visits, comparing each box's actual airflow, damper position, and zone temperature against expected values in the BAS itself and flagging deviations automatically. This is the same underlying concept behind Monitoring-Based Commissioning (MBCx): rather than treating a VAV test as a one-time snapshot at handover, MBCx layers continuous analytics on top of the BAS to flag a box drifting out of tolerance long before the next scheduled TAB visit would catch it. Guideline 36 and MBCx logic both catch faults sooner between commissioning cycles, though they work from the same BAS-reported data that can drift undetected in the first place, which is exactly why a periodic field measurement against an independent reference instrument still matters even in a building running continuous fault detection.
Frequently Asked Questions
Why can a faulty VAV box run for months without anyone noticing?
Because most BAS alarms trigger on hard failures like communication loss, while gradual drift in an airflow sensor or a damper that sticks at a plausible-looking position produces a data pattern the system reads as normal operation.
What's an acceptable margin of error for VAV airflow testing?
ASHRAE and NEBB commissioning standards set the tolerance at 10 percent of design value, measured independently with a flow hood or traverse rather than read off the BAS.
Does a VAV box that reaches its programmed setpoint always mean it's working correctly?
It confirms the controller is following its own programming, which still leaves open the possibility that the setpoint itself is wrong, so functional testing checks the setpoint against ASHRAE 62.1 ventilation requirements and the original design schedule, independent of the box's internal pass/fail logic.
How often should VAV boxes get tested and rebalanced?
A common baseline is quarterly checks on actuator travel and BAS-reported airflow, with a full commissioning-level airflow and controls verification annually, though buildings with dense occupancy or WELL/LEED targets often move to a semiannual schedule for airflow calibration.
Does automated fault detection replace the need for TAB testing?
Automated fault detection and MBCx both catch deviations faster between visits, but they still rely on the same sensors and data the BAS already trusts, so periodic field testing with an independent measurement instrument remains the check on whether that underlying data is accurate to begin with.
Where to Start
VAV faults compound quietly, and the gap between a scheduled test date and a slow drift into 5 to 30 percent wasted zone energy is exactly where hidden faults do their damage. If your building's VAV boxes haven't had a functional test against independently measured airflow recently, or you're weighing whether continuous fault detection through MBCx makes sense across a portfolio of zones, Aero's testing and balancing team can walk through where your building stands today. Request a VAV testing assessment to get started.