Prevention FAQ — FMCSR 392.7(b) Pre-Trip Inspection

Fleet safety guidance for preventing citations for failure to conduct pre-trip inspections of intermodal equipment. Checklists, documentation, and root-cause analysis based on 191 all-time citations.

Severity Weight
N/A
OOS Eligible
No
BASIC Category
Unsafe Driving
Code System
FMCSR
Code:
392.7(b)
Code System:
FMCSR
BASIC Category:
Unsafe Driving
OOS Eligible:
No
Severity Weight:
N/A

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

Violation Description

Driver failing to conduct a pre-trip inspection of Intermodal Equipment

Prevention FAQ for Fleet Managers

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

What exactly do inspectors look for when citing 392.7(b)?

Inspectors verify that drivers have physically completed and documented a pre-trip inspection of intermodal equipment before operating the vehicle. They check for:

  • Driver testimony or logbook entries confirming the inspection was performed
  • Equipment damage or defects that would have been caught in a proper pre-trip (cracks, loose fasteners, bent kingpins, locking mechanisms)
  • Absence of inspection records or documented results on the trip documentation
  • Timing — the inspection must occur before the trip, not after mechanical failure

Across our inspection records, we see 191 all-time citations for this code with a 0.0% out-of-service rate, meaning inspectors typically issue citations rather than place equipment OOS. This suggests enforcement focuses on documentation and procedural compliance rather than active safety defects.

What should a pre-trip checklist for intermodal equipment include?

A complete checklist must cover equipment-specific items beyond standard tractor/trailer inspection:

Intermodal-Specific Items:

  • Container/chassis locking mechanism engagement and security
  • Twist locks (if applicable) engaged and functional
  • Cargo securing devices (straps, chains) for damage or wear
  • Deck plate condition and attachment
  • Air suspension (if equipped) for leaks or damage
  • Kingpin and coupler integrity
  • Electrical connector pins and receptacle condition

Standard Requirements:

  • Lights, reflectors, and visibility
  • Tire condition and pressure
  • Brake system operation (air supply, response)
  • Steering and suspension components

Documentation Standard: Drivers must date, sign, and document any defects found, with repairs verified before departure. The checklist becomes the first line of evidence against 392.7(b) citations.

What documentation must drivers carry and carriers retain?

Driver Carries:

  • Completed pre-trip inspection form (signed and dated) for each trip
  • Defect report with corrective action taken (repair log or mechanic sign-off)
  • Equipment history or maintenance record for the specific intermodal unit

Carrier Retains (minimum 1 year):

  • All signed pre-trip inspection forms
  • Maintenance and repair records for each intermodal chassis/container
  • Driver training records confirming inspection procedure instruction
  • Incident reports if a citation was issued
  • Electronic logbook data or trip logs showing inspection completion

Best Practice: Use a standardized form (paper or electronic) that requires driver signature and captures specific equipment components. Maintain scanned copies or digital records to enable rapid retrieval during audits or regulatory inquiries. Missing documentation is often the basis for citation issuance.

What are the most common root causes, and how do I identify them in my fleet?

Our inspection records show 191 all-time citations for this code. While specific co-occurring violation patterns are not available in this dataset, root causes typically cluster into:

Process & Training Gaps:

  • Drivers unaware of what constitutes a pre-trip inspection for intermodal vs. standard trailers
  • Insufficient training on the difference between intermodal chassis and standard dry van or flatbed equipment
  • No enforcement of completion during driver onboarding

Organizational Issues:

  • Fleet operations pressure to move equipment quickly, skipping documented inspection
  • Lack of accountability mechanism (no audits of completed forms)
  • Unclear assignment of responsibility between operations and driver

Identify These in Your Fleet:

  • Audit 10 random trip logs per month; check for signed inspection forms
  • Interview drivers on what they inspect on intermodal equipment
  • Review maintenance records to see if defects correlate with pre-trip documentation gaps
  • Survey safety managers on current pre-trip procedures for intermodal units
How should repairs be verified before the equipment returns to service?

Once a defect is identified in a pre-trip inspection, implement this verification workflow:

Step 1: Document the Defect Driver records the issue on the inspection form with location and severity (e.g., "Twist lock #2 stuck, cannot engage").

Step 2: Assign & Repair Ops or maintenance assigns repair to qualified mechanic; defective equipment is quarantined and not released to any driver.

Step 3: Verify & Sign-Off Mechanic completes repair and signs the defect report with date and repair description (e.g., "Replaced twist lock assembly, tested engagement — FUNCTIONAL").

Step 4: Driver Re-Inspection Before next use, the assigned driver re-inspects the repaired component and confirms functionality on a new pre-trip form.

Step 5: Record Retention Store the defect report + repair receipt + second inspection form together for audit trail. This creates accountability and prevents repeat failures on the same equipment.

This cycle is essential because incomplete repairs are often cited when the same equipment fails again on the next trip.

What should a fleet do after receiving a 392.7(b) citation?

Post-citation review protocol:

Immediate (24–48 hours):

  • Obtain the inspection report and determine the exact reason for citation (missing form, unsigned form, defect not documented, etc.)
  • Interview the cited driver about what occurred and whether an inspection was actually performed
  • Review the driver's logbook and any electronic evidence (timestamps, geolocation) around the inspection window

