Prevention FAQ — FMCSR 393.87B: Load Projection Flagging

Fleet safety guidance on preventing warning flag violations. Covers inspector focus, pre-trip checks, root causes from co-occurring violations, and audit frequency based on 13 million inspection records.

Severity Weight
1
OOS Eligible
No
BASIC Category
Vehicle Maintenance
Code System
FMCSR
Code:
393.87B
Code System:
FMCSR
BASIC Category:
Vehicle Maintenance
OOS Eligible:
No
Severity Weight:
1
Violation Group:
Warning Flags

Ranks #1,384 of 3,146 FMCSR codes by citation frequency • OOS rate of 2.4% is below the FMCSR-wide average of 33.3%.

Violation Description

Improper warning flag placement

Prevention FAQ for Fleet Managers

Pre-trip discipline, inspector focus, and root-cause fixes

What exactly do inspectors look for when they cite 393.87B?

Inspectors verify that loads projecting beyond the rear or sides of the vehicle are marked with warning flags—typically red and white or reflective material visible in daylight and darkness. Our inspection records show Texas accounts for 28 citations in the last 180 days, with a 10.7% out-of-service rate, suggesting inspectors there focus heavily on visibility and retroreflectivity. Look for citations when:

  • Projection distance exceeds 4 feet beyond the rear without flags
  • Side projections lack retroreflective material
  • Flags are present but damaged, faded, or improperly secured
  • Night-time inspections find flags that don't meet nighttime visibility standards

Inspectors in high-citation states like Texas are more likely to stop and document load projection violations, so compliance intensity varies by region.

What should the pre-trip checklist include for load projections?

Add these steps to your driver pre-trip inspection form:

  1. Measure the load — Verify actual projection distance from rear and sides using a tape measure or mark on the vehicle.
  2. Flag presence & condition — Confirm warning flags are present for any projection over 4 feet; inspect for tears, fading, or looseness.
  3. Visibility test — Walk around the vehicle in low light to confirm flags are visible from at least 500 feet.
  4. Retroreflectivity check — Use a flashlight to verify flags reflect light in all directions; reflective tape should not be peeling or damaged.
  5. Attachment security — Tug flags to ensure they won't detach during transit.
  6. Documentation — Record load projection distance, flag count, and condition in the DVIR if any projection is present.

Make this checklist mandatory for any flatbed, drop-deck, or open-bed load. Driver signature requirement reduces liability and creates an audit trail.

What documentation should drivers carry and fleets retain?

Drivers must carry and be able to produce on demand:

  • Load ticket or bill of lading — Clearly indicating load dimensions (length, width, height) and noting any projection.
  • Pre-trip DVIR — Completed before departure, documenting load projection distance and flag installation.
  • Shipper/receiver photos — Optional but recommended: timestamped photos of the flagged load before departure.

Fleets should retain (typically 1 year, per FMC recordkeeping standards):

  • All DVIRs mentioning load projections
  • Incident reports or citations related to flagging
  • Training records showing driver completion of load projection training
  • Maintenance records documenting flag inventory, replacement dates, and inspection

This documentation protects the carrier in DataQs challenges and demonstrates due diligence if an OOS citation is issued. Across our 13 million records, carriers with robust DVIR practices show fewer repeat violations.

What root causes commonly lead to this violation—and what does the co-occurrence data reveal?

Our inspection data shows 393.87B frequently pairs with three systemic issues:

1. Driver fatigue (392.2RG, 4 co-occurrences in last 90 days) — Tired drivers are more likely to skip or rush pre-trip checks, including load flagging. Implement mandatory rest breaks and consider fatigue-risk management training.

2. Brake or coupling defects (393.55E, 3 co-occurrences; 393.45DLPC, 3 co-occurrences) — Vehicles with brake or coupling problems often carry overweight or unevenly distributed loads that project further than normal. Root cause: incomplete pre-load vehicle inspections. Require brake and coupling certification before accepting a load.

3. Inoperable lighting (393.9, 2 co-occurrences) — Vehicles with failed lamps are more likely to have missing or degraded warning flags. Suggests inadequate pre-departure inspections across multiple safety systems.

Prevention strategy: Implement a load-acceptance protocol requiring a fresh vehicle inspection (brakes, coupling, lights) before any load projection is permitted on the vehicle.

How should we verify repairs and flag replacement before returning a vehicle to service?

After a citation or flag replacement, require a formal repair verification checklist:

  1. Sourcing — Ensure replacement flags meet DOT retroreflectivity standards (VOSB sheeting or equivalent). Keep receipts and product datasheets.
  2. Installation — Verify flags are secured with corrosion-resistant fasteners or cable ties; test attachment strength manually.
  3. Measurement re-check — Re-measure load projection distance. If projection has changed, adjust flag placement accordingly.
  4. Nighttime visibility test — Conduct final inspection at dusk or under lowered lighting; verify flags are visible from 500+ feet.
  5. Driver sign-off — Have the driver complete a secondary DVIR confirming flag installation and testing.
  6. Maintenance record — Log the repair date, flag serial numbers (if tracked), technician name, and sign-off in the vehicle maintenance file.

Do not return the vehicle to revenue service until all steps are documented and signed. This creates a clear audit trail in case the same vehicle is cited again.

What should a fleet review after a 393.87B citation?

