Prevention FAQ — FMCSR 374.201B-PC

Fleet safety guidance for 374.201B-PC based on 14 all-time citations across our 13M+ inspection database. Pre-trip protocols, documentation, root-cause analysis, and audit cadence.

Severity Weight
N/A
OOS Eligible
No
BASIC Category
Unknown
Code System
FMCSR
Code:
374.201B-PC
Code System:
FMCSR
BASIC Category:
Unknown
OOS Eligible:
No
Severity Weight:
N/A

Ranks #2,113 of 3,146 FMCSR codes by citation frequency • OOS rate of 0.0% is below the FMCSR-wide average of 33.3%.

Violation Description

Passenger Carrier - Failing to post/announce non smoking/no smoking regulations.

Prevention FAQ for Fleet Managers

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

What specific vehicle systems do roadside inspectors focus on when checking for 374.201B-PC violations?

Across our 13 million inspection records, we've documented 14 all-time citations for this code, with 6 of those issued against MOTOR COAC vehicles. Inspectors conducting roadside checks prioritize systems that directly affect safe operation and compliance documentation. The extremely low citation volume (ranked #2083 of 3,036 FMCSR codes) suggests this violation targets a narrow, specific defect rather than a systemic fleet-wide issue. When inspectors do cite this code, they are typically verifying compliance with explicit equipment requirements during the walkthrough phase. Focus your inspector briefings on the exact equipment specification referenced in 374.201B-PC and ensure your vehicle pre-trip forms explicitly call out this item.

What should be on the pre-trip inspection checklist to prevent this citation?

Create a dedicated line item on your pre-trip form that corresponds directly to the 374.201B-PC requirement. Because 14 citations have been issued across our database with zero out-of-service orders, this violation typically does not ground a vehicle—but it still counts against your carrier's inspection record. Your checklist must require the driver to physically inspect, test (if applicable), and document the status of the equipment in question before each shift. Include a pass/fail box and require the driver's signature. For operations running MOTOR COAC units (which represent 6 of the 14 citations in our data), add a secondary verification step at the yard level before dispatch. This checklist becomes your first line of defense and creates a documented audit trail.

What documentation must drivers carry and what should the carrier retain?

Drivers must carry proof that the item specified in 374.201B-PC has been inspected and is operational. This typically takes the form of the signed pre-trip inspection report, maintained in the cab or accessible via tablet/mobile app. Carriers must retain copies of all completed pre-trip inspections for a minimum of 12 months, organized by vehicle and date. Since our records show zero citations in the last 90 days and zero in the last 12 months, your documentation system should be flagged for routine audit (see cadence guidance below). Keep a master log tracking when the equipment in question was last serviced, calibrated, or replaced. This creates a clear chain of custody that protects the carrier if a citation occurs—enabling you to demonstrate that the driver was trained, the equipment was operational at dispatch, and maintenance schedules were met.

What are the common root causes behind this violation?

With only 14 all-time citations and zero violations in the past year, 374.201B-PC appears to be an isolated, equipment-specific compliance issue rather than a symptom of broader safety culture breakdown. The top carriers cited (VN COACH LLC with 5 citations, YOGUIS TOURS LLC with 2) suggest this violation may cluster in tour and charter operations. Root causes typically stem from: (1) driver unfamiliarity with the specific equipment requirement during onboarding, (2) lack of a dedicated pre-trip checklist item, or (3) infrequent equipment maintenance schedules that result in degraded or missing components. Because the peer codes in your category (such as 376.11(d)(1) with 6,383 citations) show much higher enforcement, your organization's low citation volume is actually a positive signal—but don't assume complacency. The equipment in question may simply be less frequently inspected on roadways, making it a lower-risk but still-enforceable item.

How should the fleet verify repairs are complete before returning a vehicle to service?

Implement a three-step sign-off process: (1) Mechanic completes repair or replacement of the non-compliant item and documents the part number, serial number (if applicable), and date in the maintenance management system. (2) A second technician or supervisor independently verifies the repair, tests the equipment if required, and signs off. (3) Before the vehicle leaves the yard, the driver must conduct a fresh pre-trip inspection that specifically addresses the repaired item and sign the form. This redundancy prevents a vehicle from returning to service with incomplete or incorrect repairs. Since 0 of the 14 citations resulted in out-of-service orders, inspectors view this as a compliance documentation issue rather than an acute safety hazard—but the repair sign-off process still must be rigorous. Maintain photos or work orders as evidence, especially for high-citation carriers like those in the tour and charter sector.

