ELD Malfunctions: Paper Logs, 8-Day Repair Rule and Reporting

At 05:50 the cab display in truck 4417 lights its malfunction indicator. The driver photographs the screen, texts dispatch and starts the first stop of the day. Dispatch plans the afternoon reload from hours shown on the back-office portal, which stopped updating at midnight. By early afternoon the driver is at a weigh station with no paper logs for the previous week, no blank graph-grids in the cab and no record that the carrier was ever told in writing.

ELD malfunction rules are short, but they bind two parties on two separate clocks. The driver has 24 hours to give written notice and must keep paper records until the device is fixed; the carrier has 8 days to correct the malfunction, or 5 days to ask FMCSA for more time. Run both clocks from one ticket, and a failed device costs a few hours of paperwork instead of a violation, a stranded load and a hole in your detention evidence.

• What this guide covers: the malfunction and data diagnostic codes, the driver duties in 49 CFR 395.34(a), the in-cab packet in 395.22(h), the repair and extension clocks in 395.34(d), and dispatch planning while a truck runs on paper.
• What it adds: a worked repair calendar, a malfunction ticket payload, a timestamped roadside failure, a cost model for one episode, and questions for your ELD provider before renewal.

Malfunction or data diagnostic: reading the cab indicator

A malfunction means the device can no longer be trusted to record hours, so paper takes over; a data diagnostic event is a warning about data quality that the driver resolves with the carrier and provider. The regulation gives each its own indicator, and treating a diagnostic as a malfunction, or the reverse, is the most common first mistake.

Appendix A to subpart B of Part 395 requires a single visual malfunction indicator for all drivers, visible from the normal driving position and continuously communicated while the device is powered. Data diagnostic status has a separate indicator, and it applies only to the driver logged in. Table 4 of the appendix assigns letter codes to malfunctions and number codes to diagnostic events, and each comes from a monitoring rule in section 4.6.1.

The code letters above are the standard set in Table 4, which the eCFR publishes as an image. Table 4 also reserves code O for other ELD-detected malfunctions, which is where the technology-specific checks a provider adds under section 4.6.1.8 surface. Whatever your provider's screen calls them, record the code on the ticket, because the extension request and the repair record both need to say what failed.

The driver's first 24 hours under 49 CFR 395.34(a)

When a malfunction is set, the driver has three duties: note it and give the carrier written notice within 24 hours, reconstruct the current 24-hour period and the previous 7 consecutive days on graph-grid paper logs, and keep logging on paper until the device is repaired. Nothing in the section requires the truck to stop.

The reconstruction duty has an exception that saves most drivers an hour of copying. Under 395.34(a)(2), the driver need not rebuild the prior records if the driver already possesses them or they are retrievable from the ELD. A provider app that can still display or print the last seven days counts; a tablet that will not power on usually does not, unless the records can be pulled from the provider's server to the driver.

ELD malfunction handling under 49 CFR 395.34(a) requires written notice to the motor carrier within 24 hours and paper records of duty status for the current day plus the previous 7 consecutive days, unless retrievable from the ELD, so a driver must carry graph-grids covering at least 8 days.

The paper logs must follow 49 CFR 395.8, which sets the four duty statuses, the graph grid and the fields that sit beside it. Drivers who have not used paper since training forget the side fields more often than the grid itself.

• Header fields: date, total miles driving today, truck or tractor and trailer number, name of carrier and main office address, as listed in 395.8(d).
• Grid and totals: the 24-hour period starting time, each duty change on the grid, and total hours at the far right edge.
• Location remarks: city, town or village with state abbreviation for each change of duty status, as 395.8(c) requires.
• Load and crew fields: shipping document numbers or shipper and commodity, the co-driver's name, and the driver's signature or certification.

What must already be in the cab before a device fails

The malfunction response depends on paper that has to be in the truck before anything breaks. Section 395.22(h) makes the carrier responsible for an ELD information packet in every vehicle, and the blank graph-grids in that packet are the item most often missing at roadside.

