All Technical Guides

Permanent Diagnostic Trouble Codes (Mode $0A): Why Clearing Codes Fails

CM
Written by Christopher Anthony Mellers, Automotive Software Engineer & Trade Mechanic.
Updated September 2026 • Technical Diagnostic Series

The History and Purpose of Permanent DTCs (Mode $0A)

In 2010, the California Air Resources Board (CARB) and the EPA mandated the implementation of Permanent Diagnostic Trouble Codes (PDTCs) under OBD2 Service Mode $0A. Permanent codes were introduced to solve an enduring regulatory problem: drivers clearing trouble codes in the parking lot of an inspection station and driving through before the Check Engine Light illuminated again.

Unlike stored codes (Mode $03) or pending codes (Mode $07), a Permanent DTC cannot be erased by ANY scan tool, diagnostic computer, or battery disconnection. If you disconnect the car battery for three days, or press "Clear Codes" on a professional $5,000 diagnostic tablet, active codes and readiness monitors will be erased, but the Permanent DTC remains locked in non-volatile electrically erasable programmable read-only memory (EEPROM).

The only entity on Earth that has the cryptographic and functional authority to delete a permanent trouble code is the vehicle's own engine control module—and it will only do so after it runs the relevant diagnostic monitor in real-world driving and verifies that the physical fault is cured.

How Permanent DTCs Clear Themselves

To have the ECU automatically erase a Permanent DTC under Mode $0A, the vehicle must satisfy three distinct criteria:

Permanent DTC Telemetry Reference Table

The operational telemetry tracked by the ECU regarding permanent code clearing includes:

Telemetry Parameter Standard PID / Service Normal Operating Range Fault / Failure Threshold
Permanent DTC Count Mode 0x0A Service 0 Permanent DTCs stored > 0 (blocks inspection in CA/NY)
Warm-up Cycles Since Clear PID 0x30 > 40 warm-up cycles completed < 15 cycles (insufficient monitor run time)
Distance Since Codes Cleared PID 0x31 > 200 km (125 miles) < 50 km (indicates recent clearing)
Time Run with MIL On PID 0x4D 0 minutes (healthy system) Accumulated engine run time with active fault

Passing Emissions Inspections with Permanent Codes

If you live in a state or province that enforces permanent DTC inspection checks (such as California under BAR OBD inspection rules), understanding how inspectors evaluate permanent codes is critical:

  1. The 200-Mile / 15 Warm-Up Cycle Exemption Rule: Recognizing that some monitors take weeks to complete under normal driving, CARB rules allow vehicles with an active Permanent DTC to pass inspection if: (a) all standard readiness monitors are Ready, (b) the MIL is off, and (c) the vehicle has been driven at least 200 miles and completed 15 warm-up cycles since the last code-clearing event.
  2. Do NOT Clear Codes Again: The most common mistake drivers make after completing a mechanical repair is pressing "Clear Codes" repeatedly. Every time you send the Mode $04 clear command, you reset the Distance Since Codes Cleared (PID 0x31) back to zero miles and reset all readiness monitors back to Not Ready. This restarts the 200-mile clock from scratch!
  3. Let the MIL Turn Off Automatically: Once you complete a repair (such as replacing an ignition coil for P0300), do not erase the codes. Drive the vehicle normally. After three consecutive driving cycles where the monitor passes, the ECU will automatically extinguish the Check Engine Light. Shortly thereafter, the Permanent DTC will vanish from Mode $0A.

Related OBD2 Diagnostic Trouble Codes

Review individual fault code definitions, ECU detection mechanisms, and evidence tables:

P0420 Guide →P0171 Guide →P0300 Guide →P0455 Guide →

Diagnose Telemetry Live on Android

OBDAssistant pairs with any Bluetooth OBD2 scanner to chart live PIDs, read Mode $06 monitors, and explain trouble codes tailored to your vehicle.

Install OBDAssistant Free