Prevention FAQ — FMCSR 393.83(e): Exhaust Discharge Location
Fleet manager guide to preventing 393.83(e) citations: inspector focus areas, pre-trip steps, root causes, CSA impact, and audit cadence.
- Code:
- 393.83(e)
- Code System:
- FMCSR
- BASIC Category:
- Vehicle Maintenance
- OOS Eligible:
- No
- Severity Weight:
- 1
- Violation Group:
- Exhaust Discharge
Ranks #403 of 3,146 FMCSR codes by citation frequency • OOS rate of 1.4% is below the FMCSR-wide average of 33.3%.
Violation Description
Exhaust - System discharging from a truck or truck-tractor at a location other than at the rear of the cab.
Prevention FAQ for Fleet Managers
Pre-trip discipline, inspector focus, and root-cause fixes
› What specifically do inspectors look for when citing 393.83(e) during a roadside inspection?
Inspectors are checking whether the exhaust system on a truck or truck-tractor is venting gases at any point other than behind the cab. Practically, that means walking the exhaust routing from the manifold to the exit point and flagging any discharge occurring at or beneath the cab itself — including cracked flex sections, loose stack connections, or re-routed piping that exits mid-chassis.
With 3,923 all-time citations in our inspection records, this is a real enforcement target despite showing zero citations in the last 12 months. Inspectors who focus on vehicle maintenance violations — a broad category that includes codes with hundreds of thousands of citations — are trained to inspect exhaust routing as part of a thorough Level I or Level II inspection. The exit point of the stack is a fast visual check, so non-conforming routing stands out immediately.
› What pre-trip checklist items should drivers perform to catch a potential 393.83(e) issue before hitting the road?
Add these specific items to the pre-trip exhaust section of your DVIRs:
- Stack exit point: Confirm the exhaust exits at or behind the rear of the cab, not underneath or alongside it.
- Flex pipe and bellows: Visually inspect for cracks, separations, or blowout marks (soot streaks on nearby surfaces are a telltale sign).
- Clamps and hangers: Check that all exhaust pipe hangers are intact and that no section has dropped or shifted position.
- Cab underside and frame rails: Look for carbon or heat discoloration on frame rails near the cab — a sign of misdirected exhaust.
- Recent repair verification: If the truck had exhaust work done, the driver should confirm with the shop that the exit point was not altered.
Freightliner units account for 589 citations in our database — the most of any make — so drivers operating Freightliners should pay particular attention to the DPF-adjacent piping and stack connections on those platforms.
› What documentation should carriers retain to support compliance with 393.83(e)?
While 393.83(e) is not OOS-eligible under normal circumstances, documentation still matters for DataQs challenges and CSA BASIC management.
Retain the following:
- DVIRs covering the inspection period, showing the driver performed and signed off on exhaust checks.
- Repair orders for any exhaust work, including the technician's notation that the exit point was verified to be at the rear of the cab upon completion.
- Pre/post repair photos of the exhaust stack exit point — a timestamped photo takes seconds and is invaluable if you dispute a citation.
- Periodic inspection records — our database shows that peer code 396.17(c) (no proof of periodic inspection) has 198,331 citations in the same Vehicle Maintenance category; inspectors who find one maintenance gap often look for others, so having these records accessible is critical.
Retain all records for a minimum of 12 months, longer if a citation is under review.
› What are the most common root causes behind 393.83(e) citations, and what do the co-occurring violations reveal?
Our inspection records show 393.83(e) does not have co-occurring violation data published in this dataset, so the root-cause analysis must draw from what we know about the violation's nature and the peer category context.
Based on the carrier profile — the top 10 cited carriers are all Mexican cross-border operators, including OPERADORA DE TRANSPORTE INTERNACIONAL SA DE CV with 40 citations and AUTOTRANSPORTES ROMEDU SA DE CV with 34 — a strong systemic pattern emerges: vehicles operating under high-mileage, high-heat cross-border duty cycles are prone to exhaust hanger fatigue and flex pipe failure, causing the stack to shift or re-route over time.
Three root causes to address in your program:
- Deferred maintenance cycles — long runs between PM services allow hanger wear to go undetected.
- Post-repair routing errors — exhaust work done outside the carrier's own shop sometimes results in non-compliant re-routing.
- Vibration fatigue — heavy-haul and long-haul profiles (common in the top carrier set) accelerate clamp and hanger failure.
› How should repairs be verified before a vehicle with a 393.83(e) citation returns to service?
Because this code is not OOS-eligible — the all-time OOS rate is only 1.4% against an all-FMCSR average of 31.4% — vehicles are rarely pulled off the road at the point of inspection. That makes shop-level verification discipline the critical control.
Return-to-service checklist:
- Technician must physically trace the full exhaust routing and document the exit point is at the rear of the cab.
- A second-party sign-off (shop foreman or fleet safety coordinator) should review and sign the repair order.
- A timestamped photograph of the corrected stack exit point must be attached to the repair order before the file is closed.
- The driver must note the corrected condition on the post-trip or pre-trip DVIR for the next dispatch.
- If the repair involved rerouting any piping — not just clamp tightening — treat it as a post-repair inspection event and schedule a follow-up DVIR check at the next PM interval.
› What post-citation review process should the fleet run after receiving a 393.83(e) violation?
Run a structured review within 72 hours of the citation entering the system:
- Pull the inspection report and confirm the specific location where the exhaust was found to be discharging — stack mid-cab, underbody, or other.
- Cross-reference the DVIR history for that unit. Was the exhaust condition noted on any prior report? If yes, was a repair order generated?
- Audit similar units in the fleet — particularly other Freightliners, Kenworths (367 citations in our database), and International trucks (319 citations), which together represent the three most-cited makes for this code.
- Interview the driver about what they observed during pre-trip and whether the condition was present before the stop.
- Document findings in a corrective action report, noting whether the root cause was driver oversight, missed PM, or post-repair error.
- If the citation appears incorrect based on your evidence, initiate a DataQs challenge within 60 days.
› How does a 393.83(e) citation affect the carrier's CSA Vehicle Maintenance BASIC score?
Any citation that reaches the FMCSA Safety Measurement System adds to your Vehicle Maintenance BASIC, and 393.83(e) is no exception. With 3,923 all-time citations, it ranks #392 out of 3,036 FMCSR codes by volume — meaning it is a mid-tier enforcement code, not a rare anomaly.
The good news: the 1.4% OOS rate signals that inspectors treat this as a correctable maintenance defect rather than an imminent hazard. Compare that to the all-FMCSR average OOS rate of 31.4% and the peer code 396.3(a)(1) which carries a 45.3% OOS rate — this code is relatively low-severity in terms of immediate operational disruption.
However, BASIC scoring is cumulative and time-weighted, so even lower-severity violations stack up. Fleets with multiple cross-border units — like the top cited carriers in our records — are especially vulnerable to score accumulation if this issue is systemic across a fleet rather than isolated to one unit.
› What driver training topics most directly close the gap on 393.83(e) violations?
Our inspection records show Freightliner leads all makes with 589 citations, followed by Kenworth at 367 and International at 319. Training should be platform-aware:
Topics to include:
- Exhaust system routing basics — show drivers (using make-specific diagrams) where the stack exit should be on their assigned units. Freightliner, Kenworth, and International all have distinct exhaust configurations that affect what "correct" looks like.
- Visual cue recognition — soot streaks on frame rails, cab-side discoloration, and unusual heat shimmer near the cab are all detectable on a walkaround.
- DVIR documentation standards — drivers must know how to write a specific, actionable defect note (not just "exhaust issue") so the shop can act without a back-and-forth.
- Post-repair walkthrough — train drivers to physically check the stack exit after any exhaust repair, not just accept the shop's verbal confirmation.
For cross-border fleets, deliver training in both English and Spanish given the carrier demographics visible in our citation data.
› Under what circumstances should a fleet file a DataQs challenge for a 393.83(e) citation?
File a DataQs challenge when you have documented evidence that one or more of the following applies:
- The exhaust exit was at the rear of the cab and you have timestamped photos from that day's pre-trip inspection or a recent repair order confirming compliant routing.
- The unit cited does not match your records — VIN discrepancies in inspection reports do occur.
- The DVIR shows the condition was noted and a repair was completed before the inspection took place, meaning the violation may have been corrected prior to the stop.
- The violation is a duplicate entry in the SMS system.
Given that 3,923 all-time citations exist for this code with zero in the last 12 months, this is not a code with active enforcement momentum — which means citations that do appear are worth scrutinizing carefully. The 54 instances where vehicles were placed out of service despite this code being technically non-OOS-eligible are also worth challenging if the OOS determination appears unsupported by the inspection narrative.
› How frequently should the fleet self-audit for exhaust routing compliance, and what cadence does the enforcement trend support?
Our inspection database shows 0 citations for this code in both the last 90 days and the last 12 months, down from 3,923 all-time. This suggests enforcement intensity has dropped sharply — but it does not mean the underlying mechanical risk has disappeared. Exhaust hanger fatigue and routing drift are physical processes that continue regardless of enforcement cycles.
Recommended audit cadence:
- Every PM service (typically every 25,000–30,000 miles): Include exhaust routing and exit point as a mandatory line item on the PM checklist.
- Post-repair inspection: Any time exhaust work is performed, a supervisor-level sign-off on exit point compliance must occur before dispatch.
- Quarterly fleet-wide spot check: Pull 10–15% of units for a dedicated exhaust routing walk — prioritize Freightliner, Kenworth, and International units given their disproportionate share of citations in our records.
The flat recent-trend data means you are unlikely to encounter this in an inspection today, but a systemic audit gap will surface the next time enforcement attention returns to vehicle maintenance fundamentals.
Related Records
Data sources & freshness
TruckCodex aggregates official public-sector datasets. See the Source registry for dataset-level coverage and the Freshness log for last-import timestamps.
Census, SAFER, SMS, Licensing & Insurance (L&I), roadside inspections, crashes, and authority history.
Vehicle recall campaigns, defect investigations, and consumer safety complaints (SCRS).
Cross-border carrier registry and Canadian recall campaigns where applicable.
TruckCodex is an independent aggregator; it is not affiliated with FMCSA, NHTSA, EIA, or Transport Canada. Always verify compliance-critical information directly with the originating agency.