Alberta Stack Testing Code vs EPA Part 60

When a permit, approval, or performance test references both provincial and U.S. methods, the risk is not usually the sampling run itself. The real problem is assuming the Alberta Stack Testing Code and EPA CFR 40 Part 60 stack testing methods are interchangeable without checking how each framework handles method selection, quality assurance, and reporting. That assumption can create avoidable compliance gaps, especially when data must stand up to regulatory review.

For most industrial facilities, this is not a debate about which framework is better. It is a question of which one governs the test objective, and where the technical differences can change the final result. Boilers, heaters, engines, cement operations, combustion systems, and manufacturing sources often operate under approvals or reporting obligations that pull from both Canadian and U.S. references. In practice, that means a stack testing program has to be designed around the governing requirement, not around the method a team happens to know best.

Alberta Stack Testing Code Versus EPA CFR 40 Part 60 Stack Testing Methods

The Alberta Stack Testing Code is a provincial compliance framework that sets expectations for source testing, method use, planning, execution, and reporting within Alberta’s regulatory environment. EPA CFR 40 Part 60, by contrast, is tied to U.S. federal New Source Performance Standards and the reference methods incorporated into those standards. Both rely on established source testing procedures, but they do not serve exactly the same regulatory purpose.

That distinction matters. Alberta may accept, modify, or reference EPA methods, but acceptance of an EPA reference method does not automatically mean every procedural detail, deviation policy, or reporting element will be treated the same way under the provincial code. A test program can use the same train components and still fail to meet the applicable compliance expectation if the wrong framework was used to justify the work.

Where facilities usually see differences

Method selection is the first pressure point. EPA Part 60 methods are often highly prescriptive because they are written to support federal standards with defined applicability, run criteria, and calculation rules. Alberta’s code can incorporate those methods while adding requirements on pre-test submissions, operating conditions, documentation, and regulator-facing reporting. If a source test is being performed for an Alberta approval condition, the provincial code usually controls the overall testing and reporting approach, even when the analytical procedure comes from an EPA method.

Deviations are another common issue. Under EPA methods, minor field deviations may sometimes be addressed through documented technical justification, depending on the method and the applicable standard. Under Alberta requirements, the acceptability of a deviation may depend not only on technical equivalency but also on whether the regulator expects prior approval, explicit notation in the protocol, or a more conservative interpretation of method compliance. That is why deviation management cannot be handled as an afterthought once the field crew is on site.

Quality assurance expectations also deserve attention. Both systems value calibration, leak checks, traverse integrity, isokinetic control where applicable, sample recovery, and chain of documentation. The difference is often in how rigorously those elements must be presented in the final package and how the regulator expects the data narrative to be structured. A valid test is not just one that was run properly. It is one that can be defended clearly from planning through final report.

EPA reference methods are often the technical base, not the whole compliance answer

In many programs, EPA methods remain the technical backbone. Methods for particulate, moisture, gas concentration, velocity, molecular weight, and organics are widely recognized because they provide established measurement protocols. That familiarity is useful, especially at facilities with corporate standards spanning Canada and the United States.

Still, relying on EPA familiarity alone can create blind spots. If a facility team builds the protocol around CFR 40 Part 60 language but the approval requires Alberta-specific stack testing code compliance, the issue may not surface until protocol review or final report submission. At that point, fixing the problem can mean retesting, delayed reporting, or difficult discussions about data acceptability.

How to decide which framework should lead the program

Start with the regulatory driver. If the test is required by an Alberta approval, provincial code requirements should generally anchor the protocol, with EPA methods used where the code or approval references them. If the driver is a U.S. federal standard, then Part 60 method applicability and interpretation become central. Some facilities also test for multiple objectives at once, such as permit compliance, emissions inventory support, and engineering diagnostics. In those cases, one test plan may need to satisfy more than one audience.

That is where experienced technical planning matters. The protocol should identify the governing requirement, the reference methods, any proposed alternatives, the operating conditions to be tested, and how exceptions will be handled if plant conditions shift during the campaign. It should also address whether the resulting data will be used only for compliance or for additional reporting programs such as emissions inventories or greenhouse gas calculations.

For Alberta facilities, the safest approach is to treat the Alberta code as the compliance framework and EPA methods as the measurement tools when that is what the approval structure requires. That keeps the test aligned with the regulator’s expectations while preserving recognized technical methodology.

A defensible stack test is not built by choosing Alberta or EPA in the abstract. It is built by matching the method, the protocol, the field execution, and the final report to the exact obligation the facility must satisfy. When that alignment is done properly, the data is more useful for regulators, internal engineering teams, and long-term compliance planning.