FMCSR 395.26(a): ELD Malfunction & Paper Logs — Q&A

No. Across all inspections in our database, 395.26(a) citations have resulted in a 0.0% out-of-service rate. This means no drivers cited for failing to reconstruct records of duty status on paper when their ELD malfunctioned were placed out of service on the spot. While this code is OOS-eligible under FMCSA rules, the enforcement pattern we track shows inspectors have not used that authority for this violation.

The CSA severity weight for 395.26(a) is 5 points. This weight is applied within a 30-day window; if you receive multiple citations in that period, points stack. The weight of 5 places this violation in the moderate-severity range—serious enough to impact your Safety Management Cycle scores, but not the heaviest penalty FMCSA assigns. Consult your carrier's safety team on how this affects your driving record or insurance status.

Immediately:

1. Document the ELD malfunction—note the date, time, and what failed (display, recording function, etc.).
2. Confirm you did reconstruct your records on paper graph grid, as required.
3. Collect that paper reconstruction and any ELD error logs.
4. Report to your carrier's safety or compliance team same day.

Within 24 hours:

• Have your ELD serviced or replaced if still malfunctioning.
• Do not wait; continued use of a broken ELD violates multiple HOS rules.

For the citation:

• Review the inspection report for specifics on what the officer found missing or incorrect.

Yes, relatively benign. Our records show 395.26(a) has never triggered an out-of-service order (0.0% OOS rate). Compare that to related violations: 395.8(a)(1) (not using the right method to record HOS) has a 93.2% OOS rate; 395.8A1-HOSP (no RODS using prescribed method) sits at 92.9%. Even 395.8(e)(1) (false duty status records) reaches 26.0% OOS. The most similar code, 395.24 (ELD form/manner issues), also runs 0.0% OOS but has logged 106,486 citations versus your code's zero all-time.

Yes. The FMCSA DataQs system allows drivers and carriers to contest violations through the Record Dispute Resolution (RDR) process. For 395.26(a), your challenge should center on whether you actually did reconstruct your records on paper when the ELD failed—a documentation-based claim. Gather your paper logs, any ELD service records, and the malfunction timeline. You have 90 days from the inspection to file a dispute. A lawyer or carrier compliance officer can help frame the submission, but the core question inspectors will review is straightforward: did you comply with the reconstruction requirement?

Extremely rare. Our database of 13 million+ roadside inspections shows zero citations for 395.26(a) in the last 12 months, last 90 days, and all-time. This is a code on the books but not actively enforced in the field. That changes the nature of your citation—if you received one, the inspector flagged a specific and clear failure to reconstruct records during an ELD outage. Do not treat this as a routine paper-pushing violation; the enforcement scarcity suggests inspectors cite it only when the breach is obvious.

Both. FMCSR 395.26(a) sits in the Hours of Service BASIC 2 category, which counts toward both driver and carrier CSA scores. A violation hits your personal record and your carrier's fleet safety metrics. Your company is accountable for your compliance, and your safety history influences the entire operation's CSA percentile ranking. Discuss with your safety manager how the violation affects your standing and any required training or monitoring.

When your ELD malfunctions, you must reconstruct your record of duty status on a paper graph grid. You cannot simply skip logging hours or estimate them later. The rule exists because paper RODS is the fallback that keeps you compliant during equipment failure. Once your ELD is repaired, you resume electronic logging. The intent is to ensure your hours are never unrecorded—whether by device or pen—so FMCSA and your carrier can verify you stayed within legal limits during the outage.