Prevention FAQ — FMCSR 393.11TL: Lighting Devices/Reflectors

Inspectors cite 393.11TL when a CMV has inadequate or missing lighting devices or reflectors — not just lamps that won't illuminate (that's 393.9), but physically absent, broken, obscured, or improperly mounted hardware. Our inspection records show 393.11TL is ranked #120 of 3,036 FMCSR codes by citation volume, signaling it is a high-frequency target. Texas dominates enforcement with 6,622 citations in the last 180 days alone, meaning Texas-routed fleets face the heaviest exposure. Inspectors will walk the full perimeter of the tractor and trailer looking for:

• Missing or cracked reflector tape on trailer sides and rear
• Absent or broken clearance/marker lamp lenses
• Reflectors that are faded, painted over, or obscured by mud
• Any required lamp position that has no hardware present at all

Because Texas accounts for the vast majority of recent citations, pre-dispatch checks for vehicles entering or running Texas lanes must be especially thorough.

Build these steps into the lighting section of your pre-trip DVIR form:

1. Reflectors: Confirm all required side and rear reflectors are physically present, clean, uncracked, and unobscured.
2. Marker and clearance lamps: Verify every lens is intact — not just that the bulb lights, but that the housing and lens are undamaged.
3. Trailer rear: Check that the reflector cluster and any conspicuity tape required by your trailer configuration are fully intact.
4. Mud/road grime: A thick mud coat over reflectors is still a citation. Require a wipe-down before sign-off in dirty road conditions.
5. Coupling area: Pay special attention near landing gear and the kingpin area where lamps and reflectors take the most physical abuse.
6. Tractor cab corners: Inspect cab marker lamps for cracked or missing lenses, particularly on Freightliner (FRHT) units — our database shows FRHT vehicles account for 7,344 all-time citations under this code, more than any other make.

Document each step with a checklist signature, not just a generic "lights OK" note.

Documentation serves two purposes: it satisfies the periodic inspection requirement and gives you DataQs evidence if you need to challenge a citation.

Retain these records:

• Signed DVIRs showing the lighting/reflector check was completed — drivers must note any defect and mechanics must note the repair and return-to-service signature.
• Periodic inspection reports that cover lighting and reflector items. Our data shows 393.11TL co-occurs with 396.17C (No proof of periodic inspection) in 562 shared inspections in the last 90 days — meaning inspectors who find a lighting defect are actively cross-checking for the inspection document too. A missing periodic inspection record will double your citation exposure.
• Repair orders from any lamp or reflector replacement, including part numbers and technician sign-off.
• Photos taken during pre-trip or post-repair confirmation, timestamped and linked to the vehicle unit number.

Retain all records for a minimum of 12 months and make them accessible to safety personnel for CSA review.

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

1. Lamp failures go undetected until inspection — 393.11TL shares 1,441 inspections with 393.9 (Inoperable Required Lamp). When both codes appear together, it signals that pre-trip checks are not catching lighting defects before the vehicle hits the road. The root cause is usually an inadequate DVIR process, not hardware failure alone.

2. Deferred maintenance culture — Co-occurrence with 396.17C (No proof of periodic inspection) in 562 inspections indicates vehicles are running past their scheduled maintenance windows. Lighting components don't get replaced because the vehicle never goes through a formal inspection cycle.

3. Broad vehicle neglect — Co-occurrence with 393.95A (Fire extinguisher missing/defective) in 559 inspections and 396.5B (Fuel system leak) in 476 inspections points to a pattern where lighting is just one symptom of a fleet not conducting systematic condition reviews. Lighting defects in these cases are trailing indicators of a broader maintenance gap, not isolated events.

Because 393.11TL is not OOS-eligible — our records show only 2 out-of-service placements across 23,327 all-time citations — drivers can continue operating after receiving the citation. That creates a real risk of vehicles returning to service with the defect still unresolved.

Establish a mandatory repair verification workflow:

1. Citation triggers a mandatory shop visit within 24 hours, regardless of OOS status.
2. Technician documents the specific lamp or reflector replaced, including part number, position, and photo of the completed repair.
3. Second-person sign-off: A shop supervisor or safety coordinator — not the driver — must confirm the repair before the vehicle is re-dispatched.
4. Linked record: The repair order must reference the citation number and inspection report date so the documents are traceable.
5. Post-repair DVIR: The driver on the next dispatch must complete a full lighting check and sign the DVIR confirming the cited defect area is clear.

This chain of documentation is also your evidence base if you subsequently file a DataQs challenge.

A citation is a data point — use it to find the failure in your process, not just the failure on the vehicle.

Within 48 hours:

