RTO INLET DESIGN / SOURCE CAPTURE

RTO VOC Capture Efficiency Calculation for Hoods

Connect hood airflow and source release evidence with the VOC load that actually reaches an industrial RTO.

Published 29 October 2026Engineering guide

Direct answer: Estimate source capture efficiency as ηc = mCaptured / mReleased × 100%, where both mass rates refer to the same time interval and source boundary. Use hood and enclosure geometry, measured airflow, release conditions and a representative test to determine mCaptured. Do not infer collection performance from fan capacity or RTO destruction efficiency alone.

An RTO VOC capture efficiency calculation helps a buyer separate two questions that are often blended in a quotation: how much solvent is collected at the process, and how much pollutant is destroyed after collection. A regenerative thermal oxidizer can only treat the gas that enters its duct. Poor capture can leave workers, buildings or surrounding areas exposed even when the oxidizer outlet meets its own test condition.

This guide presents a screening equation and a hypothetical example. The figures are arithmetic illustrations, not Yuehua project measurements, permit limits or a recommended hood design. Final capture criteria must follow the process hazard review, applicable environmental requirements, industrial-hygiene objective and an agreed test method.

Define the source and capture boundary

State what is released and what is collected

Start with a source inventory: solvent application, mixing, drying, charging, cleaning or storage. Define the release boundary and time window. A batch vessel may release a short peak during opening while a coating line emits continuously. If the source is partly enclosed, identify the access doors, product openings, conveyor gaps and leakage paths that remain during production.

Define mReleased as the solvent or VOC mass leaving the source during the selected interval. It may come from a measured material balance, a controlled release, a species-resolved process estimate or a documented upper design case. Record whether the rate is total VOC, one compound or mass as carbon. Keep the reporting convention consistent with the exhaust measurement.

Separate capture from treatment

mCaptured is the portion that enters the intended collection system and travels toward the RTO boundary. Material exhausted through a different fan, lost through a door, retained in a product or condensed in a drain has a different fate. Do not call every measured reduction at the process a capture result until the mass boundary is clear.

For the RTO itself, use the RTO VOC mass loading calculation guide to convert compatible inlet concentration and gas flow into a solvent load. The two calculations connect at the RTO inlet, but they answer different questions and should retain separate uncertainty statements.

Use the capture-efficiency equation correctly

For a defined source and time interval, the basic screening equation is:

ηc = mCaptured / mReleased × 100%

Both mass rates must use the same time base. If release is reported in kilograms per batch, integrate captured mass over that batch. If the source is steady, compare compatible kilograms per hour. A concentration by itself is not a mass rate; it needs a matched gas flow, measurement basis and sampling boundary.

When a direct source balance is unavailable, use a tracer or controlled challenge only after documenting how the test represents production. A tracer result may estimate transport and mixing, but it does not automatically prove that a sticky, condensing or reactive solvent behaves the same way. Identify the detector response, sampling locations, background correction and uncertainty.

For multiple sources, calculate each source or operating combination separately before summing. A header result can hide one poorly captured branch behind several well-captured branches. Keep source identity, active fans, damper positions and enclosure openings in the test record.

Check airflow, geometry and operating conditions

Match hood flow to the release pattern

Measure airflow at a defensible location and state whether the value is actual or reference flow. A duct average can support an exhaust balance, but it does not show the velocity field at the source. Capture depends on the distance from the hood, opening size, cross-drafts, thermal plumes, source momentum and the direction of release.

An enclosure can reduce the airflow required for collection, yet a frequently opened door can dominate the result. For an open hood, map the face velocity and inspect whether room supply air pushes vapor away from the hood. For a slot or canopy, document the design assumption that relates hood flow to the release direction. The RTO selection guide explains why the complete collection and inlet profile belongs in the equipment inquiry.

Test the real production state

Run the test with the product, line speed, solvent temperature, fan configuration and access positions that matter. Include startup, cleaning, changeover and credible simultaneous operations when they affect the release. A clean, empty hood test can confirm a fan setting while saying little about an operator opening a vessel beside a cross-draft.

Record room pressure, supply-air changes, damper position, filter condition and RTO operating mode. If a variable-speed fan follows a pressure setpoint, capture the setpoint and actual speed during the release. Repeat enough operating cases to distinguish repeatable collection from one favorable moment.

Work through a hypothetical mass-rate example

Calculate one batch interval

Assume a cleaning step releases an estimated 8.0 kg of VOC over 40 minutes. A hypothetical exhaust and tracer balance attributes 6.4 kg to the intended RTO collection header during the same interval. The screening capture result is 6.4 / 8.0 × 100% = 80%.

That arithmetic does not prove that every minute had 80% capture. A short opening event may have been captured at a lower rate while the later steady period was higher. Preserve the time series or sub-interval calculations when the release is strongly transient. Also state whether the 8.0 kg source estimate includes material retained in the product or cleaning cloths.

