P1B28 – Crash detection (Mitsubishi)

Mitsubishi-specific code — factory diagnostic data

Last updated: March 29, 2026

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

P1B28 means your 2016 Mitsubishi Outlander logged a “crash detection” fault. In plain terms, the vehicle thinks a crash event signal happened or that crash data looks wrong. That can change how the vehicle behaves after an impact. It can also limit starting or disable some powertrain functions on certain Mitsubishi platforms. According to Mitsubishi factory diagnostic data, this is a Mitsubishi-defined code meaning Crash detection. Treat it as a safety-related input or message problem, not a confirmed failed part. Your job is to prove which module set it and what crash-related signal it received.

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

P1B28 Quick Answer

P1B28 on Mitsubishi means the powertrain side saw a crash detection condition. Verify which module reported it and confirm the crash input or network message before replacing anything.

What Does P1B28 Mean?

Official definition: “Crash detection.” That means a Mitsubishi control module stored a DTC because it saw a crash event status that did not match expectations. In practice, the car may act like it experienced an impact, even if it did not.

What the module checks: the module does not “sense” a crash by itself in most designs. It validates a crash status coming from another module, a dedicated crash/impact sensor path, or a network message. Why that matters: diagnosis must focus on the signal path and message integrity first. Per SAE guidance, the DTC points to a suspected trouble area. It does not prove a bad airbag module, sensor, or ECU.

Theory of Operation

Under normal conditions, Mitsubishi modules share vehicle status over the network. Crash status typically originates in the restraint system side. The powertrain module then uses that status to make safety decisions.

P1B28 sets when the powertrain-side logic sees an implausible crash status. It can also set when crash status appears at the wrong time. Lost messages, corrupted data, low module voltage, or a reset during key events commonly cause that mismatch.

Symptoms

P1B28 often shows up with scan-tool clues first, then possible drivability or safety-function changes.

• Scan tool behavior Crash-related status shows “active,” “latched,” or “implausible,” or the code returns immediately after clearing
• MIL/Check Engine Check engine light on, depending on Mitsubishi strategy and stored status
• Warning lamps Additional warning indicators may appear if other modules also flag faults
• No-start Engine may crank and not start on some configurations after a crash status
• Reduced power Limited throttle response or torque reduction on some platforms
• Intermittent Code sets only after bumps, battery service, or wet weather
• Related DTCs Network, low-voltage, or module reset codes stored alongside P1B28

Common Causes

• Crash-status message latched by a safety module: A crash event can set a status that other modules store as a crash detection fault until the event clears correctly.
• CAN communication interruption during or after an impact event: A brief loss of network messages can make the powertrain side interpret crash detection as invalid or missing.
• Low system voltage during crank or after battery service: Voltage sag can corrupt module messaging and trigger a crash-related plausibility fault in Mitsubishi logic.
• High resistance at shared power or ground splice: Corrosion at a splice can drop module voltage under load and distort crash-status inputs or network bias.
• Connector damage near the front structure or kick panels: Impact or water intrusion can loosen terminals and cause intermittent open circuits on networks and module feeds.
• Aftermarket device interference on the CAN circuits: Trackers, remote starts, or audio interfaces can load the network and disrupt the crash-status data stream.
• Incorrect module configuration after replacement: If a Mitsubishi module loses coding or setup, it may not publish or interpret crash-related status correctly.
• Faulty crash-related input path used by the powertrain module: Depending on platform, a discrete signal or gatewayed message can fail and point the code at crash detection logic.

Diagnosis Steps

You need a scan tool that can read Mitsubishi OEM-enhanced data and run a full network scan. Use a quality DMM and a test light. Have back-probing pins and terminal tools ready. A wiring diagram and connector views matter here. If you suspect intermittent faults, use a scan tool snapshot during a road test.

