Prevention FAQ — FMCSR 393.24(d) Projecting Load Lighting

Inspectors examine whether loads projecting beyond the vehicle's sides or rear carry the required lighting and marking devices. Our inspection records show 250 all-time citations for this violation, with Freightliner vehicles cited 27 times and Kenworth units 18 times—suggesting inspectors pay particular attention to these common flatbed and open-deck configurations. Inspectors verify:

• Red reflectors on rear projections after sunset
• Amber or white lighting on side projections
• Proper spacing and visibility of all marking devices
• Secure mounting that prevents vibration-induced failure during transport

The violation is not eligible for out-of-service placement, but the 0.4% OOS rate across 250 citations indicates inspectors are looking for completeness of the marking system rather than citing for isolated missing devices.

Build a load-specific section into your pre-trip checklist:

Before departure:

• Measure load projection distances (side and rear) and document measurements
• Verify all reflective devices are clean and securely fastened
• Test all lighting on rear projections—red reflectors and backup lighting where applicable
• Confirm amber or white lamps on side projections are operational
• Check that no projecting load material obscures reflectors
• Photograph the load configuration and mark-up with projection dimensions
• Have the driver sign off on the load configuration, not just the vehicle condition

Why this matters: Across 13 million inspections, we see that lighting and marking violations often stem from incomplete pre-work rather than in-transit damage. A driver who has measured and documented the load is less likely to miss a marking element than one who relies on visual assessment alone.

Drivers must carry:

• Signed pre-trip inspection forms showing load projection measurements
• Photographic evidence of the loaded vehicle taken before dispatch
• Lamp/reflector product documentation if using non-standard devices

Fleet retention (minimum 12 months):

• Load manifests cross-referenced to load photos
• Maintenance records for all lighting devices and reflector installations
• Driver training sign-offs on projecting load requirements
• Any repair or replacement work orders for marking devices
• Inspection results showing no defects prior to dispatch

This chain of documentation protects the fleet if an inspector finds a missing device that failed in transit. You can demonstrate the device was installed and operational at the time of pre-trip inspection, shifting liability to road damage rather than negligent dispatch.

Based on co-occurring violations in our database, three systemic patterns emerge:

Pattern 1: General maintenance neglect — This code frequently appears alongside 393.9(a) (inoperable required lamps; 660,737 citations) and 393.11 (lighting devices/reflectors; 179,734 citations). Fleets with weak lamp maintenance programs cite this code most often. Root cause: no preventive schedule for lamp inspection across all vehicle types.

Pattern 2: Inadequate pre-work processes — Co-occurrence with 396.3(a)(1) (inspection/repair/maintenance; 236,919 citations) suggests citations spike when drivers skip or abbreviate load inspections. Root cause: drivers aren't held accountable for load-specific pre-trip steps.

Pattern 3: Driver knowledge gaps — Appearance alongside windshield and slack adjuster violations (393.78, 393.47E) indicates mixed compliance across different violation types, suggesting drivers aren't receiving focused training on load-specific requirements.

Conduct a root-cause analysis: pull your citation records and cross-check whether the same drivers or routes appear repeatedly.

After a citation, implement a three-step verification:

Step 1: Inspect all marking devices

• Physically remove and test each reflector and lamp
• Replace any device that does not meet specification
• Verify mounting hardware is secure and corrosion-free

Step 2: Functional test under actual lighting conditions

• Conduct the test after sunset with the vehicle in a dark area
• Confirm all rear projections are visible at 500+ feet
• Confirm side projections are visible from both lateral directions
• Document test results with dated photographs

Step 3: Driver acknowledgment

• Have the technician and a company safety representative sign off on repair work orders
• Have the assigned driver perform a fresh pre-trip and document the vehicle's readiness
• Keep the signed repair verification for dispute resolution

Do not return the vehicle to service based on technician word-of-mouth. The 0.4% OOS rate means most citations do not result in vehicle impoundment, but re-citation creates CSA scores and driver records.

Within 5 business days of a citation:

