ELD & Hours of Service • ELDT.LIVE
Daylight Saving Time Ends: What the Repeated Hour Means for ELD Logs
The November 1 clock change repeats the 1 a.m. hour, but it does not create extra driving time or reset a commercial driver's HOS limits.
Most of the United States returned to standard time
Daylight saving time ended at 2 a.m. local time on Sunday, November 1, 2026. In areas that observe the change, the clock moved back to 1 a.m., so that hour appeared twice. Hawaii, most of Arizona, and several U.S. territories do not observe daylight saving time. Drivers crossing state or time-zone boundaries should confirm which clock a shipper, receiver, dispatch office, and home terminal are using.
A compliant ELD is designed to account for the change
Federal ELD specifications require a device to capture date and time in Coordinated Universal Time and convert it to the time standard in effect at the driver's home terminal. The specification expressly requires the conversion to take daylight saving time into account. FMCSA guidance says the UTC offset should include daylight saving time only while it is in effect at the home terminal.
The repeated hour does not add legal driving time
Moving the wall clock backward does not give a driver a twelfth driving hour, extend the 14-hour window, shorten the required 10 consecutive hours off duty, or restart a 60- or 70-hour calculation. Those limits depend on actual elapsed driving, on-duty, and off-duty time. The ELD's underlying UTC records preserve the sequence even when the displayed local hour repeats.
Logs remain tied to the home terminal's time standard
A driver's record of duty status uses the time standard in effect at the home terminal, not the local clock at every point along the route. A driver based at a Central Time terminal may therefore show Central time during an inspection in another zone. The carrier's home-terminal configuration and 24-hour starting time should remain consistent unless the carrier makes a legitimate configuration change.
Delivery appointments still need an explicit time zone
ELD time and customer appointment time are separate planning issues. Shippers and receivers generally schedule by their local clock, while the driver's log is displayed in home-terminal time. Dispatch messages such as 'deliver at 0600' should identify the time zone, especially for overnight trips that crossed the November 1 change or a geographic time-zone boundary.
Check the device instead of inventing a correction
Drivers should review the ELD header, duty-status graph, event sequence, and remaining-hours display after the transition. A repeated 1 a.m. label can be normal; a missing interval, incorrect home-terminal zone, unexpected offset, or changed event order may indicate a configuration or device problem. Do not create a false duty-status entry merely to make the display look familiar.
Follow the malfunction process if the record is actually wrong
If the ELD cannot accurately record or present required data, the driver must note the malfunction, notify the motor carrier within 24 hours, and reconstruct the current day and previous seven days when required under 49 CFR 395.34. The carrier generally has eight days from discovery or notification to repair, replace, or service the device, unless FMCSA grants more time. Keep the required paper logs or equivalent blank records available for a genuine malfunction.
What drivers and dispatchers should verify today
Confirm the home-terminal time zone in the driver profile; compare the ELD clock with an authoritative time source; verify that the UTC offset changed only where daylight saving time is observed; label pickup and delivery appointments with a time zone; recalculate estimated arrival using elapsed time; and preserve accurate records. If anything looks inconsistent, contact the carrier's ELD support process before accepting an unsafe or impossible schedule.
The clock change is a compliance check, not an HOS exception
No special federal hours-of-service exception is created by the end of daylight saving time. Carriers should not schedule an extra hour of driving because a wall clock repeated an hour, and drivers should not certify a log they know is inaccurate. The safe approach is to plan with elapsed time, verify the device output, and document any real malfunction through the existing federal process.
Educational summaries help you prepare, but official FMCSA and state licensing sources remain the authority for current requirements.
Official sources
NIST — Daylight Saving Time Rules for 2026 ↗U.S. Department of Transportation — Daylight Saving Time ↗FMCSA — ELD UTC Offset and Daylight Saving Time Guidance ↗49 CFR Part 395, Appendix A — ELD Functional Specifications ↗49 CFR 395.34 — ELD Malfunctions and Data Diagnostic Events ↗ELDT.live independently creates and reviews its content. We do not present practice questions as official examination questions and do not guarantee a licensing result.