Prevention FAQ — FMCSR 393.43D: Relay/Emergency Valve

Fleet safety FAQ on preventing 393.43D citations: inspector focus areas, pre-trip steps, CSA impact, and root-cause analysis from 4,729 real inspections.

OOS Eligible
Severity Weight
4
OOS Eligible
Yes
BASIC Category
Vehicle Maintenance
Code System
FMCSR
Code:
393.43D
Code System:
FMCSR
BASIC Category:
Vehicle Maintenance
OOS Eligible:
Yes
Severity Weight:
4
Violation Group:
Brakes All Others

Ranks #349 of 3,146 FMCSR codes by citation frequency • OOS rate of 93.6% is above the FMCSR-wide average of 33.3%.

Violation Description

No or defective automatic trailer brake

Prevention FAQ for Fleet Managers

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

What exactly do inspectors examine when writing a 393.43D citation, and which states should my fleet prioritize?

Inspectors check whether the relay or emergency valve on the air brake system operates as designed — testing for delayed response, air leaks at the valve body or supply ports, valve sticking, or failure to release/hold pressure correctly. With a 93.4% OOS rate across 4,729 all-time citations in our database — nearly three times the all-FMCSR average of 31.4% — inspectors treat any functional defect here as an automatic pull.

Concentrate compliance pressure on Texas (861 citations, 91.3% OOS rate in the last 180 days) and Iowa (253 citations, 98.0% OOS rate). North Carolina, Illinois, and New Mexico each show a 100% OOS rate in the same period, meaning every cited vehicle was parked. Plan pre-trip valve checks before any load entering these states.

What specific items should go on the pre-trip checklist to prevent a 393.43D write-up?

Add the following discrete line items to the brake section of your DVIRs:

  1. Air build-up test — confirm system reaches governor cut-out (typically 120–130 psi) within the required time; sluggish build can indicate a failing relay valve.
  2. Valve body visual — inspect for cracks, corrosion, or physical damage at the relay and emergency valve housings.
  3. Supply/delivery port leak check — apply brakes, hold, and listen/feel for air escaping the valve.
  4. Emergency valve function — with a tractor-trailer combination, disconnect the supply line briefly to confirm the emergency valve actuates and holds.
  5. Response lag test — time the lag between brake application at the cab and actuator movement at the rear axle; noticeable delay is a red flag.

Drivers should initial each line item, not just sign the bottom of the form.

What documentation must drivers carry and what must the carrier retain to protect against a 393.43D citation or DataQs challenge?

Drivers must carry: The completed DVIR for the current trip (showing a signed-off brake section) and, where required, proof of the most recent periodic inspection. Our data shows 396.17C (No proof of periodic inspection) co-occurred with 393.43D in 253 shared inspections in the last 90 days — the top co-occurring code — meaning inspectors almost always check for the periodic inspection record when they find a valve defect.

Carriers must retain:

  • DVIRs for at least 90 days
  • Annual/periodic inspection reports for at least 14 months
  • Repair work orders documenting the specific relay/emergency valve serviced, part numbers replaced, and the technician's certification
  • Pre-/post-repair air brake performance test results

Keep digital copies accessible to dispatchers so a record can be produced during a roadside interaction or DataQs filing.

What root causes does the co-occurrence data point to, and what systemic issues should I investigate first?

Our inspection records show three dominant co-occurrence patterns across the last 90 days that point to specific systemic failures:

396.17C — No proof of periodic inspection (253 shared inspections): Vehicles cited for the valve defect overwhelmingly lack current inspection records. The root cause is typically a PM scheduling gap or a paper-based tracking system that lets inspections lapse unnoticed.

392.2RG — Operating while ill or fatigued (249 shared inspections): This pairing suggests drivers under schedule pressure are skipping pre-trip brake checks. The valve defect existed but wasn't caught because the DVIR was rushed or falsified.

393.95A — Fire extinguisher missing/defective (198 shared inspections): Co-occurrence with missing safety equipment signals fleet-wide maintenance neglect rather than an isolated valve failure. When one item is deferred, multiple items tend to be deferred together.

Address all three: tighten PM scheduling, enforce DVIR completion accountability, and conduct spot audits of emergency equipment alongside brake inspections.

How should repairs be verified before the vehicle returns to service after a 393.43D defect is found?

Require a post-repair brake performance certification from a qualified brake technician before the vehicle moves under load. At minimum, the verification record must document:

  • The specific valve replaced or repaired (manufacturer, part number, location on the vehicle)
  • Air pressure supply and delivery readings before and after repair
  • Application/release response time at each affected actuator
  • Leakdown test result (pressure drop over a timed period with brakes applied and released)
  • Technician's signature and certification number

Given the 93.4% OOS rate our records show for this code, do not allow a driver self-certification on relay/emergency valve repairs. The repair order must include objective test data, not just a notation that the valve was "replaced." File the repair order against the vehicle's maintenance record immediately so it's available for the next inspection.

What post-citation review process should the fleet run after receiving a 393.43D violation?

