TorqueMech Beta
TorqueMech OBD Code Guide

P0119 - Engine Coolant Temperature Circuit Intermittent

The coolant temperature sensor signal is intermittent.

Treat the code as the starting point: compare symptoms, likely causes, and repair paths before pricing parts or moving into an estimate.

Explore Related Systems

Use system hubs to compare the code against nearby repair families before estimating parts.

Common Next Steps

Use these checks to turn the code into a practical workflow before estimating parts.

Review fuel trims

Compare trims at idle, 2500 RPM, and cruise before pricing sensors.

Add Inspection
Inspect vacuum leaks

Check intake boots, PCV hoses, and post-MAF leak paths.

Open Workflow
Check MAF sensor

Inspect MAF contamination and airflow data after intake leaks are considered.

Add Inspection
Inspect intake tubing

Look for cracked ducts, loose clamps, and unmetered air after the MAF.

Add Inspection

Related Inspection

Code Overview

The coolant temperature sensor signal is intermittent.

Common Causes

  • Loose coolant temperature sensor connector
  • Failing ECT sensor dropping in and out
  • Broken or chafed wiring in the ECT circuit
  • Coolant intrusion or corrosion in the connector

Symptoms

  • Temperature gauge or scan data jumps around
  • Cooling fans may cycle oddly
  • Intermittent rich or lean cold-start behavior

Diagnostic Steps

  1. Wiggle-test the ECT connector and harness while watching scan data
  2. Inspect the connector for corrosion or coolant intrusion
  3. Check reference voltage, ground, and signal integrity at the sensor
  4. Compare ECT behavior to actual engine temperature during warm-up

Repair Difficulty

Easy

General difficulty estimate for the most common repair path.

Likely Repairs & Cost Guides

Use symptoms, scan data, and quick checks to confirm the likely repair path before pricing parts. The estimator helps compare repair paths before replacing anything unnecessarily.

Engine coolant temperature sensor replacement

Estimator-ready next step after the fault path is confirmed.

Next Steps

Move from code lookup to diagnosis, then estimate the likely repair only after symptoms, causes, and checks point to the same path.