• User's manual: a manual describing how to operate the ELD, which may be electronic.
• Transfer instruction sheet: step-by-step instructions to produce and transfer the driver's records to an authorized safety official, by every method the device supports.
• Malfunction instruction sheet: the reporting requirements and recordkeeping procedures during a malfunction, which should name your own notice form and contact.
• Blank graph-grids: a supply sufficient to record duty status and related information for a minimum of 8 days.

Make the packet a line on the vehicle inspection checklist rather than a driver responsibility. A missing pad found in the yard costs one minute; the same gap found by an inspector costs a violation and, for a driver without records, the day's remaining freight.

The carrier's eight-day repair clock and five-day extension request

The carrier must take action to correct the malfunction within 8 days of discovering it or of the driver's notice, whichever comes first. If repair will take longer, the carrier must ask the FMCSA Division Administrator for the state of its principal place of business within 5 days after the driver's notice.

Count from the earlier date. If a maintenance technician sees the indicator on Monday and the driver's written notice arrives on Tuesday, the 8 days run from Monday. A fleet that waits for the driver's form loses a day it never notices, and the dates on the repair work order become the evidence of when the clock started.

{
  "ticket_id": "ELD-MAL-2026-1103-4417",
  "unit": "4417",
  "eld": { "make": "per registration", "model": "per registration", "serial": "SN-77C1904" },
  "malfunction_code": "R",
  "discovered_at": "2026-11-03T05:50:00-06:00",
  "driver_written_notice_at": "2026-11-03T08:15:00-06:00",
  "clock_start": "min(discovered_at, driver_written_notice_at)  -> 2026-11-03",
  "repair_due": "clock_start + 8 days  -> 2026-11-11",
  "extension_request_due": "driver_written_notice_at + 5 days  -> 2026-11-08",
  "paper_logs": { "reconstructed_days": 8, "source": "provider portal printout", "grid_pads_in_cab": true },
  "extension": { "needed": false, "addressee": "FMCSA Division Administrator, state of principal place of business" },
  "closed_when": "device serviced AND no active malfunction AND paper records filed with carrier"
}

Because 8 November 2026 falls on a Sunday, a carrier that may need more time should send its request by Friday 6 November. The regulation counts days, not business days, so plan as though weekends count. Section 395.34(d)(5) treats a carrier that has sent a compliant request as meeting the ELD requirement until FMCSA decides, provided paper logging continues.

• Representative details: name, address and telephone number of the carrier representative filing the request, per 395.34(d)(2)(i).
• Device details: make, model and serial number of each affected ELD, per (d)(2)(ii).
• Failure details: date and location of each malfunction as the driver reported it, per (d)(2)(iii).
• Good-faith statement: a concise account of repair, replacement or service efforts and why more than 8 days is needed, per (d)(2)(iv), signed by the carrier.

Diagnostic events that clear and diagnostics that escalate

Most data diagnostic events clear once the cause is fixed, but three of them are early warnings of a malfunction with a fixed escalation path. Watching those three daily lets the carrier act before paper logs become mandatory.

Unidentified driving is the clearest example. Under section 4.6.1.6 of Appendix A, more than 30 minutes of unidentified driving in 24 hours sets a diagnostic event for every driver logged into that ELD, and it clears only when unidentified driving over the current 24 hours and previous 7 days drops to 15 minutes or less. Review and annotation of that time follow 395.32, which sibling guides cover in depth.

• Data transfer escalation: the device checks its transfer mechanism at least every 7 days; after a failure it checks every 24 hours, and three more consecutive failures set malfunction S.
• Engine data escalation: a diagnostic event is recorded when engine values cannot be acquired within 5 seconds of need, and a malfunction E follows once the connection has been lost for more than 30 minutes in 24 hours.
• Power escalation: a power diagnostic event marks possible missed records, and malfunction P follows when understated driving reaches 30 minutes in 24 hours across all profiles.
• Missing data elements: diagnostic code 3 flags a required field missing at recording; it does not escalate on its own but signals a configuration or sensor gap worth a ticket.

Data transfer monitoring under section 4.6.1.7 of Appendix A to Part 395 subpart B runs at least every 7 days, tightens to every 24 hours after a failed check, and sets malfunction code S after three further consecutive failures, giving a fleet roughly 3 days to fix transfer before paper logs start.

