ELD Malfunctions and the 8-Day Repair Rule: What FMCSA Actually Requires

Every ELD on the US FMCSA Registered List is required to self-diagnose six specific failure modes. When one of them fires, the device shows a yellow or red icon and the compliance clock starts. The driver has work to do the same day; the carrier has until day 8 to make the malfunction go away. Miss either step and the violation goes straight into the HOS Compliance BASIC.

The six malfunction categories

49 CFR 395.22(h) lists exactly six conditions that qualify as a malfunction — not merely a diagnostic warning:

1. Power compliance. ELD loses power to the engine or the device itself, preventing automatic recording.
2. Engine synchronization. Device cannot read engine power status, vehicle motion, miles driven, or engine hours for more than 30 minutes over the last 24 hours.
3. Timing compliance. Internal clock drifts more than 10 minutes from UTC.
4. Positioning compliance. Cannot acquire a valid GPS position for more than 60 minutes cumulative over 24 hours.
5. Data recording compliance. Memory cannot record or retain any required event.
6. Data transfer compliance. Device cannot transmit the standardized output file to an authorized safety official.

Anything outside this list is a diagnostic event, not a malfunction, and does not require paper logs. The inspector at the roadside will know the difference, and so will your DOT auditor.

The 8-day clock, step by step

1. Hour 0. Driver notices the malfunction indicator. Note on the paper log header for that day.
2. Hour 24. Driver provides written notice to the carrier — email, text, or ELD system message, but it must be written.
3. Hour 24 onward. Driver records duty status on paper or a graph-grid form that meets 395.8 format. This continues until the ELD is compliant again.
4. Same time window. Driver reconstructs the prior 7 days (which are still sitting in the broken ELD) on paper logs and keeps them with the current log book.
5. Day 8. Carrier has repaired, replaced, or service the ELD. If more time is needed, the carrier must request an extension from the FMCSA Division Administrator in writing — not via email to the ELD vendor.

Violation codes and CSA weight

The three most severe combinations we see in our monitoring data are 395.8(a) + 395.22(h)(1) on the same Level III inspection — the driver kept no logs at all during the malfunction window and tried to produce the ELD data to the inspector anyway. Severity weights add up fast, and the inspector almost always writes a driver OOS under the CVSA criteria for HOS documentation.

Extensions: when and how

The 8 days are measured in calendar days, not business days. When a part is on back-order or a manufacturer recalls a firmware build, the carrier can request an extension of up to an additional 5 days. Requirements:

• Written request to the FMCSA Division Administrator for the state of the carrier's principal place of business.
• Description of the malfunction and the cause of the delay.
• Evidence of the repair effort: vendor ticket, back-order confirmation, shipping tracking.
• Submitted before the 8-day deadline expires.

What auditors look for

During an off-site or on-site audit, FMCSA investigators cross-reference three sources:

• The ELD malfunction log (required under 395.22(h)(5))
• The driver's paper logs for the malfunction period
• The carrier's repair records and written driver notices

Any gap between the three — a malfunction shown in the ELD system but no matching paper log, or a written notice dated after the repair was completed — triggers a deeper review. Carriers with a documented process that ties all three together rarely see escalation past an off-site review.

Where Deadline Safe fits

Deadline Safe cannot read your ELD directly. What we do is watch FMCSA for 395.x violations attached to your USDOT and alert you the moment one posts to QCMobile. If an inspector cited your driver for an ELD malfunction issue, you see it within 15 minutes of the state feeding the data to FMCSA — often hours before the driver's next pre-trip, and certainly before the broker or insurer pulls your SAFER snapshot.

Start a 30-day free trial to see your next inspection alert in real time.