Comprehensive diagnostic guide for OBD-II code B0109

Important Notes

• B0109 is a body (B) category OBD-II code. The exact OEM-specific description of B0109 varies by manufacturer and model year, so the precise DTC description must come from the vehicle's OEM diagnostic data or service documentation. In general, B-codes in the body domain often relate to occupant detection/airbag systems or related body-sensor circuitry.
• summarize OBD-II structure and the existence of B-codes as part of body diagnostics, but do not give a universal, year/model-specific meaning for B0109. Therefore, treat B0109 as vehicle-specific and verify the exact description with OEM information (scan tool description, service data, or manufacturer bulletins).
• If OEM data for B0109 is available via your scanning tool or service manual, use that exact definition as the primary diagnostic target.
• The following guide provides a thorough, safe, fault-tree style diagnostic approach applicable when B0109 is present, with symptom-based reasoning and safe repair practices. It also includes probability-based guidance when no NHTSA-compiled data is available and relies on ASE-field experience.

Symptoms

• Airbag/RSN (sensing and safety) warning light is ON or intermittent.
• Occupant classification or seat weight sensor indicators show fault or inconsistent readings (e.g., "unoccupied" reading when a person is seated).
• Intermittent SRS warning with seat movement or recline actions.
• No obvious engine symptom; warning lights illuminate the vehicle may still run, but safety modules are disabled or degraded.
• User complaints often center on the airbag indicator being lit, or the occupant-detection system not recognizing a proper seated occupant.

Safety and precautions (must-do before working on SRS/occupant systems)

• These systems deploy in a crash; do not work on them unless you are trained and qualified.
• Disconnect the battery carefully and follow proper SRS service procedures. Many OEMs require a minimum wait period (often several minutes) after battery disconnect to avoid accidental airbag deployment.
• Use proper PPE and store airbag modules in a safe position if removal is required.
• Avoid applying static electricity or turning the ignition on/off repeatedly while the system is under test.

Tools and data you'll typically use

• OBD-II scan tool capable of reading enhanced (OEM) DTC descriptions and freeze-frame data; a technician-level or higher tool is preferred to view vehicle-specific DTC text.
• OEM service information for the vehicle (workshop manual, SI/service bulletins) to interpret B0109 precisely.
• Data stream access to occupant detection system (OCS) / seat weight sensor parameters if your tool provides them.
• Basic electrical test equipment: multimeter, test leads, known-good wiring harness reference, and a seat cushion sensor resistance/diagnostics guide if applicable.

Diagnostic Approach

1) Verify the DTC and gather context

• Confirm B0109 is current (not a historical code) and note any freeze-frame data. If freeze-frame data includes specific readings (seat weight sensor values, airbag system status, ignition status, etc.), document them.
• Check for related DTCs in the same subsystem (other body/SRS codes such as those in the occupant classification/airbag family). The presence of multiple body/SRS codes often points to a common cause (sensor harness, module, or calibration).

2) Determine the OEM description for this vehicle

• Access the OEM diagnostic description for B0109 in the vehicle's service data or via the scan tool's OEM description. The exact description guides the initial fault hypothesis (for example, occupant classification system fault, seat mat fault, airbag module fault, or related harness fault).
• If OEM data is not available, proceed with a structured body/OCS-airbag oriented diagnostic flow and treat B0109 as a potentially vehicle-specific occupant or airbag system fault.

3) Symptom-focused data gathering

• If available, review the occupant classification system data in the data stream (OCS sensor reading, seat sensor status, occupant classification sensor calibration state).
• Note any abnormal readings associated with the seat or occupant sensor: unusual weight readings, sensor out-of-range values, intermittent loss of signal, or sensor not ready states.
• Observe any physical indicators: seat harness connector corrosion, seat cushion damage, or seat wiring that moves with seat adjustment.

4) Electrical and wiring checks (common failure points)

• Inspect the seat/wiring harness where it travels under the seat. Look for damaged insulation, loose connectors, bent pins, or exposed conductors caused by seat movement.
• Check the seat occupant sensor/weight sensor (if accessible). Some systems use a pressure/weight sensor under the seat; others use electronic sensing in the seat mat. Inspect connectors and test continuity and resistance if service data provides a sensor map.
• Check vehicle ground points related to the SRS/body controller and the occupant detection system. A poor ground can cause intermittent sensor behavior and fault codes.
• Inspect main SRS power and communication lines for voltage stability and clean, dry connections.

5) Component-level testing (vehicle-specific as available)

