Listen to an in-depth podcast of this post
A walk through what last night’s fall-back clock change actually means for a small fleet: why the repeated 1 a.m. hour on the ELD isn’t a violation, and why the last route of the day now quietly ends in the most dangerous hour of the day for pedestrians.
- Federal ELD rules (49 CFR Part 395, Appendix A to Subpart B, Section 4.4.3) require every ELD to convert and track time in UTC, then display it using the time standard in effect at the driver’s home terminal — “taking the daylight savings time changes into account.” That’s why the 1:00–1:59 a.m. hour on fall-back night shows up twice on a local-time log; the underlying UTC timestamps never repeat or run backward.
- 49 CFR 395.8(f)(8)(i) requires a record of duty status to be “prepared, maintained, and submitted using the time standard in effect at the driver’s home terminal” — so the repeated local hour is the format the rule itself mandates, not a data error. A genuine ELD “timing compliance malfunction” under 49 CFR 395.34 is a different, narrower problem: the device’s internal clock drifting more than 10 minutes off UTC.
- NHTSA’s 2024 Traffic Safety Facts report on pedestrians (DOT HS 813 818, published June 2026) counted 7,080 pedestrian deaths nationwide — one every 74 minutes — and found 76 percent of them happened in the dark, versus 20 percent in daylight, 2 percent at dusk, and 2 percent at dawn.
- IIHS (April 2025) found that in the weeks after clocks fall back, fatal crashes involving pedestrians and bicyclists rise about 13 percent while fatal crashes involving vehicle occupants fall about 7 percent — a pattern IIHS president David Harkey attributed to the sudden loss of evening daylight, not the time change itself. After the spring-forward switch, pedestrian and cyclist deaths fall about 24 percent in that same kind of before/after window.
- A route or stop that wrapped up at 5:30 p.m. in daylight last week wraps up at the same clock time tonight — after sunset, in the same hour the data above says is now the most dangerous hour on the road for anyone on foot near the truck.
At 2:00 a.m. local time this morning, clocks across the country fell back an hour. On a commercial driver’s electronic log, that means the hour between 1:00 and 1:59 a.m. happened twice.
That repeated hour isn’t a violation and isn’t an ELD malfunction — the rule requires it. The part of today’s clock change that actually matters for a small fleet is quieter: the last route of the day now ends an hour earlier in the dark, during the window when 76 percent of pedestrian deaths happen.

The Repeated Hour on the ELD Isn’t a Violation — Here’s the Rule That Requires It
Appendix A to Subpart B of 49 CFR Part 395 — the ELD functional specifications — tells every device exactly how to handle today’s clock change. Section 4.4.3, “Date and Time Conversions,” requires an ELD to “convert and track date and time captured in UTC standard to the time standard in effect at [the] driver’s home terminal,” explicitly “taking the daylight savings time changes into account.”
In practice, that’s why an overnight driver’s local-time display can show the 1:00 a.m. hour twice on fall-back night: the device’s underlying record never stops moving forward in UTC, but the home-terminal clock it’s required to display did just reset by an hour. 49 CFR 395.8(f)(8)(i) requires the record of duty status itself to be “prepared, maintained, and submitted using the time standard in effect at the driver’s home terminal” — so that local, DST-adjusted display is the format the rule demands, not a glitch in it.
A genuine ELD problem — a “timing compliance malfunction” under 49 CFR 395.34 — is a different and narrower failure: the device’s clock drifting more than 10 minutes off UTC. A log that shows an overlapping or seemingly backward hour once a year, on the one night the rule itself accounts for, doesn’t meet that bar, and treating it as a malfunction wastes a driver’s time reconstructing paper logs for nothing.

The Hour Nobody Notices Losing: Why Tonight’s Last Stop Is More Dangerous Than Last Week’s
NHTSA’s newest Traffic Safety Facts report on pedestrians (DOT HS 813 818, data year 2024, published June 2026) counted 7,080 pedestrian deaths nationwide — a person killed roughly every 74 minutes. Seventy-six percent of those deaths happened in the dark, compared with 20 percent in daylight, 2 percent at dusk, and 2 percent at dawn.
IIHS’s own before/after analysis of crash data around each clock change, published in April 2025, found that fatal crashes involving pedestrians and bicyclists rise about 13 percent in the weeks following the fall-back switch to standard time, while fatal crashes involving vehicle occupants fall about 7 percent over the same stretch. IIHS president David Harkey tied the swing to the sudden drop in evening daylight rather than to the clock change itself — the spring-forward switch, which adds an hour of evening light, sees pedestrian and cyclist deaths fall about 24 percent in that same kind of window.
None of that changes the clock on a dispatch board. A route, a last delivery stop, or a service call that wrapped up at 5:30 p.m. in daylight last week wraps up at 5:30 p.m. tonight — after sunset, in the same window where the deaths above are concentrated.

