B1652 – Crash recorded in passenger side airbag (Replace SRSCM) (Kia)

Kia-specific code — factory diagnostic data

B1652 means the Kia EV6 SRS has stored a crash record tied to the passenger-side airbag. For most owners, the real-world effect is simple. The airbag warning light stays on and the SRS may not protect you correctly until repairs are completed. According to Kia factory diagnostic data, this manufacturer-specific code indicates “Crash recorded in passenger side airbag (Replace SRSCM).” This code does not act like a typical wiring fault. It points to a post-crash event record inside the SRS control module, not a loose connector you can wiggle and fix.

🔍Decode any Kia EV6 VIN — free recalls, specs & safety ratings — free VIN decoder with NHTSA data

B1652 Quick Answer

On Kia vehicles, B1652 sets when the SRS control module logged a crash/deployment record for the passenger-side airbag. If a collision occurred, follow Kia post-collision SRS procedures, which typically require SRSCM replacement and a full SRS verification.

What Does B1652 Mean?

Officially, Kia defines B1652 as “Crash recorded in passenger side airbag (Replace SRSCM).” In plain terms, the SRS control module decided a crash threshold happened for the passenger side, and it saved that event in memory. In practice, you treat the vehicle like it has post-collision SRS needs, even if the exterior looks “fine.”

Technically, the SRSCM (SRS Control Module) monitors crash sensor inputs, internal accelerometers, and deployment loop status. When it detects a crash event that meets its logic, it writes a crash record and may lock certain functions. That matters for diagnosis because you must confirm the event record and collision evidence first. SAE J2012 guidance applies here: the DTC message identifies a suspected trouble area, not the root cause.

Theory of Operation

In normal operation, the Kia EV6 SRSCM continuously evaluates impact severity and direction. It uses that data to decide if it must command restraints, such as airbags and pretensioners. The module also runs self-tests and monitors SRS readiness. It turns the airbag warning lamp off only after it confirms proper system status.

When the module logs a crash record tied to the passenger-side airbag, it stores that data as a safety event. Many Kia platforms treat this as a non-clearable record with a standard scan tool. The system then keeps the warning lamp on until you complete post-crash service steps. If the vehicle was not in a crash, you must prove why the module wrote the record before you replace anything.

Symptoms

Drivers and technicians usually notice one or more of these symptoms with B1652:

• Airbag light stays on or returns immediately after clearing attempts
• SRS message displays a restraint system warning in the cluster
• Code persistence B1652 resets as “current” right after a key cycle
• No clear scan tool cannot clear the code due to event memory status
• Post-repair clues signs of prior interior work near passenger airbag components
• Other SRS DTCs additional crash-related or configuration codes stored with B1652
• Readiness SRS may show “not ready” or “fault present” in scan tool status

Common Causes

• Prior collision with passenger-side airbag event recorded: The Kia SRS control module stores a crash record when it calculates a deployment-level event on the passenger side.
• Deployed or replaced passenger-side SRS components after an impact: A deployed passenger airbag, seat belt pretensioner, or related restraint component often accompanies a stored crash record and triggers this DTC.
• SRSCM internal crash memory locked from clearing: Kia designs many SRS controllers to retain crash data that a scan tool cannot erase, even after repairs.
• Low system voltage during a severe event or jump-start: A voltage collapse can corrupt event data or set SRS memory flags that mimic a recorded crash condition.
• Incorrect post-collision repair sequence: Skipping required SRS inspections, leaving deployed devices connected, or reinstalling parts out of order can keep the module in a crash-recorded state.
• Damaged SRS wiring or connectors on the passenger side: Harness pinch, connector damage, or water intrusion near passenger-side components can create implausible signals that lead to a false event record.
• Non-OEM seat, dash, or interior work affecting SRS sensing: Aftermarket interior work can disturb impact sensor mounting, harness routing, or grounding, which can affect crash detection logic.
• Poor SRSCM power or ground integrity: High resistance at the module power feed or ground can cause resets or memory write errors that resemble a stored crash record.

Diagnosis Steps

You need an OEM-capable Kia scan tool that can access SRS event data and full DTC details. Use a quality DMM for power and ground voltage-drop checks. Have OEM service information for SRS depower procedures and connector handling rules. Do not probe airbag or pretensioner squib circuits with standard meter leads.

