Safety Systems

Diagnosing SRS Warning Light Conditions

Anthony CalhounASE Master Tech8 min read

Written by Anthony Calhoun, ASE Master Tech A1-A8

The SRS warning light is one of the most mishandled dashboard lights in the shop. Customers ignore it. Shops clear it without diagnosing it. And technicians who are not familiar with airbag system architecture make dangerous assumptions about what it means. This guide covers SRS diagnosis from code interpretation through repair verification, written for working technicians who need to get it right the first time.

What the SRS Warning Light Actually Means

SRS stands for Supplemental Restraint System. The airbag, pretensioners, and related components are all supplemental — they work alongside seatbelts, not instead of them. When the SRS light is on, the airbag control module has detected a fault in the system and stored a diagnostic trouble code.

Here is the part that matters most: when the SRS light is on, the airbags may not deploy in a crash. In some fault conditions, they may deploy unexpectedly. Both outcomes are potentially fatal. This is not a warning light you put a piece of tape over and hand the car back to a customer. The vehicle should not be driven until the fault is properly diagnosed and repaired.

Do not let customers pressure you into clearing the light without diagnosing it. Do not let a service advisor promise the customer it is probably nothing. The SRS system is a life-safety system. Treat it that way every time.

Normal SRS Light Behavior — What You Should See

On key-on, the SRS light should illuminate for approximately three to six seconds. This is the bulb check — the module is running a self-test, verifying the system, and confirming the light circuit itself is functional. After that self-test, the light should go off and stay off during normal driving.

If the light stays on after the bulb check, a fault code is stored. If the light comes on while driving, the module detected a fault after startup — the code will be stored and the system may be disabled. If the light flashes in a pattern, some older systems use a blink code sequence to communicate fault information without a scan tool, though this varies widely by manufacturer and era.

Any deviation from the normal bulb-check-and-off pattern means there is a stored code. You must pull that code before doing anything else.

Understanding SRS Code Structure

SRS codes are B-codes — body codes. The generic OBD-II system uses P-codes for powertrain, C-codes for chassis, B-codes for body, and U-codes for network communication. Airbag system codes fall under the B-code range because the SRS module is a body control system.

Common B-code ranges for SRS faults include codes in the B0000 through B0999 range for generic SRS faults, though manufacturers often use manufacturer-specific codes in the B1000 through B3999 range. The code structure gives you information: the first digit after the B identifies whether it is generic (0) or manufacturer-specific (1-3), the second digit identifies the subsystem, and the remaining digits identify the specific fault.

Common SRS codes you will see on the regular include:

  • B0051 / B0052 and similar — Clock spring (steering wheel angle sensor, driver airbag squib circuit) faults. These are the most common codes across all makes and models.
  • Driver airbag squib resistance codes — High or low resistance detected in the driver airbag inflator circuit, usually the clock spring or a connector issue.
  • Passenger airbag codes — Similar resistance faults on the passenger side, often connector-related under the dash or at the airbag module itself.
  • Side airbag codes — Door curtain airbags or seat-mounted side airbags, frequently caused by connector damage or corrosion in the door jamb area.
  • Pretensioner codes — Seatbelt pretensioner circuit faults, check the buckle connector and the pretensioner squib connector at the B-pillar.
  • OCS codes — Occupant Classification System faults, related to the weight-sensing mat in the passenger seat.
  • Crash sensor codes — Fault detected at a front or side impact sensor, often caused by physical damage from even minor collisions.
  • Internal ACM faults — The module itself has failed or has recorded a crash event. These almost always require module replacement.

Always look at the full description of the code, not just the code number. The description tells you the circuit (which component), the fault type (open, short to ground, short to voltage, out of range), and gives you a starting point for diagnosis.

Clock Spring Failures — The Most Common SRS Code

If you work in a shop that sees a reasonable volume of SRS complaints, clock spring failure will account for a large percentage of them. The clock spring — also called a clock spring assembly, spiral cable, or contact reel depending on the manufacturer — is a ribbon cable coiled inside a plastic housing mounted between the steering wheel and the steering column. It allows the steering wheel to rotate while maintaining an electrical connection to the airbag, horn, cruise control switches, and other steering wheel-mounted components.

