A2L Leak Detection and Mitigation Response
Purpose
An A2L appliance carries a refrigerant detection system as a listed part of the equipment, and when it trips it does two things at once: it records that refrigerant reached the sensor, and it drives the unit into a mitigation state that usually means the indoor blower runs and the compressor will not. To a homeowner that is "the fan runs all the time and there is no cold air." To a tech who has not met one it reads like a stuck contactor, and the fastest way to close the call is to cycle power and watch it run.
That reset is the failure this procedure prevents. The detection system is the only witness to a leak that has already happened, and clearing it destroys the evidence while returning a leaking system to service in an occupied house. The sensor is also the last thing to suspect: a correctly operating protective device that opened is telling you something, and replacing it reaches the same end state one step slower and with a part number on the invoice.
Scope
Covers the service response to a suspected or confirmed A2L detection event on residential and light-commercial equipment: gating the space, reading the event history, confirming the mitigation ran, locating the source, and the return-to-service verification.
Does not cover the leak-rate decision or the repair-versus-replace authorization, which the refrigerant leak response and repair authorization SOP owns, nor recovery, brazing or recharging, each of which has its own SOP. Does not cover the ventilation and ignition-control regime for a store, restaurant or apartment, which the occupied-space SOP owns and which this procedure hands off to.
Roles and responsibilities
| Role | Owns | Hands off |
|---|---|---|
| Dispatcher | Asking whether the blower is running with no cooling, and flagging it as a possible mitigation event | An A2L flag plus the symptom wording, before the truck rolls |
| Service tech | Steps 1 to 8, and the decision not to clear a fault before it is read | The event history and the source location, written, before any repair starts |
| Service manager | Any decision to leave a system in service with a detection fault present | Either a system locked out or a written deviation with a date on it |
| Office | Scheduling the return visit when a part holds the system out of service | The customer told the unit stays off until then |
Procedure
1. Gate the space before you touch a control, and do not clear the fault. Open the closet or room, get air moving through it, move occupants out, and shut off any fuel-fired appliance sharing the space. Acceptance: the space ventilating, occupants clear, no open flame or standing pilot in it, control untouched. What wrong looks like: cycling power on arrival, which clears the stored event on many controls; stop rule is that no ventilation path, or an open flame you cannot shut off, means nobody works until it is resolved. Hazard at this step: A2L vapor is heavier than air and pools low, and a gas dryer sharing a laundry closet sits in that layer with a live ignition source, so its gas cock closes before you kneel down.
2. Read the control's event history before power is cycled. Pull the fault log through the manufacturer's service interface or display sequence and write every event with its date and time. Acceptance: an event count, the most recent timestamp, and whether the control is in mitigation now or self-cleared. What wrong looks like: a lone "current fault" with no history, which cannot separate a one-off from a leak that has tripped for two weeks; stop rule is that a control which will not give up its history goes on the ticket as unread, never as empty. Hazard at this step: hands and a tool go into an energized compartment, so work per 29 CFR 1910.333(b)(2) as a qualified person under 1910.332.
3. Confirm the mitigation actions the listing requires actually happened. Compare what the unit is doing against what the service literature says mitigation looks like on that model, written to the edition of UL 60335-2-40 the appliance was listed to. Acceptance: blower running at the airflow the literature names for mitigation, compressor and electric heat locked out, cooling calls not honored. What wrong looks like: a detection fault logged with the compressor still running, meaning the mitigation path itself is broken; stop rule is that mitigation which did not run goes to the manufacturer's technical line and the system stays off. Hazard at this step: the blower is turning, so the cabinet is not opened past the point a hand can reach the wheel.
4. Search with your own instrument, in the order that separates the candidates. Work the evaporator cabinet and its brazed connections first, then the line set penetration, then the outdoor unit, with the detector bump-tested for this refrigerant. Acceptance: a named location where the detector responds repeatably plus at least two where it does not. What wrong looks like: one alarm at the return grille called "the coil," which is where every leak in the house reports to; stop rule is that no repeatable response anywhere, with the system holding full pressure, sends you to step 6 rather than into the system. Hazard at this step: opening a coil cabinet disturbs the pooled layer and pushes it toward you, so the search runs with the space still ventilating and the fuel appliance still off.
5. Establish the loss before you name the repair. Recover the remaining charge per the recovery SOP and weigh it against nameplate, or where the system still holds a working charge, record pressures and temperatures against the manufacturer's chart. Acceptance: recovered net weight against nameplate, stated as pounds lost and as a percentage of nameplate. What wrong looks like: "it was low" with no weight, which supports neither a warranty claim nor a repair-versus-replace conversation; stop rule is that a leak in a small enclosed space hands off to the occupied-space SOP first. Hazard at this step: cracking a port on an A2L system releases a liquid that freezes skin on contact and a refrigerant that burns, so gauntlet gloves and sealed eye protection for the freeze, and no ignition source in the release path: the fuel appliance stays off, nothing is lit, no switch or non-rated vacuum is operated there, and the room stays ventilating while the port is open. Stand out of line with the fitting.
6. Where no refrigerant is found, work the false-trip list before you condemn the sensor. Detection sensors respond to more than refrigerant: solvent vapor, aerosol propellant, fresh paint and some cleaning chemicals in the same closet will trip one, and every sensor has a published service life. Acceptance: storage inventoried, the sensor's install date or service-life marking read, wiring checked to the manufacturer's diagnostic. What wrong looks like: a sensor ordered on one trip with a spray can under the air handler; stop rule is that a sensor within its service life, wired correctly, with a plausible vapor source present is not replaced. Hazard at this step: pulling a sensor connector means the unit is proved dead on a known live source before and after, per NFPA 70E-2021, 120.5.
7. Route the repair and say what stays out of service until it is done. Leak repair goes to the brazing SOP and then the charging SOP; a sensor or harness is an ordered part with a lead time. Acceptance: a named repair path, a part on order where needed, and a written statement of what the customer has meanwhile. What wrong looks like: leaving the system in cooling until the part comes on a unit whose detection function is not working; stop rule is that a system whose detection cannot be verified does not run in cooling, and that call belongs to the service manager. Hazard at this step: none, a decision made at the kitchen table, and the honest version is that the unit will not cool until the return visit.
8. Restore, re-arm and prove the protective function before you leave. Put power and refrigerant back, clear the fault only after the history is recorded, then run the manufacturer's field verification of the detection system. Acceptance: a normal cooling cycle completed, the fault history clear of new events over that run, and the detection function responding to the prescribed field test with the step 3 mitigation actions observed again. What wrong looks like: calling the repair good because the unit cools, which tests everything except the thing protecting the house; stop rule is that a detection function which does not verify holds the system out of cooling and the visit stays open. Hazard at this step: refrigerant, power and airflow all go back into an occupied house here, so the panel goes on before the disconnect closes, everyone stands clear of the blower opening, and the fuel appliance shut off at step 1 is relit and its operation confirmed before you leave.
The record this produces
One detection-event block on the ticket, read by both a warranty administrator and the next tech.
Fields: refrigerant designation and nameplate charge; the event count and timestamps from step 2; whether mitigation ran as the literature describes; every location searched at step 4 with response or no response for each, not just the hit; recovered net weight and the loss in pounds and as a percentage of nameplate; the repair; the sensor service-life marking where step 6 was worked; and the step 8 verification result.
The next tech reads the search list, because the locations that did not respond are what stop a second visit repeating the first. The warranty administrator reads the weight and the percentage, since a claim on a coil needs a number. And the shop reads the event timestamps across visits: a system that tripped three times before anyone called is a customer who was living with it.
Worked pass: R-454B air handler in a second-floor laundry closet
Call taken as "fan runs all the time, no cold air," flagged A2L off the equipment history. 3-ton system, nameplate charge 6 lb 8 oz.
Step 1: closet doors open, hallway window open, family moved downstairs. The closet also holds a gas dryer, so its gas cock was closed before the tech knelt at the return opening. Control not touched.
Step 2: history shows 3 detection events across 11 days, the most recent 40 minutes before arrival, and the control currently sitting in mitigation.
Step 3: blower running continuously at the mitigation airflow this model's literature names, compressor locked out, cooling call not honored. Mitigation is working, so the event is real rather than a control defect.
Step 4: detector responds repeatably at the evaporator suction connection inside the coil cabinet, and not at the line set penetration through the closet wall or anywhere at the outdoor unit. Three locations searched, one hit, and the two misses go on the ticket.
Step 5: charge recovered into a listed machine and weighed at 3 lb 14 oz, which is 3.875 lb, against a nameplate of 6 lb 8 oz, which is 6.5 lb. So 6.5 minus 3.875 leaves 2.625 lb lost, and 2.625 divided by 6.5 is 40.4 percent of nameplate gone. That is a number the warranty claim can carry.
Step 6 was not worked, because step 4 located refrigerant. Joint repaired under the brazing SOP, system evacuated and recharged to 6.5 lb by weight under the charging SOP, subcooling confirmed against the manufacturer's chart.
Step 8 FAILED and took its stop rule. The unit cooled normally and everything looked finished. The manufacturer's field verification of the detection system produced no response from the sensor and no mitigation actions. Under this step's acceptance that is a fail regardless of how well the system cools, so the compressor was left locked out at the control, the customer was told the unit would not cool until the return visit, and a sensor was ordered that evening. Its marking showed it near the end of the published service life, consistent with a device that had been detecting a real leak for 11 days.
Note what step 8 bought. The repair was good, the charge was right, the system cooled. A tech who verified nothing beyond cooling hands back a working air conditioner with dead refrigerant detection, and nothing the customer sees would reveal it.
References
- UL 60335-2-40, in the edition the appliance was listed to, which binds the manufacturer and reaches the tech through the appliance's service literature, for the detection system and its mitigation actions
- ASHRAE Standard 15.2 for residential refrigeration system safety, and ASHRAE Standard 34, each in the edition your jurisdiction's adopted mechanical code references
- 29 CFR 1910.333(b)(2) for electrical work practices, with qualified-person requirements at 1910.332, and NFPA 70E-2021, 120.5 for the live-dead-live proving sequence
- See related: the refrigerant leak response and repair authorization, A2L service readiness and tool inventory, and servicing an A2L system in an occupied space SOPs