• Pull the full inspection report and identify every co-occurring violation. Our data shows 393.11TL frequently appears alongside codes like 393.78 (Windshield condition defective) in 766 shared inspections in the last 90 days — if your citation also includes 393.78, you have a pattern of crews not completing full exterior/glass checks.
• Review the last three DVIRs on that unit. Was the defect previously noted and not repaired? Or was it not noted at all?
• Check the vehicle's periodic inspection date against the maintenance schedule.

Within 7 days:

• Brief the driver and the technician who last serviced the unit.
• If the same vehicle has multiple 393.11TL citations, flag it for a root-cause audit.
• Update your pre-trip checklist or training materials if the review reveals a systemic gap.

Document the post-event review in your safety management system — this demonstrates good faith to enforcement agencies.

393.11TL carries a CSA severity weight of 3, which is on the lower end of the Vehicle Maintenance BASIC scale — but volume matters. Our inspection records show 393.11TL generated 14,955 citations in the last 12 months, and enforcement is concentrated: the top cited carriers include operations that have accumulated 35 citations (BUOYANT ENERGY LLC) down to 24 citations (GONCO LOGISTICS LLC and STATEWIDE TRUCKING CORP) all-time under this single code.

For a carrier receiving multiple 393.11TL citations within a rolling 24-month window, the cumulative severity score builds quickly even at weight 3. More importantly, the peer codes in this category carry much higher OOS rates — for example, 396.3(a)(1) carries a 45.3% OOS rate with 236,919 citations. When 393.11TL appears alongside those codes in the same inspections (as the co-occurrence data shows it often does), the BASIC impact multiplies across codes, not just within one.

Fleets should treat repeated 393.11TL citations as a leading indicator that higher-weight codes are also accumulating.

The vehicle make data points to where training should focus. Our database shows FRHT (Freightliner) vehicles account for 7,344 citations, Kenworth (KW) for 3,775, and Peterbilt (PTRB) for 3,766 under 393.11TL all-time — together those three makes represent the majority of citations. If your fleet runs any of these, model-specific training is warranted.

Core training modules to build:

1. Lamp and reflector identification by vehicle type: Show drivers, using their actual assigned vehicles, where every required reflector and clearance lamp is located. Many drivers can identify a burned lamp but cannot locate a missing reflector bracket.
2. "Present and intact" vs. "lit": Train drivers that 393.11TL is about physical presence and condition, not just function — a cracked or mud-covered reflector is still a defect.
3. Post-coupling trailer checks: Emphasize that trailer rear and side reflectors must be checked after coupling, not just on the tractor.
4. DVIR specificity: Train drivers to note the exact location of any defect (e.g., "driver-side rear marker lamp lens cracked") rather than generic entries.

Reinforce training after any citation event.

A DataQs challenge is warranted when the citation record contains a verifiable error — not simply because the violation was inconvenient. For 393.11TL, legitimate challenge grounds include:

• The cited defect was repaired before the inspection: If your repair order and timestamped photo show the lamp or reflector was replaced prior to the inspection date, the citation may be inaccurate.
• Wrong vehicle or unit number: If the citation references a vehicle that was not at the inspection location, document the discrepancy with GPS/ELD records.
• The cited component is not required by regulation for that vehicle configuration: If your trailer type is genuinely exempt from a specific reflector position, document the applicable configuration.

Do not challenge a citation simply because the vehicle was not placed out of service — the near-zero OOS rate (only 2 OOS placements in 23,327 citations) is normal for this code and does not indicate the citation was incorrect.

Support every challenge with the repair order, timestamped photos, the DVIR from the same or prior day, and the periodic inspection report. Unsupported challenges waste compliance resources and are rarely successful.

The volume trend in our data justifies a monthly self-audit cadence at minimum. In the last 12 months, 393.11TL generated 14,955 citations nationwide, averaging over 1,200 per month — with peaks of 1,487 in February 2026 and 1,434 in October 2025. The last 90 days alone account for 3,295 citations. This is not a periodic spike — it is a persistent, high-volume enforcement target.

Recommended self-audit structure:

• Monthly: Random sample of 10–15% of active units; technician walks each vehicle using the same criteria as a roadside inspector (physical presence, condition, and cleanliness of every lamp and reflector position).
• Quarterly: Full-fleet lighting audit tied to the periodic inspection cycle. Cross-reference with DVIR defect logs to identify units with repeated entries for the same positions.
• Event-triggered: Any 393.11TL citation triggers an immediate audit of all vehicles in the same operational lane or region — Texas in particular, given that state's 6,622 citations in the last 180 days.

Document audit results and corrective actions in a format you can produce during a compliance review.