The clock spring wears out because it flexes every single time the wheel turns. Over enough miles and enough turns, the ribbon cable develops a break. When it fails, you will typically see a combination of symptoms: the airbag light is on, the horn does not work, and cruise control buttons are inoperative. That three-symptom combination points directly at the clock spring before you even pull a code.

Clock spring replacement requires the steering wheel to be centered before removal. If the wheel is not centered, the clock spring will be installed off-center and will fail prematurely — or immediately — because the ribbon cable will reach its end of travel before the steering wheel does. Standard procedure is to set the wheels straight, mark the clock spring housing before removal, and install the new unit in the centered position. Follow the manufacturer's procedure for your specific vehicle — some require the airbag module to be removed first, some require column shroud removal, and torque specs for the steering wheel nut matter.

Vehicles known for frequent clock spring failures include older Jeep Grand Cherokees, various Dodge Ram and Chrysler products, Toyota Tacomas of certain years, Honda Pilots, and Nissan trucks. If you see these come in with airbag light plus horn issues, go straight to the clock spring.

Seat-Related SRS Codes

The seat area is a major source of SRS faults, and it is often overlooked. There are several components under and inside the seat that feed into the SRS system:

  • Occupant Classification System (OCS) sensor mat — A pressure-sensing mat inside the passenger seat cushion that tells the module whether someone is sitting in the seat and approximately how much they weigh. This determines whether the passenger airbag should deploy and at what level. OCS mats fail from physical damage, moisture, and age. Replacement typically requires removing the seat cushion cover.
  • Seat belt buckle switch — The buckle has a switch that tells the module whether the occupant is belted. Faults here generate codes and can affect pretensioner operation. Check the connector at the buckle before assuming the buckle itself is bad.
  • Side airbag connector under the seat — On vehicles with seat-mounted side airbags, the airbag inflator is inside the seat. The connector runs under the seat and is prone to being kicked loose by rear passengers, pinched when seats are adjusted, or damaged during seat removal for carpet work. This is your first inspection point for any seat-mounted side airbag code.
  • Seat track position sensor — Some vehicles adjust airbag deployment thresholds based on seat position. A faulty track sensor generates SRS codes and may disable deployment optimization.

Before replacing any seat-related SRS component, remove the seat and inspect every connector in the harness. Yellow SRS connectors under the seat are common culprits — look for pushed-back terminals, corrosion, and physical damage. Many seat-related SRS codes clear permanently after connector inspection and reconnection. Do not skip this step.

Also be aware that aftermarket seat covers that do not have deployment windows sewn in will block side airbag deployment. This is not a code issue, it is a physical hazard. If a customer has aftermarket seat covers, document it and advise them of the risk.

Connector and Wiring Issues

The SRS system uses yellow connectors throughout the vehicle harness specifically because they are a visual indicator to technicians that they are working with airbag circuits. These connectors also contain shorting bars — a passive safety mechanism. When the connector is unplugged, the shorting bar connects the two terminals together, preventing an accidental voltage spike from triggering the squib and deploying the airbag. This is why you never probe an SRS connector with a test light or standard multimeter.

Connector corrosion is a significant issue, particularly in side curtain airbag circuits routed through door jambs and doors. Water intrusion from leaking door seals, worn grommets, and damaged weatherstripping allows moisture into the connector cavity. Corrosion increases resistance, which the module reads as a circuit fault. Inspect the connectors, clean them with electrical contact cleaner if appropriate, and verify terminal tension before condemning components.

Pinched wiring under carpet is another common fault source. When floor mats are improperly installed, or when seats are removed and reinstalled without routing the harness correctly, the SRS wiring under the carpet gets pinched. Over time this creates an intermittent or permanent open circuit. Lift the carpet and inspect the harness routing before spending time chasing a code to a component.

