Prevention FAQ — FMCSR 393.87: Warning Flags on Projecting Loads
Fleet safety guidance on load-flag compliance. Pre-trip checklists, inspector focus areas, documentation practices, and root-cause analysis for preventing 393.87 citations.
- Code:
- 393.87
- Code System:
- FMCSR
- BASIC Category:
- Vehicle Maintenance
- OOS Eligible:
- No
- Severity Weight:
- 3
- Violation Group:
- BASIC 5
Ranks #3,037 of 3,146 FMCSR codes by citation frequency.
Violation Description
Failure to properly flag loads that project beyond the rear or sides of the vehicle.
Prevention FAQ for Fleet Managers
Pre-trip discipline, inspector focus, and root-cause fixes
› What exactly do roadside inspectors look for when checking for missing or improper warning flags?
Inspectors visually verify that any load projecting beyond the rear or sides of the vehicle carries the required warning flags. They examine flag condition, placement, visibility, and reflectivity—especially in low-light conditions. Our inspection records show this violation exists within the Vehicle Maintenance category alongside high-enforcement codes like 393.9 (inoperable lamps, 660,737 citations) and 393.11 (lighting/reflectors, 179,734 citations). The proximity of these codes suggests inspectors often conduct holistic visibility audits during roadside stops. Focus inspector attention on loads carried on flatbeds, drop decks, and open trailers where projections are most common. Ensure flags are not obscured by cargo, damaged, or faded. Inspectors may also note if flag placement is haphazard or non-compliant with spacing requirements.
› What should our pre-trip checklist include to prevent 393.87 violations?
Add a dedicated load-projection section to your DVIR template:
- Measure & mark projections: Record load length vs. trailer length; flag any overhang exceeding legal limits before departure.
- Flag inventory: Verify each driver has spare flags aboard and knows replacement locations.
- Flag condition: Check all flags for tears, fading, reflectivity loss, and secure attachment.
- Placement verification: Confirm flags are mounted at the furthest projection point(s), not clustered near the cab.
- Night visibility: In evening shifts, test flag reflectivity with flashlight.
- Cargo shift risk: Document loads prone to movement and recheck flag security post-departure if applicable.
Make this a line-item sign-off, not a checkbox. Pair this with your existing lamp/lighting checks (393.9, 393.11) since inspectors audit visibility comprehensively.
› What documentation must drivers carry and what should the fleet retain?
Driver documentation onboard:
- Load ticket or BOL showing overall dimensions and trailer type
- Flag inspection log (date, time, flag count verified)
- Photo evidence of proper flag placement taken before departure (optional but recommended for high-value loads)
Fleet retention (minimum 12 months):
- Signed pre-trip DVIRs noting load projections and flag status
- Monthly flag inventory audits (quantity, condition, replacement dates)
- Training records showing driver certification in flag placement per FMCSR 393.87 requirements
- Any roadside inspection reports or warnings (even non-citations) to track enforcement patterns
- Maintenance logs for flag storage and replacement schedules
Documentation serves dual purposes: prevents citation disputes via DataQs challenges and provides evidence of a deliberate safety culture if the fleet faces a compliance review.
› What root causes typically underlie 393.87 violations in a fleet?
Our data shows 393.87 co-occurs with vehicle maintenance and lighting codes. The most relevant peers are inoperable lamps (393.9, 660,737 citations, 15.4% OOS rate) and lighting/reflectors (393.11, 179,734 citations, 1.8% OOS rate).
Pattern 1 – Visibility failure ecosystem: Inspectors citing missing flags often find concurrent lighting defects. This suggests root cause is systemic visibility oversight: drivers or maintenance teams aren't conducting full pre-trip visibility audits.
Pattern 2 – Load preparation gaps: Flagging failures often accompany general inspection/maintenance backlogs (396.3(a)(1), 236,919 citations). This indicates load planning and securement aren't integrated with vehicle readiness checks.
Pattern 3 – Driver knowledge: Repeated flags-on-projecting-loads violations within a fleet suggest inconsistent training on load measurement and flag placement standards.
Root-cause interview questions: Are flagging instructions included in new-hire safety training? Do drivers understand legal overhang limits by trailer type? Is there accountability for failed pre-trip flag checks?
› How should we verify that a flagging issue has been corrected before the vehicle returns to service?
Implement a three-step verification:
-
Visual inspection by maintenance or safety staff (not the driver who failed the original check): Physically walk the load, measure projections, confirm flag presence and reflectivity. Use a checklist with sign-off.
-
Photographic documentation: Take dated photos showing:
- Load overhang with measuring tape if needed
- Each flag in place with visible reflective material
- Full side and rear views of the vehicle
-
Supervised re-check by second driver or supervisor: The driver responsible for the violation should re-perform the pre-trip check under observation, signing off that flags are verified.
Record all three steps in the vehicle's maintenance file and DVIR history. This prevents recurrence and demonstrates remedial intent if a follow-up citation occurs. Tie this process into your broader vehicle-readiness workflow alongside lamp checks (393.9) and reflector audits (393.11).
› What should our post-citation review process look like?
If a driver receives a 393.87 citation:
-
Immediate debrief: Interview the driver about load characteristics, load planning process, and whether they checked flags pre-trip. Ask why the flag was missing or improper.
-
Inspect the vehicle and load: Physically verify the current state. Measure projections and check all flags.
-
Review load-planning records: Did dispatch communicate load dimensions to the driver? Was the correct trailer assigned? Were overweight or oversized permits issued?
-
Audit driver training records: Confirm the driver received instruction on FMCSR 393.87 flagging requirements and knows your fleet's load-measurement process.
-
Analyze fleet patterns: Check if this driver has prior flagging warnings. Check if certain shipper accounts, routes, or load types correlate with violations.
-
Document root cause: Categorize as training gap, equipment issue (missing/defective flags), process failure (load planning), or driver performance.
-
Assign remedial action: Retrain, procure flags, revise load planning, or implement additional pre-trip supervision.
File the full review in the driver's safety record and share findings with dispatch and maintenance.
› How does a 393.87 citation impact our CSA Vehicle Maintenance BASIC score?
FMCSR 393.87 carries a CSA severity weight of 3, placing it in the moderate range within the Vehicle Maintenance BASIC category. While the all-time citation count across our 13 million inspection records is zero, this does not mean the code is low-risk; it indicates the violation is either rare, correctly labeled, or inconsistently cited.
For context, peer codes in the same category show high enforcement intensity: 393.9 (inoperable lamps) has 660,737 citations and 393.11 (lighting/reflectors) has 179,734 citations. Any citation on 393.87 would contribute to the Vehicle Maintenance BASIC and could influence your CSA percentile ranking during safety audits or carrier evaluation processes.
A single citation's impact depends on your fleet's total safety record, inspection frequency, and peer comparison. More importantly, flagging failures signal broader visibility-readiness gaps that often co-occur with lighting violations, which carry much higher enforcement volume. Prevent 393.87 citations to reduce overall Vehicle Maintenance BASIC exposure.
› What driver training topics should we emphasize to close gaps?
Develop training covering:
-
Load overhang measurement: Teach drivers how to measure trailer length, load length, and calculate legal projections. Include trailer-type variations (53-ft, 48-ft, doubles, specialized).
-
Flag placement standards: Show photos of correct placement (furthest projection point, secure attachment, reflective side visible). Clarify spacing and quantity requirements.
-
Flag condition assessment: Train drivers to inspect flags for tears, fading, and reflectivity loss. Include when to report or replace flags.
-
Load planning coordination: Explain how drivers communicate with dispatch when loads exceed standard dimensions and when flagging is necessary vs. permitting required.
-
Pre-trip discipline: Integrate flag checks into the broader Vehicle Maintenance pre-trip routine, pairing with lamp and reflector checks (393.9, 393.11).
-
Night visibility: Address unique challenges of flagging visibility in darkness and low-light conditions.
Deliver training annually and on hire. Use case studies of 393.87 citations (anonymized) to illustrate real consequences. Test comprehension with scenario-based questions (e.g., "Is this load 4 feet over the trailer? What flags are needed?").
› When should we consider a DataQs challenge if cited for 393.87?
File a DataQs challenge if any of the following apply:
-
Inspection error: The inspector misidentified the load dimensions or flag placement. Evidence: your photos, load ticket, or eyewitness accounts showing flags were properly installed.
-
Documentation discrepancy: Your records (BOL, pre-trip DVIR, photos) clearly show flags were in place and properly positioned at the time of the roadside stop. The citation may reflect a timing or measurement error.
-
Ambiguous regulation interpretation: The inspector cited the violation based on a non-standard interpretation of flag placement or spacing that your fleet can refute with regulatory guidance.
-
Equipment failure after departure: If the flag was dislodged during transit (evidenced by driver statement, photos from a rest stop, or witness account), the violation occurred post-departure and doesn't reflect pre-trip negligence.
For 393.87, DataQs success depends on photographic or eyewitness evidence. Retain all pre-trip photos and inspector contact information. Challenges are most credible when your fleet demonstrates a documented training and verification program (as outlined above). Do not challenge frivolously; use DataQs for genuine factual disputes.
› How often should we self-audit for 393.87 compliance across the fleet?
Our inspection records show zero citations for 393.87 in the last 90 days and zero in the last 12 months, suggesting this violation is either rarely encountered or well-managed across the industry. However, this does not justify low audit frequency; instead, it underscores that prevention is working fleet-wide.
Recommended cadence:
- Monthly: Spot-audit 10% of vehicles during routine maintenance. Verify flag inventory, condition, and placement on any vehicle with active loads. Document findings.
- Quarterly: Full-fleet inventory audit. Count flags, replace worn units, confirm secure storage accessible to all drivers.
- Annually: Comprehensive compliance audit paired with Vehicle Maintenance BASIC review. Audit 100% of fleets carrying projecting loads; interview dispatch, drivers, and maintenance on load-planning and flag-readiness processes.
- Post-citation: If a violation occurs, increase monthly audits to 25% for 6 months; require pre-departure photographic proof from affected drivers.
Tie audits to your existing Vehicle Maintenance schedule (393.9, 393.11 checks). This prevents flagging from becoming an isolated task and normalizes comprehensive visibility-readiness as a continuous practice.
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.