Prevention FAQ — FMCSR 393.23: Required Lamp Not Powered by Vehicle Electric
Fleet safety FAQ for FMCSR 393.23: inspector focus areas, pre-trip checklists, root-cause analysis, CSA impact, and audit cadence based on real inspection data.
- Code:
- 393.23
- Code System:
- FMCSR
- BASIC Category:
- Vehicle Maintenance
- OOS Eligible:
- No
- Severity Weight:
- 2
- Violation Group:
- Clearance Identification Lamps/Other
Ranks #322 of 3,146 FMCSR codes by citation frequency • OOS rate of 85.6% is above the FMCSR-wide average of 33.3%.
Violation Description
Required lamp not powered by vehicle electric
Prevention FAQ for Fleet Managers
Pre-trip discipline, inspector focus, and root-cause fixes
› What exactly do inspectors look for when they write up a 393.23 violation, and which states are hitting fleets hardest right now?
Inspectors are checking whether every lamp required by Part 393 is drawing power directly from the vehicle's own electrical system — not from a portable battery pack, auxiliary generator, zip-tied aftermarket wiring, or any other off-circuit power source. The lamp may be lit and functional; what triggers 393.23 is how it is powered.
Our inspection records show that over the last 180 days, Texas accounts for 26 of the citations under this code — far more than any other state — followed by North Carolina (4) and Iowa (2). If your lanes run through Texas, that enforcement intensity alone justifies building this check explicitly into pre-trip procedures for Texas-routed equipment. The 50.0% OOS rate seen in Texas, North Carolina, and Iowa in that same window is also notable given that 393.23 is not formally OOS-eligible, which means inspectors are finding compounding violations on the same inspection.
› What specific items should appear on the pre-trip checklist to prevent a 393.23 citation?
Add these discrete line items to your pre-trip form:
- Power source trace — At each required lamp location (headlights, taillights, marker lights, brake lights, turn signals, clearance lights), the driver must confirm the lamp is wired to the vehicle's OEM or certified-permanent electrical circuit, not to a supplemental power source.
- Visible wiring integrity — Check for exposed splice points, unsecured wire runs, or aftermarket add-on connectors at any lamp socket.
- Trailer pigtail/ABS connector check — Confirm all trailer electrical connections are fully seated and drawing from the tractor's power supply.
- No auxiliary lamp adapters — Confirm no portable or clamp-on lights are present and counted as required lamps.
- Post-repair verification note — If any lamp was replaced since the last trip, confirm shop paperwork shows the repair tied back to the vehicle circuit.
Drivers should sign off on each item individually, not as a bundled 'lights OK' checkbox.
› What documentation should drivers carry and what records should the carrier retain to defend against or prevent a 393.23 citation?
Drivers should carry:
- The most recent pre-trip inspection report showing the lamp power-source check was completed.
- Any repair order from the last 30 days referencing lamp or electrical circuit work, including the technician's sign-off that the repair used vehicle-sourced power.
Carriers should retain:
- Preventive maintenance (PM) records documenting that lamp wiring was inspected at each service interval, with the technician noting power-source compliance specifically.
- Annual vehicle inspection reports (AVIRs) that confirm lamp circuits passed, since 393.23 co-occurs frequently with other lighting codes (see co-occurrence data below).
- Driver Vehicle Inspection Reports (DVIRs) for at least 90 days — our database shows 12 citations in the last 90 days, meaning active enforcement is ongoing and a contemporaneous DVIR is your first line of defense in a DataQs challenge.
Retain all electrical repair work orders for the life of the vehicle, not just the standard 12-month window, because all-time citation history on 393.23 runs 5,781 records and inspectors can pattern-match a unit's history.
› What are the root causes of 393.23 violations, and what does the co-occurrence data reveal about systemic fleet issues?
Our inspection records show three patterns in the last 90 days that point directly to systemic causes:
1. Broader lamp and lighting system neglect — 393.9 (Inoperable Required Lamp) appeared in 5 shared inspections with 393.23. When a lamp is both unpowered from the vehicle circuit and inoperable, the underlying issue is almost always deferred electrical maintenance or an incomplete repair that left a lamp running off a temporary source.
2. General vehicle condition deterioration — 393.83G (exhaust discharging toward the cab) appeared in 4 shared inspections. A vehicle accumulating multiple Part 393 defects simultaneously suggests PM intervals are being stretched or pre-trip inspections are not catching compound defects.
3. Driver-state compliance pressure — 391.11B2-Z (English language proficiency) and 392.2RG (operating while ill or fatigued) each appeared in 4 shared inspections. These are driver-condition codes, not vehicle codes — their co-occurrence with 393.23 suggests inspections triggered by driver issues are also uncovering vehicle electrical problems that would otherwise go unreported.
› How should a technician verify the repair before the vehicle returns to service after a 393.23 citation?
A 393.23 repair is not complete until the technician has confirmed the following and documented each step:
- Circuit continuity test — Use a multimeter to verify the lamp socket is receiving voltage directly from the vehicle's primary electrical circuit, not a secondary source.
- Load test under operating conditions — Run the engine and cycle all required lamps (including brake actuation and turn signals) to confirm stable power from the vehicle system.
- Remove and document removal of any auxiliary power source — If a portable or add-on power device was present, log its removal on the repair order with a description of what it was and where it was installed.
- Second-tech sign-off — Require a second technician or shop foreman to initial the repair order confirming the power-source test was performed.
- Update the DVIR — The driver accepting the repaired vehicle must complete a new DVIR noting the defect as corrected before the first dispatch.
Given the all-time OOS rate of 85.6% on 393.23 — nearly three times the all-FMCSR average of 31.4% — inspectors clearly find co-violations on these units. A thorough post-repair walk-around covering all Part 393 lamp systems before return to service is essential.
› What post-citation review process should the fleet run after a driver receives a 393.23 citation?
Run this five-step review within 72 hours of the citation:
- Pull the inspection report — Identify every code written on that inspection. Given that 393.23 co-occurs with nine other codes in our last-90-day data, assume this is not an isolated lamp issue.
- Audit the unit's maintenance history — Review the last three PM cycles for that specific vehicle. Flag any lamp or electrical work orders and verify they documented power-source compliance.
- Interview the driver — Determine whether the pre-trip that morning included a power-source check or only a 'lamp lit' check. Update training if the driver conflated the two.
- Check the vehicle make — Our database shows FRHT units account for 535 all-time citations under 393.23, more than any other make. If the cited unit is a Freightliner, prioritize electrical circuit inspection across the entire fleet of that make.
- Flag sister units — If the cited vehicle shares a maintenance facility or driver pool with similar-make units, inspect those units before their next dispatch. A single citation in a fleet often signals a pattern.
› How does a 393.23 citation affect the carrier's CSA Vehicle Maintenance BASIC score, and how serious is this code in the ranking system?
393.23 sits at national rank #316 out of 3,036 FMCSR codes by all-time citation volume, with 5,781 total citations in our database. That places it in the top 11% of all codes by frequency — it is not an obscure edge case.
More importantly, the all-time OOS rate for this code is 85.6%, compared to the all-FMCSR average of 31.4%. Even though 393.23 is not formally OOS-eligible on its own, the 85.6% rate reflects how often inspectors find additional OOS-eligible violations on the same inspection. Each of those companion violations carries its own severity weight and BASIC points.
Every citation under 393.23 lands in the Vehicle Maintenance BASIC, and the severity multiplier applied to citations found during inspections where OOS violations co-occur is higher. Fleets in the top_carriers list — J B HUNT TRANSPORT INC with 33 all-time citations, UNITED PARCEL SERVICE INC with 27, and XPO LOGISTICS FREIGHT INC with 22 — illustrate that even large, well-resourced carriers accumulate BASIC exposure on this code over time.
› What specific training topics should close the knowledge gap for drivers, and does the vehicle-make data suggest any targeted approach?
Our inspection records show that FRHT (Freightliner) units account for 535 all-time citations — the highest of any make — followed by FORD (288), FREIGHTLIN (269), KW (Kenworth, 205), and INTL (International, 192). This distribution means driver training should be tailored by fleet make, not delivered generically.
Training topics to cover:
- Lamp power-source identification — Show drivers the difference between a lamp wired to the vehicle circuit and one running off an auxiliary source. Use make-specific diagrams for FRHT, KW, and INTL units given their prevalence in the data.
- What 'required lamp' means under Part 393 — Drivers need to know which lamps are federally required, not just which ones are currently lit.
- How to flag electrical anomalies on a DVIR — Train drivers to write 'lamp wiring suspect — not confirmed vehicle circuit' rather than just 'lamp out'.
- Trailer electrical connections — Given the co-occurrence with 393.11 lighting codes (3 shared inspections), add a dedicated module on trailer pigtail inspection and ABS power draw verification.
Use vehicle-specific simulator exercises for the top three makes in your fleet.
› Under what circumstances should a fleet file a DataQs challenge on a 393.23 citation, and what evidence is needed?
File a DataQs challenge when you can demonstrate one or more of the following with documentation:
- The lamp was provably on-circuit — If you have a pre-trip DVIR from that morning showing a power-source check was completed, and the inspection report does not specify how the lamp was allegedly off-circuit, you have grounds to challenge the factual basis.
- The repair order predates the inspection — If a lamp electrical repair was completed and signed off before the date of the citation, and the work order confirms vehicle-circuit power, challenge on the grounds that the defect did not exist at the time of inspection.
- Inspector code error — 393.23 is specifically about power source, not lamp operability. If the inspection narrative describes only a non-functioning lamp without identifying an auxiliary power source, the citation may have been entered under the wrong code and should be corrected to 393.9.
Do not challenge simply because the lamp was repaired after the inspection — that does not void the citation. With 5,781 all-time citations on this code, FMCSA reviewers are familiar with it; your challenge must be documentation-specific, not argument-based.
› How frequently should the fleet self-audit for 393.23 exposure, and what does the trend data say about timing?
Our database shows 61 citations in the last 12 months and 12 citations in the last 90 days under 393.23. The monthly breakdown reveals a clear spike pattern: December 2025 produced 11 citations, July 2025 produced 10, and August 2025 produced 7. Citations drop sharply in some months (September 2025: 2; April 2025: 1) and then surge again — a pattern consistent with enforcement campaign cycles rather than steady-state detection.
Recommended audit cadence:
- Monthly targeted inspection — Pull 10% of your fleet for a lamp power-source circuit test during PM. Given the December and July spikes, schedule heavier audits in November and June to get ahead of the surge windows.
- Post-repair mandatory check — Any time a lamp or electrical circuit is serviced, a power-source verification must be completed and logged before the unit dispatches.
- Quarterly fleet-wide DVIR review — Review DVIRs from the prior 90 days for any lamp-related defect entries and confirm each was closed with a documented circuit-level repair, not just a bulb swap.
With 12 citations in 90 days, enforcement is active enough that quarterly audits alone are insufficient for high-mileage or Texas-routed fleets.
Top Enforcing States
Where 393.23 is most commonly cited (last 180 days)
Often Cited Together
Other violations commonly found on the same inspection (last 90 days)
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.