AABC Test and Balance Engineer (TBE) common mistakes
AABC Test and Balance Engineer (TBE) · Understand the traps and how to avoid them.
Applying a single fan-law correction to a measured airflow without first confirming the measurement plane meets straight-duct and traverse criteria, then reporting the corrected value as the definitive cfm.
Candidates memorize the affinity laws and reach for them as a universal correction; they skip the prerequisite that the traverse location itself be valid, so a bad baseline gets mathematically 'improved' rather than rejected.
What to do instead
Before any correction, verify duct geometry (upstream/downstream straight lengths, traverse-point count, absence of obstructions) and document it. If the plane fails, relocate or use an alternate method; report corrected values only from a valid baseline.
Reading dry-bulb and wet-bulb from a sling or digital psychrometer and entering them into a chart without correcting for the actual barometric pressure at the site.
Standard sea-level psychrometric charts are what candidates practiced on, and the pressure dependence of humidity ratio and enthalpy is easy to overlook under time pressure.
What to do instead
Record local barometric pressure with the psychrometric data and use a pressure-corrected chart or software. State the pressure basis on the data sheet so the enthalpy/ humidity-ratio values are traceable.
Treating a single-point or centerline velocity reading as representative of average duct velocity, then multiplying by area to get cfm.
Single-point pitot or anemometer measurements are fast and produce a plausible number; candidates underestimate how much velocity profile skews the result.
What to do instead
Perform a proper velocity traverse (log-linear or equal-area method per the applicable standard), average the velocities, and apply the density correction. Reject single-point estimates for reporting.
Reporting instrument readings to more significant figures than the instrument's accuracy and calibration status support, and omitting calibration due dates from the report.
Candidates equate a digital display's resolution with its accuracy, and they treat calibration records as paperwork rather than part of the measurement result.
What to do instead
Report values with an uncertainty statement consistent with instrument accuracy, resolution, and calibration traceability. Include instrument ID, calibration date, and due date in the report appendix.
Balancing a hydronic circuit by adjusting the balancing valve until flow 'looks right' on a readout without verifying the pump curve operating point or confirming gauge/flow-meter calibration.
Candidates chase the terminal flow number and forget the system-level interaction; pump speed, suction conditions, and instrument error all shift the true operating point.
What to do instead
Establish the pump operating point first (differential pressure vs. curve), verify flow-meter calibration, then proportionally balance branches and recheck the system total and pump operating point after adjustments.
Setting building pressurization by adjusting a single exhaust fan or relief damper without measuring the pressure differential across the envelope at multiple locations and under design outdoor conditions.
A single manometer reading at one door is easy to obtain and looks convincing; candidates miss that stack effect, wind, and multiple zones make one reading unrepresentative.
What to do instead
Measure envelope differential pressure at several representative locations and at more than one operating condition (e.g., design and part-load), and coordinate supply/exhaust/relief together. Document the test conditions.
Assuming a DDC point is reading the true value because the graphic shows a number, without verifying sensor calibration, point mapping, or that the trend matches an independent field measurement.
Candidates trust the BAS interface as ground truth and skip the cross-check between the control system value and a calibrated field instrument.
What to do instead
Cross-check each critical point against an independent calibrated instrument, verify point-to-physical mapping, and review trends for plausibility. Note any discrepancy between BAS value and field measurement in the report.
Submitting a report that lists measured values but omits design values, tolerances, and pass/fail determination, leaving the reader unable to judge compliance.
Candidates focus on collecting data and treat the report as a data dump; they don't structure it around the standard's required comparisons.
What to do instead
Build the report around a design-vs-measured-vs-tolerance table with explicit pass/fail, cite the governing standard and its acceptance criteria, and include deficiencies with corrective recommendations.
Proceeding with a test that requires occupied-space or confined-space entry without completing a hazard assessment, permit, or PPE check because the schedule is tight.
Schedule pressure and the desire to 'get the reading' override safety procedure; candidates underestimate how often test locations involve confined spaces, energized equipment, or fall hazards.
What to do instead
Complete the hazard assessment and required permits before entry, confirm PPE and atmospheric monitoring, and stop work if conditions change. Safety takes precedence over schedule; document the decision.
Accepting a verbal scope change or field directive from a contractor without written authorization, then performing the added work and billing or reporting it as if it were in scope.
Candidates want to be helpful and avoid conflict on site; they conflate cooperation with authority to change contract scope.
What to do instead
Route any scope change through a written change order or RFI with owner/engineer authorization before performing the work. Document verbal directives and confirm them in writing the same day.