AutoLogicTools

OBD-II trouble code

B0095: Right Frontal Restraints Sensor (Subfault)

On a left-hand-drive vehicle this is the kerb-side corner, and kerbs, gutters and wheel-arch debris are what it lives with. It also sits in a decision chain the other frontal sensor does not — the one that decides whether the passenger airbag should fire at all.

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
$120$800
DIY difficulty
Shop recommended

What does B0095 mean?

B0095 is stored by the airbag control module against the right frontal restraints sensor — the forward crash sensor on the right-hand side of the front structure. The module has found the circuit outside the narrow tolerance restraint circuits are held to, or has stopped receiving data it considers credible.

Start by orienting yourself, because right and left are defined from the driver's seat looking forward regardless of which side the steering wheel is on, and getting this wrong sends people to the opposite corner of the car. On a left-hand-drive vehicle this sensor sits on the front passenger corner, which is the kerb side. On a right-hand-drive vehicle it sits on the driver's corner, which is the crown side. The physical exposure is different in each case and it is worth knowing which you have before you form an opinion about the cause.

On left-hand-drive vehicles — the larger population for this code — being the kerb-side corner has real consequences. It is the corner that meets kerbs during parking, the corner that takes debris thrown up out of the gutter, and the corner that sits in the standing water that collects at the road edge. It is also, in most cases, the side that has already had a wheel-arch liner damaged or partly detached, because that is what kerb strikes and potholes do to plastic liners. A missing or torn liner takes away the shielding between the road and the harness, and once that is gone the connector gets a direct feed of spray and grit for as long as the liner stays broken. Checking the liner is part of diagnosing this code, not a separate observation.

The second thing that distinguishes this sensor from its counterpart on the other side is what its data feeds into. Both frontal sensors report the crash, but the passenger side of the restraint system carries a decision the driver's side does not: whether to deploy the passenger airbag at all, and at what force, given what the occupant classification system is reporting about who or what is in that seat. An empty seat, a child seat, or a light occupant all change the answer. So on a left-hand-drive vehicle a right frontal sensor fault sits inside a chain that also includes the seat weight or occupant classification sensor, the passenger belt buckle switch, and on many vehicles a passenger airbag status lamp on the dashboard.

That has a practical consequence when reading the fault memory. If this code appears alongside occupant classification faults, or if the passenger airbag status lamp has been behaving oddly, resist treating those as unrelated. The module makes one decision for that side of the car using several inputs, and a fault in one of them will often have prompted the driver to notice a symptom they attributed to something else entirely.

Beyond that, the failure modes are the ordinary ones for a component mounted at the very front of a vehicle: corrosion inside the connector, a chafed or crushed harness, a cracked housing, a bent bracket. Front-mounted restraint connectors fail from water and salt far more often than the sensors inside them do, so a connector that looks poor is a finding rather than an incidental observation.

Repair history is worth asking about specifically. A nearside kerb strike, a pothole taken at speed, or a low-speed parking scrape on the passenger corner all produce front-end work — a liner, a bumper cover, sometimes a headlamp — and every one of those jobs happens within reach of this sensor and its wiring. A code that appeared shortly after that kind of repair points at what was disturbed rather than at what failed.

The vehicle drives normally. Nothing about the engine, transmission, brakes or steering is affected, which is exactly why this fault gets left. Treat it as professional work: the restraint system must be safely disabled with the manufacturer's standing time observed before any connector is separated, and a crash sensor reads through its mounting, so it has to be refitted to specification rather than merely tightened.

Common causes

  • Corrosion in the right frontal sensor connector from kerb-side spray and standing water
  • Damaged or missing wheel-arch liner leaving the harness unshielded
  • Kerb strike or pothole impact on the nearside front corner
  • Failed right frontal impact sensor
  • Harness chafed where it runs along the right front rail or behind the liner
  • Previous nearside front-end repair that disturbed the sensor, bracket or wiring
  • Sensor refitted loose, over-torqued or with incorrect hardware
  • Wrong part number fitted during a repair
  • Shared supply or ground fault affecting more than one restraints sensor
  • Failed input channel in the airbag control module

Symptoms

  • Airbag or SRS warning lamp illuminated
  • B0095 stored in the restraints module
  • Passenger airbag status lamp behaving unexpectedly on some vehicles
  • No change at all in how the vehicle drives
  • Fault appearing after a kerb strike or nearside parking scrape
  • Fault appearing after wheel-arch liner, bumper or headlamp work on that corner
  • Occupant classification codes stored at the same time
  • Warning lamp returning within a few key cycles of being cleared

