OBD-II Code · Powertrain
P0193
Fuel Rail Pressure Sensor "A" Circuit High
Severity
high
Left alone, this one tends to take other parts with it.
Can you drive it
Not for long
Driving on this one risks further damage. Get it to a shop rather than carrying on with it.
Indicative cost (USD)
$150–$700
Varies by vehicle, diagnosis, parts, and local labor. This is not a repair quote.
HP rail sensor reading too high.
How a shop works this
Work from evidence to part, not the other way round. A code names a circuit or a symptom; it does not name the part that failed.
Note every code that is set, not just this one.
Codes that appear together usually narrow the cause faster than any one of them read alone.
Read the freeze frame — the conditions the fault was recorded under.
Cold or warm, idle or load, road speed and engine speed. A fault that only appears cold is a different fault from one that only appears under load, even with the same code on the scanner.
Confirm the fault is current rather than history.
Clear the code and see whether it returns under those same conditions. A code that does not come back may have been logged during a repair, a flat battery, or a bad connection that has since been disturbed.
Then work the likely-causes list in the order shown.
That order is what a shop checks first for this code — wiring and connections before the component they run to, because a connector costs nothing to inspect and is a common answer.
If the code comes back after a repair, the underlying fault is still there. That is the point to bring in a scanner with live data and freeze-frame, or a shop that has one.
Common symptoms
- Hard start
- Stall
Likely causes
- Failed sensorMost common
- Wiring open
- Sensor disconnected
Read the full diagnostic procedureP0193 is the opposite of P0192, meaning the fuel rail pressure sensor voltage exceeded the high threshold, typically above 4.8 volts on a 0 to 5 volt…
P0193 is the opposite of P0192, meaning the fuel rail pressure sensor voltage exceeded the high threshold, typically above 4.8 volts on a 0 to 5 volt scale.
Cheapest first
- scan FRP sensor voltage with key-on-engine-off; a reading pinned at 4.9 to 5.0 volts means either the signal wire is shorted to the 5-volt reference, the ground return is open, or the sensor has failed internally.
- Disconnect the sensor and check whether the signal voltage drops to 0 volts at the ECM (good harness, bad sensor) or stays pinned high (short between signal and reference in the harness).
- Verify the sensor ground at the connector reads under 0.1 volts back to battery negative; an open ground will float the signal high.
- Inspect the connector for water intrusion, which is the most common cause on engines where the sensor sits in a low spot on the rail.
- Caveat: a mechanically failed regulator that actually traps the rail at maximum pressure will also set P0193 with a perfectly good sensor, so verify with a mechanical gauge before replacing the sensor.
Vehicle-specific patternsFord 6.7L Power Stroke (2011-2019) sees P0193 from FRP sensor moisture intrusion at the connector.
- 2011-2019Ford 6.7L Power Stroke sees P0193 from FRP sensor moisture intrusion at the connector.
- 2010-2018GM 3.6L LFX and 2.0T LTG sets P0193 from FRP sensor failure on the high-pressure rail.
- 2011-2019Hyundai/Kia 2.0T and 2.4 Theta II GDI sets P0193 from rail pressure sensor connector corrosion. Nissan VR30DDTT 3.0T (2016-2022 Q50, Q60) sees P0193 from failed FRP sensor as a known weak point.
Estimated repair$90 to $480.
Look up another code
P0193 — frequently asked
What does a P0193 code mean?
HP rail sensor reading too high.
What causes a P0193 code?
Common causes: Failed sensor; Wiring open; Sensor disconnected.
What are the symptoms of a P0193 code?
Typical symptoms: Hard start; Stall.
Is it safe to drive with a P0193 code?
Not for long. Driving on this one risks further damage. Get it to a shop rather than carrying on with it. Estimated repair: $150-$700.
How do I diagnose a P0193 code?
Work from evidence to part, not the other way round. A code names a circuit or a symptom; it does not name the part that failed. 1. Note every code that is set, not just this one. 2. Read the freeze frame — the conditions the fault was recorded under. 3. Confirm the fault is current rather than history. 4. Then work the likely-causes list in the order shown.
More free tools