Conduct a post-citation review within 48 hours:

  1. Driver interview — Ask the driver when flags were last inspected, whether they checked load projection, and if they understood the flagging requirement. Document their response.
  2. Vehicle inspection — Inspect the specific vehicle cited. Check for flag inventory, condition, and attachment. Photograph the results.
  3. Load check — If the cited load is still on the vehicle, re-measure projection distance and compare to citation notes.
  4. Shipper/receiver communication — Contact the loading facility to understand how load dimensions were communicated to the driver and whether the driver was present during loading.
  5. Trend analysis — Check your records: Is this driver's first violation or a repeat? Is this vehicle a repeat? Is this shipper a repeat source?
  6. Root cause — Categorize: (a) Driver knowledge gap, (b) Flag inventory shortage, (c) Vehicle maintenance lapse, or (d) Shipper miscommunication.
  7. Corrective action — Assign targeted retraining, flag replacement, vehicle service, or shipper feedback based on root cause.

Document all findings in a fleet safety file. This practice reduces recurrence and demonstrates due diligence to insurers and regulators.

How does a 393.87B citation affect our CSA Vehicle Maintenance BASIC score?

Each 393.87B citation carries a CSA severity weight of 3, placing the code in the mid-range for impact. Nationally, across our inspection database, 393.87B ranks #1374 of 3,036 FMCSR codes by citation volume—a relatively low-frequency violation.

For comparison, peer codes in the Vehicle Maintenance category show much higher citation volumes: inoperable lamps (393.9) account for 180,097 citations with a 6.9% OOS rate, and general inspection/repair failures (396.3) have 236,919 citations with a 45.3% OOS rate.

Because 393.87B citations are infrequent (71 in the last 12 months across the nation) and rarely trigger OOS status (2.6% OOS rate), a single citation will have modest impact on your Vehicle Maintenance BASIC. However, a pattern of citations—especially if accompanied by co-occurring brake, coupling, or lighting violations—will accelerate BASIC deterioration. Prevention is more cost-effective than remediation: one citation can trigger a CSA audit, towing costs, and shipper delays, easily exceeding the cost of flag inventory management and driver training.

What training topics should drivers complete to prevent this violation?

Design driver training to cover:

  1. Load projection identification — Teach drivers how to measure or estimate projection distance (>4 feet triggers flagging requirement). Use yard demonstrations with actual flatbeds and mock loads.
  2. Flag types and standards — Show examples of compliant flags (red/white, retroreflective) and non-compliant flags (faded, torn, loose). Explain why retroreflectivity matters (nighttime visibility).
  3. Pre-trip inspection workflow — Walk through the checklist: measure load, count flags, check condition, test visibility. Make it a routine step before departure.
  4. Shipper/receiver coordination — Explain how to communicate load dimensions to dispatchers and how to refuse a load if projection cannot be safely flagged.
  5. Co-occurring risk patterns — Train drivers to recognize when fatigue, brake issues, or lighting defects increase the likelihood of a citation. Encourage drivers to report vehicle defects immediately.
  6. Citation consequences — Show actual examples from your fleet (anonymized) of citations, repair costs, and CSA impact.

Our data shows that drivers at the top-cited makes (Peterbilt, Kenworth, Freightliner) account for 65 of 117 all-time citations, suggesting training should be make-specific if your fleet operates these vehicles.

When should we consider filing a DataQs challenge on a 393.87B citation?

File a DataQs challenge if you can document:

  1. Factual measurement error — You have photos or measurement records proving the load projection was under 4 feet (or flags were present when the citation states they were absent).
  2. Missing inspection notes — The citation lacks detail about which specific projection (rear vs. side) lacked flags, or doesn't specify flag condition (torn vs. missing).
  3. Driver signed DVIR — You have a pre-trip DVIR signed by the driver confirming flags were installed and inspected; this creates a documented discrepancy with the inspector's finding.
  4. Vehicle maintenance record — You have service records showing flags were recently replaced or the vehicle was inspected within days of the citation, contradicting an OOS placement.
  5. Shipper documentation — Load dimensions from the shipper/bill of lading contradict the projection distance claimed in the citation.

DataQs challenges are most effective when you have photographic or written evidence created before or immediately after the citation. Generic disputes ("the driver says flags were there") rarely succeed. Given the low OOS rate (2.6%) for this code, most 393.87B citations are civil warnings; challenge only if you have strong evidence and the citation is on your safety record.

How often should we self-audit for 393.87B compliance?

Set your audit frequency based on violation trend data. Over the last 90 days, our records show 16 citations; over the last 12 months, 71 citations. This indicates a seasonal or operational pattern, not a consistent, low-level risk.

Recommended audit cadence:

  • Quarterly (every 3 months) — Full fleet audit of all flatbed, drop-deck, and open-bed vehicles. Check flag inventory, condition, and attachment. Cost: 1–2 hours per 10 vehicles.
  • After each citation — Immediate inspection of the cited vehicle and re-audit of any other loads from the same shipper or destination in the prior 30 days.
  • Seasonal pre-audit — Before peak loading seasons (Q2 and Q4, based on our 12-month trend showing May with 9 citations and July with 8 citations), conduct a 2-week sprint audit of all load-bearing equipment.
  • Post-hire driver audit — Within 30 days of a new driver's start date, observe their pre-trip load-projection inspection to confirm training retention.

Monthly tracking of projecting loads (count, measurement, flag status) will reveal trends early and allow intervention before an inspector citation occurs.

Last updated: 2026-04-20T15:23:46.063Z Guidance derived from TruckCodex inspection data Read the full article → Quick Q&A →

Top Enforcing States

Where 393.87B is most commonly cited (last 180 days)

1. Texas
18
OOS 11.1%
2. Illinois
4
OOS 0.0%
3. North Carolina
1
OOS 0.0%

Often Cited Together

Other violations commonly found on the same inspection (last 90 days)

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.

Refreshed daily.

Vehicle recall campaigns, defect investigations, and consumer safety complaints (SCRS).

Refreshed daily.
EIA

Retail diesel and gasoline price history and state fuel-tax tables.

Refreshed weekly.

Cross-border carrier registry and Canadian recall campaigns where applicable.

Refreshed weekly.

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.