ELD Unidentified Driving Records – Data Diagnostic Event: Vehicle Movement Without Authenticated Driver

Code Details

Plain-English Meaning

Every ELD driving segment must be attributable to an identified, authenticated driver. When the vehicle moves without any driver logged into the ELD, those segments are stored under an unidentified driver profile. The ELD flags this with a data diagnostic event because unidentified driving time creates an HOS accountability gap — there is no driver record to attach the trip to, and the FMCSA requires that every mile of driving in a regulated CMV be accounted for. The most common legitimate cause is a driver moving the vehicle before completing the ELD login process — for example, pulling forward at a fuel stop before logging in. Yard moves, shop movements, and pre-trip moves within a terminal are also common scenarios. The driver or carrier should review the unidentified driving records, and the responsible driver should claim those records through the ELD's interface. Carriers are required under FMCSA guidance to assign unidentified records to a specific driver when possible.

49 CFR 395 Appendix A and FMCSA ELD guidance specify that driving time under the unidentified driver profile triggers a data diagnostic event when accumulated unidentified driving time exceeds the defined threshold within a 24-hour period. The device displays the event and the driver is expected to review the unidentified records when logging in. FMCSA guidance places an obligation on motor carriers to review unidentified driving records through their back-office systems and to assign them to a driver when the responsible driver can be identified. Records that remain unidentified are subject to FMCSA audit review.

Common Symptoms

• ELD unidentified driving diagnostic event indicator or banner on the device display
• ELD prompts the driver to review and accept or reject unidentified driving records when logging in
• Carrier back-office system shows driving segments with no driver attribution for this vehicle
• Log review reveals a gap between when the engine was running and when a driver authenticated in the ELD
• Multiple short-duration unidentified segments across a day that add up to more than minor movements

Possible Causes

Possible causes may include the items below. The list is not a parts diagnosis.

• Driver moved the vehicle before completing the ELD login — a common occurrence at fuel stops, weigh stations, or the start of a shift
• A different driver moved the vehicle between shifts without logging in — shop move, yard spotting, or test drive without ELD authentication
• ELD was in an unauthenticated state due to a power cycle that required re-login, and the vehicle moved before the driver completed the login sequence
• Engine synchronization or power malfunction prevented the ELD from recognizing the authenticated driver during a period of driving
• Shared-vehicle operation where the outgoing driver logged out but the incoming driver had not yet logged in

First Checks

• Review the unidentified driving records on the ELD — note the time, duration, and location of the unidentified movement to determine which driver was responsible.
• If you were driving during the unidentified period, accept and claim those records through the ELD's review interface; the records will move to your log under the appropriate edit annotation.
• If the movement was a legitimate non-HOS operation (yard move, personal conveyance, shop move), annotate accordingly using the ELD's approved exception workflow.
• If the unidentified movement cannot be attributed to any driver, the carrier's safety department must review the records and follow the FMCSA unidentified-driving assignment procedures.
• Review pre-trip and log-in procedures with the driver to prevent future occurrences — the root cause is almost always a login that did not happen before the vehicle moved.

Can I Keep Driving?

This is an HOS record attribution issue, not a vehicle safety condition. The vehicle operates normally. Unidentified driving records should be reviewed and resolved promptly because they represent unaccounted driving time in the regulatory HOS record.

Related Lookup Pages

• Electronic Logging Device fault codes
• ELD Malfunction Indicator symptom page
• Search this code