Prevention FAQ — FMCSR 393.17: Lamps and Reflectors
Fleet safety guidance on lamp and reflector inspections, pre-trip protocols, documentation, root-cause analysis, and audit cadence based on 258 all-time citations and 87.2% OOS enforcement rate.
- Code:
- 393.17
- Code System:
- FMCSR
- BASIC Category:
- Vehicle Maintenance
- OOS Eligible:
- Yes
- Severity Weight:
- 6
- Violation Group:
- Lighting
Ranks #1,155 of 3,146 FMCSR codes by citation frequency • OOS rate of 86.9% is above the FMCSR-wide average of 33.3%.
Violation Description
No/defective lamp/reflector-towaway operation
Prevention FAQ for Fleet Managers
Pre-trip discipline, inspector focus, and root-cause fixes
› What specific lamp and reflector defects do roadside inspectors focus on for 393.17?
Across our inspection records, 393.17 citations represent low-volume but high-consequence enforcement: 87.2% of the 258 all-time citations resulted in out-of-service placement, compared to the all-FMCSR average of 31.4%. Inspectors examine headlamp aim and function, marker lights on all four corners, reflectors on rear axles and trailers, and clearance lights. Recent data shows enforcement concentrated in North Carolina (1 citation, 100% OOS rate in the last 180 days) and Texas (1 citation, 0% OOS rate), indicating state-specific inspection priorities. The severity weight of 3 means this code contributes meaningfully to your CSA Vehicle Maintenance BASIC score. Focus your team on lights that are burned out, cracked lenses, missing reflectors, or misaligned headlamps—these are the defects that trigger immediate removal from service.
› What should our pre-trip checklist specifically include for lamps and reflectors?
Your checklist must cover: (1) Headlamps—both low and high beam function, aim, and lens clarity; (2) Marker lights—all perimeter identification and clearance lights, both front amber and rear red; (3) Reflectors—rear axle reflectors, trailer reflectors, and side-striping reflectors; (4) Brake lights and turn signals—function from behind the vehicle; (5) License plate illumination; (6) Spare bulb inventory—drivers should carry spares for all replaceable lamp types. Have drivers test lights in darkness or low-light conditions to catch dim or failing bulbs before they fail completely. Document the checklist completion with date, driver name, and odometer reading. Any defect found during pre-trip must be tagged for repair before dispatch—do not defer lamp repairs to the next maintenance window.
› What lamp and reflector documentation must drivers carry and what must the fleet retain?
Drivers must carry proof that all required lamps and reflectors are installed and functional—this is implicit in FMCSR 393.17 compliance. Fleets should retain: (1) Pre-trip inspection records showing lamp checks completed before each trip; (2) Work orders for any lamp repairs or bulb replacements, including date, technician, part replaced, and vehicle mileage; (3) Inspection reports from third-party DOT inspections (roadside or terminal); (4) Bulk spare-parts invoices tracking when lamp stock is replenished. Because the all-time OOS rate for 393.17 is 87.2%, a single citation often results in vehicle impoundment—documentation of prior compliance strengthens a DataQs challenge if the citation is disputed. Maintain records for at least two years to demonstrate continuous compliance patterns.
› What root-cause patterns does your data reveal for lamp and reflector failures?
Our inspection records show only one co-occurring violation in the last 90 days: 393.71H10 (fifth wheel defective). While this is a single-case snapshot, it suggests that lamp failures may cluster in fleets with broader deferred-maintenance cultures. More broadly, peer codes in the Vehicle Maintenance category show that 393.9(a) (inoperable required lamps) has generated 660,737 citations with a 15.4% OOS rate—indicating that lamp defects are systemic across the industry but 393.17 (inadequate lamps or reflectors) is cited less often but more severely. This pattern suggests that when inspectors cite 393.17 specifically, they are detecting structural or chronic defects (missing reflectors, extensive corrosion, bent housings) rather than isolated burned-out bulbs. Root-cause analysis should focus on environmental exposure (corrosion from salt or moisture), lack of preventive bulb replacement, and physical damage from debris or collision.
› How should the fleet verify lamp and reflector repairs before returning a vehicle to service?
After any lamp or reflector repair, implement a three-step verification: (1) Daytime visual inspection—check that lenses are clear, bulbs are seated fully, housings are intact, and all reflectors are affixed without cracks; (2) Nighttime functional test—dim all lights with the engine off, then turn on headlamps (low and high), marker lights, brake lights, turn signals, and clearance lights from a distance of 20+ feet to confirm brightness and alignment; (3) Technician sign-off—the repair technician must document which lamps were replaced, the part number, the mileage, and the date. Do not return the vehicle to service until the driver performs a fresh pre-trip inspection and signs off on the completed repair. For fleets with high turnover or multiple technicians, photograph the vehicle under nighttime lighting conditions post-repair and store images in your maintenance management system for evidence of compliance.
› What should our post-citation review process include?
After any 393.17 citation, conduct a structured post-event review: (1) Determine whether the citation was accurate—review the inspector's notes, photograph the vehicle, and identify the exact defect cited; (2) Trace maintenance history—pull all work orders, pre-trip inspections, and inspection records for the cited vehicle in the 90 days prior; (3) Assess driver knowledge—interview the driver about their lamp-check procedure and whether they reported the defect before roadside inspection; (4) Review fleet-wide patterns—cross-reference the cited vehicle's make/model against your maintenance schedule (our data shows FORD with 23 citations and INTL with 20 citations, suggesting these makes may have lamp-housing wear patterns); (5) Identify systemic gaps—check whether spare-parts inventory includes lamps, whether technicians are trained on lamp installation and testing, and whether the maintenance schedule includes proactive bulb replacement at recommended intervals; (6) Issue a corrective action plan and communicate outcomes to all drivers and maintenance staff.
› How does a 393.17 citation affect our CSA Vehicle Maintenance BASIC score?
FMCSR 393.17 carries a CSA severity weight of 3, placing it in the mid-range for vehicle maintenance defects. While the code ranks #1137 of 3,036 FMCSR codes by all-time citation volume (258 total), its 87.2% out-of-service rate is dramatically higher than the all-FMCSR average of 31.4%. This means a single 393.17 citation is treated as a serious vehicle defect and will increase your Vehicle Maintenance BASIC score substantially. For fleets with fewer than 12 months of roadside inspection history, even one citation can trigger heightened scrutiny. The CSA algorithm weights recent violations more heavily—the 7 citations in the last 12 months show sustained, low-level enforcement risk. To avoid CSA escalation, prevent citations through proactive pre-trip audits and maintenance scheduling rather than reactive roadside repair.
› What specific driver training topics should we address?
Your driver training program should include: (1) Lamp anatomy—teach drivers to identify the functional purpose of each lamp and reflector (headlamps for visibility, marker lights for identification, reflectors for passive night visibility); (2) Pre-trip inspection technique—demonstrate how to test lamps with the ignition on, engine off, and doors open, and how to walk around the vehicle in darkness or twilight to verify all lights are functioning; (3) Immediate reporting—drivers must report any burned-out bulb, cracked lens, or missing reflector to dispatch or the maintenance team before the next trip, not after a roadside inspection; (4) Vehicle-make-specific details—our data shows FORD (23 citations) and INTL (20 citations) vehicles account for a large share of 393.17 citations, so include orientation on these chassis' lamp locations, bulb types, and common failure modes. Conduct refresher training annually or after any citation, and make driver feedback on lamp defects a key performance indicator in your safety metrics.
› When should we consider filing a DataQs challenge on a 393.17 citation?
File a DataQs challenge if: (1) The citation is factually incorrect—e.g., the inspector cited a lamp as inoperable when it was functioning at the time of inspection, or cited a reflector as missing when it was present; (2) The defect was pre-existing and documented in prior inspections—use your maintenance records and pre-trip logs to show that the lamp was functioning earlier in the day or week; (3) The vehicle was under active repair at the time of inspection—if a lamp was removed for servicing and the vehicle should not have been in operation, provide the work order as evidence; (4) The citation conflicts with a prior DOT inspection clearance—if another inspectorate cleared the same vehicle for the same defect within a recent timeframe, note the discrepancy. Document everything photographically (daytime and nighttime images of the vehicle), retain all maintenance records, and file the challenge within 60 days of citation. The low citation volume (7 in the last 12 months) means each citation carries weight; a successful challenge improves your CSA standing and reduces enforcement risk.
› How often should we conduct self-audits for lamp and reflector compliance?
Conduct self-audits quarterly (every 90 days) at minimum. Our inspection records show 1 citation in the last 90 days and 7 citations in the last 12 months, indicating sustained but low-frequency enforcement. This pattern suggests that citations are episodic and concentrated in specific fleets or vehicle types—so a quarterly audit cadence allows you to detect and correct defects before roadside inspection occurs. Each audit should include: (1) Nighttime functional testing of a random sample of 10–20% of your fleet; (2) Visual inspection of 100% of vehicles scheduled for imminent dispatch; (3) Documentation review—verify pre-trip logs are complete and repairs are logged; (4) Inventory check—confirm spare bulbs and reflector stock are available and technicians know part numbers for your vehicle makes. After any roadside citation, increase audit frequency to monthly for 90 days to validate the corrective action. Track audit results in a spreadsheet and trend defect rates over time to identify chronic problem vehicles or technician training gaps.
Top Enforcing States
Where 393.17 is most commonly cited (last 180 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.