Relate capture to the RTO load

If the same batch is used for an RTO design screen, 6.4 kg is the captured mass before any duct loss or parallel treatment path is accounted for. It is not an outlet destruction result. If the inlet analyzer reports a different mass, investigate sampling timing, moisture basis, flow measurement, condensation, unmonitored branches and the source estimate before selecting a factor to force agreement.

Use synchronized concentration and flow records. A delayed extractive analyzer can make a batch appear to enter the RTO after the source event. The RTO VOC sampling delay guide describes transport, analyzer dynamics and short-peak evidence that should be considered before comparing timelines.

Validate capture with a defensible test plan

A procurement package should state the proposed method: material balance, tracer release, local exhaust ventilation survey, compound-specific sampling or a combination. Define the release point, detector location, background period, calibration, averaging time and acceptance calculation before the test begins. Ask the supplier to distinguish measured values, calculations and assumptions.

For a tracer study, confirm that the release rate is stable and that the tracer reaches the intended sampling points without bypassing the hood. Check whether the detector can resolve the expected concentration and whether its response time is short relative to the release. A response correction may be needed, but it must be documented rather than guessed.

For solvent sampling, record species, moisture, temperature, pressure, flow basis and sample-line condition. Condensation or adsorption can make a collected stream look smaller than it is. Use the VOC condensation and dew point control guide when heated lines, cold spots or wet filters could affect the evidence.

Include a visual smoke or airflow survey only as supporting evidence unless the method defines how it becomes quantitative. Smoke movement can reveal cross-drafts and leakage, but it cannot by itself provide a mass capture percentage. Pair observations with measured airflow and concentration or a justified release balance.

【【人工行业案例插入区】】

Turn a result into an engineering action

If capture is lower than the agreed basis, first identify the failure mode. The hood may be too far from the source, the enclosure may have an open gap, the fan may be at the wrong operating point, or room supply air may sweep the plume away. A dirty filter, leaking duct or incorrect damper position can also change the distribution.

Corrective measures can include enclosure changes, hood repositioning, local airflow adjustment, make-up-air balancing, fan control, duct repair or a revised operating procedure. Verify that a change does not move the problem to another branch or overload the RTO with a new peak. Re-test the same operating cases and retain the before-and-after boundary definitions.

When capture data changes the solvent load, review heat and safety implications with the RTO autothermal concentration calculation guide. When the source profile is intermittent, include the peak duration and airflow correlation rather than applying one average to every design case.

For emissions acceptance, keep capture performance separate from oxidizer destruction efficiency. The RTO destruction efficiency calculation guide sets out compatible inlet and outlet mass-flow boundaries. A satisfactory stack test cannot erase an uncollected source, and a capture test cannot establish outlet compliance.

Frequently asked questions

Is hood capture efficiency the same as RTO destruction efficiency?

No. Hood capture efficiency describes the fraction of a source release that enters the intended exhaust system. RTO destruction efficiency describes pollutant removal across the oxidizer boundary. A high oxidizer result cannot prove that uncaptured VOC was collected, and a strong hood does not prove oxidation performance.

Can capture efficiency be calculated from fan airflow alone?

No. Airflow is an input, but capture also depends on hood geometry, source distance, cross-drafts, enclosure openings, release momentum and operating positions. A fan nameplate or one duct flow reading does not establish how much vapor reaches the hood. Use measured source and exhaust information with a representative test.

Does a tracer-gas test measure real solvent capture?

It can provide useful evidence when the tracer release, detector response and test geometry represent the actual process. A tracer is not automatically equivalent to every solvent. Explain the tracer properties, release rate, mixing, sampling locations and conversion assumptions, then confirm the result against process observations and VOC measurements where appropriate.

Should uncaptured VOC be added to the RTO design load?

The RTO inlet design basis should use the measured or credibly bounded load that reaches the oxidizer. Uncaptured emissions remain an environmental and workplace concern, but adding an unsupported fraction to the RTO load can distort sizing. Resolve capture uncertainty through process testing, enclosure improvements and a documented design case.

What capture result is acceptable for a procurement decision?

There is no universal value that replaces the applicable permit, industrial-hygiene objective, process hazard review and test method. Define the required collection performance for each source, the operating cases, the uncertainty and the corrective action when the result is outside the agreed basis. Have the responsible engineers and environmental team approve the criterion.

Review your VOC capture basis

Send Yuehua your source inventory, hood and enclosure drawings, airflow measurements, solvent release estimate, operating schedule and any tracer or VOC test records. Our engineering team can help define a comparable collection and RTO inlet review while final acceptance criteria remain with the responsible project and environmental teams.

Send capture data for technical review