What PFAS Emissions Mean for Industrial Sites

A PFAS question can quickly become an air emissions question. A facility may handle fluorinated materials in products, coatings, process additives, wastewater residuals, or legacy equipment, then face uncertainty about whether those compounds can reach an exhaust stream. The central challenge with PFAS emissions is not simply detecting a chemical. It is producing data that accurately represents a complex source while standing up to regulatory, technical, and operational review.

For plant managers and environmental teams, that requires a disciplined approach. PFAS testing cannot be treated as a routine add-on to a conventional stack test. Sampling media, field handling practices, analytical targets, blank controls, source conditions, and the intended regulatory use of the data all need to be defined before the field crew arrives.

Why PFAS emissions require a different testing approach

Per- and polyfluoroalkyl substances are a broad class of fluorinated compounds with differing chemical structures, physical properties, and behavior in industrial processes. Some may be associated with particles, aerosols, condensable material, or vapor-phase emissions. Others may be precursors that transform during thermal processing, treatment, transport, or analysis.

That variability makes a simple question such as, “What is coming out of the stack?” more difficult than it sounds. A result for a targeted compound list does not necessarily represent all fluorinated substances present. Conversely, a total fluorine measurement may indicate fluorine is present without identifying which PFAS compounds contributed to the result. These approaches answer different questions and should not be treated as interchangeable.

The source itself also matters. Combustion units, thermal treatment systems, coating operations, chemical manufacturing processes, drying systems, incinerators, and control devices can each create different sampling conditions. Temperature, moisture, acid gases, particulate loading, flow variation, and process cycling can influence collection efficiency and the representativeness of the final sample.

A defensible program begins by defining the decision the data must support. That may be a permit application, a regulator information request, a facility risk assessment, source characterization study, control device evaluation, or internal due diligence exercise. The decision determines the appropriate sampling design.

Identifying likely PFAS air emission pathways

The most useful first step is a source inventory. Environmental and operations personnel should trace fluorinated materials from receipt through storage, use, treatment, waste handling, and final discharge points. Safety data sheets and supplier documentation are helpful, but they may not identify every relevant constituent, precursor, or proprietary fluorinated component.

The review should extend beyond the main process stack. Depending on facility operations, potential pathways can include thermal oxidizers, ovens, process vents, scrubber exhausts, material handling points, wastewater treatment vents, sludge or residuals handling, and fugitive releases. A wastewater stream containing PFAS, for example, may create a separate air question if aeration, heating, agitation, or treatment processes transfer compounds into the gas phase or aerosol.

Process knowledge is essential when prioritizing locations. A stack with high flow may not be the highest-concentration source, while a smaller intermittent vent may release material during a specific batch stage. Testing only during a low-production period can produce technically valid samples that do not represent the facility's normal or maximum-emission condition.

A pre-test review should document operating rates, fuel use, material feed rates, formulation changes, control equipment configuration, operating temperatures, pressure differentials, and planned process events. These operating records are not administrative extras. They are necessary context for interpreting the emissions data.

Building a PFAS sampling plan that can withstand review

There is no universal stack test that answers every PFAS question. Method selection must match the source, compounds of interest, sample matrix, detection limits, and governing program requirements. For stationary sources, teams may consider procedures such as EPA Other Test Method 50 where appropriate, while recognizing that regulators, permits, and project objectives can require specific modifications, validation steps, or alternate approaches.

A sampling plan should clearly establish the target analyte list, expected concentration range, reporting limits, number and duration of runs, traverse requirements, operating conditions, laboratory method, and data validation criteria. If the purpose is to compare results with a permit limit or an agency-requested screening level, those requirements should be confirmed before field work begins. Retrofitting a test plan after results are received is expensive and may leave the data unsuitable for its intended use.

Representative stack conditions matter

Conventional stack test principles still apply. The team must characterize the sampling location, gas velocity, temperature, moisture, oxygen or carbon dioxide where relevant, particulate conditions, and flow rate. For sources with particulate-bound PFAS, isokinetic sampling considerations may be particularly important. For vapor-phase or condensable compounds, the collection train and temperature control strategy become equally critical.

The test window should represent the operating condition of concern. Facilities sometimes need multiple test scenarios: normal production, maximum throughput, different raw materials, startup or shutdown, or a control device performance range. The right scope depends on the compliance driver and the variability of the process.

Contamination control is not optional

PFAS can be present in common field materials, personal care products, packaging, waterproof fabrics, and some fluoropolymer components. That makes contamination control a central quality assurance requirement rather than a laboratory detail.

The field and laboratory teams should establish material restrictions, handling procedures, equipment cleaning requirements, sample custody practices, and appropriate blanks before mobilization. Equipment selection must account for potential fluoropolymer contact surfaces and other materials that could compromise low-level results. Field blanks, equipment blanks, and trip blanks may be necessary to identify contamination introduced during preparation, sampling, transport, or analysis.

A blank result does not automatically invalidate a test, but it must be evaluated against the project quality objectives, sample concentrations, and laboratory reporting conventions. A result near the detection limit can be meaningful only when the associated quality control evidence supports it.

Understanding targeted PFAS, total fluorine, and precursor questions

Targeted analytical methods measure a defined list of compounds. Their strength is specificity: they can identify and quantify individual analytes within the validated method scope. Their limitation is that they cannot quantify compounds that are not included in the target list.

Total fluorine or extractable organic fluorine techniques can provide broader screening information, depending on the method and sample matrix. However, they do not provide a direct compound-by-compound PFAS inventory. Inorganic fluorine, fluorinated polymers, sampling artifacts, and extraction limitations must be considered when interpreting the result.

Precursor compounds add another layer of uncertainty. Some PFAS-related materials can transform under process conditions or during environmental transport. For that reason, a low result for a short targeted list should not be communicated as proof of zero PFAS-related emissions. The technically sound statement is narrower: the target analytes were not detected above the applicable reporting limits under the tested operating conditions.

This distinction matters in regulatory correspondence, public disclosures, and internal risk assessments. Precision in language protects the facility from overinterpreting the data while preserving the value of a well-executed test.

Turning test results into a compliance program

A PFAS emissions report should do more than present laboratory tables. It should explain the source configuration, process conditions, sampling location, field methods, quality control results, calculation basis, and limitations of the dataset. Emission rates should be clearly distinguished from concentrations, and results should identify whether they are reported on actual or dry basis, corrected to a reference condition, or normalized to production where appropriate.

Facilities should compare the findings against the applicable permit terms, agency requests, internal benchmarks, and material-use information. If emissions are identified, the next question is not automatically whether a new control device is needed. The answer depends on the compound profile, mass rate, release pattern, existing control equipment, feasibility of source reduction, and regulatory obligations.

In some cases, the most effective action is upstream: changing a process additive, improving material containment, segregating PFAS-containing residuals, or revising waste handling practices. In others, the facility may need further characterization of the control device inlet and outlet, different operating conditions, or multiple source locations before selecting a control strategy.

Air Research Group approaches complex source testing with the same principle that applies to conventional compliance work: credible decisions require credible measurements. That means aligning the test objective, field execution, analytical method, and reporting package from the outset.

For facilities evaluating PFAS concerns, the practical next step is to assemble process information before a sampling date is set. A careful technical review at that stage can prevent a costly test from answering the wrong question.