Detailed guide for SPN 3720 FMI 16
Back to top ↑Soot load is climbing. If you keep interrupting regens, you eventually force a shop regen or get derated.\n\nFix the reason soot is high, not just the symptom.
Jump to
Share ↓SPN 3720 FMI 16Severity: Warning
SPN 3720 FMI 16: DPF soot load high – regen required soon
Quick Answer
DPF soot load high – regen required soon
Code
SPN 3720 FMI 16
Severity
Warning
Applies to
Check OEM application
Can I drive?
Driving suitability is not established by this code alone.
Common Symptoms
- Regen requested more often
- Fuel economy drops
- May progress to derate if ignored
Likely Causes
- Interrupted regens
- Excessive idle time
- Engine running rich or producing excess soot
Common Fixes
- Complete regen without interruption
- Fix soot sources (boost leaks, EGR issues)
- Verify sensors and exhaust leaks
Full technical sections↓
What does SPN 3720 FMI 16 mean?
Back to top ↑DPF soot load high – regen required soon
BigRigFaults Community
Community discussions related to SPN 3720 FMI 16
Compare symptoms, repairs and real-world experience from drivers, technicians and owner-operators.
Fault Codes / SPN / FMI
SPN 1590 FMI 19 - Meaning, Causes & Diagnostic Discussion
0 replies7 views
Fault Codes / SPN / FMI
SPN 4077 FMI 14 - Meaning, Causes & Diagnostic Discussion
0 replies11 views
Fault Codes / SPN / FMI
SPN 84 FMI 21 - Meaning, Causes & Diagnostic Discussion
0 replies8 views
Fault Codes / SPN / FMI
SPN 1071 FMI 5 - Meaning, Causes & Diagnostic Discussion
0 replies7 views
Still stuck with SPN 3720 FMI 16?
Ask the community and include your truck year, make, engine, active codes, symptoms and recent repairs so people can give useful answers instead of performing mechanical astrology.
Ask the Community →Related fault codes
No related faults found yet.
Mechanic community notes for SPN 3720 FMI 16
Back to top ↑Real-world tips from technicians. Submissions are moderated to keep spam and “my cousin fixed it with duct tape” content out.
Share your fix / advice
Keep it useful: symptoms, what you checked, what fixed it, and whether the code stayed inactive after a drive cycle.