Run a structured five-step review within 72 hours of notification:

  1. Pull the DVIR chain — review every DVIR for that vehicle going back 30 days. Determine whether the valve defect was ever noted and, if not, why it was missed.
  2. Review the PM record — confirm the last annual inspection date and whether the relay/emergency valve was specifically tested and signed off.
  3. Check the driver's pre-trip compliance rate — if DVIRs show no defects for weeks before the citation, investigate whether inspections are being completed thoroughly.
  4. Fleet-wide valve check — pull every vehicle of the same make and model year for an immediate relay/emergency valve inspection. Our data shows 383.23A2 (operating without a CDL) co-occurred in 147 shared inspections, suggesting some cited vehicles may have underlying qualification issues compounding maintenance lapses.
  5. Update the corrective action log — document findings and corrective steps; this record supports any future DataQs challenge and demonstrates good faith in SMS scoring.
How does a 393.43D citation affect our CSA Vehicle Maintenance BASIC score, and how serious is the exposure?

393.43D carries a CSA severity weight of 7 out of 10, placing it in the high-severity tier within the Vehicle Maintenance BASIC. Combined with the 93.4% OOS rate — meaning 4,415 of 4,729 all-time citations resulted in an out-of-service order — virtually every citation also generates an OOS event, which multiplies the CSA point impact.

At #352 of 3,036 FMCSR codes by citation volume, this code is cited often enough that SMS algorithms see it regularly. In the last 12 months alone, our database records 3,011 citations — roughly 250 per month. A carrier accumulating multiple hits on a severity-7 code at a 93.4% OOS conversion rate will see Vehicle Maintenance BASIC percentile climb quickly. Even one citation on a small carrier (under 20 power units) can push the BASIC into intervention territory.

What driver training topics close the gap for this violation, and does the vehicle make data suggest any fleet-specific focus?

Our inspection records identify Ford (1,563 citations) and RAM (1,129 citations) as the top-cited vehicle makes for 393.43D, followed by Dodge (550 citations) and Chevrolet (501 citations). If your fleet runs any of these makes — particularly medium-duty Ford or RAM chassis — prioritize hands-on training with those specific brake configurations.

Training topics to cover:

  • Air brake system fundamentals — how relay valves and emergency valves function, why they fail, and what failure feels like from the cab
  • DVIR precision — specifically how to test and document brake response during a pre-trip, not just a visual check
  • "When in doubt, write it out" — build a culture where drivers flag any brake anomaly rather than completing a run first
  • Emergency valve function in combination vehicles — trailer emergency valve activation upon breakaway is frequently misunderstood

Use actual citation photos and inspection narratives from our database in training materials to make the content concrete.

When does it make sense to file a DataQs challenge on a 393.43D citation, and what evidence wins those challenges?

Challenge a 393.43D citation when you can demonstrate one of three things: (1) the valve was inspected and documented as serviceable within the same pre-trip DVIR, (2) a repair work order shows the defect was corrected before the inspection occurred and the repair record was not reviewed by the inspector, or (3) the inspector's notation is inconsistent with post-inspection testing results documented by your shop within hours of the stop.

The strongest evidence package includes: the signed DVIR, a dated repair order with part numbers and post-repair test readings, and the periodic inspection certificate showing the valve was evaluated. Given that 396.17C (no proof of periodic inspection) co-occurred in 253 shared inspections over the last 90 days, a well-documented periodic inspection record alone may resolve a challenge where the inspector had no proof to examine at the roadside. Do not file a DataQs challenge without a complete evidence package — a dismissed challenge with weak documentation counts against the carrier.

How frequently should our fleet self-audit for relay/emergency valve condition, and what does the trend data suggest about timing?

Our database records 541 citations in the last 90 days against 3,011 in the last 12 months, meaning roughly 18% of the annual volume landed in a single quarter — the most recent one. Monthly counts peaked at 328 in October 2025 and have remained elevated, averaging over 250 per month for most of the trailing year. This is not a seasonal spike; it is a sustained enforcement environment.

Recommended self-audit cadence:

  • Every PM service interval — relay/emergency valve function test must be a mandatory line item, not optional
  • Quarterly fleet-wide inspection — pull every unit specifically for valve condition independent of other maintenance triggers
  • After any brake-related repair — re-test valve response before returning the vehicle to line-haul service

With 93.4% of citations converting to OOS orders, a deferred audit means a very high probability of a parked truck if an inspector finds the issue first. The cost of one OOS event — driver detention, load delay, towing — exceeds the cost of a quarterly valve inspection program many times over.

Last updated: 2026-04-20T13:14:38.182Z Guidance derived from TruckCodex inspection data Read the full article → Quick Q&A →

Top Enforcing States

Where 393.43D is most commonly cited (last 180 days)

1. Texas
534
OOS 93.3%
2. Iowa
129
OOS 99.2%
3. Illinois
69
OOS 100.0%
4. North Carolina
42
OOS 100.0%
5. New Mexico
9
OOS 100.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.