Prevention FAQ — FMCSR 391.41(a): Physical Qualification

Fleet safety manager guide to preventing 391.41(a) citations: inspector focus areas, documentation, root-cause patterns, and audit cadence based on 42,270 real inspection records.

OOS Eligible
Severity Weight
1
OOS Eligible
Yes
BASIC Category
Driver Fitness
Code System
FMCSR
Code:
391.41(a)
Code System:
FMCSR
BASIC Category:
Driver Fitness
OOS Eligible:
Yes
Severity Weight:
1
Violation Group:
Medical Certificate

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

Violation Description

Operating a property-carrying vehicle without a valid medical certificate in possession or on file with the state drivers licensing agency. History of either failing to produce a medical certificate or having an expired medical certificate.

Prevention FAQ for Fleet Managers

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

What exactly do inspectors target when they write a 391.41(a) citation at roadside?

Inspectors are verifying that the driver currently meets the physical qualification standards required to operate a CMV — not just that paperwork exists, but that the driver's actual condition is consistent with their medical certification. Our inspection records show 42,270 all-time citations for this code, ranking it #74 of 3,036 FMCSR codes by volume, so it surfaces regularly.

The North Carolina data is a sharp warning signal: in the last 180 days, NC logged 482 citations with 456 resulting in OOS placement — a 94.6% OOS rate in that state alone. That tells you NC inspectors are specifically probing qualification status and acting decisively when they find a gap. Inspectors will ask to see the medical certificate, cross-check expiration dates, look for physical limitations visible during the inspection (e.g., mobility issues), and verify the driver's license class matches the vehicle being operated.

What items specific to 391.41(a) should appear on the pre-trip checklist?

The pre-trip process should include a driver self-certification step before the vehicle leaves the yard:

  • Medical certificate validity: Driver confirms their FMCSA medical certificate is current and physically in possession (or on file with the state licensing agency per applicable rules).
  • Expiration date check: Flag certificates expiring within 45 days for immediate renewal scheduling — don't wait for roadside.
  • Prescription/condition status: Driver self-attests no new medical conditions, medications, or changes since last exam that could affect qualification. This is especially relevant given that 392.2FT (operating while ill or fatigued) appears in 42 shared inspections alongside 391.41(a) in our last-90-day data — inspectors who pull one often look for the other.
  • License-to-vehicle match: Confirm CDL class and endorsements are appropriate for the assigned vehicle before dispatch.

This checklist step takes under 60 seconds and directly addresses the document and condition gaps that trigger this code.

What documentation must drivers carry and what must carriers retain to defend against this citation?

Driver must carry:

  • A current, valid FMCSA medical examiner's certificate (Form MCSA-5876) — not expired, not a photocopy presented as original where prohibited by state.
  • A CDL that reflects any required medical variance or skill performance evaluation on file.

Carrier must retain in the driver qualification (DQ) file:

  • Original or copy of the medical certificate, with a log of all renewals and exam dates.
  • Documentation of any exemptions, waivers, or SPE certificates granted by FMCSA.
  • Records of any medical conditions disclosed by the driver and any follow-up examinations.

Our inspection database shows 391.41APC (operating without a valid medical certificate on file) has generated 49,539 citations with a 97.1% OOS rate — the strongest indicator that certificate absence or expiration is the enforcement tripwire. Build a 30-day-out automated alert into your DQ management system so no expiration goes unnoticed.

What are the root-cause patterns behind 391.41(a) citations, based on co-occurring violations?

The co-occurrence data from the last 90 days reveals three systemic failure patterns:

  1. 383.23A2 (Operating without a CDL) — 81 shared inspections. The most frequent pairing. This suggests drivers are being dispatched in vehicles that require qualifications they don't hold, pointing to a dispatch/onboarding breakdown, not just a driver error.

  2. 392.2FT (Operating while ill or fatigued) — 42 shared inspections. When a driver is visibly unwell at roadside, inspectors immediately question whether they meet physical qualifications. This pairing suggests inadequate fit-for-duty screening at departure — drivers are leaving the yard in a condition that invites scrutiny on both codes.

  3. 396.17C (No proof of periodic inspection) — 39 shared inspections. This vehicle-side violation appearing alongside a driver-fitness code strongly suggests a systemic compliance culture gap, not isolated incidents. Operations that miss vehicle inspection schedules tend to also slip on driver qualification tracking.

Address all three root causes in your corrective action plan — dispatch controls, departure health screening, and DQ file discipline.

How should the fleet verify a driver is cleared to return to service after a 391.41(a) OOS event?

Our records show 6,861 OOS placements out of 42,270 all-time 391.41(a) citations — a 16.2% OOS rate. When OOS is triggered, the driver cannot operate until the deficiency is resolved.

Return-to-service protocol:

  • Obtain a new or updated medical examiner's certificate from a FMCSA-registered examiner; a supervisor's verbal clearance is not sufficient.
  • Upload the new certificate to the DQ file before the driver is reassigned to any CMV.
  • If the OOS was driven by a condition discovered during the inspection (not just an expired cert), require a written medical release specific to CMV operation.
  • Document the resolution date, examiner name and NRCME ID, and the name of the safety manager who authorized return to service.
  • For drivers involved in the 383.23A2 co-occurrence pattern (81 shared inspections), also confirm the CDL class and endorsements are correct before the next dispatch.
