Prevention FAQ — FMCSR 393.28: Wiring Improper/Inadequate

Inspectors target wiring that is insecurely routed, chafing against metal edges, missing protective loom or conduit, or showing splices that lack weatherproof connectors. They check cab-to-trailer connections, underchassis harnesses, and any wiring near heat sources like exhaust or brake components.

Our inspection records show Texas accounts for 739 of the citations logged in the last 180 days — by far the highest volume state for this code. Illinois follows with only 21 citations but carries a 19.0% out-of-service rate in that same window, meaning inspectors there write it up less often but act on it more severely. If your fleet runs I-20/I-10 corridors through Texas or any lane through Illinois, treat wiring condition as a primary inspection priority, not a secondary one.

Build these discrete line items into your pre-trip form — generic "electrical check" entries will not catch what inspectors find:

• Cab wiring: Confirm no exposed conductors at firewall pass-throughs; check that all looms are clipped and intact.
• Underchassis harness: Walk the frame rail and look for harness sections contacting the exhaust pipe or brake tubing — our data shows 393.45B2UV (brake tubing) co-occurs with this code in 94 shared inspections over the last 90 days, signaling shared routing failures.
• Trailer pigtail and ABS harness: Inspect for cracked insulation, bent pins, and unsecured coil.
• Splices and connectors: Any field splice must be heat-shrunk and strain-relieved; tape-only repairs are a citation waiting to happen.
• Mounting hardware: Verify all P-clips and tie wraps holding the harness are present and not cutting into insulation.

FRHT vehicles account for 1,123 all-time citations under this code — if your fleet runs Freightliners, pay particular attention to the frame-rail harness behind the cab.

Drivers do not need to carry wiring-specific documents at roadside, but carriers must be prepared to produce:

• DVIR records: Any driver vehicle inspection report noting a wiring defect, plus the signed repair acknowledgment, must be retained for 90 days. A gap in this chain is itself citable.
• Repair work orders: Retain shop records showing what was repaired, the technician's name, and the date returned to service. These are your first line of defense in a DataQs challenge.
• Annual inspection report: Our data shows 396.17C (no proof of periodic inspection) co-occurs with 393.28 in 53 shared inspections over the last 90 days. Drivers should carry a current Annual Inspection decal or report copy — its absence amplifies inspector scrutiny of every electrical system on the vehicle.
• Pre-trip logs: Electronic or paper pre-trips that show the wiring was checked and found satisfactory support a challenge if the citation appears unjustified.

The co-occurrence data from our last 90 days of inspection records points to three systemic failure patterns:

1. Aging or neglected electrical systems — 393.9 (inoperable required lamp) appears in 160 shared inspections with 393.28, the highest overlap of any code. When lamps fail and wiring is simultaneously cited, the root cause is typically the same: deteriorated harnesses that were never replaced during lamp repairs. Fix the lamp and the feed.

2. Poor compartment protection — 393.45B2UV (brake tubing/hoses inadequate) co-occurs in 94 shared inspections. Wiring and brake tubing share underchassis routing; when one is damaged by road debris, heat, or improper clamping, the other usually is too. This signals a whole-system routing inspection is needed, not a spot repair.

3. Deferred maintenance culture — 396.3A1 (inspection, repair, and maintenance) co-occurs in 56 shared inspections. When this appears alongside 393.28, it nearly always reflects a pattern of skipped PMs rather than a single-event failure. The corrective action here is scheduling discipline, not just a technician.

Do not allow the vehicle to dispatch based on a verbal "fixed it" confirmation. Use a structured return-to-service process:

1. Technician sign-off on work order: The repair order must describe exactly which wiring sections were repaired or replaced, not just "electrical repaired."
2. Functional test under load: Cycle all lights, ABS, and powered accessories after the repair to confirm no intermittent faults. A wiring defect that only appears under vibration or load will produce a repeat citation on the next stop.
3. Secondary inspection: Have a second technician or shop foreman physically walk the repaired routing before sign-off. This is especially important for FRHT and KW vehicles, which together account for 1,742 all-time citations under this code.
4. DVIR loop close: The driver must sign the corrected DVIR certifying the defect was repaired before the vehicle moves. Retain that document for 90 days minimum.

Run a structured post-citation review within 48 hours:

