Prevention FAQ — FMCSR 390.33

Fleet safety guidance for 390.33 violations. Pre-trip checklists, inspector focus areas, documentation practices, and root-cause analysis based on 20 all-time citations.

Severity Weight
N/A
OOS Eligible
No
BASIC Category
General/Admin
Code System
FMCSR
Code:
390.33
Code System:
FMCSR
BASIC Category:
General/Admin
OOS Eligible:
No
Severity Weight:
N/A

Ranks #1,970 of 3,146 FMCSR codes by citation frequency • OOS rate of 80.0% is above the FMCSR-wide average of 33.3%.

Prevention FAQ for Fleet Managers

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

What exactly do inspectors look for when citing 390.33?

Across our 13 million inspection records, 390.33 citations remain extremely rare—only 20 all-time and zero in the last 90 days. When inspectors do cite this code, they place the vehicle out of service 80% of the time, compared to the all-FMCSR average of 31.4%, signaling high severity. Our data shows the violation concentrates among passenger carriers: KINGKONG TOUR INC (USDOT 4048552) and FIRST STUDENT INC (USDOT 354406) each appear in the top carriers list. Inspectors are looking for documentation and administrative compliance issues that directly impact vehicle safety oversight. Focus your inspection readiness on carrier record systems, driver files, and maintenance logs that inspectors routinely verify during roadside stops.

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

Build your pre-trip checklist to include verification of carrier registration status, proof of current DOT authority, and driver qualification files. Because the 80% out-of-service rate indicates inspector discretion is triggered by serious deficiencies, ensure drivers can produce: current medical certificates, driver qualification files, hours-of-service records, and vehicle maintenance logs. Train drivers to recognize that these documents must be organized, legible, and available in the vehicle or accessible within 24 hours. Schedule a monthly audit where a designated safety manager walks through 3–5 vehicle files to confirm completeness. This preventive discipline eliminates the administrative gaps that trigger the high severity outcome we see in the data.

What documentation must drivers carry and carriers retain?

Drivers must carry or have accessible within 24 hours: a valid commercial driver license, medical examiner's certificate, vehicle registration, proof of insurance, and hours-of-service records. Carriers must retain driver qualification files, training records, vehicle maintenance records, and inspection reports for the required retention period. Our inspection database shows that carriers with strong documentation systems—filed chronologically and cross-referenced to vehicle and driver—avoid the escalation that leads to the 80% out-of-service rate. Implement a centralized filing system (physical or digital) with quarterly audits. Assign one staff member to verify that every driver's file is current and that maintenance records match the vehicle's service history. Missing or disorganized documents are the root trigger for citations.

What are the common root causes behind 390.33 citations?

Because 390.33 is an administrative code with very low citation volume (20 all-time), root causes center on systemic documentation and record-keeping failures rather than mechanical defects. The 80% out-of-service rate suggests inspectors cite this code only when they uncover severe compliance gaps—typically missing driver qualification files, expired medical certificates, or incomplete maintenance records. Our data shows that passenger carriers dominate the cited list (tour companies, limousine services, school bus operators), indicating that high-volume driver turnover and complex vehicle schedules create documentation backlogs. The pattern points to one root cause: insufficient administrative staffing or training on file maintenance. Assign a dedicated compliance coordinator to manage driver files, update certifications 60 days before expiration, and perform monthly spot audits on vehicle records.

How should repairs be verified before a vehicle returns to service?

After any citation or repair, implement a two-step verification: (1) A certified mechanic must sign off on the repair and document it in the maintenance log with date, mileage, and specific work performed. (2) A supervisor unrelated to the repair must inspect the vehicle and sign a return-to-service checklist. For 390.33 violations rooted in administrative deficiency rather than mechanical failure, the 'repair' is documentation completion—ensure all files are consolidated, filed in a consistent location, and accessible. Cross-reference the driver's file with the vehicle's maintenance history to confirm no gaps exist. Given the 80% out-of-service rate, inspectors will re-inspect your entire administrative system; returning to service without clearing all documentation deficiencies risks a repeat citation.

