AutoLogicTools

OBD-II trouble code

B009C: Left Side Restraints Sensor 6 (Subfault)

The airbag module has a fault with left-side impact sensor 6. The word Subfault in the title is the important part — the base code tells you almost nothing, and the symptom byte stored with it tells you almost everything.

High severityBodyAirbag / SRS RestraintsDrivable short-term

Quick facts

System
Body
Category
Airbag / SRS Restraints
Severity
High severity
Drivable
Usually safe to drive short-term
Repair cost range
$100$1,400
DIY difficulty
Shop recommended

What does B009C mean?

B009C is a body code stored by the airbag control module against the sixth satellite impact sensor on the left side of the vehicle. The character after B009 is the letter C rather than a number, because these codes are hexadecimal. Satellite sensors are the small accelerometers distributed through the doors, pillars and rocker structure that tell the module how hard and how fast a side impact is developing, and their data is what the module uses to decide whether to fire side airbags, curtains and belt pretensioners.

The most useful thing to understand about this code is the word Subfault in its title, because it changes how the code should be read. B009C on its own is not a diagnosis. It identifies which sensor the module is complaining about and nothing more. Stored alongside it is a symptom byte — a second value that states what kind of fault the module actually saw: an open circuit, a short to ground, a short to voltage, a signal present but implausible, an internal sensor self-test failure, or a communication error with the sensor. Those are entirely different repairs with entirely different costs, and they share one base code.

This has a practical consequence that trips a lot of people up. Many generic scan tools either cannot access the airbag module at all or display the base code with the symptom byte truncated. Two vehicles can present with an identical B009C on a cheap reader and need completely different work. If the tool in front of you shows B009C and nothing after it, the diagnosis has not started yet — it needs a tool that reads the manufacturer's restraints module properly and displays the full fault with its sub-fault description. That is not an upsell, it is the difference between testing a circuit and guessing at one.

The second consideration is specific to the left side of a left-hand-drive vehicle: it is the traffic side. It faces oncoming and overtaking vehicles, it takes mirror clips in narrow lanes, and it is the side involved in the everyday minor contact that owners do not always mention or even notice. That matters because satellite sensors are designed to detect exactly this kind of lateral event. A left-side satellite fault following any sort of side contact, however minor, raises a question that has to be answered before parts are ordered: has the module recorded a crash event?

That question has teeth. On a number of manufacturers, once the restraints module has stored crash data it will not clear, regardless of how correct the subsequent repair is. The module either has to be replaced or sent for professional reset by a specialist. A technician who repairs a genuine wiring fault, clears the code and watches it return immediately may conclude the repair failed, when in fact the repair was fine and the module is locked by stored event data. Check the module's crash-data status early, not after the third attempt.

The vehicle drives normally. Nothing about this fault affects the engine, the brakes or the steering. What it affects is whether the left-side restraints do their job in an impact, and that is reason enough not to leave it. Airbag systems contain pyrotechnic devices that can fire if the system is not safely powered down first, so this is work for someone equipped to disable the system correctly.

Common causes

  • Open, short to ground or short to voltage in the sensor circuit — the symptom byte identifies which
  • Corroded or water-intruded connector at the left-side satellite sensor
  • Wiring damaged by door-hinge flex where the harness crosses into the door
  • Failed satellite sensor reporting an internal self-test error
  • Restraints module locked by stored crash data from an earlier event
  • Sensor mounting bolt loose or the sensor not seated flat against the structure
  • Shared supply or ground fault affecting several left-side satellites at once
  • Previous body repair on the left side that disturbed the sensor or its harness
  • Non-approved splice or crimp repair in a circuit whose resistance window is tightly specified

Symptoms

  • Airbag or SRS warning light illuminated
  • B009C stored in the restraints module with a symptom byte appended
  • No effect whatsoever on engine, braking or handling
  • Fault that changes state when the left front door is opened and closed
  • Code that returns immediately after clearing, which may indicate stored crash data rather than a failed repair
  • Other left-side satellite sensor codes stored at the same time
  • Generic scan tool showing the base code only, with no sub-fault detail

