Prevention FAQ — FMCSR 393.40 Inadequate Brakes

Fleet safety guide to brake system compliance. Pre-trip inspection protocols, documentation requirements, root-cause analysis from 457 citations, and audit cadence based on enforcement trends.

OOS Eligible
Severity Weight
8
OOS Eligible
Yes
BASIC Category
Vehicle Maintenance
Code System
FMCSR
Code:
393.40
Code System:
FMCSR
BASIC Category:
Vehicle Maintenance
OOS Eligible:
Yes
Severity Weight:
8
Violation Group:
BASIC 5

Ranks #967 of 3,146 FMCSR codes by citation frequency • OOS rate of 23.2% is below the FMCSR-wide average of 33.3%.

Violation Description

Commercial motor vehicle equipped with brakes that are inadequate or fail to meet performance requirements.

Prevention FAQ for Fleet Managers

Pre-trip discipline, inspector focus, and root-cause fixes

What specific brake conditions do roadside inspectors focus on for 393.40?

Inspectors evaluate whether your brakes meet performance standards under FMCSR 393.40—that is, they function adequately and meet manufacturer and regulatory specs. Our inspection records show that across the last 180 days, Texas accounted for 4 citations with a 75.0% out-of-service rate, the highest regional enforcement intensity we track. Inspectors typically measure brake force, check for excessive wear, test responsiveness, and verify that air loss, lag time, and stopping distance fall within spec. They pay close attention to vehicles with mixed fleet ages; Ford units lead our all-time citation list with 40 citations, followed by trailers (39) and Dodge pickups (29). Inspectors also look for signs of recent repairs that may not have been validated properly. If you operate in Texas or similar high-enforcement states, expect heightened scrutiny of brake condition logs and maintenance records at the roadside.

What should be on our pre-trip brake inspection checklist?

Your pre-trip must include: (1) Brake fluid level and condition—check for contamination or low levels; (2) Air pressure in all reservoirs—verify against manufacturer spec and note any creep; (3) Brake pad/lining thickness—measure remaining material and compare to minimum allowed; (4) Drum condition—look for cracks, heat scoring, or out-of-round; (5) Slack adjuster free-play—confirm it's within limits and moves freely; (6) Hoses and lines—inspect for cracks, leaks, bulging, or pinches; (7) Brake lag and response—test pedal feel and stopping distance in a controlled low-speed test; (8) ABS indicator lights—confirm all warnings clear after startup. Document each item with date, driver initials, and specific measurements (e.g., "4.2 mm pad depth, within spec"). Our data shows 396.3A1BOS (20%+ brake defects) is the most frequently paired violation with inadequate brakes in the last 90 days—3 shared inspections—suggesting that systemic wear across multiple brake components is a primary failure mode. Make the checklist granular enough that a driver can catch a degrading system before an inspector does.

What documents must drivers carry and fleets retain for brake compliance?

Drivers must carry: (1) Current pre-trip inspection report signed and dated before departure; (2) Maintenance and repair records for the past 12 months showing all brake service; (3) Brake performance test results if the vehicle underwent recent certification or recertification; (4) Manufacturer specs for your vehicle's brake system (stopping distance, air pressure, adjustment limits). Fleets must retain: (1) Complete maintenance log for each vehicle, including every brake adjustment, pad replacement, hose replacement, and fluid service; (2) Inspection audit trail—weekly or bi-weekly pre-trip records stored for minimum 12 months; (3) Out-of-service records—if a brake issue was found, document the repair, parts replaced, shop receipt, and the re-inspection sign-off before returning to service; (4) Driver training certificates confirming brake system knowledge. Roadside inspectors will ask to see maintenance history. Absence of records can reinforce a 393.40 citation even if brakes now pass. Our records show carriers like Morelli Logistics LLC (6 citations all-time) that cite 393.40 repeatedly may lack systematic documentation. Store records digitally and in hard copy to survive accidents or audits.

What root causes does our violation co-occurrence data reveal?