What post-citation review should the fleet run?

Within 72 hours of any 390.33 citation, convene your safety team to conduct a root-cause analysis focused on the specific document or record that triggered the violation. Review the driver's qualification file, the vehicle's maintenance log, and the inspection report side-by-side. Document what was missing and trace backward: Was the file never created, was it lost, or was it filed incorrectly? Assign accountability (e.g., 'The onboarding process did not require submission of medical certificates'). Then implement a corrective action: retrain staff, update your filing system, or add a verification step to your hiring process. Our data shows that carriers with robust post-citation reviews avoid repeat violations. Schedule this review as a formal meeting with attendance logged; document findings and actions in writing. Share results with all drivers to reinforce the importance of compliance.

How does this code affect our CSA Vehicle Maintenance BASIC score?

390.33 is classified as a General/Admin code and is not eligible for out-of-service placement under standard CSA rules—yet our data shows an 80% out-of-service rate, indicating the severity of violations inspectors are catching. This anomaly suggests the violations cited are severe enough that inspectors exercise discretionary authority. While 390.33 may not directly impact your Vehicle Maintenance BASIC, the underlying administrative failures often correlate with inadequate maintenance oversight, which does impact CSA scores. Our inspection records rank 390.33 at #1938 of 3,036 codes by volume, meaning citations are rare but serious when they occur. To protect your CSA scores, treat a 390.33 citation as a red flag to audit your entire compliance infrastructure—vehicle records, driver files, and maintenance logs—to ensure no secondary violations are hiding.

What training topics should drivers and staff receive?

Develop a two-track training program: (1) For drivers: document retention, what to carry, how to organize their personal files, and the consequences of missing records. Emphasize that an 80% out-of-service rate means violations are serious and costly. (2) For administrative staff: file management protocols, certification renewal calendars, and audit procedures. Include a hands-on session where staff practice organizing a complete driver qualification file and vehicle maintenance log from start to finish. Our data shows passenger carriers (tour operators, limousine services, school bus companies) represent the top violators, suggesting these high-turnover operations need robust onboarding training. Train new hires within 30 days of start date and require annual refreshers. Record attendance and competency checks. Make file management a performance metric: link incentives or evaluations to audit compliance scores.

When should we consider filing a DataQs challenge?

File a DataQs challenge if: (1) The citation documents a violation that was already corrected before the inspection, (2) The inspection report lacks sufficient detail to identify the specific deficiency, or (3) The citation was issued in error (e.g., the driver's file was present but the inspector overlooked it). Our inspection database records show only 20 citations all-time for 390.33, making each one notable. Before filing a challenge, gather comprehensive documentation: the complete driver file as it existed on the citation date, witness statements from your staff, records of prior submissions, and the inspection report itself. A successful challenge requires proof, not argument. If your documentation is airtight and the citation is factually incorrect, DataQs can remove it and protect your safety record. Consult your legal or compliance team before filing, but do not delay—the challenge window is time-limited.

How often should the fleet self-audit for 390.33 risks?

Audit monthly. Our inspection records show zero citations for 390.33 in the last 90 days and zero in the last 12 months, indicating either effective fleet compliance or very low inspector focus on this code. However, the 80% out-of-service rate for the 20 all-time citations means that when violations do occur, they are severe. A monthly audit cadence ensures your administrative systems remain tight and catches gaps before an inspector does. Assign a staff member to randomly select 3–5 driver files and 3–5 vehicle records, then verify completeness against your compliance checklist. Document findings in a log and escalate any gaps to your safety manager within 24 hours. This disciplined approach costs minimal time but eliminates the systemic weaknesses that trigger the high-severity citations we observe in the data. Use the log as evidence of good-faith compliance if ever questioned by regulators.

Last updated: 2026-04-20T16:23:48.527Z 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.