A daily exception report sorted by these escalation paths gives maintenance a two-to-five-day head start on most malfunctions. The fleet that only reacts to the malfunction indicator spends that head start on paperwork instead.

Who records, repairs and signs off during a malfunction

Name one owner for each record the episode creates, because the driver, maintenance, safety and dispatch each hold a piece and the extension request needs all of them on one page within 5 days.

The 13-day submission and 6-month retention come from 395.8(a)(2)(ii) and 395.8(k)(1). They matter here because paper logs from a malfunction are filed outside the ELD back office, and an auditor reviewing that week will look for them in the same place as the device's records.

Dispatch and yard planning while a truck runs on paper

While a truck is on paper logs, dispatch loses the live hours feed, so the plan must come from the driver's paper totals read back by phone at each duty change. The 11-hour driving limit, the 14-hour window and the 30-minute break in 49 CFR 395.3 still apply exactly as before.

The detention and layover record is the quieter casualty. ELD arrival and departure events are often the evidence behind a detention bill, as the detention and layover billing audit guide describes. That guide audits the charge; this one keeps the record alive when the device fails, by asking drivers to write arrival and release times in the paper log remarks and to photograph signed in and out times on the bill of lading.

1. Tue 05:50, indicator on: unit 4417 shows malfunction R; the tablet freezes on reboot. The driver texts a photo to dispatch but completes no notice form.
2. Tue 06:20, stale plan: the dispatcher books reload LD-30871 for 15:00 using the portal's last sync at 00:04, which shows 9 hours 40 minutes of driving left.
3. Tue 13:35, roadside inspection: the driver has no records for the previous 7 days, cannot retrieve them from the dead tablet, and the cab has no graph-grid pad.
4. Tue 14:10, load reassigned: the driver cannot continue until records are produced; LD-30871 moves to another truck with a $420 empty repositioning cost and a missed 15:00 appointment.
5. Controlled version: the ticket opens at 05:55 from the driver's photo, safety prints the 7 prior days from the provider portal to the next yard, the cab pad covers today, and dispatch replans LD-30871 from read-back totals.

Yard moves need the same discipline. A driver on paper who shunts trailers between doors must log those moves as on-duty time, because the device that would normally classify them is down. The hours-of-service dispatch SOP covers the gate and dock steps that keep these moves visible.

Counting the cost of one malfunction episode

A single malfunction handled well costs a few hundred dollars in parts and staff time; handled badly, it costs a lost load, a violation and a week of weaker detention claims. The illustrative figures below compare the two paths for one tractor in a 120-truck fleet.

The gap of $1,090 per episode excludes any civil penalty, which depends on the enforcement outcome and is not estimated here. Across a fleet that sees eight malfunctions a year, the ticket path saves roughly $8,700, more than the annual cost of spare display units held at two yards.

Carrier repair of an ELD malfunction under 49 CFR 395.34(d)(1) must start within 8 days of discovery or driver notice, whichever is earlier, and an extension request reaches the FMCSA Division Administrator within 5 days; a fleet holding spare units can usually close the ticket within 1 to 2 days.

Monitoring a fleet can automate and judgements it should keep

Clocks, counts and missing-document checks can run automatically from the ELD provider's event feed; deciding whether records are retrievable, whether a repair effort is in good faith, and what the driver may still drive needs a person.

An AI model that reads a photo of a paper log is useful to a dispatcher at 06:00, but it cannot certify anything. The driver's signed paper log stays the legal record until the device is repaired, and any figure the model extracts must be confirmed against it.

Testing an ELD provider's malfunction support before renewal

Judge an ELD provider by how it behaves on a bad day: how fast it surfaces a malfunction to the back office, whether records stay retrievable when the cab unit fails, and how quickly it ships a replacement. Test those points in writing before you renew.

For more on the hours rules behind dispatch planning, see the hours-of-service dispatch architecture guide and the wider logistics and supply chain library. If you are replacing an ELD provider or tying malfunction tickets into your TMS and maintenance system, you can share your requirements with us and we will scope the integration.