Prevention FAQ — FMCSR 390.3(e): Clearinghouse Prohibition

Inspectors are verifying that a driver currently prohibited from performing safety-sensitive functions under the Drug and Alcohol Clearinghouse is not operating a CMV. At the roadside, this means the inspector queries the FMCSA Drug and Alcohol Clearinghouse (or has access to a carrier's Clearinghouse query results) and confirms the driver has an active prohibition on record. Our inspection records show 4,935 all-time citations for this code, and a striking 98.6% of those resulted in the driver being placed out of service — compared to the all-FMCSR average OOS rate of 31.4%. That gap signals inspectors treat any confirmed Clearinghouse hit as an immediate removal situation. Inspectors are not looking at the vehicle condition — this is a driver-status check, pure and simple. The citation is written the moment a prohibited driver is confirmed to be operating.

Build a mandatory Clearinghouse query gate into every dispatch workflow — not just at hire, but as an ongoing status check. Your pre-trip process should include:

• Daily dispatch verification: Before any driver is assigned a load, the TPA or safety manager confirms the driver has no active prohibition in the Clearinghouse.
• Driver self-attestation: Require drivers to sign a daily form affirming they are not prohibited and have not received a Clearinghouse notification since their last shift.
• Blocked dispatch flag: If the driver's Clearinghouse status cannot be confirmed (TPA unreachable, system outage), the driver does not roll until confirmation is in hand.
• Return-to-duty gate: Any driver who has had a prior violation must present a completed RTD process — SAP evaluation, prescribed treatment, and a negative RTD test — with documentation in the file before dispatch will assign a trip.

The 98.6% OOS rate in our database makes clear there is no grace window at the roadside. Prevention must happen before the truck moves.

Drivers should carry no Clearinghouse document themselves — the system is carrier- and employer-facing. However, carriers must retain:

• Annual general consent records: Signed consent from each driver authorizing the carrier to conduct limited queries.
• Query results: Timestamped records of every Clearinghouse query run, including the response received ("no records" or "prohibited"). Retain for a minimum of three years.
• Full query results for new hires: Before a driver first operates, a full query must be completed; retain the response.
• RTD documentation package: For any driver who completed the return-to-duty process, retain the SAP referral, all test results, follow-up testing schedule, and completion sign-off.
• TPA service agreements: Proof that a qualified Third Party Administrator is contracted to manage queries on the fleet's behalf.

Our inspection records show 4,935 citations against this code — many traceable to carriers who had no query record to produce when challenged. Documentation gaps become carrier liability fast.

The STATISTICS block for this code does not include a co-occurring violations list, so this answer is built from the enforcement pattern itself rather than paired-code data.

Our database of 4,935 citations points to three recurring systemic failures:

1. Clearinghouse query gaps at hiring: Carriers skip or delay the pre-employment full query, allowing a prohibited driver to operate before results return. Fix: make a completed full query a hard prerequisite in onboarding — no CDL, no load.

2. TPA relationship breakdown: Carriers rely on a Third Party Administrator for ongoing limited queries but fail to verify the TPA is actually running them on schedule. Fix: require monthly TPA confirmation reports and audit them quarterly.

3. Return-to-duty process not completed before reinstatement: A driver finishes SAP-prescribed treatment but is put back behind the wheel before the negative RTD test is on file. Fix: create a locked dispatch status for any driver in RTD process — only the safety director can lift it, and only with the negative test document in hand.

All three failures are process failures, not knowledge failures — they require system controls, not just training.

After a 390.3(e) citation, the driver's prohibition does not lift automatically. The carrier must work through a structured return-to-duty sequence:

1. Confirm the prohibition source: Log into the Clearinghouse and identify the specific violation and reporting employer that triggered the prohibition.
2. SAP referral and evaluation: The driver must be evaluated by a DOT-qualified Substance Abuse Professional. The SAP's written recommendations become the RTD roadmap — do not skip or compress this step.
3. Complete prescribed education or treatment: Follow the SAP's plan exactly. Partial completion does not clear the prohibition.
4. Negative RTD drug/alcohol test: Administered under direct observation. The result must be logged in the Clearinghouse by the Medical Review Officer or employer before the prohibition is removed.
5. Clearinghouse prohibition lifted: Confirm the prohibition status shows "resolved" in the Clearinghouse before reassigning the driver to any safety-sensitive function.
6. Follow-up testing plan: The SAP will specify a follow-up testing schedule (minimum 6 tests in 12 months). Enroll the driver in a follow-up pool immediately upon RTD.

Our data shows 4,866 of 4,935 citations resulted in OOS — do not move the driver until each step above is documented.

Run a structured root-cause review within 48 hours of the citation. The review should answer six questions:

1. When was the last Clearinghouse query run on this driver? Pull the TPA query log. If the last query is more than 12 months old, the annual query cycle has lapsed.
2. Did our TPA run the query — and did we verify it? Confirm the TPA's records match your internal log. If they don't match, the TPA relationship needs auditing.
3. Was this driver in a post-violation RTD process? If so, who authorized them to operate before the prohibition was lifted? Identify the process failure and the individual accountable.
4. How many other drivers in our fleet have not had a query in the past 12 months? Run a full fleet sweep immediately.
5. Is our dispatch system capable of blocking a driver with an active prohibition? If not, build that control before the next shift.
6. What is the citation's impact on our FMCSA record? Review the inspection report number and confirm the details are accurate before the 60-day DataQs window closes.

Document the review findings and corrective actions in writing — this record protects you in any subsequent audit.

FMCSR 390.3(e) sits in the General/Admin category in FMCSA's BASIC system, meaning it maps to the Controlled Substances/Alcohol BASIC — one of the most heavily weighted BASICs in the SMS scoring model. Our inspection records show this code ranks #341 out of 3,036 FMCSR codes by all-time citation volume, with 4,935 total citations on record. That places it in the top 12% of all cited codes by frequency, which is significant for a violation that has produced zero citations in the last 12 months and zero in the last 90 days in our database. The enforcement volume is concentrated in earlier periods, but the code remains active and inspectors have the tools to write it whenever a Clearinghouse hit is found. Because the OOS rate is 98.6% — more than three times the all-FMCSR average of 31.4% — nearly every citation adds an OOS event to the carrier's record, compounding the SMS impact beyond a simple violation point.

Our database shows Freightliner (FRHT) vehicles account for 473 citations under this code — the highest of any make — followed by Peterbilt (PTRB) at 201 and Kenworth (KW) at 174. These are the dominant makes in OTR and regional trucking fleets, which suggests this is not a vehicle-type-specific problem but a fleet-size and operational-density problem: larger fleets with more drivers have more exposure to Clearinghouse prohibitions slipping through.

For training, focus on:

• What the Clearinghouse is and how it works: Many drivers do not understand that a violation reported by a previous employer follows them into the Clearinghouse and is visible to all current and future employers. Make this concrete in onboarding.
• Driver obligations after a violation: Drivers must understand they are legally prohibited from operating — and that operating anyway is not a gray area. The 98.6% OOS rate in our data confirms inspectors enforce it as absolute.
• The RTD pathway: Walk drivers through what SAP evaluation, treatment, and the RTD test sequence look like, so the process is not a mystery if they ever face it.
• No self-clearance: Drivers cannot clear their own prohibition. Only a completed RTD process removes it.

File a DataQs challenge when you have documented evidence that the citation was written in error. Grounds worth pursuing:

• The driver had no active Clearinghouse prohibition at the time of the inspection: If your TPA query log shows a "no records" result dated on or before the inspection date, that is direct evidence the citation was improper. Attach the timestamped query result to your DataQs submission.
• The Clearinghouse record was not the driver cited: If the prohibition on file belongs to a different driver (name or CDL number mismatch), document the discrepancy and submit it with the inspection report.
• The prohibition had been resolved before the inspection date: If the RTD process was completed and the Clearinghouse shows the prohibition lifted prior to the roadside stop, the inspection data is inaccurate. Submit the Clearinghouse resolution timestamp and the RTD documentation.

Do not file a DataQs challenge to delay — the 60-day window from the inspection date is firm, and submissions without supporting documentation are routinely denied. Given the 98.6% OOS rate attached to this code, a successful challenge removes both the violation and the OOS event from your SMS record, making it worth the effort when the facts support it.

Our database shows zero citations for 390.3(e) in the last 90 days and zero in the last 12 months, against a total all-time count of 4,935. That pattern does not mean enforcement has stopped — it reflects a shift in how Clearinghouse violations surface. Most enforcement activity happens during targeted audits and compliance reviews rather than purely at roadside. Fleets that wait for a roadside citation to discover a Clearinghouse problem are operating well behind the detection curve.

Recommended self-audit cadence:

• Monthly: Confirm your TPA has run all required limited queries for the month and that every active driver has a query on record within the past 12 months.
• Quarterly: Audit the TPA's query log against your active driver roster. Flag any driver missing a query and hold them from dispatch until resolved.
• At every new hire: Verify the full query is completed and returned before the first trip — no exceptions.
• After any drug/alcohol program event: Run an immediate full-fleet query sweep if any driver in your fleet has a Clearinghouse violation reported, to confirm no other prohibited drivers are in service.

The near-zero recent citation rate makes internal audits your primary detection tool — not roadside enforcement.