P0087: measuring low rail pressure from tank to injector
P0087 reports that commanded fuel-rail pressure could not be achieved. Low-side supply, control valves, pump capacity, injector return and sensor plausibility are separated under load.
Advanced diagnostics and measurement9 sourcesUpdated 2026-07-31
DTC QUICK ANSWER
P0087 · Fuel Rail/System Pressure Too Low
System reported by the code: Use the verified English application data on this page and confirm vehicle, model year, market and powertrain identity before applying technical values.
Save freeze-frame, pending/confirmed state and companion codes before clearing anything.
Verify battery/charging, controller power and grounds under load.
Compare requested and actual fuel/rail pressure at the same load; separate low-side supply with an independent measurement.
Test sensor feedback, regulation, pump delivery and injector internal leakage as separate branches.
Exact thresholds, pins or service values require the OEM procedure for the exact vehicle application.
Use the code as a measurement starting point, not a failed-part label. Preserve event data and compare symptoms, likely causes, live data and physical measurements under the same operating condition.
MEASUREMENT-BASED DIAGNOSTICS
Technical flow from measurement to verification
Capture freeze-frame/event data, first/last occurrence conditions and system voltage.
Verify power, ground, fuses, connectors and shared reference circuits before replacing parts.
Compare commanded values with actual sensor or actuator feedback under the same operating conditions.
Separate electrical causes from mechanical, hydraulic, pneumatic or flow-related causes with independent measurements.
Recreate the monitor or operating condition after repair and confirm that the fault does not return.
Generic/reference DTC context; manufacturer-specific meaning must be verified separately.
COMMON RAIL · LOW SUPPLY · LOAD TEST
P0087: measuring low rail pressure from tank to injector
IDENTITY
Map the fuel-system architecture
Lift pump, suction system and valve layout vary by engine.
Identify engine code, pump/injector supplier, filter type and rail-pressure control strategy.
Use freeze frame to locate cranking, full-load, hot-fuel or low-tank occurrence.
Record companion P0093, regulator, low-voltage and injector-circuit codes.
Note recent wrong-fuel, filter, tank or pump work.
MEASUREMENT
Build a pressure chain from tank to rail
Prove the input and output of every stage.
Measure low-side pressure/vacuum and flow at the manufacturer test point.
Compare filter restriction, pump current and supply voltage under the same load.
Log rail desired/actual and quantity/pressure-valve commands during cranking and load.
Verify injector return flow and rail-sensor circuit independently.
DIFFERENTIAL
Separate lost capacity from false sensing
A low reading does not always mean low mechanical pressure.
With poor low-side supply, prioritise tank strainer, pump, filter, crushed line and air ingress.
With normal supply, maximum command and low rail pressure, inspect high-pressure pump, valves and internal leakage.
If pressure collapse coincides with pump-current change, investigate electrical supply or pump seizure.
If sensor signal conflicts with physical engine response, inspect 5 V reference, ground and interference.
VALIDATION
Demonstrate reserve in the worst condition
Clearing the code at idle is incomplete verification.
After filter or line work, bleed the system and inspect for external leakage.
Safely reproduce low fuel, hot fuel or controlled-load conditions from the event.
Desired/actual pressure error and regulator reserve must remain stable without saturation.
Check pending status, corrections and hot restart on the final scan.
FIELD WORKFLOW
Evidence-preserving diagnostic sequence
Confirm engine and fuel-system identity.
Capture freeze frame and companion codes.
Measure tank, pump, filter and line supply.
Log desired/actual rail pressure and commands under load.
Verify return flow and sensor plausibility.
Reproduce the event and perform a pending-code scan.
DIFFERENTIAL DECISION MATRIX
Connect the symptom to evidence, not a guessed part
Evidence
Observation / condition
Correct next action
Pattern
Low-side pressure is also low
Resolve tank, pump, filter, line and aeration.
Pattern
Low side normal, rail command saturated
Test high-pressure generation and internal leakage.
This file is not a shortcut parts list. Exact numerical values are not published until vehicle identity, production period, control-unit software, test conditions and the manufacturer procedure are aligned.
6-step technical decision tree
Verify identity
Preserve first-event data
Compare command and feedback
Confirm with physical measurement
Isolate root cause
Retest under the same condition after repair
P0087 manufacturer/application research dossiers
The records below are research dossiers sharing the same base DTC code in source data. This list is not a confirmed-fitment claim; verify brand, model year, ECU/TCU and software identity for the actual vehicle.
OEM EVIDENCE DOSSIER
Verified technical facts and application boundary
P0087 is defined as Fuel Rail/System Pressure Too Low; the code alone does not identify a failed component.[S1]
Ford SSM 48397 states that certain 2013–2015 GTDI applications may show loss of power or stalling when placed in gear with P0087 among the possible fuel-pressure DTCs.[S2]
The same Ford bulletin places the Fuel Low Pressure sensor in the supply line to the high-pressure pump and says the FLP PID can be compared with a manual pressure gauge.[S2]
Volkswagen TSB 2041063/11 for 2009–2012 Golf/Jetta/Jetta SportWagen 2.0 TDI CBEA/CJAA requires low-side supply-pressure and injector/N276 internal-leakage checks before the final HPFP inspection step.[S3]
Verified application matches
The matches below are published only within the stated market, model-year and evidence scope. Fitment is not extrapolated to uncited variants.
Market: North America
Model year: 2013–2015
Model: Ford Fusion / MKZ / Escape / MKC
Engine: 1.6L, 1.5L or 2.0L GTDI
Evidence scope: Ford SSM 48397; P0087 may occur with related low-pressure fuel DTCs
Split the fuel system into tank/transfer pump and low-pressure supply → high-pressure pump → rail/pressure regulation → injectors.
Low-side sensor/PID, rail-pressure sensor and pump/regulator control are different fault paths; a biased PID alone does not prove mechanical pump failure.
The ECM/PCM compares requested fuel pressure with feedback under operating conditions, so target-vs-actual deviation should be captured with load, RPM and supply conditions.
DTC / SPN-FMI / symptom discrimination map
With P0087 plus loss of power/stall, preserve freeze-frame data and separate companion low-side codes such as P008A/P008B/P018C/P018D; where the application supports it, validate low-side fuel pressure independently.
On common-rail diesel, check supply pressure, restriction/filter condition, injector internal leakage and pressure regulation before escalating to the high-pressure pump.
Metal-particle inspection is a final application-specific service step only where the manufacturer procedure calls for it; P0087 by itself is not a direct HPFP replacement instruction.
Measurement and diagnostic strategy
Before clearing codes, capture RPM, load, requested/actual fuel pressure, low-side pressure PID where available, system voltage and companion DTCs.
On applications covered by Ford SSM 48397, compare the FLP PID with a manual pressure gauge according to the manufacturer pinpoint procedure; a PID/physical-pressure mismatch redirects diagnosis toward sensor/wiring.
On the Volkswagen TDI bulletin scope, complete low-side supply-pressure and injector/N276 internal-leakage checks before the N290/HPFP inspection step.
After repair, recreate the original load/temperature condition and verify requested-vs-actual pressure deviation, pending/current DTC state and the original power/stall symptom together.
Exact pinouts, torque values, pressure thresholds or service limits are published only when explicitly verified by the applicable OEM service source.
Do not treat the code label as a parts diagnosis. Narrow root cause through freeze-frame, simultaneous module codes, power/ground, live data and active testing.
P0087 · Fuel Rail/System Pressure Too Low · Fuel pressure
1. Event context
Capture freeze-frame, first/last occurrence, load, rpm, temperature, vehicle speed and system voltage.
2. Eliminate shared causes
Rule out battery/charging, power, ground, fuses, network communication and shared-reference faults before replacing parts.
3. Compare command and result
Compare commanded values with real sensor/actuator response under the same operating condition.
4. Prove the repair
Clearing codes is not enough; recreate the monitor condition and verify that code/symptom does not return.
Fuel-pressure isolation
Compare low-pressure supply, rail target/actual pressure, regulator command, injector return behaviour and electrical supply in the same capture. Low pressure does not automatically mean a failed pump.
Evidence-led DTC checklist
Capture freeze-frame/event data and a full-module scan before clearing the code.
Separate DTC status bits: active, pending and history/permanent do not carry the same diagnostic weight.
Eliminate supply, grounds, 5 V reference and network health as shared causes.
Graph ECU command against actual sensor/actuator feedback.
Load-test wiring and validate the system physically before replacing parts.
After repair, check readiness/DTC return under the same operating condition.
Verify the code against vehicle identity and system context
The same DTC can lead to different root causes across manufacturers, controllers and operating conditions. Cross-check model, engine/transmission and the measurement chain.
This powertrain context reference is intentionally kept manufacturer-aware. Confirm the exact definition for the vehicle, model year and controller before replacing parts.
1 · Capture the event
Save DTC status, freeze-frame/event data, operating state and companion codes before clearing memory.
2 · Verify identity and power
Confirm the reporting module, supply, grounds, fuses and connector condition before judging a sensor or actuator.
3 · Compare command and feedback
Use live data to compare commanded state with actual feedback under the same operating condition.
4 · Measure the circuit or system
Use the OEM procedure for pin locations and exact thresholds; separate electrical/network faults from mechanical, hydraulic, pneumatic or flow faults.
5 · Reproduce and verify
After repair, reproduce the original load and operating condition and confirm that the code and related symptoms do not return.
This code does not automatically condemn a component; it describes fault behaviour observed by the controller in a monitored system. Preserve event data and eliminate shared causes before narrowing the root cause with system-specific measurement.
Code classPowertrain
SystemYakıt basıncı
Reference severitymedium
Family-based first diagnostic chain
Capture freeze-frame and system voltage.
Compare target and actual fuel pressure under the same load.
Separate low-pressure supply, regulation, sensor and injector-return causes.
Compare electrical command with mechanical/hydraulic result.