Prevention FAQ — FMCSR 393.87(a): Warning Flags on Projecting Loads

Inspectors verify that any load extending beyond the rear or sides of the vehicle is marked with the required warning flags — typically a red or orange flag of minimum dimensions at each outermost projection point. They check flag placement (must be visible from behind and from the side), flag condition (faded, torn, or missing flags are cited just as readily as no flag at all), and whether the flag is actually secured versus simply resting on the load.

Across our 13 million inspection records, 393.87(a) has generated 2,735 all-time citations and sits at #466 of 3,036 FMCSR codes by citation volume — not a fringe code. Notably, despite being listed as OOS-ineligible, our database shows a 52.7% OOS rate for this code, more than 21 percentage points above the all-FMCSR average of 31.4%. That gap tells inspectors are pairing this citation with other defects that do trigger OOS. Expect close scrutiny of the entire load securement package whenever a projecting load is in play.

Add a dedicated Projecting Load section to your standard pre-trip form that drivers must complete before any load that extends past the rear bumper or vehicle sides:

1. Flag count verified — one flag per outermost projection point, plus rear if load extends beyond 4 feet.
2. Flag dimensions confirmed — not torn, faded to unrecognizable, or smaller than required.
3. Flag attachment method checked — zip-tied, wire, or bracket; not friction-resting.
4. Flag visibility confirmed from 500 feet — walk 50 feet back and look; adjust if obstructed by other cargo.
5. Overhang distance measured and recorded — document rear and side overhang in feet on the trip sheet.
6. Load shift check at every fuel stop — flags that are present at origin can be knocked off or repositioned en route.

PTRB and FRHT vehicles account for 143 and 138 citations respectively in our records — the highest of any make — suggesting flatbed and heavy-haul tractors pulling specialty loads are disproportionately inspected. Make the checklist standard on all flatbed and lowboy assignments for those fleets.

Drivers should carry:

• The completed pre-trip inspection form with the projecting-load section signed and dated.
• A bill of lading or shipping document that lists overhang dimensions, confirming the flag requirement was known at dispatch.
• A photo (timestamped, taken at origin) showing flags in place — stored on the driver's phone or a fleet app is acceptable.

Carriers should retain:

• Copies of pre-trip forms for a minimum of 90 days (align with your existing driver records retention schedule).
• Load-specific safety instructions issued by dispatch noting flag requirements.
• Any repair or corrective-action records if a flag was found missing during a stop and replaced.

Documentation serves two purposes: it supports a DataQs challenge if the citation is factually incorrect, and it demonstrates due diligence in a post-accident or audit scenario. Given that our inspection data shows 2,735 all-time citations for this code, enforcement is real and documented pre-trip compliance is your first defense.

Our inspection records identify clear co-occurrence patterns that reveal systemic gaps rather than random oversights. The top co-occurring violations indicate three distinct failure modes:

1. Load securement breakdowns — 393.87(a) frequently pairs with broader load securement defects. When a driver fails to check flag status, they are typically also not verifying tie-down counts, tensioner condition, or load shift — a symptom of an inadequate pre-trip discipline across the entire securement package.

2. General vehicle maintenance neglect — co-occurrences with maintenance-category codes suggest some fleets treat projecting-load moves as informal or one-off operations where the normal inspection checklist is skipped. The 52.7% effective OOS rate confirms these trucks often have multiple defects, not just missing flags.

3. Dispatch/planning gaps — carriers like US LBM LOGISTICS LLC (8 citations) and GOLDEN STATE LUMBER INC (5 citations) are lumber and building-material haulers. The pattern suggests that loads are sometimes staged or rerouted without re-briefing drivers on flag requirements after load changes at the yard.

Address all three in root-cause corrective action plans.

Because 393.87(a) is not an OOS-eligible code on its own, the vehicle is not placed out of service for the flag violation alone — but our data shows a 52.7% OOS rate, meaning the cited vehicle was frequently held for other defects. Verify return-to-service readiness with this sequence:

1. Confirm flag replacement — a supervisor or terminal manager (not the cited driver) physically inspects and photographs the corrected flag placement before the vehicle moves.
2. Clear any accompanying OOS conditions — because co-occurring violations drove the actual OOS decisions in many of those 1,440 cases, every defect on the inspection report must be addressed and signed off.
3. Log the corrective action — document the repair in your maintenance system with the inspector's name, date, and DVIR number.
4. Driver debrief before re-dispatch — a five-minute verbal review of what failed and why adds accountability without creating a paperwork burden.

Do not treat flag replacement as a trivial fix-and-go. The accompanying violation profile in our data makes clear these events are rarely isolated.

