🔧 ELD Malfunction: What to Do — A Driver's Step-by-Step Guide

The ELD screen goes red in the middle of Nebraska, and the first thought is always the same: "Am I legal right now?" Yes, you are — if you know the drill. A broken logging device is one of the few situations where the FMCSA wrote you an exact script: what to note, whom to tell, what to write on paper and how many days everyone has. Drivers get in trouble not because the ELD failed, but because they kept rolling for weeks pretending it didn't. Here's the whole script, in the order you'll use it.

🚨 Malfunction or data diagnostic event — which one are you looking at?

The regulations split ELD problems into two very different buckets, and your duties depend on which one is on the screen.

A data diagnostic event is a yellow flag: the device noticed something odd about the data — a lost engine connection for a few minutes, a record missing a field, unidentified driving piling up. You resolve it, often right from the cab, and you do not have to switch to paper. A malfunction is a red flag: the device can no longer do its legal job, and the script from 49 CFR 395.34 kicks in.

Every compliant ELD uses the same one-letter malfunction codes, so a Motive, Samsara or Garmin unit may look different but speaks the same language:

Diagnostic events use digits instead of letters — 1 power, 2 engine synchronization, 3 missing required data, 4 data transfer, 5 unidentified driving, 6 other. Rule of thumb: a digit means fix the data, a letter means fix the device — and a letter that won't clear means the 395.34 script below.

📋 What does 49 CFR 395.34 tell you to do, step by step?

Four moves, in order. As of September 2026 the section reads the same as it has since the mandate, but check the current text if you're reading this much later — rules may change.

1. Note the malfunction. The moment you see a malfunction indicator you can't clear, write down the code, date, time and odometer. Photograph the screen — a timestamped photo settles a lot of arguments later.
2. Tell your carrier in writing within 24 hours. "In writing" is the operative word: a phone call to dispatch is a good start, but back it up with a message that leaves a trail — an email, a text, a note through the ELD system itself. Keep your copy. This notice is what starts the carrier's 8-day repair clock and what proves at an inspection that you did your part.
3. Reconstruct the current 24 hours and the previous 7 days. If the malfunction ate your past records, rebuild them on paper graph-grids: use the ELD's display or printout if it still shows history, your own notes, fuel receipts, bills of lading and dispatch records. If the ELD can still produce those days accurately — or you have printouts — you don't need to redraw what already exists.
4. Run paper logs until the unit is fixed. Every day from the malfunction to the repair gets a manual record of duty status. Not "when I remember" — every day, current, certified with your signature.

One thing the malfunction does not change: your hours-of-service limits. The 11-hour driving limit, the 14-hour window and the 70-hour cycle all still apply — you're just keeping score with a pencil for a while. Same goes for special statuses: if you use personal conveyance, mark it on the paper grid with a remark, exactly as you would annotate it in the app.

📝 How do you run paper logs right?

The paper log that satisfies the rule is the classic graph-grid from 49 CFR 395.8 — the same form drivers used before ELDs. Each day needs the grid plus the header details: date, carrier name and main office address, truck number, starting odometer, shipping document numbers, co-driver if any, and your total miles for the day. Draw the four duty lines, flag your location at each change of status, total the hours, sign it.

Two practical points drivers miss:

• You're required to have blanks on board. The ELD information packet every truck must carry — under 49 CFR 395.22(h) — includes a user's manual, an instruction sheet for transferring logs to an officer, an instruction sheet for malfunction procedures, and a supply of blank graph-grids for at least 8 days. Check tonight that yours are actually in the truck and not in a drawer at the yard. The manuals can be electronic; the blank grids are the part you'll physically write on.
• Keep the story consistent. Your paper logs should line up with the paper trail you already generate — fuel stops, tolls, scale tickets, BOLs and PODs. An officer who suspects a "creative" reconstruction will compare your grid against exactly those documents, so build the grid from them in the first place.

👮 What do you show at a roadside inspection with a broken ELD?

A malfunctioning ELD is not an automatic violation — hiding one is. At a DOT roadside inspection or a weigh station check, the winning move is to say it up front: "My ELD flagged a malfunction on Tuesday, I reported it, here are my papers." Then hand over, in this order:

1. The device itself — show the malfunction indicator and the code on the screen. If the ELD can still display or print past days, offer that too.
2. Paper logs for the current day and for every day since the malfunction.
3. Records for the previous 7 days — printouts, the ELD display, or your paper reconstruction, whichever covers them.
4. Your written notice to the carrier — the email or message with its date. This is the difference between "driver following 395.34" and "driver with a dead logbook."
5. The ELD information packet — manual and instruction sheets, if asked.

An inspector who sees a documented malfunction, clean paper logs and a dated notice usually writes it up as equipment in the process of repair — the carrier may get a note, you drive on. An inspector who catches an unreported malfunction that's weeks old is looking at a driver with effectively no records of duty status, and that's the kind of finding that can put you out of service on the spot.