Diagnostic steps

  1. 1.Establish which physical corner you are looking for before you jack anything up. Left and right are defined from the driver's seat looking forward regardless of where the steering wheel is, so on a left-hand-drive vehicle this is the front passenger corner and on a right-hand-drive vehicle it is the driver's corner. Getting this backwards sends people to the opposite side of the car.
  2. 2.Check the wheel-arch liner on that corner before anything else. On the kerb side it is routinely torn, partly detached or missing after a kerb strike or a pothole, and that liner is what shields the harness and connector from spray and grit. If it is damaged, you have both a likely cause and a repair that has to be done or the new connector will go the same way.
  3. 3.Read the whole restraints fault memory and look specifically for occupant classification and passenger belt buckle faults. The passenger side of the restraint system carries a decision the driver's side does not — whether to fire that airbag at all and at what force, based on what is in the seat — so codes in that chain are frequently related rather than coincidental. Ask whether the passenger airbag status lamp has been behaving oddly.
  4. 4.Disable the restraint system following the manufacturer's procedure and observe the specified standing time before separating any connector. The system holds enough reserve energy to fire a pyrotechnic device after the battery is disconnected.
  5. 5.Inspect the connector with a light rather than by feel, looking inside both halves for green or white deposits, terminals that have lost tension, and a seal that has hardened or slipped from its groove. Front-mounted restraint connectors fail from water and salt considerably more often than the sensors behind them do.
  6. 6.Follow the harness by hand from the connector back through the arch and along the rail, checking where it crosses a bracket edge, passes a fastener or sits against bodywork. On the kerb side, damage tends to be abrasive rather than a clean break — look for a sheath worn shiny or flattened.
  7. 7.Measure the circuit against the manufacturer's specification from the sensor end and again from the module end. That separates a harness fault from a failed sensor in one step. Restraint circuits use narrow make-specific bands, so a generic value is not a substitute.
  8. 8.If the corner has had recent body repair, check the sensor part number, the bracket and the torque before condemning anything. A crash sensor reads acceleration through its mounting, so an incorrectly torqued bolt, a distorted bracket or substituted hardware changes what the module receives even when the electrical readings are perfect.
  9. 9.After the repair, clear the code, complete the specified ignition cycles and confirm the lamp performs its bulb check and extinguishes. Confirm the passenger airbag status lamp is behaving correctly as well if the vehicle has one.

Repair cost

$120$800

Diagnosis is $100 to $200 and requires a scan tool with restraints module coverage. Repairing a corroded connector or a damaged length of front harness is $120 to $350 and is the most common outcome on this corner. Replacing a torn or missing wheel-arch liner, which is often the underlying reason the connector corroded, adds $40 to $180 and is worth doing rather than skipping. A right frontal impact sensor is $60 to $300 for the part plus half an hour to two hours of labour, at the upper end where the bumper cover or liner has to come off. If the fault involves the occupant classification system rather than the sensor itself, that is a separate diagnosis with its own cost. Where several restraint sensors are implicated and the fault traces to the control module, module service or replacement with configuration is $400 to $1,300.

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

Which side of the car is the right frontal sensor on?

Right and left are always defined from the driver's seat looking forward, regardless of which side the steering wheel is on. So on a left-hand-drive vehicle this sensor is on the front passenger corner — the kerb side — and on a right-hand-drive vehicle it is on the driver's corner. It sounds obvious, but this is a common way to lose an hour, because the assumption that right means the driver's side is very natural and wrong half the time.

Why would a kerb strike cause an airbag code?

Because on a left-hand-drive vehicle this is the kerb-side corner, and the damage kerbs do is not always to the wheel. A kerb strike or a pothole routinely tears or partly detaches the wheel-arch liner, and that liner is what shields the sensor's harness and connector from road spray and grit. Once it is gone the connector gets a direct feed of water and salt for as long as the liner stays broken, and corrosion follows. If you replace the connector without replacing the liner, you will be doing the same job again.

The passenger airbag light has been odd too. Are they connected?

Quite possibly, and it is worth mentioning to whoever diagnoses the car. The passenger side of the restraint system carries a decision the driver's side does not: whether to deploy that airbag at all and at what force, based on what the occupant classification system reports about who or what is in the seat. That decision draws on several inputs — the frontal sensor, the seat weight or classification sensor, the belt buckle switch — so faults in that chain often show up together, and drivers usually notice the status lamp before they notice the SRS lamp.

Is it safe to carry a passenger with this code stored?

The car drives normally and the restraint system has not been switched off, but it has told you it cannot vouch for its full performance on that side, and this is not a fault to postpone. Seat belts remain your primary restraint and should be worn as normal. If the passenger airbag status lamp is also behaving unexpectedly, treat that as additional reason to get it looked at promptly rather than as a separate minor annoyance.

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.