Run a structured after-action review within 72 hours of the citation:

Step 1 — Pull the inspection report. Identify every cited violation, not just 393.87(a). The 52.7% OOS rate in our database signals that companion defects are common; each one needs its own corrective action.

Step 2 — Trace the load origin. Determine where the load was staged, who loaded it, and who dispatched the move. Was a projecting-load checklist completed? If not, why?

Step 3 — Review driver training records. Confirm the driver completed any load securement or special cargo training in their file. If the gap is a knowledge issue, schedule targeted retraining.

Step 4 — Audit similar moves in the prior 30 days. Pull pre-trip forms for other projecting-load assignments. If documentation is thin across the board, the problem is systemic.

Step 5 — Document the corrective action plan with a responsible owner and completion date. This record is essential if the same driver or vehicle is cited again and you need to demonstrate good-faith remediation to FMCSA.

Every 393.87(a) citation carries a CSA severity weight of 3, placing it in the lower-middle tier of the severity scale. While a single citation will not spike your Vehicle Maintenance BASIC on its own, the scoring context matters:

• The violation ranks #466 of 3,036 FMCSR codes by all-time citation volume — it is not rare enough to dismiss.
• Points are time-weighted, with citations in the most recent six months counting most heavily.
• More importantly, because our data shows 393.87(a) co-occurs frequently with higher-severity violations, the real CSA risk is the bundle — a single inspection event that triggers multiple citations in the Vehicle Maintenance BASIC can move the needle significantly.

For fleet managers, the practical implication is that preventing 393.87(a) citations is less about the severity-3 flag hit and more about closing the systemic gaps that allow higher-severity companion violations to appear on the same inspection report. Fix the process that produces the flag citation and you will suppress the broader defect cluster.

Our citation data by vehicle make tells a clear story: PTRB (143 citations), FRHT (138), FORD (123), KW (111), and MACK (105) account for the largest share of 393.87(a) citations. These are predominantly Class 7–8 tractors assigned to flatbed, lowboy, and lumber hauling. Training should be targeted at drivers in those assignments.

Core training topics:

1. Flag specification and sourcing — what size, color, and material qualifies; where flags are stored on the truck.
2. Measurement and trigger thresholds — when a load legally requires flags vs. when it does not; drivers should be able to measure overhang without guessing.
3. Attachment techniques — flags that blow off at highway speed are a recurring failure mode; train on secure attachment, not just placement.
4. En-route flag checks — make a fuel-stop flag check as habitual as a tire walk-around.
5. Scenario-based exercises — have drivers practice on actual flatbed configurations at the terminal before their first projecting-load assignment.

Carriers like RYDER TRANSPORTATION SOLUTIONS LLC and J B HUNT TRANSPORT INC appear in the top-cited list despite having mature safety programs, which confirms this is an execution gap, not just a knowledge gap.

File a DataQs challenge when the inspection record contains a factual, documentable error. Grounds that are typically successful:

• Photo evidence contradicts the citation — if the driver's timestamped pre-trip photo shows flags in place and the citation claims flags were missing, submit the photo with the challenge.
• Load did not legally require flags — if the overhang dimensions documented on the bill of lading are below the threshold that triggers the flag requirement, document that with measurements.
• Wrong vehicle or driver identified — confirm DOT number, license plate, and driver name on the inspection report match your records.

Grounds that are unlikely to succeed: driver simply says they remember having flags, or the flag was present but fell off before inspection. Those are disputed facts without supporting documentation, and DataQs does not resolve credibility disputes.

Before filing, check whether 393.87(a) is the only citation on the report. If companion violations are also incorrect, challenge the full event together — a single successful event-level challenge removes all associated violations from CSA scoring.

Our inspection database shows 0 citations in the last 90 days and 0 in the last 12 months for 393.87(a). That dormancy does not mean enforcement has stopped — it reflects a low-volume code with 2,735 all-time citations that surfaces in concentrated enforcement waves, often tied to load securement inspection blitzes or commercial vehicle safety alliances campaigns.

Recommended audit cadence:

• Monthly for active flatbed and lowboy fleets — spot-check 10–15% of projecting-load pre-trip forms for completeness and flag-attachment documentation.
• Quarterly terminal walk-throughs — physically inspect flag inventory (quantity, condition, storage location) at each terminal.
• Triggered audit after any load securement citation — even if the cited code is not 393.87(a), the co-occurrence pattern in our data means a securement defect is a predictor of flag compliance gaps.

The zero-citation trend in the past year should be read as an opportunity to cement good habits before the next enforcement uptick, not as permission to deprioritize the checklist.