1. Confirm B1652 sets in the Kia EV6 SRS menu and record all SRS codes. Save freeze frame or “environment data” for ignition state, battery voltage, and any event/status flags. Freeze frame shows what happened when the DTC set. A scan-tool snapshot is technician-triggered and helps catch intermittent voltage drops.
2. Inspect fuses and power distribution that feed the SRS system before you touch the SRSCM connector. Check for blown fuses, loose fuse legs, heat damage, and signs of prior bypass work. Verify the correct fuse type and seating in the fuse block.
3. Verify SRSCM power and ground under load with voltage-drop testing. Backprobe only approved power and ground circuits, not squib circuits. Load the circuit with key ON so the module wakes up, then measure drop across grounds and feeds. Keep ground drop under 0.1V with the circuit operating.
4. Confirm whether the vehicle actually had a collision or deployment-level event. Inspect the passenger side for replaced trim, dash fasteners, new seat belts, pretensioner marks, airbag seams, or evidence of panel repair. Compare VIN history and repair invoices when available.
5. Use the scan tool to read SRS crash/event records and status data. Look for “crash stored,” “deployment command,” “pretensioner activated,” or similar event indicators. Document what the SRSCM reports for passenger-side deployment status and any “replace module” direction.
6. Depower the SRS system using Kia service information and wait the specified time before disconnecting anything. Then inspect SRSCM connectors for water tracks, corrosion, bent pins, pin push-out, or improper terminal tension. Reconnect using correct locking steps and verify no harness strain exists.
7. Inspect passenger-side SRS-related harness routing and connector condition. Focus on areas disturbed during body work, dash work, or seat removal. Look for crushed conduit, chafing near brackets, and connector CPA locks left open.
8. If you find no crash evidence and event data looks inconsistent, perform targeted circuit integrity checks for SRSCM power, ground, and communication lines only. Do not ohm-check or apply test power to squib circuits. Confirm stable battery supply during key ON and during crank, since resets can create memory faults.
9. Attempt to clear the DTC with the OEM-capable scan tool after you correct any power, ground, or connector issues. Cycle the ignition and rescan. A true stored crash record will usually remain and the module will still report a crash-recorded state.
10. Confirm the repair using a full SRS self-test and a complete rescan. Verify the airbag warning lamp proves out correctly and stays off. Recheck for stored and pending SRS codes after a key cycle and after a short road test, following Kia post-repair verification steps.

Professional tip: Treat B1652 as a post-crash record first, not a wiring fault. The fastest wrong turn involves chasing passenger-side connectors before you review SRS event data. If freeze frame shows a normal key-on setting with stable voltage, the SRSCM likely retained a crash record. If freeze frame shows low voltage, verify power and ground drops before you condemn anything.

Possible Fixes

• Complete Kia post-collision SRS inspection and service procedure: Verify all deployed or damaged restraint components and replace required items before final code clearing attempts.
• Repair SRS power or ground feed issues: Correct high-resistance connections, damaged fuse contacts, or poor grounds that can corrupt SRSCM memory writes.
• Repair connector or harness damage affecting the SRS system: Restore terminal tension, remove corrosion, and correct routing or pinched sections using approved methods.
• Replace the SRSCM only after confirmation steps: If event data confirms a stored crash record, follow Kia procedures, then set up and calibrate as required and perform full SRS verification.
• Correct improper prior repairs: Rework non-OEM splices, incorrect interior installation, or missing connector locks that can keep the SRS system in a faulted state.

Can I Still Drive With B1652?

You can usually drive a Kia EV6 with B1652 in the sense that the car will still move normally. Do not treat that as “safe.” This DTC points to a crash event record stored by the SRS control logic for the passenger side airbag. When the SRS stores a crash record, you must assume the restraint system may not operate as designed in the next impact. Plan on professional service immediately. Avoid carrying a front passenger until a qualified shop completes post-collision SRS inspections and verifies full system status with an OEM-capable scan tool.

How Serious Is This Code?

B1652 is serious because it involves the Supplemental Restraint System. It does not typically cause drivability issues like misfires or stalling. It can feel like an “inconvenience” if the only symptom is an airbag warning lamp. That mindset causes costly mistakes. The SRS system should be treated as potentially compromised any time it logs a crash record. Proper diagnosis requires SRS-certified equipment, training, and OEM procedures. Do not attempt DIY testing of airbag circuits or modules. Incorrect probing can deploy components or create new faults.

Common Misdiagnoses

Technicians often misread B1652 as a passenger airbag circuit fault and start chasing connectors, seat harnesses, or the passenger airbag module. That wastes time because this DTC centers on a stored crash event record, not a simple open or short. Another common error involves trying to clear codes repeatedly and returning the vehicle without completing post-crash SRS inspection steps. Shops also skip confirming crash history and physical evidence, then argue about “false codes.” Avoid those traps by pulling SRS event data with Kia-capable tooling, confirming collision indicators, and following the post-collision workflow before any parts decisions.

Most Likely Fix

If the vehicle experienced a collision and the SRS logged a crash threshold event affecting the passenger side airbag logic, the most common repair path follows Kia post-collision SRS procedures. That typically includes replacing the SRSCM and completing required setup, coding, and system verification with factory-level diagnostics. Do not treat replacement as automatic until you confirm the crash record and inspect the restraint system end-to-end. If you find no crash evidence, then investigate secondary causes like prior module installation errors, power supply interruptions, or damaged harnesses.

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: April 9, 2026

Definition source: Kia factory description · Autel MaxiSys Ultra & EV. Diagnostic guidance is based on factory-defined fault logic for this code.