Door jamb wiring is a known failure point on high-mileage vehicles. The flex section of harness that runs through the door hinge area bends thousands of times over the life of the vehicle. Eventually the insulation cracks and individual wires break internally while still appearing intact externally. If you have a side curtain or side airbag code on a high-mileage vehicle and the connector looks clean, wiggle the door jamb harness while watching the code live data or a resistance reading from the scan tool.

Crash Sensor Faults

Crash sensors — also called impact sensors or satellite sensors — are mounted at strategic points around the vehicle to detect collision forces and signal the ACM to deploy airbags. There are typically front impact sensors mounted near the front bumper or radiator support, and side impact sensors mounted in the doors or B-pillars.

Front impact sensors are physically vulnerable. A minor fender bender that does not trigger airbag deployment can still physically damage or shift a front impact sensor enough to generate a fault code. If a vehicle comes in with a front impact sensor code and there is any sign of front-end damage — even small damage that was repaired at a body shop — inspect the sensor mounting location first. Check that the sensor is present, undamaged, and mounted in the correct orientation. Many sensors are directional — mounting them at the wrong angle affects their ability to detect forces in the correct axis.

Side impact sensors in doors are also vulnerable to damage during door repairs, glass replacements, and trim panel work. Any time someone has been inside a door, the side impact sensor should be verified as undisturbed and properly connected.

Sensor mounting torque matters. Under-torqued sensors can shift position during normal driving and create intermittent faults. Over-torqued sensors can crack the housing. Follow manufacturer torque specs.

Post-Accident SRS Codes and What They Mean

This section is critical. When airbags deploy in an accident, the ACM records a crash event in non-volatile memory. This event record cannot be cleared with a standard scan tool. The module has permanently stored data about the crash — deployment commands, sensor inputs, timing. On most vehicles, a module that has recorded a crash event must be replaced. You cannot clear it and reuse the module.

The way to determine whether the ACM has recorded a crash event is to read the module's live data and fault history with a scan tool capable of accessing SRS data. Many professional-grade scan tools will display crash event status directly. If the module shows a crash event recorded, that module is done — replace it.

Post-accident SRS work requires replacing every deployed component: airbag inflators, pretensioners, and the ACM. Sensors in the impact zone should also be replaced, not just inspected. Do not reuse any deployed or potentially deployed component.

Some codes generated during an accident — such as a low battery voltage code or a communication code from a module that lost power during the crash — can be cleared and do not indicate deployed components. Learn to distinguish deployment codes from non-deployment fault codes that happen to be stored during the event. If you are not certain which codes indicate deployment and which do not, refer to the manufacturer service information before making any decisions.

Never let a shop clear crash-related SRS codes and return the vehicle to a customer without fully addressing the system. If another accident occurs and the airbags do not deploy because the system was not properly restored, the consequences are catastrophic — and the liability falls on whoever signed off on the repair.

Diagnostic Procedure — Step by Step

Follow this sequence every time you work an SRS complaint:

  1. Scan for codes first. Before touching anything, connect a scan tool capable of reading SRS data and pull all stored and pending codes. Document every code. Read the full description for each one.
  2. Interpret the code. Identify which circuit is at fault (driver airbag, passenger airbag, left side airbag, pretensioner, OCS, crash sensor, etc.) and what the fault type is (open circuit, short to ground, short to voltage, resistance out of range, internal fault).
  3. Inspect the component and its connector first. Before measuring anything, physically inspect the wiring and connector for the faulted circuit. Look for obvious damage, corrosion, pushed-back terminals, and improper routing. A large percentage of SRS codes are connector-related and can be resolved at this step.
  4. Check squib circuit resistance only with an approved SRS-safe scan tool or SRS-specific resistance meter. This point cannot be overstated: do not use a standard digital multimeter or any standard test equipment directly on a squib circuit. A standard ohmmeter passes current through the circuit being tested. Squib circuits are designed to fire from a very small current pulse. The resistance-measuring current from a standard meter can be enough to deploy an airbag or pretensioner. Use only tools approved for SRS circuit testing — these use a current-limited measurement that cannot trigger a squib.
  5. Verify component resistance is within specification. SRS service data provides resistance specifications for each squib circuit. If the measured resistance is out of specification, you have identified the fault. Compare your measurement to the spec and determine whether you have an open circuit, a short, or a resistance fault in the circuit.
  6. Repair the fault. Replace the faulty component, repair the wiring, or address the connector as indicated by your diagnosis. Follow all safety precautions during component removal — disconnect the battery and wait the manufacturer-specified time (usually two to fifteen minutes, varies by vehicle) for the backup power supply to discharge before disconnecting any SRS connector.
  7. Clear codes and verify the repair. After repair, clear all SRS codes. Cycle the key and observe the SRS light through the bulb check. The light should go on for the normal self-test period, then go off and stay off. If the light goes off and stays off, the repair is verified. If a code returns, there is either a second fault in the system or the original fault was not fully resolved.