What post-event review process should the fleet run after a 391.41(a) citation?

Within 72 hours of a citation, run a structured root-cause review:

  1. Pull the full inspection report. Identify every violation cited in the same inspection. Given that 391.41(a) frequently co-occurs with 383.23A2 (81 times), 392.2FT (42 times), and 396.17C (39 times), assume there are companion violations unless the report says otherwise.
  2. Audit the driver's DQ file. Was the certificate expired, missing, or invalid? Was there a dispatch error involving vehicle class mismatch?
  3. Interview the dispatcher and terminal manager. Determine whether the driver was flagged before departure and what the departure screening process looked like.
  4. Flag all drivers with certificates expiring in the next 60 days across the entire fleet — one citation is a signal to audit broadly.
  5. Document findings and corrective actions in writing, tied to the specific root cause. CSA severity weight for this code is 7, so each citation carries real BASIC score impact — treat the post-event review as a scored process, not a formality.
How does a 391.41(a) citation affect the carrier's CSA Driver Fitness BASIC score?

FMCSR 391.41(a) sits in BASIC Group 3 (Driver Fitness) and carries a CSA severity weight of 7. That is a meaningful per-incident score hit, and at a national rank of #74 out of 3,036 FMCSR codes by citation volume, it is not an obscure edge-case violation — inspectors find it regularly.

For comparison, the all-FMCSR average OOS rate is 31.4%. This code's OOS rate of 16.2% is below that average nationally, but the NC data (94.6% OOS rate on 482 citations in 180 days) shows enforcement intensity varies sharply by state. High-OOS-rate states translate directly into higher Driver Fitness BASIC exposure because OOS events carry additional weight in the CSA scoring model.

Fleets operating in or through North Carolina should treat 391.41(a) compliance as a high-priority risk item, not a routine administrative check.

What driver training topics directly close the gap for 391.41(a) compliance?

Our citation data shows Ford vehicles account for 5,336 all-time 391.41(a) citations — the highest of any make — followed by Freightliner/FRHT (2,167) and Freightlin (1,818). The Ford concentration reflects the heavy use of Ford-platform vehicles in last-mile, service, and light commercial operations, segments where driver turnover is high and qualification tracking is often less rigorous than at large truckload carriers.

Training priorities for these segments:

  • Qualification self-awareness: Every driver should know their own certificate expiration date and understand that an expired cert means immediate OOS, not a grace period.
  • Fit-for-duty reporting: Given the 42 co-occurrences with 392.2FT (ill or fatigued), train drivers to self-report conditions that might affect their ability to operate rather than getting in the vehicle and hoping for the best.
  • Document handling: Drivers must understand what to carry, where to keep it in the cab, and how to present it at a weigh station or roadside inspection.
When should the fleet file a DataQs challenge on a 391.41(a) citation?

File a DataQs challenge when the inspection record contains a factual error that can be documented — not simply because the outcome was inconvenient.

Strong grounds for a challenge:

  • The medical certificate was valid on the inspection date and the driver had it in their possession, but the officer recorded it as expired or absent.
  • The driver's qualification records show the issue was resolved before the inspection date (e.g., a prior OOS was cleared) but the record wasn't updated correctly.
  • The citation names the wrong driver or the wrong vehicle.

Weak grounds (challenges likely to fail):

  • The certificate was genuinely expired at the time of inspection.
  • The driver didn't have the certificate physically present, even if one was on file.

Always pair the challenge with supporting documentation: a copy of the valid medical certificate with issue and expiration dates clearly visible, the driver's license, and the dispatch record placing the driver in that vehicle on that date.

How frequently should the fleet run internal audits for 391.41(a) compliance, and what does the trend data say about timing?

Run a full DQ file audit on a monthly cadence. Here's why the trend data supports that frequency:

Over the last 12 months, 391.41(a) citations have ranged from a low of 59 (May 2025) to a high of 107 (January and March 2026), with no month dropping to zero. The 90-day window shows 201 citations — roughly 67 per month — which is consistent enough to treat this as a persistent, not seasonal, risk. January 2026 (107 citations, 101 OOS) and March 2026 (107 citations, 102 OOS) are particularly notable: nearly every citation in those months resulted in OOS placement.

Audit checklist:

  • Pull every driver with a certificate expiring in the next 60 days and schedule renewals.
  • Confirm new hires added since the last audit have complete, valid DQ files before their first dispatch.
  • Cross-check CDL class against current vehicle assignments, given the strong 383.23A2 co-occurrence pattern (81 shared inspections in 90 days).

Monthly audits catch expiration drift before it reaches roadside.

Last updated: 2026-04-20T12:08:00.092Z Guidance derived from TruckCodex inspection data Read the full article → Quick Q&A →

Top Enforcing States

Where 391.41(a) is most commonly cited (last 180 days)

1. North Carolina
293
OOS 95.2%

Often Cited Together

Other violations commonly found on the same inspection (last 90 days)

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.