B1652 – Crash recorded in passenger side airbag (replace SRSCM) (Hyundai)

B1652 means the airbag system stored a crash event for the passenger-side airbag, and the SRS warning light will stay on. That can leave the Kona’s Supplemental Restraint System unable to protect you correctly in another collision. According to Hyundai factory diagnostic data, this code indicates “Crash recorded in passenger side airbag (replace SRSCM).” Treat that wording as Hyundai’s definition for this platform. Do not assume the code proves a bad module. Confirm power, ground, crash inputs, and data integrity first. Airbag work carries injury risk, so follow Hyundai SRS depowering steps before touching connectors.

B1652 Quick Answer

On Hyundai vehicles, B1652 indicates the SRS control module recorded a passenger-side airbag crash event. Diagnose the SRS module inputs and wiring first, because the message does not prove the SRSCM failed.

What Does B1652 Mean?

Hyundai defines B1652 as: “Crash recorded in passenger side airbag (replace SRSCM).” In plain terms, the SRS control module believes a deploy-level event occurred on the passenger side. Once that happens, the module can latch the event in memory. The SRS light stays on and the system may disable or limit future airbag operation.

For diagnosis, separate the definition from the detection logic. The definition tells you the suspected trouble area: crash record data tied to the passenger-side airbag. The module does not “see” a crash directly. The SRSCM evaluates impact sensor inputs, internal accelerometers, squib circuit status, and event data consistency. It also checks stored deployment records for plausibility. This matters because a crash record can set due to an actual deployment, a prior incident, corrupted event data, or abnormal sensor or power behavior during a key cycle.

Theory of Operation

On a 2019 Hyundai Kona, the SRSCM manages airbags, pretensioners, and related sensors. Under normal conditions, it monitors crash sensors and its internal acceleration sensing. It also supervises squib circuits for continuity using OEM-approved methods. The module stores “event data” when it detects a deploy-level impact.

B1652 sets when the SRSCM’s stored event information indicates a passenger-side airbag crash record. That can happen after a real deployment. It can also occur when the module sees sensor inputs that mimic an impact during an unstable power or ground event. Memory corruption or communication issues during a prior collision repair can also leave invalid crash records. The diagnostic goal stays the same: prove whether the SRSCM logged a true deploy event or logged one due to an input, power, or data fault.

Symptoms

You will usually notice a safety warning first, then scan-tool evidence in the SRS menu.

• SRS light On steadily after key-on and remains on
• Message Airbag warning message in the cluster, if equipped
• SRS scan data Crash/event record information present in SRSCM data lists
• Code behavior B1652 stored as current or history in the SRSCM
• Readiness SRS system status shows faulted or not ready for full deployment logic
• Post-repair issues Code appears after interior or dash work near SRS components
• Related DTCs Other SRS codes may accompany it, especially power, ground, or sensor faults

Common Causes

• Stored crash event in the SRSCM memory: The SRS control module (SRSCM) records a deployment-level event and sets B1652 to indicate a passenger-side airbag crash record exists.
• Low system voltage during the event record write: A weak battery, poor power feed, or unstable ignition supply can corrupt or interrupt crash data storage and trigger an internal crash-record DTC.
• High-resistance SRSCM power or ground: Corrosion, loose fasteners, or damaged wiring can drop voltage under load and cause the SRSCM to log erroneous crash-record status.
• Connector fault at SRSCM or passenger airbag circuit interfaces: Poor pin fit, water intrusion, or terminal fretting can create intermittent opens that the SRSCM interprets as a critical event context.
• Prior collision repair or interior work disturbing SRS wiring: Harness strain, swapped connectors, or pinched wiring after dash, seat, or carpet work can lead to SRS memory faults and crash-record flags.
• Incorrect SRS component configuration or variant coding: Module setup that does not match the vehicle’s restraint configuration can create implausible event logic and store crash-record related faults.
• Aftermarket electrical accessories causing voltage noise: Poorly integrated remote starts, audio amplifiers, or lighting can introduce transients that upset SRSCM logic during key cycles.
• SRSCM internal fault: Internal memory or processor errors can falsely report a recorded crash, but you must prove power, ground, and network integrity first.

Diagnosis Steps

Use a scan tool with full Hyundai SRS access and event data functions. Follow Hyundai SRS depowering procedures before touching any SRS connector. Use OEM-approved backprobing adapters or breakout tools only. Avoid standard test lights and jumper wires on SRS circuits. Keep a DVOM available for power and voltage-drop tests outside the squib circuits.

