Prevention FAQ — FMCSR 393.40(b) Inadequate Brakes
Fleet safety guidance on brake adequacy citations, pre-trip protocols, root-cause analysis, and self-audit cadence based on 13M+ inspection records.
- Code:
- 393.40(b)
- Code System:
- FMCSR
- BASIC Category:
- Vehicle Maintenance
- OOS Eligible:
- Yes
- Severity Weight:
- 4
- Violation Group:
- Brakes All Others
Ranks #2,259 of 3,146 FMCSR codes by citation frequency • OOS rate of 77.8% is above the FMCSR-wide average of 33.3%.
Violation Description
Brakes - no pedal reserve
Prevention FAQ for Fleet Managers
Pre-trip discipline, inspector focus, and root-cause fixes
› What specific brake defects do roadside inspectors focus on for 393.40(b)?
Inspectors evaluate whether brakes meet FMCSR performance standards—stopping distance, brake pressure holding, and pad/shoe wear. Our inspection records show this violation ranks #2230 of 3,036 FMCSR codes by citation volume, but when cited, it has a 77.8% out-of-service rate, significantly higher than the 31.4% all-FMCSR average. This severity suggests inspectors are checking for active brake failure or extreme wear that poses immediate safety risk, not minor adjustments. Focus your pre-trip protocol on full system pressure tests, pad thickness measurement, and brake fluid condition—not cosmetic cleanliness.
› What should the pre-trip brake inspection checklist include?
Build a driver checklist that covers: (1) brake pedal feel and stopping distance during a low-speed test; (2) brake fluid level and color (clear to slightly amber is normal; dark brown suggests contamination); (3) visual pad/shoe thickness on all wheels using a minimum thickness gauge; (4) brake pressure gauge reading if the vehicle is equipped with one; (5) audible air leak detection (listen for hissing at couplings and valves on air brake systems); (6) anti-lock brake system (ABS) warning lamp status on the dashboard. Require drivers to document findings on a signed form daily. Any deficiency—soft pedal, low fluid, pad below minimum—triggers immediate repair before departure.
› What brake inspection and maintenance records must we retain?
Maintain a vehicle-level maintenance log that includes: (1) all brake service dates, technician names, and work performed; (2) brake pressure test results and acceptance criteria (tie to FMCSR stopping distance tables); (3) pad/shoe replacement dates and thickness measurements before removal; (4) brake fluid flushes and fluid type used; (5) ABS system diagnostics and repairs; (6) annual DOT inspection reports signed by the inspector. Keep records for at least 12 months and cross-reference them with vehicle pre-trip forms. When an inspector pulls a vehicle, these records are your defense against findings that defects went undetected.
› What root causes are hidden in the co-occurring violation data?
Our database shows 393.40(b) sits in the Vehicle Maintenance category alongside codes like 393.9(a) (inoperable lamps, 660,737 citations) and 396.3(a)(1) (general inspection/repair failures, 236,919 citations). The pattern suggests that brake failures often co-occur with deferred maintenance across multiple systems. Fleets citing inadequate brakes frequently also have lighting or structural repair backlogs. This points to root causes: (1) repair shops overwhelmed and skipping thorough brake testing; (2) lack of a preventive maintenance schedule; (3) drivers not reporting brake symptoms. Audit your maintenance queue for age of open repair tickets and cross-reference with the vehicles cited for 393.40(b).
› How should we verify brake repairs before returning a vehicle to service?
Require a certified technician (not just the repair shop) to perform a post-repair test that includes: (1) a pressure retention test (hold brake pressure for 2 minutes with no drop exceeding manufacturer spec); (2) a full-system stopping distance test on a closed surface or dynamometer; (3) ABS system scan with no fault codes remaining; (4) measurement and documentation of final pad/shoe thickness; (5) a signed certification stating the vehicle meets all FMCSR 393.40 performance requirements. Do not accept "looks good" or a simple road test. Generate a repair completion report linked to the pre-citation condition, and have a safety manager review it before the vehicle leaves the facility.
› What should our post-citation review process cover?
If a vehicle is cited, conduct a root-cause meeting within 5 business days involving the driver, maintenance technician, and safety manager. Review: (1) the inspection report for the specific defect noted; (2) the vehicle's pre-trip logs for the 30 days prior—did the driver miss or ignore warning signs? (3) the maintenance schedule and whether the vehicle was overdue for brake service; (4) the repair work order to confirm the defect was actually fixed, not just documented; (5) whether similar defects appear in your peer vehicles (same make/model). Determine if the issue is a training gap, a technician competency issue, or a systemic maintenance scheduling failure. Document findings and corrective actions in your CSA Vehicle Maintenance BASIC tracking system.
› How does a 393.40(b) citation impact our CSA Vehicle Maintenance BASIC score?
Each citation of 393.40(b) carries a CSA severity weight of 8, which feeds into your carrier's Vehicle Maintenance BASIC score. Although this code ranks #2230 by citation volume (only 9 all-time citations in our database), the 77.8% out-of-service rate means inspectors perceive brake failures as acute safety hazards. Even a single citation signals to CSA auditors that your inspection and maintenance processes may have gaps. The higher the severity weight relative to citation frequency, the more auditors scrutinize whether your preventive maintenance program catches brake degradation before inspection. Focus on proving you catch issues internally, not at roadside.
› What driver training topics should we prioritize to prevent brake citations?
Train drivers on: (1) recognizing brake warning signs—soft or spongy pedal, longer stopping distance, brake warning lights, air leaks; (2) the daily pre-trip brake checklist and why each step matters; (3) when to report brake issues (immediately, not waiting for scheduled maintenance); (4) the difference between normal wear and actionable defect (brake dust is not corrosion, but scoring on the rotor is). Use your vehicle maintenance records to show drivers real examples of failed brakes from your fleet. Require drivers to sign off on brake training annually, and review brake-related citations with the driver who was operating the vehicle at inspection.
› Should we challenge a 393.40(b) citation through DataQs?
Consider a DataQs challenge only if: (1) your maintenance records prove the brake system met performance standards at the time of inspection (e.g., a recent pressure test or pad measurement dated before the roadside check); (2) the inspector's measurement or stopping distance test was performed incorrectly (e.g., wet surface, improper brake bleeding); or (3) the vehicle was taken out of service immediately upon inspection and never operated, so the defect was not a safety risk in actual service. Do not challenge if the citation is factually correct. Given the 77.8% out-of-service rate, our data shows inspectors cite this violation when brakes are genuinely unsafe. A challenge without strong documentation will damage your carrier's credibility.
› How often should we self-audit for brake adequacy across the fleet?
Conduct a full brake system self-audit quarterly (every 90 days). Our inspection records show zero citations of 393.40(b) in the last 90 days and zero in the last 12 months, which suggests this violation is rare but severe when it occurs. A quarterly cadence ensures you catch degradation before it reaches roadside inspection levels. Each audit should include: (1) pressure tests on all air brake vehicles; (2) pad/shoe thickness measurement on all wheels; (3) brake fluid condition assessment; (4) ABS diagnostics on equipped vehicles. Document and trend results month-over-month to identify vehicles approaching minimum thresholds. If any vehicle fails, take it out of service until repairs are verified.
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.