Listen to an in-depth podcast of this post
A walkthrough of exactly what has to happen in the first 24 hours after an ELD malfunction, the carrier’s 8-day repair clock, and the hidden 5-day window to ask FMCSA for more time before that clock runs out.
- The moment an ELD shows a malfunction, the driver must give the motor carrier written notice within 24 hours and start keeping paper logs, under 49 CFR 395.34(a)(1) and (a)(2).
- The driver has to reconstruct the record of duty status for the current 24-hour period plus the previous 7 consecutive days on graph-grid paper logs, then keep logging on paper until the device is fixed.
- The motor carrier then has 8 days from discovery of the malfunction or the driver’s notice — whichever happens first — to correct it, under 49 CFR 395.34(d)(1).
- If 8 days isn’t enough, the carrier must request a written extension from the FMCSA Division Administrator for its state within 5 days of the driver’s notice, under 395.34(d)(2) — there’s no option to just let day 8 pass quietly.
- A fleet that lets both clocks run out is exposed to a recordkeeping penalty of up to $1,584 per day, capped at $15,846 per violation under Appendix B to 49 CFR Part 386 — a cap that didn’t rise for 2026 because the government shutdown wiped out the October 2025 CPI-U data agencies need to adjust it.
A driver two hours into a run watches the ELD tablet throw a flashing malfunction indicator — the engine data feed stopped updating twenty minutes ago. Dispatch says, “keep rolling, we’ll sort it out back at the yard.” Nine days later the device is still broken, nobody has written FMCSA, and the fleet has quietly turned an equipment glitch into a recordkeeping violation that can run up to $15,846.
That’s not an edge case. It’s the default outcome for any small fleet that doesn’t already know three things: what the driver has to do in the first 24 hours, what the carrier has to do inside 8 days, and what happens if neither deadline gets met.

What “Malfunction” Actually Means, and What Has to Happen in 24 Hours
An ELD malfunction isn’t a judgment call the driver or dispatcher makes. The device itself is required to detect and flag seven specific conditions, each with its own numeric threshold, under 49 CFR Part 395, Subpart B, Appendix A.
Code P, power compliance, trips when the device understates in-motion driving time by 30 minutes or more, aggregated across all drivers, in a 24-hour period. Code E, engine synchronization compliance, trips when the ELD loses its connection to the engine control module’s required data for more than 30 minutes in 24 hours. Code T, timing compliance, trips the moment the device’s clock drifts more than 10 minutes from UTC. Code L, positioning compliance, trips after 60 cumulative minutes in a 24-hour period with no valid position fix. Code R covers a device that can no longer record, retain, or retrieve required logs. Code S covers a failed data transfer to an inspector at the roadside. Code O is a catch-all for anything else the device itself detects and flags as a malfunction.
Once any of those seven trips, the driver’s clock starts immediately — not when the shop gets around to looking at it. Under 395.34(a)(1), the driver must provide written notice of the malfunction to the motor carrier within 24 hours. Under 395.34(a)(2), the driver must reconstruct the record of duty status for the current 24-hour period and the previous 7 consecutive days, and record it on graph-grid paper logs, unless the records are already recoverable from the device. From that point forward, the driver keeps manually preparing a paper record of duty status under 395.8 until the ELD is serviced and brought back into compliance.

The Carrier’s 8-Day Clock, and the Only Way to Stop It
The carrier’s obligation starts on the same trigger as the driver’s, not after. Under 395.34(d)(1), the motor carrier must take action to correct the malfunction within 8 days of discovery of the condition or the driver’s notification, whichever occurs first.
There’s a second, shorter clock hiding inside that 8-day window. Under 395.34(d)(2), if the carrier needs more than 8 days, it must notify the FMCSA Division Administrator for the state of the carrier’s principal place of business within 5 days after the driver’s notice — in writing, with the specific reasons more time is needed. A carrier that does this correctly is deemed in compliance with 395.8(a)(1)(i) and (a)(2) until FMCSA makes a determination on the request.
That means the extension-request deadline falls three full days before the repair deadline, not after it. A small fleet that waits until day 7 to admit the shop can’t make day 8 has already missed the day-5 window to ask for more time. By day 8, there’s no clock left to stop — only a repaired device or a violation.

