Prevention FAQ — FMCSR 393.87(b) Projecting Load Flags

Inspectors verify that any cargo, equipment, or structural component projecting beyond the rear or sides of the vehicle displays proper warning flags or reflectors. They check flag color (typically red and white), attachment security, and visibility from approaching traffic. Our inspection records show 241 citations for this violation across our 13 million database records, with most violations occurring on flatbeds, trailers, and equipment-haul configurations. Focus your pre-trip protocol on loads extending more than 4 feet beyond the vehicle's rear and any lateral protrusions exceeding the side width by more than 4 inches. Inspectors also assess whether flags are weathered, faded, or loose enough to flap dangerously—a common citation trigger on repeat violators.

Your checklist must require drivers to inspect and document the presence, condition, and secure attachment of all warning flags before departure. Include: (1) Visual confirmation that flags are red and white, clearly visible, and securely affixed with no tears or fading; (2) Verification that flags are positioned to be seen from at least 500 feet away in daylight; (3) A secondary check for reflector tape condition if used; (4) Documentation of any load that extends beyond standard vehicle dimensions, including the direction of protrusion. Require a photo or written note in the pre-trip report if projections are present. This step-by-step approach prevents surprise citations and creates a paper trail demonstrating due diligence. Train drivers to flag any newly added cargo that shifts the load configuration mid-route.

Drivers should carry load manifests or bills of lading that note overall load dimensions and any projections beyond the vehicle body. Carriers must retain load documentation for at least 12 months, including shipping paperwork, load photos (especially for oversized or irregular cargo), and pre-trip inspection reports noting flag presence. When a load is added or reconfigured, document the date, time, and driver's signature confirming flag compliance. Maintain a log of flagging supplies issued to each vehicle—this demonstrates that drivers have access to compliant flags. If a citation is issued, preserve the inspection report, photographs of the alleged violation, and your contemporaneous records. This documentation is essential if you file a DataQs challenge or respond to CSA scoring inquiries.

Across our 13 million inspections, codes frequently paired with 393.87(b) citations reveal systemic patterns. The co-occurrence with lighting and reflector violations (393.9 and 393.11) suggests drivers may not understand or prioritize visibility compliance broadly—training should address the connection between flag presence and reflector function. When this code appears alongside general maintenance defects (396.3), it often reflects a broader gap in pre-trip discipline rather than a single missing flag. Root-cause analysis should ask: Are drivers loading cargo without supervisor approval? Is there no clear load-dimension policy? Do drivers lack access to proper flagging materials? The answer typically reveals whether the problem is knowledge, accountability, or resources—each requires a different corrective action.

After a citation or identified deficiency, implement a two-person verification: the driver performs the repair (flag installation or replacement) and a supervisor or designated safety officer independently confirms compliance before the vehicle leaves the yard. Require a signed repair work order noting the date, time, vehicle ID, and specific action taken (e.g., "installed red/white warning flags on rear protrusion"). Take a photograph showing the corrected flag placement and condition. For fleet vehicles, maintain a digital record linking the repair ticket to the original inspection or citation. If a flag was damaged in transit, verify not just that a new flag is installed but that the attachment method prevents future loosening—this is especially important for flatbeds and trailers with higher vibration exposure.

Schedule a formal safety meeting within 5 business days of the citation. Gather the driver, the inspector's report, your pre-trip documentation, and load records from the violation date. Ask: (1) Was a flag present but not compliant (damaged, faded, loose)? (2) Was the load dimension correctly identified in the manifest? (3) Did the driver know flags were required for this load type? (4) Was flagging material available on the vehicle? Review the driver's pre-trip report—if it's missing or shows no inspection, retraining is needed. Check whether the same vehicle or driver has prior violations; repeat issues suggest accountability gaps. Document your corrective action plan and share it with the driver. Track whether similar violations recur within 90 days to assess whether your intervention worked. This structured review converts a single citation into fleet-wide risk reduction.

Each 393.87(b) citation carries a CSA severity weight of 3, placing it in the lower range of violation weights—for comparison, inoperable required lamps (393.9) weigh 4 points. Across 13 million inspections, 393.87(b) ranks #1169 of 3,036 FMCSR codes by citation volume, meaning it is relatively rare compared to high-volume maintenance violations like lighting defects or inspection failures. However, the national average out-of-service rate for all FMCSR codes is 31.4%; this code's rate is only 2.1%, meaning inspectors rarely place vehicles OOS for missing flags alone. This suggests citations are issued for visibility or minor flag issues rather than critical safety defects. To minimize CSA impact, address violations quickly, document corrective actions, and maintain strong pre-trip protocols that prevent recurrence within audit windows.

Training must address when flags are legally required (any load projecting beyond vehicle dimensions) and what compliant flags look like (red and white, securely attached, visible from 500+ feet). Our citation data shows flatbeds, trailers, and specialized equipment carriers—vehicles with models like FRHT, PTRB, WSTR, and MACK—account for the highest citation counts. Use make-specific examples during training: show drivers how flatbed side rails, equipment binders, and rearward protrusions on these platforms commonly trigger flag violations. Teach drivers to inspect flags at every stop, not just pre-trip. Cover the regulatory reasoning: flags protect other drivers. Role-play scenarios where load configuration changes during transit (dropped cargo, strap failure shifting the load) require immediate flag inspection. End training with a signed acknowledgment and a practical demonstration on the vehicle types your fleet operates.

Yes, if your records clearly show that compliant flags were present at the time of inspection. File a DataQs challenge if: (1) your pre-trip inspection report or photo documentation dated before the roadside stop shows flags in place and good condition; (2) the inspector's report contains factual errors about the load configuration or flag presence; or (3) your load manifest contradicts the inspector's violation description. Include copies of pre-trip inspections, load photos, and any driver statements. The challenge requires evidence that a flag was physically present and compliant—vague claims that "we always flag our loads" will not succeed. Given that only 241 citations for this code exist across 13 million inspections, the violation is relatively uncommon, which means an incorrect citation stands out and may be worth the administrative effort to contest.

Conduct formal audits monthly for vehicles that regularly carry projecting loads (flatbeds, equipment haulers, specialty trailers). Inspect at least 10% of your active fleet per month, focusing on the makes that appear most frequently in citation data: FRHT, PTRB, WSTR, and MACK. Because our records show zero citations for this code in the last 90 days and zero in the last 12 months, proactive internal auditing is your best defense—external enforcement is infrequent, but non-compliance can still occur. Supplement monthly audits with spot checks during seasonal load changes or after any load-dimension policy updates. Document every audit, noting which vehicles were checked, flag condition, and any deficiencies found. Use audit results to identify training gaps or supply shortages. A monthly rhythm ensures consistent compliance culture without excessive overhead and keeps the issue visible to drivers.