1. Connect the scan tool and run a complete vehicle DTC scan. Confirm B1652 in the SRS/SRSCM menu and record code status (stored, history, or current). Save freeze frame or event record context, including battery voltage, ignition state, and any companion SRS codes.
2. Review freeze frame versus a technician-triggered snapshot. Freeze frame shows conditions when B1652 set. A snapshot helps catch intermittent voltage dips during cranking or key-on. Do not clear codes as a test step on SRS faults.
3. Check for other SRS DTCs that point to power supply, communication, or specific passenger-side components. Treat those as priorities, because B1652 often appears as a result code when the SRSCM sees an abnormal event environment.
4. Inspect fuses and power distribution feeding the SRS system before you access the SRSCM. Check the related fuses for correct rating and tight fit. Inspect the fuse box for heat damage, moisture, or loose terminals.
5. Verify SRSCM power and ground integrity with voltage-drop testing under load. Command SRS-related modules awake with the scan tool if applicable. Measure voltage drop on the main ground path while the circuit operates, and keep ground drop below 0.1V. Repeat on the power feed side to catch high-resistance connections.
6. Depower the SRS system using Hyundai’s specified procedure and waiting time. Then inspect the SRSCM connectors and harness routing. Look for water intrusion, bent pins, backed-out terminals, or signs of prior interior repair. Pay close attention to harness pinch points near the center console and floor.
7. Inspect passenger-side airbag related connectors and harness segments that interface with the SRSCM logic. Do not probe squib circuits with standard meter leads. Use only Hyundai-approved methods and adapters to avoid accidental deployment and terminal damage.
8. Check network and module communication health if your scan tool supports topology. Confirm the SRSCM appears on the network scan consistently. If the SRSCM drops offline during crank or key transitions, return to power and ground diagnosis and inspect shared grounds.
9. Use the scan tool to read SRS event/crash data status and configuration information, if available. Confirm the vehicle configuration matches the installed restraint components. Mismatched coding after module replacement or repair can produce implausible status flags.
10. After you correct any verified wiring, power, ground, or configuration issues, run the required Hyundai SRS verification routine. Recheck for B1652 and related codes. Confirm the warning lamp behavior matches Hyundai specifications and that the code does not reset on key-on.

Professional tip: Treat B1652 as a “suspected trouble area” indicator, not proof the SRSCM failed. On Hyundai SRS systems, a marginal ground or power feed can mimic internal module faults. Prove the electrical basics with voltage-drop under load first. Use the scan tool’s SRS data to guide you, and avoid any test method that touches squib circuits with generic tools.

Possible Fixes

• Restore SRSCM power and ground integrity: Clean and secure ground points, repair damaged wiring, and correct any fuse/terminal fit issues found during voltage-drop testing.
• Repair connector or harness faults: Address backed-out terminals, corrosion, water intrusion, or pinched wiring at the SRSCM and related passenger-side SRS harness routing.
• Correct SRS configuration or variant coding: Perform the proper Hyundai setup procedures when the system configuration does not match the vehicle’s restraint equipment.
• Remove or correct aftermarket electrical interference: Rework accessory wiring that causes key-on voltage transients or unstable power delivery to the SRS feeds.
• Replace the SRSCM only after verification: If power, ground, connectors, communication, and configuration test good, replace the SRSCM and complete required Hyundai post-install procedures.

Can I Still Drive With B1652?

You can usually drive a 2019 Hyundai Kona with B1652 without engine or braking changes, but you should not treat it as “safe to ignore.” This manufacturer-specific Hyundai SRS code indicates the SRSCM has crash event data tied to the passenger-side airbag. When this code sets, the SRS warning lamp often stays on, and the system may disable part or all of the airbag and pretensioner strategy. Do not attempt DIY probing or “quick checks” at airbag connectors. Follow Hyundai SRS depowering procedures before any SRS work, and use a scan tool with full SRS access to confirm system status.

How Serious Is This Code?

This code is serious because it involves the Supplemental Restraint System, not because it affects drivability. In many cases the vehicle drives normally, so owners keep using it. That creates risk during a collision. Treat the SRS system as potentially compromised whenever the SRS lamp stays on or an SRS DTC remains current. Diagnosis requires OEM-approved SRS test methods and proper training. Standard multimeters, test lights, and back-probing can damage SRS circuits or trigger deployment risk. A professional-level scan tool must read Hyundai SRSCM data, event history, and readiness states before any repair decisions.

Common Misdiagnoses

Technicians often misread B1652 as a simple “bad passenger airbag” and order parts immediately. Others replace the SRSCM because the description mentions it, without verifying power, ground, and network integrity first. Some shops chase seat wiring and the passenger presence system, even though this code points to crash record logic stored in the SRSCM. Another common mistake involves unsafe testing. Probing squib circuits with standard leads can alter resistance and create new faults. Avoid wasted spending by confirming SRSCM communication, checking for other SRS codes, and verifying module power/ground voltage drop under load before any module decision.

Most Likely Fix

The most common confirmed repair direction involves correcting the reason the SRSCM reports a crash record, then performing the Hyundai-required service action for event data. That may include SRSCM replacement and programming, but only after you verify proper battery supply, ignition feed, grounds, and CAN communication at the SRSCM connector. A second frequent direction involves resolving related SRS DTCs that accompany the event record, such as pretensioner or passenger airbag circuit faults, before condemning the module. Use OEM procedures for depowering, connectors, and post-repair SRS checks.

Repair Costs

SRS/airbag repair costs vary significantly by component. Diagnosis must be performed by a qualified technician with SRS-capable equipment. Do not attempt airbag system repairs without proper training and safety procedures.

Last updated: March 31, 2026