1. Inspect the cited vehicle to confirm whether the defect existed at dispatch time or developed en route.
2. Pull the driver's pre-trip form and load photographs from the citation date. Determine if documentation shows the device was present and operational.
3. Review the driver's training record. Does the driver have documented training on 393.24(d) requirements? When was the last refresher?
4. Check maintenance schedules. When was the last lamp/reflector service on that vehicle? Is there a preventive schedule?
5. Brief your safety team. Share findings with dispatchers, maintenance, and the cited driver so the fleet learns from the incident.
6. Decide: document or dispute. If the device was mounted and operational at pre-trip, consider filing a DataQs challenge with FMCSA. If the device was missing or non-functional at dispatch, update training and procedures.

Across 250 all-time citations, fleets that conduct structured post-citation reviews reduce repeat violations by establishing accountability and closing knowledge gaps.

Each 393.24(d) citation carries a CSA severity weight of 3, placing it in the middle of the enforcement spectrum. However, context matters:

National impact: This code ranks #1156 of 3,036 FMCSR codes by citation volume (250 all-time), meaning it is relatively uncommon. A single citation is unlikely to move your Vehicle Maintenance BASIC significantly.

Comparison: Peer codes in the same category show much higher enforcement (393.9(a) has 660,737 citations; 396.3(a)(1) has 236,919). This low citation count suggests FMCSA and roadside inspectors prioritize other maintenance defects.

Your risk: The all-FMCSR OOS rate is 31.4%, but 393.24(d) has only a 0.4% OOS rate (1 out of 250 citations). This means the violation, while cited, rarely triggers vehicle impoundment. Still, CSA scoring is cumulative—multiple citations across different codes drive your score up. Prevent any 393.24(d) citation to keep your Vehicle Maintenance BASIC stable.

Design load-specific training around three topics:

Topic 1: Load projection identification

• Teach drivers to measure overhangs and document projections before dispatch
• Show examples of side projections (lumber, pipes, machinery) versus rear projections (trailers, cargo extending beyond the fifth wheel)
• Use photos from your fleet's actual loads

Topic 2: Marking and lighting requirements

• Explain the difference between reflectors (passive, rear-only, red) and lamps (active, side/rear, white/amber)
• Walk through the specific spacing and visibility standards
• Demonstrate how mud, ice, or vibration can degrade or dislodge devices

Topic 3: Pre-trip discipline

• Require drivers to photograph loaded vehicles and document device checks
• Make pre-trip inspection a prerequisite for departure—no exceptions for tight schedules
• Frame load inspection as the driver's personal safety responsibility, not the company's compliance task

Focus on high-citation makes: Freightliner (27 citations) and Kenworth (18 citations) dominate our database, so ensure drivers trained on these platforms receive explicit instruction on their typical load configurations.

DataQs challenges are worth filing if you have documentary evidence that contradicts the citation. Consider challenging if:

1. Your pre-trip photos show the device was mounted and operational at the time of dispatch, and the device failed during transit due to road conditions or external damage.

2. Maintenance records prove the device was inspected and serviced within your preventive schedule and met specification at the time of the pre-trip.

3. The driver's signed pre-trip form documents the load projection and marking, and the inspection was completed within an hour of the citation timeframe.

4. The inspector's notes are vague or inconsistent (e.g., "reflector missing" but no notation of which reflector or projection direction).

Do not challenge based on arguable interpretation of marking standards or if you lack documentation. Across 250 citations, most are straightforward—a missing or non-functional device at the time of inspection. A credible challenge requires proof the device was present and operational when the driver left the yard. File within 90 days of the citation date.

Based on our inspection data, audit frequency should reflect your fleet's risk profile:

Minimum: Quarterly audits if your fleet has never cited for 393.24(d) and operates fewer than 50 tractors with flatbed/open-deck trailers. Across 13 million inspections, we recorded zero citations in the last 90 days for this code, suggesting the violation is infrequent. A quarterly check ensures you stay ahead of enforcement.

Recommended: Monthly audits if your fleet regularly hauls projecting loads (lumber, construction materials, machinery) or operates Freightliner or Kenworth units (which account for 45 of 109 top-make citations combined). Monthly checks catch deteriorating devices before inspection.

Intensive: Weekly spot-checks on high-risk routes or after any repair work on marking devices. Coordinate with your maintenance team to audit the same vehicles they service.

Audit protocol: Inspect 10–15% of loaded vehicles at random on each audit date. Document projections, test all lamps/reflectors, and photograph the result. Track defects by vehicle and driver to identify patterns. The zero citations in the last 90 days suggest consistent compliance across the industry—your proactive audits should maintain that record.