Across the last 90 days, we tracked violations co-occurring in the same inspection. 396.3A1BOS (20%+ defective brakes) appeared in 3 shared inspections with 393.40—the strongest signal—indicating that your brake failure stems from systemic wear across multiple axles or components, not a single point defect. This suggests a maintenance cadence that's too infrequent or drivers not reporting brake feel changes. 392.2RG and 392.2MI (fatigue/illness) appeared in 2 and 1 shared inspections respectively, hinting that fatigued drivers may ignore subtle brake degradation or operate vehicles in poor brake condition because they're impaired by fatigue—a compounding safety issue. 393.43 (brake relay emergency valve) and 393.47F (brake actuators/chambers) each appeared once, reflecting pneumatic system failures tied to brake adequacy. Root cause action: Implement monthly brake component audits on a rolling basis rather than annual inspections. Add fatigue risk management training to emphasize brake system vigilance. Cross-check brake citations against driver logs to identify whether fatigue is a co-factor in your fleet's incidents.

How should we verify brake repairs before returning a vehicle to service?

After any brake repair, follow this verification protocol: (1) Inspect the repair ticket—confirm the shop identified the original defect, documented the fix, and listed all parts replaced; (2) Perform a bench test—have a qualified mechanic apply the brakes and measure stopping performance under controlled conditions (parking lot at 5, 10, and 20 mph); (3) Check air pressure stability—run the engine for 10 minutes and confirm no more than 3 psi loss over 10 minutes; (4) Measure slack adjuster free-play again—ensure adjustment is within spec and repeatable; (5) Road test—drive the vehicle at 30 mph and confirm linear pedal feel, no grabbing or pulling, and adequate stopping distance; (6) Document sign-off—have the certifying mechanic and a fleet safety manager co-sign a return-to-service form with date, mileage, and specific measurements. Store this form with the repair invoice. Our data shows 105 out of 457 citations (23.0% OOS rate) result in out-of-service placement, meaning inspectors found unsafe brakes. Verification eliminates the risk of returning a half-repaired vehicle to the road. If the repair shop cannot provide documentation, do not accept the vehicle.

What should we review after a 393.40 citation?

Immediately upon citation, run a structured post-event review: (1) Interview the driver—ask what they noticed before the stop (brake feel, warning lights, air loss, pedal changes) and whether they reported it; (2) Retrieve the repair history—pull the past 12 months of maintenance for the cited vehicle to identify gaps or recurring issues; (3) Compare to fleet baseline—check whether this vehicle's brake citation rate is above or below your fleet average; (4) Check the inspection report—confirm the specific defect cited (e.g., worn pads, air leak, slack adjuster out of spec) and trace it to a root cause; (5) Audit similar vehicles—inspect the same make/model and year across your fleet; our data shows Ford (40 citations) and trailers (39) are top-cited, so if you operate these types, prioritize them; (6) Review co-occurring violations—if the citation was paired with fatigue (392.2RG/2MI) or other maintenance codes, flag the driver or vehicle for additional training or deeper maintenance. Document findings and corrective actions in your fleet safety file. This review takes 2–3 hours but prevents repeat citations and liability.

How does 393.40 impact our CSA Vehicle Maintenance BASIC score?

FMCSR 393.40 carries a CSA severity weight of 8, placing it in the upper-middle range of violation weights. Across our 13 million inspection records, this code ranks #954 out of 3,036 FMCSR codes by citation volume (457 all-time, 31 in the last 12 months). While not in the top tier by frequency, the 23.0% out-of-service rate is notably lower than the all-FMCSR average of 31.4%, meaning fewer citations result in immediate removal from service—but that also suggests many brake inadequacy violations are cited as warnings or correctable defects rather than safety shutdowns. The Vehicle Maintenance BASIC aggregates all maintenance and equipment violations into a carrier safety score used by insurers, brokers, and regulators. A single 393.40 citation contributes modestly to your BASIC, but repeated citations (e.g., Morelli Logistics LLC with 6 all-time citations) raise red flags and trigger audits. If your fleet accumulates multiple brake citations in a 12-month period, your Vehicle Maintenance BASIC score will climb, potentially affecting insurance rates and shipper confidence. Prevention is economically essential: one citation costs $200–$500 in fines plus downtime; six citations cost your reputation.

What training topics should we cover with drivers to prevent brake citations?

