Duct leakage is easy to specify badly. A line such as “ductwork shall be airtight” cannot be tested, priced or enforced. Leakage classification exists to turn that intention into a number.
What a leakage class is
In the SMACNA approach to duct leakage testing, a leakage class (CL) expresses how leaky a duct system is allowed to be relative to the pressure it is tested at. The commonly used relationship is:
F = CL × P^0.65
where F is the allowable leakage in cfm per 100 square feet of duct surface area and P is the test pressure in inches of water gauge. A lower class number means a tighter requirement.
A worked example
Suppose a specification requires Leakage Class 6, tested at 2 in. w.g.:
• P^0.65 = 2^0.65 ≈ 1.57
• F ≈ 6 × 1.57 ≈ 9.4 cfm per 100 sq ft
For a tested section with 5,000 sq ft of duct surface, the allowable leakage is roughly 50 × 9.4 ≈ 470 cfm at that pressure. (This is an illustration only; always apply the class, pressure and method required by your project specification.)
Test pressure matters
The same leakage class gives a different allowable airflow at different test pressures. The specification should state the test pressure explicitly, usually linked to the duct’s pressure class or the system’s operating pressure, so that everyone tests to the same basis.
Seal class is not leakage class
These terms are often confused. A seal class describes which joints and seams must be sealed during construction. A leakage class describes the measured leakage limit during testing. A project may use both, but they are different requirements and should not be used interchangeably.
Where standards and codes come in
Many projects are influenced by energy and mechanical codes and standards such as ASHRAE 90.1, the IECC, the IMC and the UMC, which can set requirements for sealing and, in certain cases, leakage testing of ducts. The exact requirements depend on the edition adopted and the local authority, so the project’s applicable documents should always be confirmed. Duct pressure testing carried out to SMACNA methodology gives a recognised way to demonstrate compliance.
What a good specification includes
• The leakage class (or maximum allowable leakage) for each system or pressure class.
• The test pressure for each.
• The proportion or sections of ductwork to be tested.
• The test method and equipment requirements.
• Who witnesses the tests and who approves the results.
• What happens on a failed test: sealing, retesting and any expansion of the sample.
• The reporting format and records to be handed over.
How a duct leakage test works
Although details vary by standard and project, the basic procedure is consistent:
- Define the section to be tested, including its surface area, so that allowable leakage can be calculated.
- Isolate the section by blanking off open ends, terminals and branches that are outside the test.
- Connect a calibrated test fan and flow-measuring device to the section through a suitable connection.
- Raise the pressure to the specified test pressure and hold it steady.
- Read the airflow needed to maintain that pressure, which equals the leakage at that pressure.
- Compare the result with the allowable leakage and record the outcome.
If the section fails, the leaks are located, sealed and the section is retested. Locating leaks can be done by listening, by feeling for air movement, or with smoke or other aids, depending on access and conditions.
Why surface area and sampling matter
Because allowable leakage is expressed per 100 square feet of duct surface, the area calculation must be correct. Small errors in area become errors in allowable leakage. Specifications also commonly define how much of the system must be tested and what happens if a tested section fails: for example, expanding the sample to additional sections. Where a specification is silent, disputes about sampling can arise at the end of the project, when time is shortest.
Common mistakes in specifying and testing
• Specifying a class with no test pressure, which leaves the allowable leakage undefined.
• Mixing up seal class and leakage class in the same clause.
• Testing after concealment, when access to repair leaks is limited.
• Not recording conditions, such as test pressure, equipment used and sections covered.
• Treating testing as a pass/fail event only, rather than as information about workmanship and the need for corrective action.
Why leakage class matters for performance
Leakage class is not only a compliance number. A tighter class generally means less conditioned air lost, lower fan energy to deliver a given airflow, and more predictable balancing, because the air arriving at each terminal is closer to what the design assumed. For consultants, setting an appropriate class is part of designing for delivered airflow. For contractors, building to the class and testing early is the most reliable way to avoid expensive repairs after the ceilings are closed.
Sealing and retesting
If a test fails, the corrective approach depends on the system. Leaks at joints and seams can be sealed by hand with approved sealants and tapes where access allows. Where ductwork is already concealed or access is difficult, other sealing methods may be considered. Whichever method is used, a retest at the specified pressure is the only way to confirm that the section now meets its limit.
Writing a clear acceptance clause
A short, unambiguous clause avoids most disputes. For example, a specification can state the leakage class for each pressure class of ductwork, the test pressure, the proportion of each system to be tested, the requirement to test before insulation and concealment, and the requirement to repair and retest any failed section at the contractor’s cost. When these elements are written clearly, testing becomes a routine quality check that all parties understand from the start, and the finished ductwork is far more likely to perform as the designer intended.
Conclusion
Leakage classification gives consultants and contractors a shared, measurable language. When class, pressure, scope and acceptance criteria are written clearly at the outset, testing becomes a routine verification step rather than a late-stage dispute.
