Prevention FAQ — FMCSR 393.42(a) Parking Brake Defects

Fleet safety guidance on parking brake inspections, root-cause analysis, and prevention strategies based on 652 all-time citations and real co-occurrence patterns.

Severity Weight
6
OOS Eligible
No
BASIC Category
Vehicle Maintenance
Code System
FMCSR
Code:
393.42(a)
Code System:
FMCSR
BASIC Category:
Vehicle Maintenance
OOS Eligible:
No
Severity Weight:
6

Ranks #862 of 3,146 FMCSR codes by citation frequency • OOS rate of 30.1% is in line with the FMCSR-wide average of 33.3%.

Violation Description

No Brakes On All Wheels As Required

Prevention FAQ for Fleet Managers

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

What exactly do inspectors focus on when checking the parking brake system?

Inspectors verify that the parking brake can hold the vehicle stationary without creep or rollback on level and inclined surfaces. They'll apply the brake and attempt to move the vehicle by hand or gently with the tractor; any movement means an OOS write-up is likely. Our inspection records show Ford vehicles account for 111 of the 652 all-time citations for this code, suggesting older or higher-mileage Ford fleets face elevated scrutiny. Inspectors also check:

  • Brake pedal engagement and holding pressure
  • Cable or rod tension and corrosion
  • Drum/disc seating and wear
  • Manual release lever operation and wear

Test the parking brake yourself during pre-trip, especially after any brake service or long idle periods.

What should the driver's pre-trip checklist include to catch parking brake issues early?

Your checklist must include three active tests:

  1. Level ground test: Park on flat pavement, engage the parking brake, shift to neutral, and verify the vehicle doesn't roll forward or backward when you gently test the throttle.

  2. Incline test: On a 5–10% grade, engage the brake, shift to neutral, and confirm no creep. Don't rely on engine braking.

  3. Visual inspection: Check for cable slack, corrosion, broken mounting brackets, and drum/disc condition. Listen for grinding or clicking when the brake is applied.

Document all three findings on the pre-trip form, even if the result is "pass." Drivers in fleets with recent parking brake citations should increase test frequency to every shift, not just daily.

What records must drivers carry, and what should the carrier retain?

Drivers must carry:

  • Pre-trip inspection reports (last 8 days) showing parking brake test results
  • Brake service work orders and dates
  • Any mechanic notes on parking brake adjustment or repair

Carriers must retain:

  • Complete brake maintenance records (all vehicles, 2+ years)
  • Calibrated torque wrench logs if cables are tensioned
  • Repair tickets with mechanic signature and date
  • Inspection photos of brake components (helpful for DataQs disputes)
  • Driver training attendance records for brake system checks

Inspectors may request these on roadside; absence creates a secondary violation (396.11 — maintenance records). Link all records to specific vehicle VIN and odometer reading.

What are the common root causes, based on co-occurrence patterns in roadside data?

Our inspection records show parking brake defects often occur alongside other brake and maintenance failures, signaling systemic issues:

  • Paired with 393.47E (slack adjuster defective, 180,363 citations): Suggests mechanics are not adjusting the full brake system holistically. When slack adjusters are worn, parking brake cables may also be slack. Remedy: retrain techs to perform full brake audits, not isolated repairs.

  • Paired with 396.3(a)(1) (inspection/repair/maintenance general, 236,919 citations, 45.3% OOS rate): Indicates deferred maintenance culture. Parking brake failures are typically slow-developing—they signal a fleet that delays non-critical fixes. Remedy: establish a mandatory brake inspection cycle every 90 days.

  • Paired with 393.9(a) (inoperable lamps, 660,737 citations): Both suggest rushed pre-trip inspections or mechanic shortcuts. If drivers miss lamp checks, they may miss brake signs too. Remedy: standardize pre-trip time and training.

How should repairs be verified before the vehicle returns to service?

After any parking brake repair, follow this verification protocol:

  1. Mechanic certification: Repair work order must be signed by a technician, include date completed, and list the specific repair (e.g., "cable tensioned to 45 lbs", "drum resurfaced").

  2. Post-repair test: The mechanic must perform the same level-ground and incline tests the driver uses, documenting hold duration (aim for >30 seconds without creep). Record odometer.

  3. Driver sign-off: Before the vehicle re-enters service, the assigned driver must verify the repair in the cab and sign the work order. This creates accountability and lets drivers report incomplete work before roadside contact.

  4. Photo documentation: Capture the brake assembly before and after repair, especially cable condition. This evidence protects you in a DataQs appeal.

  5. Re-test cycle: Retest the parking brake after 500 miles and again at the next scheduled service.

What post-citation review should the fleet run?