Root Cause Analysis (1 week):

  • Examine 5–10 prior trip records from the same driver to identify patterns (incomplete forms, missing signatures)
  • Compare the cited equipment's maintenance history to see if defects were visible and reportable
  • Check training records: when was the driver last trained on pre-trip procedures?

Corrective Action (ongoing):

  • If the driver was negligent: conduct retraining on intermodal pre-trip procedures and audit their next 10 trips
  • If the issue was procedural (missing forms): revise checklist design, add digital prompts, or switch to electronic logging
  • If it was a dispatcher error (pressure to move equipment): reinforce policy with operations leadership

CSA Impact:

  • This citation counts toward Vehicle Maintenance BASIC scores; track the violation code and monitor whether repeat citations occur
Will this citation hurt my CSA Vehicle Maintenance BASIC score?

Yes. Citations for 392.7(b) are classified under the Unsafe Driving category and contribute to your Vehicle Maintenance BASIC in FMCSA's Safety Management System.

Impact Magnitude: Across our inspection records, this code ranks #1229 of 3,036 FMCSR codes by citation volume (191 all-time). By comparison, the broader Unsafe Driving category includes much higher-volume violations like 392.2 (Operating a CMV while ill or fatigued), which has generated over 1.2 million citations. While 392.7(b) is relatively uncommon, every citation counts toward your BASIC percentile.

CSA Scoring: Each citation increases your Vehicle Maintenance BASIC value. If your percentile exceeds 50th (worse than 50% of carriers), you may be subject to targeted audits or enforcement actions.

Mitigation: The 0.0% out-of-service rate for this code suggests citations are typically non-emergency violations, meaning your carrier can operate while working to prevent recurrence. Focus on documented compliance (signed inspection forms) to prevent stacking citations and degrading your score over time.

What training should drivers receive to prevent this citation?

Driver training should cover:

Equipment-Specific Knowledge:

  • Intermodal vs. Standard Trailers: How intermodal equipment (chassis, containers, platforms) differs mechanically and inspectionally from dry vans or flatbeds
  • Locking Mechanisms: Twist locks, king pin couplers, and deck securing devices; how to verify engagement and identify failure modes
  • Damage Patterns: Common defects on intermodal equipment (bent kingpins, corroded twist locks, cracked deck plates) and why they're critical

Procedural Requirements:

  • Completion & Documentation: Pre-trip inspection must be performed before departure; results must be signed and dated on the required form
  • Defect Reporting: How to describe defects clearly (location, severity, functional impact) so mechanics can repair correctly
  • Refusal to Operate: Driver authority and obligation to refuse an unsafe unit

Frequency: Initial training during onboarding; annual refresher for all drivers who handle intermodal equipment. Reinforce with supplemental training after any citation.

Verification: Test drivers on checklist items and require signed attestation of training completion in your records.

Should I challenge this citation via DataQs?

Consider a DataQs challenge if one or more of these conditions apply:

Strong Candidates for Challenge:

  • Driver Did Perform Inspection: You have logbook entries, GPS data, or witness evidence that the inspection occurred, but the form was lost or the inspector disagreed on documentation standards
  • Form Was Completed & Signed: The inspection form exists, is properly signed and dated, but the inspector misread or misinterpreted the requirements
  • Equipment Was Serviceable: You have maintenance records proving the intermodal equipment was defect-free at the time; citation was based on missing documentation only, not actual equipment condition
  • Training Records Exist: You can produce driver training records, certification, and prior inspection forms showing consistent compliance before this isolated incident

Weak Challenge:

  • No inspection form exists and driver cannot recall performing one
  • Multiple prior trips show incomplete or unsigned forms
  • Equipment later revealed defects that should have been caught

Process: File a DataQs challenge within 30 days of citation. Provide signed affidavits from the driver and maintenance staff, copies of all inspection forms from the past 90 days, and your training documentation. The burden is on you to prove the citation was factually or procedurally incorrect.

How often should the fleet audit for pre-trip inspection compliance?

Recommended Cadence: Monthly Full Audit

Our inspection records show zero citations in the last 90 days and zero in the last 12 months for 392.7(b), indicating this violation is currently rare in enforcement. However, this does not mean your fleet should reduce vigilance; it reflects low citation volume historically, not low risk.

Monthly Audit:

  • Randomly sample 15–20 completed trip inspection forms
  • Verify signature, date, and legibility of driver name
  • Check that defects (if noted) have repair sign-offs
  • Audit the driver who submitted the form: are all prior month's forms present and complete?
  • Document audit results; flag drivers with missing or unsigned forms for retraining

Quarterly Deep Dive:

  • Audit all trip records for drivers with 1+ prior violations or incomplete forms
  • Review maintenance logs for equipment cited in prior inspections; verify repairs align with documented defects
  • Conduct 2–3 ride-alongs to observe pre-trip inspection in real-time

Annual Assessment:

  • Aggregate all monthly audit data; identify carriers or equipment types with patterns of non-compliance
  • Review CSA Vehicle Maintenance BASIC score and trending
  • Update training curriculum based on findings

Justification: Because citations are rare but carry CSA impact, consistent documentation prevents the sudden spike that could trigger enforcement attention.

Last updated: 2026-04-20T15:08:18.824Z 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.