• Occupant Classification Sensor / Seat Weight Sensor:
  • If service data provides a resistance/voltage map, compare your measurements to spec at known seating conditions (empty seat vs. occupied).
  • Inspect the sensor for signs of wear, moisture intrusion, or damage.
  • If a single sensor appears out of spec consistently, plan for sensor replacement (and recalibration if required by OEM).
• Occupant Detection Module or OC Sensor Module:
  • Check for module ground integrity and power supply.
  • Look for fault indicators in the module (wiring harness issues, mis-mounted module, or software faults).
• Airbag System Modules and Crash Sensors:
  • Scan for any related airbag crash sensor or module faults if OEM data ties B0109 to the airbag system.
  • Check for damaged or corroded connectors at the airbag modules or their harnesses.

6) Perform calibration/learning procedures if applicable

• Some occupant classification systems require recalibration or "learning" after a sensor or seat assembly replacement. If OEM data indicates a calibration procedure, perform it exactly as specified (and verify after calibration that the system transitions to a ready/OK state).
• Do not skip calibration steps if the OEM procedure requires them; post-calibration, re-check the DTC list and perform a drive cycle to ensure no reoccurring fault.

7) Clear codes and verify repair

• After performing the suspected repair (sensor replacement, harness repair, ground fix, re-seat electrical connections, or software update), clear the DTCs with the scan tool and perform a vehicle power-on self-test (if the tool supports it).
• Drive or cycle the ignition as required by the OEM procedure and re-scan to confirm that B0109 does not return and that any related codes are resolved.
• Monitor for any intermittent reappearance; if it recurs, re-check wiring and connectors and consider alternative fault sources (e.g., a failed module or software issue).

Common Causes

• Faulty seat weight sensor / occupant classification sensor in the seat: high likelihood (roughly 35-45% in many vehicles with OC systems). This is a frequent cause when B0109 ties to occupant detection or seat sensor signals.

• Damaged or loose seat harnesses and connectors under the seat: common cause, particularly with seat adjustments or sliding seats causing connector wear or pin damage (about 20-30%).

• Airbag module or crash sensor fault within the body/SRS network: moderate likelihood (roughly 10-20%), especially if B0109 is paired with other SRS codes or if the warning light behavior suggests a module fault.

• Software/OCS calibration or learning requirement not yet performed after work: smaller but real possibility (roughly 5-15%), particularly after sensor or module replacement.

• Other wiring or grounding faults in the body/OCS network: residual probability (roughly 5-15%), often secondary to root cause changes or intermittent connections.

• Because the exact B0109 description is vehicle-specific, consult OEM service data for a definitive description and recommended test steps. If OEM data is unavailable, use the symptom-driven flow above as a robust diagnostic approach.

• If you have access to GitHub repositories with standard DTC definitions, they can help confirm that B0109 is a body-domain code and provide a general sense of how B- codes map to occupant/airbag systems; however, rely on OEM data for the precise description and procedure.

• If you have access to NHTSA complaints or field data for the particular vehicle, incorporate observed patterns (e.g., common failure modes and consumer-reported symptoms) to adjust the suspected-cause probabilities. In the absence of such data in your sources, rely on the ASE-field experience and the vehicle-specific OEM flow.

What to communicate to the vehicle owner

• The exact meaning of B0109 is model-specific; the diagnostic steps described above aim to identify which subsystem is causing the fault (OCS/seat sensor, airbag module, harness, or related control electronics).

• Repairs in this domain can affect passenger safety systems. Any replacement or recalibration should be performed to OEM specifications, and a post-repair safety verification should be completed (including confirming the airbag light is extinguished after a successful repair and a proper vehicle test).

• After any work on occupant sensing or airbag components, re-check for any additional codes and confirm that the system is in a ready/OK state.

• For general DTC structure and the concept that DTCs are categorized by function (P, B, C, U), see Wikipedia's OBD-II overview and sections on Diagnostic Trouble Codes and Powertrain Codes (as provided ). These sources confirm that body (B) codes exist and are part of the OBD-II diagnostic framework.

• OEM-specific meaning, wiring diagrams, sensor specifications, calibration procedures, and any related service bulletins must come from the vehicle's official service information. If you have access to GitHub-based DTC definition repositories, use them to confirm standard code type and general categories, but rely on OEM data for the actual B0109 description and test steps.

This diagnostic guide was generated using verified reference data:

• Wikipedia Technical Articles: OBD-II

Content synthesized from these sources to provide accurate, real-world diagnostic guidance.

---