Check Engine Light Diagnosis

Diagnose the cause of an illuminated Check Engine Light on a 2009 Aston Martin DB9 using an OBD-II scanner to retrieve diagnostic trouble codes and identify system faults.

Warnings

Tools required

Preparation

1. Park vehicle on level ground and apply parking brake.
2. Turn ignition to OFF position and remove key.
3. Ensure vehicle has been driven long enough to reach normal operating temperature if fault is temperature-dependent.
4. Gather vehicle service history if available to identify recurring issues.

Procedure

1. 1

   Locate OBD-II diagnostic port
   The OBD-II diagnostic port on the 2009 DB9 is located beneath the driver's side dashboard in the lower kick panel/footwell area. Consult the owner's manual or factory documentation for exact location, then crouch down and use a flashlight to locate the 16-pin trapezoid connector. Note: The OBD-II diagnostic port on the 2009 DB9 is located beneath the driver's side dashboard in the lower footwell area. Consult the owner's manual or Aston Martin service documentation to confirm the exact location for this vehicle. You may need to crouch down and use a flashlight to locate the 16-pin trapezoid connector. Note: The OBD-II diagnostic port on the 2009 DB9 is located beneath the driver's side dashboard in the footwell area. Crouch down and use a flashlight to locate the 16-pin trapezoid connector, checking the underside of the dash panel and near the steering column if not immediately visible.
2. 2

   Connect diagnostic scanner
   Plug the OBD-II scanner connector firmly into the diagnostic port. Ensure the connection is secure and fully seated. Turn the ignition key to the ON position (do not start the engine). The scanner should power on and attempt to establish communication with the vehicle's engine control module. Note that the 2009 DB9 uses an Aston Martin/Ford-derived electronics architecture, and some generic OBD-II scanners may have limited communication; full access to all modules may require the Aston Martin Diagnostic System (AMDS) or a compatible dealer-level tool.
3. 3

   Retrieve diagnostic trouble codes
   Navigate the scanner menu to read stored diagnostic trouble codes (DTCs). Record all codes displayed, including both current (active) codes and pending codes. Note the code descriptions provided by the scanner. Also record freeze-frame data associated with each code, which captures engine conditions when the fault occurred (RPM, coolant temperature, vehicle speed, etc.).
4. 4

   Document code details
   Write down or photograph all diagnostic information: the full DTC number (e.g., P0420, P0171), the fault description, freeze-frame data, and the number of fault occurrences if displayed. Note whether the Check Engine Light status is shown as continuous or intermittent. This documentation is critical for repair planning and warranty claims.
5. 5

   Check for manufacturer-specific codes
   If your scanner supports enhanced diagnostics, navigate to the manufacturer-specific code section. Aston Martin uses additional proprietary codes beyond standard OBD-II P-codes (P0xxx through P3xxx). These may provide more specific fault identification for DB9-specific systems. Record any additional codes found.
6. 6

   Perform visual inspection based on codes
   Based on the retrieved codes, perform a targeted visual inspection of related components. For oxygen sensor codes (P0130-P0167, P0420-P0434), inspect exhaust system for leaks. For mass airflow sensor codes (P0100-P0104), check air intake system for loose connections or damaged ducting. For misfire codes (P0300 random misfire, plus P0301-P0312 for individual cylinders 1 through 12 on this V12), inspect the individual coil-on-plug ignition coils and spark plugs for visible damage or oil contamination. Confirm the cylinder-to-bank numbering against Aston Martin documentation before locating a specific misfiring cylinder. Look for obvious issues like disconnected vacuum lines, damaged wiring harnesses, or fluid leaks near sensors. Note: For misfire codes (P0300-P0312, covering all 12 cylinders), inspect the coil-on-plug ignition coils and spark plugs for visible damage or oil contamination.
7. 7

   Check for technical service bulletins
   Research the specific DTCs retrieved against Aston Martin technical service bulletins (TSBs) for the 2009 DB9. Many Check Engine Light conditions have known patterns and manufacturer-recommended solutions. Check whether the retrieved DTCs correspond to any documented Aston Martin service bulletins; do not assume generic fault patterns apply to this platform without verifying against factory documentation. Document any relevant TSBs for reference during repair.
8. 8

   Assess fault severity and drive cycle status
   Determine whether the fault requires immediate attention or can be monitored. Codes related to emissions (catalyst efficiency, EVAP system) typically allow continued driving. Codes indicating misfires, fuel system issues, or critical sensor failures may require immediate repair to prevent engine damage. Note whether the fault is occurring continuously or only under specific conditions based on freeze-frame data.
9. 9

   Generate diagnostic report
   Compile all findings into a diagnostic report: list all DTCs retrieved, freeze-frame conditions, visual inspection results, related TSBs, and recommended next steps for repair. Prioritize faults by severity. Identify which components require testing with a multimeter or specialized tools versus those requiring replacement. For complex issues involving multiple related codes, identify the likely root cause versus secondary faults.
10. 10

    Disconnect scanner and prepare for repair
    Do NOT clear codes at this stage unless specifically required for a subsequent repair verification test. Turn ignition OFF and disconnect the OBD-II scanner from the diagnostic port. Store the scanner safely. If immediate repair is not planned, advise that the vehicle can typically be driven but the fault condition will persist and may affect emissions or performance.

Reassembly

1. No disassembly required for this diagnostic procedure.
2. After completing any repairs based on diagnostic findings, clear codes using the scanner and perform a drive cycle to verify the Check Engine Light does not return.

Verification

• Confirm all diagnostic trouble codes have been recorded accurately with complete descriptions and freeze-frame data.
• Verify the diagnostic report clearly identifies the affected system(s) and recommends specific repair actions.
• After subsequent repairs, verify the Check Engine Light remains off through at least one complete drive cycle (cold start, city driving, highway driving, and cool-down).
• Use the scanner to confirm readiness monitors have reset to 'Ready' status after repairs, indicating the system has completed self-tests.

Related trouble codes on this vehicle

Codes that commonly send this job to the bay — tap one for symptoms, causes, and diagnostic steps.

Chasing one of these codes and not sure which part is guilty? Ask a master mechanic about YOUR car →

More procedures for this vehicle