1. Confirm P1B28 and record all DTCs from every module. Save freeze frame data, especially battery voltage, ignition state, vehicle speed, and any related network or SRS/ETACS codes. Freeze frame shows the conditions when the DTC set. Use a snapshot later to catch an intermittent drop while driving.
2. Check battery condition and charging basics first. Inspect battery terminals for looseness and corrosion. Verify the main power distribution and related fuses for modules involved in crash detection and communication. Do a quick visual of the circuit path and harness routing before meter testing.
3. Verify ECU and network-related module power and ground under load. Use voltage-drop testing, not just continuity. Load the circuit with key ON and modules awake, then measure ground drop and power-side drop at the module connectors. Keep ground drop under 0.1V with the circuit operating.
4. Run a full Mitsubishi network scan and confirm which modules report. Note any modules that do not communicate or show “no response.” If a safety-related module drops off the network, P1B28 can become a secondary symptom. Record module IDs and the time each code logged.
5. Inspect connectors and harness sections that commonly see stress on an Outlander. Focus on areas near the radiator support, front rails, kick panels, and under-dash junction blocks. Look for backed-out terminals, water trails, bent pins, and signs of previous collision repair.
6. Check for aftermarket equipment tied into CAN, ignition, or accessory power. Remove or isolate add-on modules one at a time. Re-scan after each change. Many intermittent “crash detection” flags come from network loading or poor splices.
7. Use live data to evaluate crash-status related parameters. Look for any “crash,” “impact,” “fuel cut,” or “collision signal” PIDs available in the powertrain module and any gateway/body module. Compare the state with the vehicle condition. A stuck “active” status points to a latched input or missing reset logic.
8. Perform targeted circuit checks based on the wiring diagram. If Mitsubishi routes crash status through a gateway message, focus on the CAN circuits, termination integrity, and module wake-up behavior. If the platform uses a discrete input, check that signal for shorts to power/ground and for clean switching. Do not assume which design the vehicle uses without service information.
9. Stress-test the suspected area for intermittents. Wiggle harnesses while watching live data and module communication status. Use a scan tool snapshot to capture the exact moment the status flips or a module drops off-line. Match the snapshot timing to any new pending or confirmed faults.
10. Clear codes and perform a controlled key cycle. Recheck for immediate returns on key ON. A hard fault will typically reset quickly after clearing. If the code stays away, run a short drive with normal electrical loads and monitor battery voltage and network stability.
11. Confirm the repair by repeating the same conditions shown in freeze frame. Verify the module network scan stays stable and P1B28 does not return as pending or stored. If the vehicle uses Type B logic for this monitor, confirm it does not return on the next drive cycle.

Professional tip: Treat P1B28 as a “suspected area” code, not a condemned part. Start by proving network health and module power integrity. A single loose ground can create crash-status implausibility across multiple modules. Use voltage-drop under load to catch that fault fast.

Possible Fixes

• Repair battery terminal issues, main grounds, or corroded power distribution connections found during voltage-drop testing.
• Restore CAN harness integrity by repairing damaged wiring, replacing spread terminals, and correcting poor splices.
• Remove or rewire aftermarket accessories that load the network or share module power/ground improperly.
• Repair water intrusion sources and clean/repair affected connectors in kick panels, under-dash junction areas, or front structure zones.
• Perform correct Mitsubishi module setup or configuration after verified power/network repairs, if a replaced module lacks proper initialization.
• Replace a module only after you prove correct power, ground, and communication lines at its connector and you confirm it fails to publish or interpret crash status correctly.

Can I Still Drive With P1B28?

You can often drive a 2016 Mitsubishi Outlander with P1B28 stored, but you should treat it as a safety-related warning. This code indicates the powertrain side received a “crash detection” state. That state can force protection actions. The vehicle may limit power, inhibit start, or disable hybrid/EV functions on some Mitsubishi platforms. Do not continue driving if the car shows reduced power, warning messages, or erratic throttle response. Also stop driving after any actual impact, even a minor one. Have the vehicle inspected first. A crash event can damage wiring, grounds, and network communication. Those faults can trigger more modules and cause unpredictable behavior.

How Serious Is This Code?

P1B28 ranges from an inconvenience to a serious drivability limitation. If the Outlander drives normally and the code appears as history, you may only deal with a stored event that needs confirmation checks. However, the “crash detection” input often acts like a system-wide safety flag. Mitsubishi logic may command shutdown of certain powertrain functions to reduce risk after a collision. That can create a no-start, limp mode, or a restart lockout until modules agree on system state. If the code appears with airbag, ABS, or stability codes, treat the vehicle as compromised. At that point, focus on verifying power, grounds, and network integrity before any parts decisions.

Common Misdiagnoses

Technicians often replace parts because they assume P1B28 means a failed sensor. That wastes time and money. On Mitsubishi platforms, “crash detection” usually travels between modules over a network message or a discrete input. A weak battery, poor ground, or voltage drop during cranking can corrupt that message and set the code. Another common mistake involves clearing codes without checking freeze-frame and event history. That erases evidence of when the crash flag set. Shops also skip connector inspection after bumper or radiator support work. Pin fit problems and water intrusion near the front harness can mimic a crash event. Confirm the input state and communication first.

Most Likely Fix

The most common confirmed repair directions involve restoring clean power and communication, not replacing a “crash sensor” immediately. Start by correcting battery health, terminal tightness, and chassis ground integrity. Then repair any harness damage, corrosion, or pushed pins in the networks and module connectors that carry the crash detection status. If a scan tool shows the crash status stuck “ON” with no impact, verify the source module data and input wiring before condemning a module. When the system reports a legitimate crash event, proper reset procedures may apply. Use Mitsubishi service information to confirm required initialization steps.

Repair Costs

Repair cost depends on whether the confirmed root cause is wiring, connector condition, a sensor, a module, or the labor needed to diagnose the fault correctly.