What it means
B0051 sets when the SRS module records that airbags and/or seat-belt pretensioners were commanded to deploy in a crash. Most OEM service info classifies B0051 as a latched crash event: it’s stored after deployment is requested and does not clear with a normal scan-tool reset. Saab Wisonline+2Saab Wisonline+2
Symptoms
- Airbag/SRS indicator on; B0051 stored as a crash record. Saab Wisonline
Severity / priority
High (safety system state). The code itself indicates a prior deployment command; the system typically requires module service before returning to normal readiness. Charm
Common causes
- Actual crash event that triggered an SRS deployment command.
- On some platforms, B0051 is explicitly documented as latched (cannot be cleared); the fix is SDM/RCM replacement or a crash-data reset procedure per manufacturer policy. Charm+1
Diagnostic notes
- Confirm with an SRS-capable scan tool; review event data if accessible.
- Follow OEM service-manual instructions for post-crash handling (inspection/replacement of deployed components and control module). Charm
Possible fixes
- Replace the SRS control module (SDM/RCM) or perform an OEM-approved crash-data reset, then complete all required post-crash SRS component replacements and calibrations. Charm
Primary sources: Saab WIS “B0051 — Deployment Commanded” (conditions/criteria), and GM service-manual extracts noting B0051 is a latched code requiring SDM service/replacement. Saab Wisonline+2Saab Wisonline+2
Supplemental reference: Trade sources summarizing that B0051 reflects stored crash data in the ACM/SDM. MyAirbags