| DTC Data Sheet | |
| System | Body |
| Standard | Manufacturer Specific |
| Fault type | General |
| Official meaning | Crash recorded in 1st stage only (Frontal – Replace SRSCM) |
Definition source: Hyundai factory description · Autel MaxiSys Ultra & EV. Diagnostic guidance is based on factory-defined fault logic for this code.
B1650 means the airbag system has stored a crash record, so the SRS warning light will usually stay on and the airbags may not protect you in another crash. For most owners, the takeaway is simple. Treat this like a post-collision airbag system issue, not a “sensor glitch.” According to Hyundai factory diagnostic data, B1650 indicates Crash recorded in 1st stage only (Frontal – Replace SRSCM). Hyundai uses manufacturer-specific logic for this code, so the meaning and repair path follow Hyundai SRS post-crash procedures. This code has also been confirmed in Hyundai Ioniq and IONIQ 5 applications.
Decode any Hyundai Kona VIN — free recalls, specs & safety ratings — free VIN decoder with NHTSA data
B1650 Quick Answer
B1650 sets when the Hyundai airbag control module recorded a frontal crash event in the first stage only. If the vehicle had a collision, the correct repair path typically requires SRSCM replacement and full SRS post-crash verification.
What Does B1650 Mean?
Official definition: “Crash recorded in 1st stage only (Frontal – Replace SRSCM).” In practice, the AB (Airbag) module stored an internal crash event record. The module decided a frontal crash threshold for stage 1 was met and logged it. That record usually keeps the SRS lamp on and can inhibit normal readiness until post-crash service completes.
What the module is checking: This is not a simple wiring DTC. The SRSCM monitors internal accelerometer signals and decision logic for staged deployment. It then stores non-volatile “event” data when its algorithm crosses a calibrated frontal impact threshold for stage 1. Why it matters: You diagnose it by confirming crash history and reading SRS event data first. You do not chase squib circuits or replace sensors before you confirm the stored crash record.
Theory of Operation
Under normal conditions, Hyundai’s SRSCM (SRS control module) constantly evaluates vehicle deceleration and impact inputs. It runs an internal algorithm to decide whether deployment is needed. When conditions do not meet thresholds, the module keeps all deployment outputs inactive and maintains SRS readiness.
For this specific DTC, the SRSCM stored a frontal crash record for the first stage only. That staged decision can occur in real collisions. It can also appear after module swaps, incorrect post-collision repairs, or improper power handling that corrupts stored event status. The key point stays the same. The module logged an event, and Hyundai service logic treats it as a post-crash condition that blocks normal system status.
Symptoms
You will usually notice these SRS-specific symptoms with B1650:
- SRS warning light stays on and does not clear with normal key cycles
- Stored AB (Airbag) DTC B1650 returns immediately after clearing attempts
- Airbag readiness shows not-ready or fault status on an OEM-capable scan tool
- Crash/event data indicates a recorded frontal stage event in module data lists
- Post-collision evidence may exist, such as replaced airbags, trim, or seat belt parts
- Secondary SRS codes may appear for pretensioners, airbags, or impact sensors after a collision
- Inspection failure occurs due to the illuminated airbag indicator
Common Causes
- Confirmed collision event recorded: The Hyundai SRS control module logged a frontal crash threshold and stored a stage-1 crash record that does not clear normally.
- Prior deployment or near-deployment event: A previous impact can store event data even if some airbags did not deploy, which leaves the AB (Airbag) module locked in a post-crash state.
- Used or incorrect SRSCM installed: A salvaged or wrong-part-number module can already contain crash memory or mismatch coding, which triggers B1650 as soon as it powers up.
- Low system voltage during an impact or power-up: A weak battery, jump-start, or charging disturbance can corrupt SRS event storage and create an implausible crash record.
- Power or ground integrity fault to the SRSCM: High resistance at a ground point or power feed can reset the module during self-check and lead to stored event flags.
- Connector damage at the SRSCM from prior repairs: Backed-out terminals, water intrusion, or pin drag at the AB module connector can interrupt critical signals during initialization.
- Post-collision harness damage in the front structure: A front-end impact can stretch or pinch harness routing and disturb SRS inputs, which supports an event record diagnosis.
- Incorrect post-collision service procedure: Clearing codes without completing Hyundai’s SRS post-crash steps can leave event data active and return B1650 immediately.
Diagnosis Steps
Use an OEM-capable Hyundai scan tool or a high-end aftermarket tool with SRS access, plus a quality DVOM. Have service information for connector views and fuse locations. Follow SRS depower procedures before touching AB (Airbag) connectors. Do not probe squib or pretensioner circuits with standard meter leads.
- Confirm B1650 in the AB (Airbag) module and record all SRS DTCs. Save freeze frame or event record data if the tool provides it. Focus on ignition state, battery voltage, vehicle speed, and any crash/event status fields. Freeze frame shows the conditions when the code set.
- Interview the owner and inspect the vehicle for collision evidence before any deep testing. Look for replaced bumper covers, mismatched paint, new seat belts, deployed airbags, replaced dash parts, or fresh fasteners. Check for an insurance history or prior salvage branding if available.
- Run a full vehicle network scan and note any companion DTCs. Pay attention to restraint-related codes for pretensioners, impact sensors, and occupant classification. A crash record code often appears with post-collision repair faults.
- Check SRS-related fuses and power distribution first. Verify each fuse has correct feed and load-side power with the circuit powered. Do not jump straight to the SRSCM connector until you confirm fuse integrity and proper fuse seating.
- Verify SRSCM power and ground integrity using voltage-drop testing under load. Load the circuit with the module connected and powered. Measure voltage drop on the ground path and keep it below 0.1V with the circuit operating. Repeat on the power feed side to catch high-resistance connections.
- Depower the SRS system using Hyundai procedures and wait the specified time. Then inspect the SRSCM connectors and nearby harness routing. Look for water intrusion, corrosion, pin push-out, bent terminals, or evidence of prior probing. Repair connector or terminal issues before you consider any module action.
- Verify the module identity and configuration on the scan tool. Confirm the part number, variant coding, and calibration information match the vehicle. If the SRSCM appears used or mismatched, treat that as a primary direction before chasing other faults.
- Use the scan tool to review SRS event data and crash status parameters. Distinguish between freeze frame (captured when the DTC set) and a scan tool snapshot (captured by you during testing). A snapshot helps only if the concern appears intermittently, which is uncommon for crash record codes.
- If the vehicle shows clear crash history or stored event data, follow Hyundai post-collision SRS procedures. Plan for SRSCM replacement and required setup steps, plus inspection of related restraint components. Do not attempt to “clear” a stored crash record as a repair.
- If you find no credible crash history, no collision evidence, and the data looks inconsistent, isolate secondary causes. Recheck battery condition, charging stability, power/ground drops, and connector integrity. Then clear codes and cycle the ignition to see if B1650 returns immediately.
- Confirm the repair by running an SRS self-check and rescanning all modules. Verify the AB (Airbag) warning lamp performs the normal prove-out and stays off. Ensure no pending or stored SRS codes remain after the required verification steps.
Professional tip: Treat B1650 as a post-crash record first, not a wiring fault. A hard crash record usually returns on key-on after a clear attempt. If power and ground voltage-drop tests pass and the event data looks valid, move to OEM post-collision SRS steps instead of chasing sensors.
Possible Fixes
- Complete Hyundai post-collision SRS inspection: Inspect belts, pretensioners, airbags, front structure, and related wiring before finalizing any SRS repair.
- Replace the SRSCM per OEM procedure: If crash data remains stored, replace the SRS control module and perform required configuration and verification steps.
- Restore SRSCM power and ground integrity: Repair high-resistance grounds, loose fasteners, or damaged power feeds confirmed by voltage-drop testing under load.
- Repair SRSCM connector or terminal damage: Correct backed-out pins, corrosion, water intrusion, or harness strain found during the depowered inspection.
- Install the correct, new module and correct coding: Replace any incorrect or used SRSCM and confirm proper variant coding to prevent immediate code return.
- Stabilize battery and charging system: Correct low voltage and poor charging performance that can contribute to abnormal SRS memory behavior.
Can I Still Drive With B1650?
You can usually drive the vehicle, but you should not treat it as “normal.” Hyundai B1650 means the AB (Airbag) module stored a frontal crash event record for the 1st stage only. That record often disables parts of the SRS until the system passes post-crash service checks. The vehicle may drive fine, but occupant protection may not work as designed in another impact. Drive only if you must, avoid carrying passengers when possible, and schedule proper SRS service immediately. Do not attempt DIY airbag work or connector checks under the dash without depowering and following OEM SRS procedures.
How Serious Is This Code?
This code is serious for safety, even when drivability feels unchanged. B1650 does not behave like a typical circuit DTC you can “chase” with a meter. It indicates the SRS logic logged a crash threshold event for the frontal first stage. Hyundai platforms commonly treat that as a post-collision condition that requires an OEM-directed repair path and full SRS verification. In rare cases, an electrical issue or incorrect prior repair can mimic the record, but you must prove that with OEM-capable diagnostics. Treat the SRS as potentially compromised. Diagnosis and repair require SRS-certified tools, training, and safe depowering practices.
Common Misdiagnoses
Technicians often misread B1650 as a wiring or sensor fault and start ohming circuits. That wastes time and creates safety risk. Another frequent mistake involves clearing codes and returning the car without completing Hyundai post-crash inspections, seat belt pretensioner checks, and module replacement requirements tied to recorded events. Some shops replace crash sensors or airbags first because “stage 1 only” sounds like a sensor problem. The module record drives the repair direction, not guesswork. Avoid wasted spending by confirming crash evidence, reviewing SRS event data with an OEM-level scan tool, and following the post-collision service flow before ordering parts.
Most Likely Fix
If the vehicle experienced a frontal impact and the AB (Airbag) module stored an event, the most common OEM-correct direction involves completing Hyundai post-collision SRS service, which typically includes SRSCM replacement and a full system scan and verification. Do not treat that as automatic until you confirm the event record and inspect for deployed components and replaced interior parts. If you find no crash history or physical evidence, shift to secondary causes. Focus on power/ground integrity, module mounting damage, and prior SRS repairs that could corrupt stored event data.
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.
| Repair Type | Estimated Cost |
|---|---|
| Professional diagnosis (SRS-certified) | $150 – $250 |
| Wiring / connector / clock spring repair | $100 – $500+ |
| Side airbag / squib module replacement | $400 – $1200+ |
| SRS ECU replacement / reprogramming | $500 – $2000+ |
Key Takeaways
- B1650 on Hyundai: The AB (Airbag) module stored a frontal crash record for 1st stage only.
- Not a normal circuit DTC: The code points to a post-crash event record, not a simple open or short.
- Safety first: Assume SRS protection may be reduced until verified and repaired.
- Confirm before parts: Prove crash history and read event data with an OEM-capable scan tool.
- Typical repair path: Post-crash SRS procedure often leads to SRSCM replacement and system validation.
FAQ
Does B1650 mean the SRSCM is definitely bad?
No. Per SAE J2012 guidance, the DTC message does not prove a failed part. B1650 means the Hyundai SRS logic stored a frontal crash record for the first stage. A confirmed collision usually triggers module replacement per OEM procedure. Verify the event record, collision evidence, and post-crash inspection results before concluding anything.
Is it safe to diagnose or repair B1650 at home?
No. Treat SRS faults and crash-record codes as high-risk. Airbag and pretensioner circuits can deploy if handled incorrectly. Use Hyundai-approved depowering steps, wait times, and test methods. Do not probe squib circuits with standard test leads. An SRS-certified technician with OEM-capable scan equipment should handle diagnosis and post-crash verification.
Can a scan tool clear B1650, and will it stay cleared?
A basic scan tool may show the code, but it often cannot clear a stored crash record. Even if it clears temporarily, the AB module can re-flag the condition during its next self-check. Use an OEM-capable tool that can access SRS event data and post-crash functions. If a crash record exists, clearing alone does not complete the repair.
If there was no crash, what should I check first?
Start with proof, not guesses. Confirm no collision history and inspect for replaced airbags, seat belts, or trim. Then check module power and ground integrity with proper load testing and voltage-drop methods. Inspect SRSCM mounting and connectors for water intrusion or impact damage. Also verify no prior repair introduced incorrect parts or poor terminals.
How do I verify the repair is complete after SRS work?
Verification requires more than a short drive. Perform a full SRS scan and confirm no active or stored codes return after a key cycle and module self-test. Some Hyundai platforms run additional plausibility checks under specific conditions. Those enable criteria vary by model and system. Follow Hyundai service information for the exact post-repair check and confirmation steps.