⏱️ What's on the carrier's side of the clock?

Once you've reported the malfunction, the ball is in the carrier's court: 8 days to repair, service or replace the ELD, counted from when the malfunction was discovered or reported to them. If the carrier genuinely can't make it — a back-ordered unit, a fleet-wide provider failure — it can ask the FMCSA Division Administrator for an extension, filing within 5 days of your notice and showing a good-faith effort. The FMCSA can grant more time; nobody grants "we'll get to it eventually."

What that means for you in practice: after you send the notice, the follow-up questions are legitimate ones to ask your fleet manager. When is the replacement coming? Should you route through the shop? At ASTEL this is a short conversation — our own repair shop and mechanics are in Chicago, dispatch answers 24/7, and a truck with a dead ELD gets scheduled the way any other defect does, without a driver having to chase anyone for a week. A carrier that shrugs at day six of eight is telling you something about how it treats every other defect too.

⚠️ Which mistakes turn a glitch into a real problem?

The malfunction script is short, and almost every ELD horror story is someone skipping a line of it:

• Riding a broken ELD for weeks. "It's been showing the red wrench for a month" means a month without valid logs. Past the 8-day window with no extension, both driver and carrier are collecting violations every single day.
• Letting unassigned driving pile up. While the device half-works, miles can land in the unassigned pool. Review and claim (or annotate) them daily — a fat unassigned log is one of the first things an auditor opens.
• Uncertified days. Certifying each 24-hour record is your legal signature. A stack of uncertified days reads as "driver doesn't stand behind these logs" at the worst time.
• Verbal-only notice. "I told my dispatcher" with nothing in writing protects exactly nobody — not you, not the carrier.
• No blank grids in the truck. The rule assumes you can start papering immediately. Eight days of blanks weigh nothing; carry them.
• Creative reconstruction. Redrawing last week with more rest than you actually had is falsification — a different and much uglier violation than a broken device.

🛠️ How do you keep an ELD from failing in the first place?

Most malfunctions announce themselves as diagnostics first. A two-minute daily habit catches nearly all of them:

• Glance at the diagnostics indicator every morning and clear or report anything it shows — a code 2 today is a code E next week.
• Certify your logs every day, not in a Friday batch.
• Check unassigned driving daily and claim what's yours.
• After any engine or electrical work, confirm the ELD reconnected to the engine computer and odometer readings match — shop visits are the number-one source of E-codes.
• Mind the hardware: a snug diagnostic-port connector, an intact cable that doesn't get crushed by the seat, a mount that doesn't cook the tablet on the dash all summer.
• Keep the app updated if your ELD runs on a phone or tablet. Bring-your-own-device setups add failure points a hardwired unit doesn't have — dead phone battery, an OS update at midnight, Bluetooth drops — so a BYOD driver should also keep a charger and know where the paper blanks are. A few of the apps drivers already use can double as your evidence kit: photos, notes and timestamps all live in your pocket.

None of this is exotic. It's the same habit as checking your tires: thirty seconds of attention that saves an afternoon of paperwork.

❓ Frequently asked questions

Can I keep driving with a malfunctioning ELD?

Yes. A malfunction does not park the truck; it changes how you record your hours. Switch to paper logs, send your carrier written notice within 24 hours, and keep obeying all hours-of-service limits. The carrier then has 8 days to repair or replace the device.

Do I need paper logs for a data diagnostic event?

No. A data diagnostic event (shown as a digit code) is a data issue you resolve on the device, and the ELD is still compliant. Paper logs are required only for a malfunction (a letter code such as P, E, T, L, R, S or O) that prevents the ELD from properly recording your hours.

How many blank paper logs do I have to carry in the truck?

Enough blank graph-grid sheets to record your duty status for at least 8 days. They are part of the required ELD information packet, together with the user's manual, a data-transfer instruction sheet and a malfunction-procedures sheet.

What if the malfunction wiped out my last 7 days of logs?

Reconstruct them on paper: use the ELD display or printouts if any history survives, plus fuel receipts, bills of lading and dispatch records. If you already have accurate copies of those days, or the ELD can still produce them, you do not need to redraw them.

Will an ELD malfunction give me a violation at an inspection?

Not by itself. If you show the malfunction on the device, current paper logs, records for the previous 7 days and your dated written notice to the carrier, you are following the rule. Violations come from hiding the malfunction, driving for weeks without valid logs or reconstructing days that never happened.

Based on FMCSA regulations as of September 2026 — 49 CFR 395.34 (malfunctions and data diagnostic events), 395.22(h) (ELD information packet and blank grids), 395.8 (paper records of duty status) and Appendix A to Subpart B of Part 395 (malfunction and diagnostic codes) — and FMCSA ELD guidance. Regulations may change; check the current text at fmcsa.dot.gov and your ELD provider's malfunction sheet. Pay and mileage figures describe ASTEL driver ranges, not guarantees. This article is general information, not legal advice.