Where Small Fleets Actually Lose This
Most of the friction isn’t in the regulation. It’s in what’s physically sitting in the truck. A fleet that switched to ELDs years ago typically has no graph-grid paper log pads left in any cab — they got thrown out once the device took over. When a malfunction hits, the driver can’t comply with 395.34(a)(2) because there’s nothing in the truck to write the reconstructed week on.
A driver reconstructing 7 days of duty status from memory, without any paper trail to check against, is also the most likely way to produce a record that’s incomplete or inaccurate — which puts the fleet right back under the same recordkeeping penalty schedule the malfunction was supposed to avoid. Appendix B to 49 CFR Part 386 sets that penalty at up to $1,584 for each day a recordkeeping violation continues, capped at $15,846 per violation, for records required under parts 390 through 399 that are missing, incomplete, inaccurate, or false.
That cap hasn’t moved for 2026. Civil penalty amounts normally rise each year under the Federal Civil Penalties Inflation Adjustment Act, tied to the October Consumer Price Index. The 2025 government shutdown kept the Bureau of Labor Statistics from publishing that October data, so DOT — along with EPA and OSHA — carried the 2025 penalty table forward into 2026 unchanged, the first year since 2016 those caps haven’t increased.

What most people get wrong
The common assumption is that if the ELD comes back online within a day or two, nothing needs to be reported. That’s backwards. The notice and reconstruction duties trigger the instant the malfunction occurs, independent of how fast the shop fixes it — a device that’s repaired in six hours still required a written notice within 24 hours and a paper reconstruction for that window.
As the Responsible Fleet team sees it, the costlier mistake is dispatchers assuming the carrier’s 8-day clock starts when someone at the yard opens a repair ticket. It starts at discovery of the condition or the driver’s notification, whichever is earlier — almost always the moment the driver sees the indicator on the dash, hours or days before anyone at the office hears about it.
Frequently asked questions
What exactly counts as an ELD “malfunction” versus a minor glitch?
A malfunction is one of seven specific conditions the device itself must detect under 49 CFR Part 395, Subpart B, Appendix A — things like a power data gap of 30 minutes or more, or a clock drift past 10 minutes from UTC. Smaller issues the spec calls “data diagnostic events” are earlier warnings that don’t by themselves trigger the 24-hour notice or 8-day repair clock.
How fast does a driver have to tell the carrier about a malfunction?
Within 24 hours, in writing, under 49 CFR 395.34(a)(1).
What do the fallback paper logs actually have to cover?
The driver reconstructs the record of duty status for the current 24-hour period plus the previous 7 consecutive days on graph-grid paper logs, then keeps logging manually under 395.8 until the ELD is serviced and compliant again, per 395.34(a)(2).
How long does the carrier have to fix a malfunctioning ELD?
8 days from discovery of the malfunction or the driver’s notification, whichever happens first, under 49 CFR 395.34(d)(1).
What if 8 days genuinely isn’t enough time to get the device fixed?
The carrier must request a written extension from the FMCSA Division Administrator for the state of its principal place of business within 5 days of the driver’s notice, stating the specific reasons more time is needed. A properly filed request is deemed in compliance under 395.34(d)(2) until FMCSA rules on it.
What’s the actual financial exposure if a fleet misses both deadlines?
The relevant recordkeeping penalty under Appendix B to 49 CFR Part 386 runs up to $1,584 per day the violation continues, capped at $15,846 per violation — a cap that stayed flat into 2026 because the government shutdown disrupted the inflation-adjustment data.
The bottom line
Two deadlines overlap here, both counted in days, not weeks: 24 hours for the driver to put the malfunction in writing, 5 days for the carrier to ask for more time if it needs it, 8 days to have the device actually fixed if it doesn’t. None of it requires new equipment.
The Responsible Fleet team’s recommendation: keep a pad of graph-grid paper log sheets in every cab, and make sure whoever answers the malfunction call at the yard knows which day the clock actually started.
Want a fleet platform that keeps your drivers and dispatchers ahead of deadlines like this one?
This article is for general information and does not replace your own legal, safety, or DOT-compliance judgment. Verify the regulations for your jurisdiction and vehicle class.
The Responsible Fleet Team helps small and mid-size fleets get more out of GPS tracking, dash cameras, asset tracking, and ELD/compliance — one platform, one vendor, on flexible terms.
