ELD Malfunction Guide

Who This Applies To

• Drivers who see an ELD malfunction indicator while on the road and need to know the specific steps to take immediately — not at the next stop or terminal.
• Carriers who received a malfunction report from a driver and need to understand the exact response requirements, including the 24-hour notification confirmation and the 8-day repair deadline.
• Fleet managers reviewing paper log records submitted during an ELD malfunction period and checking whether the logs meet FMCSA requirements.
• Compliance managers conducting a post-incident review of a malfunction event that occurred during a roadside inspection and resulted in an enforcement action.
• Dispatchers who need to decide whether to send a driver on the next load segment while the ELD is out of service.
• New carriers building ELD malfunction response procedures and wanting to understand what 49 CFR 395.34 requires in the driver and carrier response timeline.

What To Verify

• Whether the ELD issue is a malfunction or a data diagnostic event — these are different. A malfunction means the device cannot meet FMCSA functional performance specifications, and the driver must switch to paper RODS immediately. A data diagnostic event means the device detected an integrity anomaly (unassigned driving, power disconnect) but may still be recording — the response to each differs.
• The specific regulatory timeline under 49 CFR 395.34: the driver must note the malfunction on current logs; the driver must notify the motor carrier within 24 hours; the carrier must repair or replace the ELD within 8 days of receiving the malfunction report. If the carrier cannot repair within 8 days, an FMCSA extension must be requested before the 8-day window closes.
• What paper RODS must show during the malfunction period. Paper logs must use the standard 24-hour duty-status grid, include all required header fields (driver name, date, carrier name, vehicle unit, starting/ending odometer), and must be annotated with the reason for using paper (ELD malfunction) and the date the malfunction was noted.
• How many days of blank paper log forms the driver must have in the vehicle at all times. FMCSA requires sufficient blank paper logs to record at least 8 days of duty status — this supply must be in the vehicle before a malfunction occurs, not ordered after one is detected.
• Whether the driver can continue operating during the malfunction. Yes — but only while using compliant paper RODS logs. A driver cannot continue operating without compliant records of any kind. If paper logs are not available and the ELD is not functioning, the driver cannot legally continue.
• How the malfunction and paper log period will appear during a roadside inspection. Inspectors accessing the ELD will see a malfunction event in the device log. The driver must show paper RODS for all driving time during the malfunction period and explain the gap in ELD records.

Step-by-Step Overview

1. When an ELD malfunction indicator appears, note the malfunction code, time, and date immediately. If the ELD can still display the duty status grid, capture the most recent records before the malfunction prevents access.
2. Switch to paper RODS immediately for any subsequent driving time. Do not wait until the next stop, the next dispatch check-in, or the next morning. The obligation to maintain compliant records is continuous — paper RODS begin the moment the ELD cannot meet performance specifications.
3. Notify the motor carrier of the malfunction within 24 hours. Document the notification: the exact time it was made, the method (phone call, text, email), and the name of the person notified at the carrier. This documentation may be required during a roadside inspection or audit.
4. The motor carrier must immediately begin the process of repairing or replacing the ELD. The 8-day repair window runs from when the carrier receives the driver's malfunction report — not from when the carrier begins investigating. Confirm with the ELD vendor the repair or replacement timeline.
5. If the 8-day window cannot be met, the carrier must request an extension from the FMCSA Field Service Center before the window closes. The request should identify the specific malfunction, the repair efforts made, and the expected resolution date.
6. After the ELD is repaired or replaced, retain the paper logs from the malfunction period for the standard records retention period — 6 months from the date of creation. Do not discard malfunction-period paper logs once the ELD is back online.

Common Mistakes

• Treating a data diagnostic event as a malfunction and unnecessarily switching to paper logs. Data diagnostic events require driver review and resolution — not a full switch to paper RODS. Confusing the two creates an unjustified paper log period.
• Waiting until the next terminal or overnight stop to start paper logs after a malfunction. The obligation to maintain records is continuous — any driving time after the malfunction is detected and not covered by either a functioning ELD or paper RODS is unaccounted time.
• Not confirming the carrier notification in writing. A driver who verbally told the carrier about a malfunction but has no documentation of when and how the notification was made cannot prove the 24-hour deadline was met.
• Not carrying blank paper log forms before a malfunction occurs. Every vehicle equipped with an ELD should have at least 8 days of blank paper log forms at all times. Discovering there are no paper forms after a malfunction leaves the driver without a compliant fallback.
• Assuming the 8-day repair clock starts when the carrier begins researching the issue. The clock starts when the carrier receives the driver's malfunction notification — slow initial response can leave insufficient time to order, ship, and install a replacement device before the window closes.
• Discarding malfunction-period paper logs after the ELD is repaired. Paper logs from an ELD malfunction period must be retained for 6 months from the date of creation and remain available for inspection even after normal ELD operation resumes.