What a Derate Is and Why It Needs Documentation
A derate is an ECM-commanded reduction in engine power output or maximum speed, applied as a response to a detected fault condition. Derates are part of both engine protection logic (protecting the engine from operation under harmful conditions) and EPA-mandated aftertreatment inducement (reducing engine performance to prompt repair of emissions-relevant faults). Documenting derate events is important because the documentation helps the service technician understand what triggered the derate, what operating conditions were present, and whether an OEM tool reset is needed after repair.
Not all derates feel the same from the driver's seat. A mild torque derate may be barely perceptible on flat terrain with a light load but very apparent when attempting a loaded grade. A governed speed derate (maximum speed limited to 55 mph or 5 mph, depending on severity) is more immediately apparent. The driver's description of how the derate felt — when it started, how severe the power reduction was, whether it released — is useful data that supplements the fault codes.
Key Information to Record During a Derate Event
When a derate occurs, document: the time and location, the active warning lamp colors (amber or red), any dashboard messages visible, the approximate severity of the power reduction (slightly less power, significantly reduced, unable to maintain speed on grade, maximum speed limited), whether the derate came on suddenly or gradually, and the operating conditions at onset (cold start, normal operation, after a heavy load climb, after extended idle).
If possible, record the active fault codes at the time of the derate — a photo of the instrument cluster showing the active lamp and any displayed code message is useful. On trucks with in-cab diagnostic displays, accessing the fault code screen during the derate captures the active code responsible. This eliminates ambiguity about which fault triggered the derate, as the derate may persist as an inactive protective state after the triggering condition temporarily resolves.
Derate Severity Levels and Their Operational Implications
Derates exist on a spectrum. A mild torque reduction of 10–20% may be barely perceptible but is still a protection or inducement response that requires attention. A more significant derate that prevents the truck from maintaining grade speed requires route planning to a service location. A governed speed derate to 55 mph or 65 mph allows the truck to operate but requires that a service appointment be scheduled promptly. An inducement derate to idle-only or 5 mph requires an immediate stop for diagnosis and repair.
After a derate is active, restarting the engine often does not release the derate — the ECM maintains the protection or inducement state until the underlying condition is addressed and, for inducement derates, until an OEM tool reset is performed. A derate that releases temporarily on restart but returns within a short time is still an active condition requiring repair. Documenting the restart behavior ('released after restart but returned in 10 minutes') is useful information for the technician.
After the Derate: What the Technician Needs to Know
When bringing a derated truck to a shop, the technician needs: the fault code(s) that were active or displayed during the derate, a description of the derate severity and duration, whether the derate is currently active or released, the vehicle's operating history in the period before the derate (recent maintenance, route type, DEF and fuel quality), and whether any prior service has been performed for a related fault.
For inducement-related derates on aftertreatment systems, the technician will check the inducement counter in the OEM diagnostic software — this shows how many miles or what distance threshold has been accumulated. This counter determines the reset procedure required after repair. A derate that resulted from an escalated aftertreatment fault may require an OEM-level reset that a standard scan tool cannot perform. Communicating that the vehicle is in an inducement derate (not just a fault code) helps the shop prepare the correct tooling.
Related Pages
Sources
- SAE J1939 Standards Collection SAE International · official · accessed 2026-05-05 · confidence medium
Source: SAE International, SAE J1939 Standards Collection. This page paraphrases factual fields only and is not a substitute for the original document.
Open source - 49 CFR Part 393 - Parts and Accessories Necessary for Safe Operation Electronic Code of Federal Regulations · government · accessed 2026-05-05 · confidence high
Source: Electronic Code of Federal Regulations, 49 CFR Part 393 - Parts and Accessories Necessary for Safe Operation. This page paraphrases factual fields only and is not a substitute for the original document.
Open source
FAQ
Is a 25 mph derate as serious as a 5 mph derate?
Both indicate the ECM has intervened to limit operation, but a 5 mph derate is the most severe stage and essentially renders the truck incapable of highway use. A 25 mph derate is more limiting than a torque reduction but still allows the truck to move to a service location. The critical point is the same: both require diagnosis and repair — the 5 mph derate just removes the option of driving to a shop across town.
The truck derates on the highway but the code shows inactive when I stop. What should I record?
This is a key situation. Write down the exact time, location, load conditions, grade, ambient temperature, and any codes that were active while driving — even if inactive by the time you stop. Many diagnostic tools can show when a code was last active and under what conditions. The more specific your record of when and where the derate occurred, the more useful it is for the technician trying to identify the triggering condition.
Does a derate always come with an active fault code?
On most modern engines, yes — a derate is triggered by a monitored condition, and that condition should be logged as a fault code. However, a code that was active during the derate can shift to inactive quickly if the condition resolves. If the ECM's internal logic clears the code before the driver connects a tool, the fault history and freeze-frame data are still in the ECM — a technician needs to pull that history data, not just read currently active codes.