Develop a brake system competency module covering: (1) Pre-trip brake inspection fundamentals—teach drivers how to visually inspect pads, hoses, and drums and what measurements trigger concern; (2) Brake system architecture—explain air vs. hydraulic systems, how slack adjusters work, and why pressure loss matters; (3) Early warning signs—soft pedal, grabbing, pulling, air loss audible hisses, warning light illumination, and what to do when they occur; (4) Reporting protocol—ensure drivers know how to radio in a brake issue and where the nearest safe stop is; (5) Fatigue and brake vigilance—tie back to co-occurring 392.2RG/2MI violations; teach that impaired drivers are less likely to notice brake degradation; (6) Maintenance records—show drivers where their vehicle's brake service log is stored and why they should review it. Use case studies from your fleet's past 393.40 citations (anonymized) as teaching examples. Ford vehicles (40 citations) and trailers (39) are over-represented in our data, so if you operate these, create model-specific modules. Training should be documented and delivered annually, with competency testing. This reduces both citations and safety incidents.

How frequently should we audit our fleet for brake system compliance?

Based on our 12-month trend data, citations for 393.40 peaked in May and June 2025 (8 and 7 citations respectively), dropped sharply in August (2 citations), and remained low through winter months (1–3 citations). This seasonal pattern—high in late spring—suggests increased inspections during warmer months and possibly pre-summer fleet mobilization. Implement a monthly rolling audit of 15–20% of your fleet's brake systems, completing 100% coverage every 6 months. Prioritize vehicles in high-enforcement states (Texas, 75.0% OOS rate in our last 180 days) and high-citation makes (Ford, trailers, Dodge). For fleets with 1–10 vehicles, conduct full brake audits quarterly; for fleets with 50+, rotate monthly. After roadside citation (which we see occurring 31 times per year nationally and 4 times in the last 90 days), re-audit that vehicle plus all others of the same model within 2 weeks. Use a digital inspection form linked to your maintenance system so that out-of-spec findings trigger automatic work orders. Document all audits with timestamps, measurements, and sign-offs. This proactive approach, tied to seasonal peaks and your own citation history, ensures brakes remain compliant and reduces roadside surprise.

When should we consider filing a DataQs challenge for a 393.40 citation?

DataQs challenges are appropriate if: (1) The citation is factually inaccurate—the brakes were tested and met spec, but the inspector misread the gauge, used an incorrect procedure, or documented the wrong measurement; provide the repair invoice, test results, and manufacturer spec to prove compliance at the time of inspection; (2) The driver was not the cause—if the vehicle suffered a sudden failure (e.g., hose rupture) between your pre-trip inspection and the roadside stop, document your inspection report showing brakes were in spec 30 minutes prior, plus the repair receipt proving the defect was mechanical failure, not maintenance neglect; (3) The citation is a duplicate—if the same vehicle was cited twice for the same brake defect within a short window and repaired between citations, the second citation may be invalid; provide both repair tickets to challenge the duplicate. Do not challenge based on subjective disagreement with the severity weight or policy. Our database shows 457 all-time 393.40 citations, and the vast majority are valid—brakes do fail. Challenge only when you have documentary evidence of inspector error, vehicle failure independent of fleet maintenance, or administrative duplication. Contact your FMCSA field office or your safety advocate before filing to assess your case.

Last updated: 2026-04-20T14:38:48.158Z Guidance derived from TruckCodex inspection data Read the full article → Quick Q&A →

Top Enforcing States

Where 393.40 is most commonly cited (last 180 days)

1. Illinois
4
OOS 50.0%
2. Texas
3
OOS 66.7%
3. North Carolina
1
OOS 0.0%
4. New Mexico
1
OOS 0.0%

Often Cited Together

Other violations commonly found on the same inspection (last 90 days)

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.

Refreshed daily.

Vehicle recall campaigns, defect investigations, and consumer safety complaints (SCRS).

Refreshed daily.
EIA

Retail diesel and gasoline price history and state fuel-tax tables.

Refreshed weekly.

Cross-border carrier registry and Canadian recall campaigns where applicable.

Refreshed weekly.

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.