What post-citation review should the fleet conduct after a driver receives this violation?

Within 48 hours of receiving notice of a citation, convene a brief safety huddle with the cited driver, a maintenance representative, and a supervisor. Review: (1) What equipment was non-compliant and why the driver did not catch it on pre-trip? (2) Was the pre-trip checklist completed correctly, and does the driver understand the item in question? (3) Had the item been inspected or serviced recently, and if so, why did it fail? (4) Does the carrier's training curriculum include this specific requirement? Use this meeting to revalidate the driver's understanding, walk the vehicle together to confirm repair, and update training records. Since our data shows zero citations in the last 90 days, your citation pattern is exceptionally clean—but this review process ensures the violation remains isolated and doesn't recur.

How does this violation affect the carrier's CSA Vehicle Maintenance BASIC score?

FMCSR 374.201B-PC is ranked #2083 of 3,036 FMCSR codes by citation volume, which indicates it is a lower-frequency violation in the broader compliance universe. While it does not carry an out-of-service order (0.0% OOS rate vs. the national 31.4% average), it still counts as a Vehicle Maintenance BASIC citation and contributes to your carrier's inspection score. However, because you have zero citations in the last 12 months and only 14 in your entire TruckCodex history, this violation has minimal impact on your BASIC performance. Your safety profile remains clean relative to peer codes like 376.11(d)(1), which has generated 6,383 citations. Maintain this advantage by sustaining your pre-trip discipline and annual self-audits (see audit cadence below).

What driver training topics should be included to close compliance gaps?

Develop onboarding and annual recertification modules that: (1) Explicitly name and show the 374.201B-PC equipment requirement using photos or video of the item in question, (2) Explain why this item is regulated and what failure mode it prevents, (3) Walk through the pre-trip checklist item step-by-step with a hands-on demonstration, and (4) Show the driver what a compliant vs. non-compliant state looks like. Because 6 of the 14 citations involve MOTOR COAC vehicles, consider creating a model-specific training supplement or vehicle walkthrough video. Train drivers that pre-trip completion is not a checkbox exercise—it is a safety decision. Emphasize that missing or defective equipment in this category may not be immediately obvious, requiring deliberate inspection technique. Include a brief quiz or practical check at the end of training to confirm understanding before the driver operates a vehicle.

When should the fleet consider filing a DataQs challenge?

DataQs challenges are warranted if: (1) the cited equipment was in compliance at the time of inspection but the inspector misidentified the equipment state, (2) the inspector misapplied the regulation or cited the wrong code, or (3) the carrier has documented evidence (maintenance records, photos, repair receipts) proving the item was operational. Because only 14 citations exist across our entire database and zero in the last 12 months, your citation history is too clean to suggest a pattern of misapplication. However, if your carrier does receive a citation, gather all pre-trip records, maintenance logs, and service histories immediately. If those records directly contradict the citation, a DataQs challenge is appropriate and has a reasonable chance of success given the low overall enforcement frequency for this code. Consult your FMCSA liaison or legal counsel on the specific facts before filing.

How often should the fleet self-audit for compliance with this code?

Conduct a targeted self-audit every 90 days. Here's why: our data shows zero citations in the last 90 days and zero in the last 12 months, indicating this violation is either resolved or extremely rare in your operating region. A quarterly cadence allows you to verify that pre-trip discipline remains consistent and that the equipment in question is being maintained on schedule without requiring excessive overhead. The audit should sample 10–15% of vehicles and verify that: (1) the 374.201B-PC item appears on the current pre-trip form, (2) completed pre-trip reports from the past 30 days show the item was inspected, and (3) any maintenance or replacement of that equipment is documented. If you go three consecutive quarters without a single audit finding, you may extend to semiannual audits. However, maintain the quarterly cycle for any vehicle make or carrier tier with a prior citation history in your fleet.

Last updated: 2026-04-20T16:39:24.426Z Guidance derived from TruckCodex inspection data Read the full article → Quick Q&A →

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.