Diagnostic steps

  1. 1.Use a scan tool that can access the manufacturer's restraints module and display the full fault including its symptom byte — the base code alone is not a diagnosis.
  2. 2.Record the symptom byte and translate it against the manufacturer's table, because open, shorted, implausible and internal-failure conditions are different repairs.
  3. 3.Ask about any recent side contact on the left, however minor, and check the module's crash-data status before ordering parts.
  4. 4.If the module has recorded an event, establish whether it can be reset or must be replaced, since a locked module will reject a perfectly good repair.
  5. 5.Locate left-side sensor 6 for this specific vehicle from the manufacturer's data rather than assuming a position.
  6. 6.With the system safely disabled to the manufacturer's procedure, inspect the sensor connector for moisture, corrosion and backed-out terminals.
  7. 7.Work the door through its full travel while monitoring, since flex damage in the door harness shows itself with movement rather than at rest.
  8. 8.Confirm the sensor is bolted down to specification and sitting flat, because a satellite that is not solidly coupled to the structure can report an implausible signal while testing electrically perfect.
  9. 9.Check supply and ground against specification, and if several left-side sensors have logged codes together, investigate the shared circuit rather than the individual sensors.
  10. 10.After repair, clear the fault with the SRS tool connected, then verify the light stays off through an ignition cycle and a road test.

Repair cost

$100$1,400

SRS diagnostic time is $100 to $220 and requires a tool that can read the restraints module properly — a generic reader that shows only the base code cannot do this job. A connector or wiring repair is $120 to $400. A satellite impact sensor is $60 to $260 in parts with the required system checks, typically $200 to $550 fitted. The outcome that changes the number completely is a module locked by stored crash data: professional reset by a specialist runs $80 to $250, while a replacement restraints module with programming is $400 to $1,400. Establishing crash-data status early is what keeps that from becoming a surprise at the end of the job.

Estimate your repair

Run the numbers for your vehicle

Open the Repair Cost Estimator with airbag / srs crash sensor replacement preselected. Adjust labor rate and vehicle category to fit your situation.

DIY vs shop

Leave this one to a qualified shop. It typically involves emissions-critical components, refrigerant handling, or other work that requires manufacturer-grade tooling, training, or certification. DIY attempts often produce a more expensive problem than the original code.

Related codes

Frequently asked questions

My scan tool shows B009C and nothing else. Is that enough to fix it?

No, and this is the central point about this code. The word Subfault in the title means the base code only names which sensor the module is unhappy about. Stored with it is a symptom byte that states what the module actually saw — an open, a short to ground, a short to voltage, an implausible signal, an internal sensor failure or a communication error. Those are different faults with different repairs and different prices, and they all display as B009C on a tool that truncates the detail. If your reader shows only the base code, the diagnosis has not begun. It needs a tool that reads the manufacturer's restraints module in full.

I repaired the wiring but the code will not clear. What now?

Before assuming the repair failed, check whether the module has stored crash data. On a number of manufacturers, once the restraints module has recorded an impact event it latches and will not clear no matter how correct the subsequent work is — the module must be replaced or professionally reset. This catches people out because a good repair and a locked module produce identical symptoms: the light comes straight back. It is worth checking the module's event status early in the process rather than after several attempts and a second set of parts.

The car had a small scrape down the left side a while ago. Is that relevant?

Very possibly. On a left-hand-drive vehicle the left side faces traffic, so it collects the minor lateral contact that satellite sensors are specifically designed to detect — mirror clips, sideswipes, contact in narrow lanes. Two things can follow. The impact itself may have disturbed the sensor or its wiring, which is a straightforward repair. Or the module may have registered the event and stored data even though nothing deployed, which affects whether the fault can be cleared at all. Mention the incident to whoever diagnoses it, even if it looked like nothing at the time.

Why can this not be a DIY repair?

Because the system contains pyrotechnic devices that can fire if it is not powered down correctly, and because the diagnosis genuinely depends on tooling most home garages do not have. Beyond the safety issue, restraints circuits are specified within narrow resistance limits, so an ordinary crimp repair that would be fine anywhere else on the car can push the circuit out of range and create a fault that passes inspection on the day and returns a fortnight later. A qualified technician can disable the system safely, read the sub-fault properly and make a repair to the manufacturer's specification.

Editorial context

About This Diagnostic Information

AutoLogicTools diagnostic guides explain OBD-II trouble codes using recognized code definitions, standard automotive diagnostic principles, and practical automotive context. A trouble code records a condition detected by a control module. It does not automatically identify a failed part, and the right diagnostic procedure can vary by vehicle.

Manufacturer service information, technical service bulletins, wiring diagrams, and vehicle-specific procedures should take precedence when available.

AutoLogicTools was founded by Vincent Fisk, an automotive locksmith and shop owner in San Diego with hands-on experience in vehicle keys, immobilizer systems, electrical issues, modules, programming, and diagnostics.