What Actually Changes at Dispatch This Week
As the Responsible Fleet team sees it, the clock change deserves two separate, concrete actions — not one vague reminder to “be careful out there.” The first: brief drivers and anyone who audits logs that a repeated 1:00 a.m. hour on fall-back night is expected, not a malfunction, so nobody burns a shift reconstructing paper records of duty status over a non-issue.
The second is the one that actually moves risk: any route whose last stop was scheduled for daylight now finishes in the dark at the same clock time, without the schedule ever being touched. For routes that end near schools, retail areas, residential pickups, or anywhere pedestrians cross near the truck, that’s worth a look at whether the last stop should move earlier, or whether headlight, mirror, and backup-camera checks need to move up the pre-trip list for the darker months ahead.
Neither fix costs anything beyond a five-minute dispatch conversation. Both come directly from what the rule already requires (49 CFR 395, Appendix A to Subpart B, Section 4.4.3) and what the federal and independent crash data already show (NHTSA DOT HS 813 818; IIHS, April 2025) — not from guesswork about what daylight saving time “probably” does to a fleet.

What most small fleets get wrong
As the Responsible Fleet team sees it, most small fleets get the clock change backward: they treat the repeated ELD hour as the real problem and the earlier darkness as a non-event. It’s the other way around.
The repeated hour is accounted for by the rule itself (49 CFR 395, Appendix A to Subpart B, Section 4.4.3) and resolves itself with no action needed. The earlier darkness isn’t accounted for by anything — it just happens to a schedule nobody adjusted, in the same hour NHTSA’s own data says is the deadliest for anyone outside a vehicle.
Frequently asked questions
Does the 1:00 a.m. hour repeating on a driver’s ELD count as a hours-of-service violation?
No. 49 CFR Part 395, Appendix A to Subpart B, Section 4.4.3 specifically requires ELDs to convert UTC time to the home terminal’s local time standard “taking the daylight savings time changes into account” — the repeated hour on fall-back night is the rule working as designed, not a data error.
What’s the difference between that repeated hour and an actual ELD “timing compliance malfunction”?
A timing compliance malfunction under 49 CFR 395.34 is the device’s internal clock drifting more than 10 minutes off UTC. The DST-driven repeated local hour doesn’t involve any drift in the underlying UTC record, so it doesn’t meet that definition.
How much more dangerous is driving after the fall-back time change, according to the data?
IIHS’s April 2025 analysis found fatal pedestrian and bicyclist crashes rise about 13 percent in the weeks after clocks fall back, while fatal vehicle-occupant crashes fall about 7 percent over the same period — a pattern tied to the loss of evening daylight rather than the clock change itself.
Does the same risk apply in reverse when clocks “spring forward”?
IIHS found the opposite pattern in spring: pedestrian and cyclist deaths fall about 24 percent in the weeks after the spring-forward switch, when evenings gain an hour of daylight instead of losing it.
What should a small fleet actually do differently this week?
Two things: confirm drivers and anyone reviewing logs know the repeated ELD hour isn’t a malfunction, and check whether any route’s last stop — especially near schools, retail areas, or pedestrian crossings — now finishes after dark at the same clock time it used to finish in daylight.
The bottom line
The Responsible Fleet team’s take: today’s clock change created one problem that’s already solved by the rule itself, and one that isn’t solved by anything unless a dispatcher actually looks at it.
The repeated ELD hour needs no action — 49 CFR 395, Appendix A to Subpart B, Section 4.4.3 already accounts for it. The last route ending in the dark does need a look, because NHTSA’s own numbers (DOT HS 813 818) and IIHS’s April 2025 findings agree that the hour after sunset is exactly when pedestrian risk is highest.
Want visibility into every load and every truck without juggling spreadsheets?
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.
