PACCAR MX-11 SPN 190 FMI 0 — Engine Speed Very High (Overspeed)

SPN 190 FMI 0 on the PACCAR MX-11 means the engine speed exceeded the overspeed protection limit. Steep downhill descents without adequate retarder use and aggressive downshift events are the most common operational causes. Connect PACCAR ESA to review the freeze-frame RPM at fault set and check for speed sensor or governor-related codes that might indicate a non-operational cause.

Code Details

Structured details for SPN 190 FMI 0
Display codeSPN 190 FMI 0
SPN190
FMI0
OEM codeNone listed
ManufacturerPACCAR
SystemEngine — Speed / Governor
ComponentEngine speed sensor / ECM governor / fuel system
Source addressUnknown or not applicable
Severityhigh
Review statussource backed
Source confidencemedium
Last reviewed2026-06-12

Plain-English Meaning

The PACCAR MX-11 ACM monitors engine speed via the crankshaft speed sensor and enforces a maximum speed limit defined in the engine calibration. When measured engine speed exceeds the overspeed threshold — whether from a steep downhill descent, an aggressive shift event, or a sensor fault — the ACM sets SPN 190 FMI 0 and activates the overspeed protection function, which reduces fuel delivery to bring engine speed back within the safe operating range. In normal operational incidents, the MX-11 returns to full performance after the overspeed protection response completes and engine speed normalizes. The fault code is stored in the ACM for review in PACCAR ESA. A speed sensor producing false high-speed signals can set this fault without an actual overspeed condition, which is why evaluating speed sensor signal integrity is a recommended diagnostic step when the fault occurs under unexpected conditions.

SPN 190 is Engine Speed; FMI 0 indicates valid data above the highest severity threshold in the engine calibration. On the PACCAR MX-11, the ACM monitors crankshaft speed and enforces the overspeed limit through the fuel control system. PACCAR ESA provides access to the freeze-frame data stored at fault detection, which includes engine RPM, vehicle speed, fuel demand, and other parameters. ESA engine speed sensor live data and signal quality checks allow a technician to evaluate whether the speed sensor is producing an accurate signal or generating anomalous high-speed readings. The ESA fault history shows all stored instances of SPN 190 FMI 0 with their individual freeze-frame snapshots.

Common Symptoms

  • Check engine lamp illuminated following a descent or shift event
  • Brief engine stumble or fuel interruption during the overspeed protection activation
  • Overspeed event in ESA fault history with freeze-frame RPM above rated speed
  • Normal driveability after the event if it was a single brief occurrence

Possible Causes

Possible causes may include the items below. The list is not a parts diagnosis.

  • Steep downhill descent without engine brake or retarder engagement allowing vehicle momentum to overspeed the engine
  • Aggressive downshift to a lower gear at elevated vehicle speed
  • Engine speed sensor or wiring fault producing erratic high-speed signal readings
  • Governor fault allowing fuel delivery to continue above the rated RPM
  • Sudden driveline load release causing a brief engine over-rev

First Checks

  • Connect PACCAR ESA and read the freeze-frame data for SPN 190 FMI 0 to determine the RPM at fault set and the vehicle speed and gear at the time
  • Evaluate the operational circumstances — steep descent or aggressive shift events are the most plausible causes in most cases
  • Monitor engine speed sensor signal in ESA live data to confirm signal quality and check for false high-speed readings
  • Inspect the engine speed sensor mounting and wiring for damage or looseness
  • If the fault recurs under normal operating conditions, check fuel system governor response and ECM calibration parameters in ESA

Can I Keep Driving?

The MX-11 typically returns to normal operation after a brief overspeed event. If SPN 190 FMI 0 recurs, investigate the cause to prevent repeated stress on rotating engine components.

Related Lookup Pages

Sources

  • PACCAR / Kenworth / Peterbilt Service Support — MX Engine Resources PACCAR Inc. · oem · accessed 2026-06-11 · confidence medium

    Source: PACCAR Inc., PACCAR / Kenworth / Peterbilt Service Support — MX Engine Resources. This page paraphrases factual fields only and is not a substitute for the original document.

    Open source
  • PACCAR Engine Technical Services PACCAR Inc. · oem · accessed 2026-06-10 · confidence medium

    Source: PACCAR Inc., PACCAR Engine Technical Services. This page paraphrases factual fields only and is not a substitute for the original document.

    Open source

FAQ

What is the rated maximum RPM for the PACCAR MX-11 and at what speed does SPN 190 FMI 0 trigger?

The PACCAR MX-11 rated speed and the specific overspeed threshold for SPN 190 FMI 0 are defined in the engine calibration and may vary by application rating and customer parameter settings. The freeze-frame data captured by PACCAR ESA at fault set will show the actual RPM recorded at the time of the event. For the exact overspeed calibration threshold for a specific MX-11 application, review the ECM calibration parameters in ESA or consult the applicable PACCAR service documentation.

Can SPN 190 FMI 0 on the MX-11 set during a downshift in a Kenworth or Peterbilt with a PACCAR automated transmission?

In Kenworth T680 or Peterbilt 579 trucks equipped with a PACCAR AMT, a transmission control fault causing an unexpected downshift at elevated road speed can drive engine speed above the overspeed threshold through the driveline, setting SPN 190 FMI 0 on the MX-11. If this fault appears alongside transmission or TCM-related codes, the transmission control module behavior at the time of the event should be reviewed. ESA freeze-frame data can confirm whether the gear was changing at the time of the fault set.

Does SPN 190 FMI 0 on the MX-11 require a dealer visit to clear?

SPN 190 FMI 0 is a standard fault code that can be cleared using PACCAR ESA once the root cause has been identified and addressed. If the event was an isolated operational overspeed incident without an underlying component fault, the code can be cleared through ESA and the engine returned to service. If the fault recurs, further diagnosis is required before clearing the code again.