When a driver receives a 393.42(a) citation, conduct a structured review within 72 hours:

  1. Root-cause interview: Ask the driver if they noticed any symptoms (stiffness, creeping, grabbing). Did they perform the pre-trip test? This surfaces whether the issue was mechanical or procedural.

  2. Vehicle history audit: Pull all maintenance records for that specific unit from the past 12 months. Check for patterns—if the parking brake was last serviced 18+ months ago, that's your culprit.

  3. Peer comparison: Review the same check on 2–3 similar vehicles in your fleet (same make/model/age). If they all show slack cables, you have a fleet-wide issue, not a one-off.

  4. Driver retraining: If the pre-trip test was skipped or done incorrectly, retrain the driver on the three-point checklist (level, incline, visual). If the truck genuinely failed and the driver reported it, escalate to maintenance.

  5. Maintenance record update: Document the root cause and corrective action in your fleet management system so you don't repeat the same repair.

How does a parking brake citation affect the fleet's CSA Vehicle Maintenance BASIC?

Parking brake defects carry a CSA severity weight of 6, making them a mid-tier concern in the Vehicle Maintenance category. Across our 13 million inspection records, this code ranks #836 by citation volume (652 all-time citations), placing it in the long tail of violations—not a front-page driver of your BASIC score, but present enough to matter if your fleet accumulates multiples.

The all-FMCSR average out-of-service rate is 31.4%; parking brake defects are cited out-of-service 30.1% of the time (196 of 652 citations), just below average. Each OOS citation damages your CSA score more than a non-OOS violation. If your fleet has 2+ parking brake citations in 12 months, prioritize this issue; you're trending above the baseline. Severity weight 6 means a single citation is roughly equivalent to 6 minor violations in CSA scoring—not catastrophic, but meaningful.

What training topics should drivers receive to prevent this violation?

Design a parking brake training module covering:

  1. System anatomy: Explain cable vs. hydraulic parking brakes, drum vs. disc mechanisms, and why older vehicles (Ford is the top cited make with 111 citations) may require more frequent adjustments due to wear.

  2. The three-point test: Walk drivers through level-ground, incline, and visual checks with hands-on practice in a training vehicle. Use a 5% slope if available; many drivers have never tested on a grade.

  3. When to report: Establish a clear threshold—any creep, any spongy feel, or any visual corrosion triggers a maintenance report before the next trip. Make reporting easy (QR code to a form, text-to-dispatch).

  4. Photos and documentation: Show drivers how to take photos of brake issues so maintenance can triage. Poor communication leads to repeated repairs.

  5. Common failure modes by vehicle age: If your fleet skews toward older Fords, Dodges, or Chevrolets (which together account for 170 of 652 citations), highlight cable corrosion and adjustment drift as predictable failure patterns.

When should the fleet file a DataQs challenge against a parking brake citation?

File a challenge if:

  1. You have repair records proving the brake was serviced within 30 days before the citation. Request that service invoice, the mechanic's test results, and the odometer reading. If the inspector found a defect just weeks after a certified repair, it suggests either inspector error or a catastrophic failure not yet documented.

  2. The inspector did not perform the standard hold test or did not document the test method. Vague citations ("parking brake inadequate" with no supporting notes) are vulnerable. Request the inspector's roadside notes; if they're blank or unclear, challenge the citation.

  3. Your fleet photo documentation from the repair shows proper brake tension/condition, and the citation was issued >500 miles later without evidence of intervening use. This suggests the issue developed after the last documented service, which mitigates fleet liability.

  4. The cited vehicle's maintenance history is clean (no prior parking brake violations in 24 months) and you've trained the driver. A single isolated violation after a documented repair is less defensible for FMCSA than a pattern.

Include photos, work orders, and driver affidavits ("I tested the brake the morning of citation and it held"). Challenges have a modest success rate, but are worth filing if evidence is clear.

How often should the fleet self-audit for parking brake defects?

Self-audit cadence: every 90 days minimum.

Why? Our inspection records show zero citations for this code in both the last 90 days and last 12 months, indicating enforcement focus has shifted or compliance has improved fleet-wide. However, the violation is not extinct—652 all-time citations confirm it remains a real risk. The absence of recent citations makes it easier to miss; complacency is a trap.

90-day cycle includes:

  • Physical brake test on 20% of your fleet (rotate units)
  • Audit of all pre-trip forms from the previous quarter
  • Mechanic spot-check of cable tension on 3–5 vehicles per shop
  • Review of maintenance intervals to confirm no vehicle exceeds 6 months without a brake service

Expand to 30-day audits if:

  • Any driver is cited for 393.42(a)
  • You discover a cable that's out of spec during a routine audit
  • Your fleet contains >50% Ford vehicles (111 citations) or older equipment

Document all audit findings in a log. This evidence demonstrates due diligence and CSA compliance culture.

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

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.