1. Pull the inspection report: Confirm which specific wiring section was cited. "Improper/inadequate" is broad — the officer's notes will narrow it to a location.
2. Check the co-occurring violations: Our data shows 393.28 regularly appears with 396.5B (fuel system leak, 85 shared inspections) and 392.2RG (operating while fatigued, 56 shared inspections). If either of those also appeared on the same inspection report, the review must expand beyond wiring into your PM cycle and driver hours practices.
3. Audit the fleet, not just the cited unit: If one vehicle's wiring was in citable condition, others with the same age or routing design likely are too. Immediately schedule a wiring-specific walkthrough on all vehicles in the same model year or mileage band.
4. Document the corrective action: Record what was found, what was repaired, who performed the repair, and what process change — if any — was made. This trail is essential if the citation later appears in a CSA intervention.

Every 393.28 citation adds a CSA severity weight of 3 to the Vehicle Maintenance BASIC. The code is not OOS-eligible, so it will not trigger a roadside shutdown, but it will accumulate in your SMS score and can push a carrier toward an intervention threshold when it stacks with other Vehicle Maintenance violations.

The enforcement volume here is meaningful: across our database, this code has 6,422 all-time citations, ranking it #300 out of 3,036 FMCSR codes by citation volume. That puts it in the top 10% of all FMCSR codes by frequency. The all-time OOS rate is only 1.6% — far below the all-FMCSR average of 31.4% — which means inspectors are writing it up without placing vehicles out of service. The practical fleet impact is therefore not shutdowns but BASIC score creep. A carrier receiving even a handful of these per quarter will see measurable score movement if no countermeasure is in place.

Driver training for this code should focus on recognition during pre-trip, not repair. Drivers are not electricians, but they can be trained to identify the visual indicators that precede a citation:

• Exposed copper or cracked insulation anywhere along accessible harness sections
• Wiring contacting exhaust components or resting against sharp metal edges
• Unsupported long harness runs that vibrate freely
• Trailer ABS and pigtail connectors with cracked boots or corroded pins

Vehicle make matters here: our inspection records show FRHT vehicles have 1,123 all-time citations, KW has 619, and PTRB has 415. If your fleet is predominantly Freightliner, Kenworth, or Peterbilt, include make-specific diagrams showing the harness routing areas most commonly cited on those platforms. Pair the training with a physical walkthrough on an actual fleet unit — showing drivers where the frame-rail harness runs on their specific truck is more effective than a classroom diagram alone.

A DataQs challenge on 393.28 is viable when you can demonstrate one of these conditions:

1. The cited wiring was compliant: You have a pre-trip DVIR signed the day of the inspection confirming the wiring was checked and found acceptable, and the repair work order shows the wiring met specification.
2. The officer applied the wrong code: If the underlying condition was actually a lighting failure (393.9) or a broken connector, not improper installation or routing, the code may be disputable.
3. The vehicle was misidentified: Confirm the DOT number, unit number, and inspection date on the report match your records exactly.

Do not challenge on the basis of the violation being "minor" — the 1.6% OOS rate and severity weight of 3 do not, by themselves, support a challenge. The challenge must rest on factual error. Given that Texas accounts for 739 citations in the last 180 days, cross-border carriers operating through that state will have the most frequent opportunities — and the most need — to maintain clean documentation that supports a challenge if one is warranted.

Our inspection records show 1,480 citations in the last 12 months and 347 in the last 90 days — meaning roughly 29% of the annual volume concentrated in the most recent quarter. Monthly counts have been climbing: citations rose from 107 in 2025-08 to 157 in 2026-01 and 163 in 2026-02 before settling to 134 in 2026-03. That upward trend means enforcement attention on this code is increasing, not static.

Recommended audit cadence:

• Quarterly: A full wiring walkthrough on every unit, timed to align with PM intervals. The 90-day trend concentration supports this — waiting six months means you are already in the enforcement window.
• Post-winter and post-summer: Temperature cycling accelerates insulation cracking and connector corrosion. Run a targeted audit after each extreme-temperature season before the next high-enforcement quarter begins.
• After any repair involving wiring adjacent to the harness: Fuel system work (396.5B co-occurs in 85 shared inspections) and brake tubing repairs disturb adjacent wiring. Add a wiring check to the completion checklist for any repair in those systems.