395.15(f): Onboard Recording Device Reconstruction Failure

What happens when you're cited for failing to reconstruct onboard recording device data. Rare violation with low out-of-service rate—here's what you need to know.

Severity Weight
5
OOS Eligible
No
BASIC Category
Hours of Service
Code System
FMCSR
Code:
395.15(f)
Code System:
FMCSR
BASIC Category:
Hours of Service
OOS Eligible:
No
Severity Weight:
5
Violation Group:
Incomplete/Wrong Log

Ranks #1,714 of 3,146 FMCSR codes by citation frequency • OOS rate of 4.9% is below the FMCSR-wide average of 33.3%.

Violation Description

Onboard recording device failure: Driver failed to reconstruct info

In-Depth Explainer

Grounded in TruckCodex roadside-inspection data

What 395.15(f) means in plain language

When a commercial vehicle is equipped with an onboard recording device (also called an electronic logging device or ELD), federal regulations require that drivers maintain accurate records of their hours of service. Code 395.15(f) is cited when an inspector finds that a driver was unable to reconstruct or provide the required information from that device during a roadside inspection.

In practical terms, this means the inspector asked you to produce or explain your duty-status records from your ELD, and you couldn't do it—either the data wasn't accessible, you didn't know how to pull it up, or the device had a malfunction you hadn't documented properly. The regulation expects that even if the device fails, a driver must be able to manually reconstruct what their hours were during the period in question.

This is different from simply having a broken ELD. The violation specifically centers on your failure to reconstruct or provide that information when asked. If your device is down but you've kept manual records or can accurately recall and document your duty status, you're in a much stronger position.

What our enforcement data actually shows

Across our 13 million inspection records, 395.15(f) is a rare citation. Our database shows 41 all-time citations for this code, with zero citations in the last 12 months and zero in the last 90 days. This places 395.15(f) at rank #1687 out of 3,036 FMCSR codes by citation volume.

When drivers are cited for this violation, the out-of-service rate is 4.9%—meaning only 2 of the 41 citations resulted in a vehicle or driver being placed out of service. By contrast, the all-FMCSR average out-of-service rate is 31.4%, so 395.15(f) citations are significantly less likely to trigger an immediate removal from service. This reflects the fact that reconstruction failures are often remedial issues rather than safety-critical conditions.

The extremely low enforcement volume in recent periods suggests that either drivers and carriers have largely resolved reconstruction-related problems, or inspectors are encountering this situation infrequently—possibly because modern ELDs are more reliable and driver familiarity with them has improved.

Who gets cited most

Our inspection records do not provide sufficient state-level or geographic breakdown for this code to name top states with confidence. However, the carriers cited for this violation show a scattered pattern: BIZ TRUCKING LLC (USDOT 2401154) accounts for 2 citations, and nine other carriers have one citation each. This distribution suggests the violation is not concentrated in any single fleet operation but appears sporadically across different carrier sizes and types.

The vehicle makes cited for 395.15(f) include a mix of trailers and tractors: Fruehauf (FRHT) appears most often with 6 citations, followed by Reitnouer (REITNOUER) with 4, and Utility (UTIL) and Freightliner (FREIGHTLIN) with 3 each. This variety indicates the violation is not specific to a particular equipment type, but rather reflects the random sample of vehicles inspected.

How severe is this compared to similar codes

Inspectors group 395.15(f) within the broader Hours of Service category. Our data shows stark contrasts with peer violations:

395.24 — HOS (ELD) Form and Manner has logged 106,486 citations (roughly 2,600 times more than 395.15(f)) with a 0.0% out-of-service rate. This code covers broader ELD compliance issues and is far more common, yet rarely leads to out-of-service action.

395.8A1-HOSP — Failing to have a record of duty status using the prescribed method accounts for 52,266 citations with a 92.9% out-of-service rate—meaning drivers cited for this are almost always removed from service. This is a much more serious violation, as it reflects a fundamental failure to maintain records at all, rather than a failure to reconstruct from an existing device.

395.8(e)(1) has 78,276 citations with a 26.0% out-of-service rate, indicating stronger enforcement action than 395.15(f) but far less severe than codes involving outright absence of records.

In context, 395.15(f) sits near the lower end of severity within Hours of Service violations. The 4.9% out-of-service rate reflects that inspectors and enforcement typically treat reconstruction failures as fixable compliance gaps rather than imminent safety hazards.

How to avoid it

Reconstruction failure boils down to being able to explain and document your duty status when asked. Here are concrete steps to take before and during every shift:

  • Test your ELD before every trip. Power it on, log in, and pull up the last few days of records. If you can't see them on screen, the device may have a connectivity or sync issue that needs immediate attention—don't drive until you resolve it or have a manual backup ready.

  • Know how to export or screenshot your records. Familiarize yourself with your ELD's function to generate a summary or export of hours. Print or save the last 7–8 days of records to your phone or a document before you start a long haul. If your device fails mid-trip, you have proof.

  • Keep a written log as backup. Even modern drivers should carry a pen and paper logbook entry for each day, noting your on-duty times, off-duty breaks, and drive time. This is your insurance if the ELD drops offline.

  • Report device malfunctions immediately to your fleet manager. If your ELD is slow, won't sync, shows gaps, or crashes, don't ignore it. Document the malfunction date and time so you have a record to show an inspector. Many regulations allow reasonable reconstruction if you can prove the device was faulty.

  • During an inspection, stay calm and ask for a moment. If an inspector asks you to pull up your records and your ELD is sluggish or offline, explain what's happening clearly. Offer your manual notes or backup files. Cooperation and transparency often result in a warning rather than a citation, especially for a code this infrequent.

The intent of 395.15(f) is not to punish you for equipment failure—it's to ensure you can account for your time behind the wheel. If you can reconstruct that account through any reliable means, you're protected.

Last updated: 2026-04-20T15:57:19.667Z Based on TruckCodex inspection data See 395.15(f) Q&A → Fleet FAQ →

Data sources & freshness

TruckCodex aggregates official public-sector datasets. See the Source registry for dataset-level coverage and the Freshness log for last-import timestamps.

Census, SAFER, SMS, Licensing & Insurance (L&I), roadside inspections, crashes, and authority history.

Refreshed daily.

Vehicle recall campaigns, defect investigations, and consumer safety complaints (SCRS).

Refreshed daily.
EIA

Retail diesel and gasoline price history and state fuel-tax tables.

Refreshed weekly.

Cross-border carrier registry and Canadian recall campaigns where applicable.

Refreshed weekly.

TruckCodex is an independent aggregator; it is not affiliated with FMCSA, NHTSA, EIA, or Transport Canada. Always verify compliance-critical information directly with the originating agency.