AutoLogicTools

OBD-II trouble code

P0184: Fuel Temperature Sensor "A" Circuit Intermittent

The fault vanishes whenever anyone looks for it, so the usual tools are the wrong ones. Freeze frame — what the vehicle was doing the moment it set — is worth more here than an hour with a multimeter.

Low severityPowertrainFuel & AirDrivable short-term

Quick facts

System
Powertrain
Category
Fuel & Air
Severity
Low severity
Drivable
Usually safe to drive short-term
Repair cost range
$0$600
DIY difficulty
Intermediate DIY

What does P0184 mean?

Every other code in this family describes a condition that is still there when the vehicle reaches the ramp. P0184 describes one that is not. By the time the light comes on the circuit has recovered, the reading looks entirely reasonable, and every measurement anyone takes comes back clean. That single fact inverts the whole approach: you cannot measure your way to an intermittent fault, because measuring only tells you about the moment you are in, and the fault is not in that moment.

Start instead with what set the code. The freeze frame captured when the fault occurred is the closest thing available to a witness statement, and it is usually decisive. Note the road speed, the engine load, the coolant temperature, and how long the engine had been running. Then read the pattern. A code that sets at low speed over broken surfaces and never on smooth motorway is mechanical — a terminal that has lost tension, a connector that is not fully latched, a wire fatigued where the loom crosses a bracket. A code that sets only after twenty or thirty minutes of running, once everything is thoroughly heat-soaked, is thermal — a cracked solder joint that opens as it expands, or a thermistor that goes open only when hot. A code that appears after rain, a car wash, or a wet week and disappears in dry weather is water: a connector seal has failed and moisture is bridging or corroding the pins. Three very different repairs, sorted before touching a tool.

There is a second reason this code cannot be dismissed just because the scan tool looks normal, and it is specific to a temperature sensor. What the controller flags is not an implausible value but an implausible rate of change. A tank of liquid fuel has enormous thermal mass; even under hard use, real fuel temperature moves over minutes, not milliseconds. So a step change of tens of degrees inside a fraction of a second cannot have been the fuel — it has to have been the circuit briefly dropping out and recovering. That is why the reading you see later is irrelevant evidence. The sensor spends almost all its time working correctly. The code is a record of a blink.

The practical consequence is that this is the member of the family where replacing the sensor first fails most often, and it is worth being blunt about that. A part that is intermittently disconnected tests perfectly on a bench and looks perfect at idle, so the temptation to fit a new one is strong and the odds are poor. Loose terminals, chafed insulation, corroded pins and failed connector seals — the causes that actually dominate intermittent codes — are all outside the sensor and all survive its replacement. The right work is provocation: reproduce the conditions from the freeze frame while watching live data, and move things while the circuit is live. Flex the harness section by section, tug each wire behind the connector, warm the area with a heat gun if the pattern is thermal, and mist it with water if the pattern is weather-linked. The moment the reading twitches, you have located the fault instead of guessing at it.

Common causes

  • Terminal that has lost tension so contact breaks under vibration
  • Connector not fully latched, or a failed seal letting water into the pins
  • Fatigue break inside insulation that still looks undamaged from the outside
  • Chafed wire that only touches ground when the harness moves
  • Cracked solder joint or internal sensor fault that opens once heat-soaked
  • Corroded pins that make and break contact as the connector shifts
  • Poor ground connection that changes resistance with temperature or vibration
  • Harness routed too close to a moving or vibrating component after previous repair work

Symptoms

  • Check engine light that comes on, sometimes clears itself, and returns days later
  • Fuel temperature reading normal every time anyone looks at it
  • Brief unexplained jumps in the reading when driving over rough surfaces
  • Fault that follows weather — appearing after rain or a car wash and gone in dry conditions
  • Fault that appears only once the vehicle is thoroughly warmed up
  • Other codes from the same circuit appearing alongside it at random