Safety Rules That Are Non-Negotiable

These rules apply every time, no exceptions:

  • Always disconnect the battery and wait for the backup capacitor to discharge before disconnecting any SRS connector or removing any SRS component. The time varies by manufacturer — look it up for the specific vehicle.
  • Never use a standard ohmmeter, test light, or voltage probe on a squib circuit.
  • Never use jumper wires on SRS circuits for testing purposes.
  • Never reuse a deployed airbag module, pretensioner, or inflator.
  • Never attempt to disassemble an airbag inflator. They are sealed pyrotechnic devices.
  • Store removed airbag assemblies with the deployment face pointed away from you and away from other people. If an undeployed airbag deploys unexpectedly while being handled, the force is directed outward from the bag face.
  • Do not expose airbag modules or inflators to heat or open flame. Dispose of undeployed airbags through an approved process — most manufacturers have procedures for in-vehicle deployment for disposal purposes.

When to Refer to a Specialist

There are situations where the right call is to refer the job to a technician who specializes in SRS systems. Knowing your limits in airbag diagnosis is not a weakness — it is professional judgment, and it can save a life.

Refer out or escalate when you encounter:

  • Internal ACM faults. If the module is reporting an internal failure, it needs to be replaced. Some replacement modules require programming or calibration that requires dealer-level tools. Know whether your shop has that capability before taking on the job.
  • Post-collision situations with multiple deployed components. Full system restoration after an airbag deployment requires systematic replacement of every deployed component, proper programming of replacement modules, and thorough verification. If you are not set up to do this correctly, the vehicle needs to go somewhere that is.
  • Multiple simultaneous SRS codes with no obvious cause. When a scan reveals five or six SRS codes all at once, it usually means one of three things: the vehicle was in an accident, the ACM itself is failing, or there is a power or ground supply issue to the ACM. These situations require careful diagnostic work and experience with SRS systems.
  • Any situation where you are not confident in the diagnosis. This is the most important one. If you are not certain about what you have found or what needs to be replaced, stop. Get a second opinion, consult a specialist, or refer the vehicle to a shop with more SRS experience. The cost of getting it wrong is too high. A customer driving away in a vehicle with an improperly diagnosed or improperly repaired SRS system is in danger.

Final Word

SRS diagnosis is methodical work. Scan the codes, understand what the code is telling you, inspect the circuit, measure correctly with the right tools, repair the fault, and verify the repair. Do not shortcut the process and do not skip safety steps. The clock spring is the most common cause of SRS faults and should be your first area of attention when the code points to the driver airbag circuit with horn and cruise symptoms. Connector issues are the second most common cause and should be inspected before any component is condemned.

The system is designed to protect people in the worst moments of their lives. When it is working, nobody thinks about it. When it fails to work in a crash because a shop cleared the code without diagnosing it, people get hurt who should not have been. Take SRS faults seriously every time, and you will earn a reputation for doing this work correctly. That reputation matters in this trade.

Related Articles

Disclaimer: This article is for educational and informational purposes only. Technical specifications, diagnostic procedures, and repair strategies vary by manufacturer, model year, and application — always verify against OEM service information before performing repairs. Financial, health, and career information is general guidance and not a substitute for professional advice from a licensed financial advisor, medical professional, or attorney. APEX Tech Nation and A.W.C. Consulting LLC are not liable for errors or for any outcomes resulting from the use of this content.