Diagnostic steps

  1. 1.Read the freeze frame before doing anything else. Road speed, engine load, coolant temperature and run time at the moment it set are the strongest evidence available.
  2. 2.Classify the pattern from that data: rough roads and low speed point to a mechanical connection fault, long run times point to a heat-related one, wet weather points to a failed connector seal.
  3. 3.Graph fuel temperature on a scan tool rather than reading a number. A dropout shows as a vertical spike that a numeric display will never catch.
  4. 4.Wiggle-test the harness in sections while watching the graph — flex each length, tug gently on each wire behind the connector, and press on the connector body.
  5. 5.If the pattern is thermal, warm the connector and the surrounding harness with a heat gun while watching live data, then let it cool and watch again.
  6. 6.If the pattern is weather-linked, mist the connector and harness with water and watch for a reaction. Check the connector seal and the drainage around where it sits.
  7. 7.Open the connector and inspect the terminals for spread contacts, green corrosion and missing seals. Test terminal tension against a known-good mating pin rather than judging by eye.
  8. 8.Resist replacing the sensor until provocation has actually reproduced the fault. Parts fitted on this code without reproduction come back.

Repair cost

$0$600

Most of the cost here is diagnostic time, because finding an intermittent takes longer than fixing it. Expect $90 to $250 for a shop to reproduce and locate the fault. The repair itself is usually a terminal, a seal or a short section of wire at $60 to $200. Sensor replacement, when genuinely warranted, is roughly $70 to $230 fitted on accessible installations.

Estimate your repair

Run the numbers for your vehicle

Open the Repair Cost Estimator with wiring harness / circuit repair preselected. Adjust labor rate and vehicle category to fit your situation.

DIY vs shop

This is an intermediate DIY job. It usually involves diagnostic steps, specialty parts, and some careful work in tight spaces. If you have the tools and a service manual or trustworthy video for your specific vehicle, it is achievable in a weekend. Otherwise, a competent independent shop will be faster.

Related codes

Frequently asked questions

The reading looks fine on my scan tool. Why is there still a code?

Because the code is a record of something that already happened. The circuit dropped out for a fraction of a second and then recovered, and the controller stored the event. What you are looking at now is the sensor working correctly, which it does almost all the time. Reading a numeric display makes this worse — the value refreshes a few times a second and a brief spike passes between refreshes. Switch the scan tool to a graph if it has one, so a dropout appears as a vertical line rather than being averaged out of existence.

What is the freeze frame and why does it matter more than usual here?

The freeze frame is a snapshot of the engine's operating conditions at the instant the code set — road speed, engine load, coolant temperature, run time. On most codes it is helpful background. On an intermittent it is the primary evidence, because the fault itself is gone and this is the only record of when it was present. Setting at low speed on rough roads points at a loose connection; setting only after long warm running points at something opening with heat; setting after rain points at water in a connector. Each of those is a different repair, and the freeze frame chooses between them before you pick up a tool.

Should I just replace the sensor?

It is the least likely thing to fix this particular code, and it is where money most often gets wasted. An intermittently open circuit tests perfectly on a bench and looks perfect at idle, so a new sensor changes nothing when the real fault is a stretched terminal, a chafed wire or a connector full of water. Those all survive the sensor swap and the light comes back a week later. Reproduce the fault first — flex the harness, heat it, wet it, whatever the freeze frame suggests — and replace the sensor only once you have watched the reading move while touching the sensor itself.

How can the controller tell an intermittent fault from a real temperature change?

By how fast the number moved. Fuel sits in a tank and in lines, and liquid has substantial thermal mass, so real fuel temperature changes over minutes even under hard driving. A jump of tens of degrees inside a fraction of a second is not something fuel can do. When the controller sees a step change no physical process could produce, it concludes the circuit briefly failed rather than the fuel briefly boiled, and it stores an intermittent code. That is why the plausible-looking reading you get afterwards does not clear the sensor of anything.

Editorial context

About This Diagnostic Information

AutoLogicTools diagnostic guides explain OBD-II trouble codes using recognized code definitions, standard automotive diagnostic principles, and practical automotive context. A trouble code records a condition detected by a control module. It does not automatically identify a failed part, and the right diagnostic procedure can vary by vehicle.

Manufacturer service information, technical service bulletins, wiring diagrams, and vehicle-specific procedures should take precedence when available.

AutoLogicTools was founded by Vincent Fisk, an automotive locksmith and shop owner in San Diego with hands-on experience in vehicle keys, immobilizer systems, electrical issues, modules, programming, and diagnostics.