Violation code

395.22(b)(2)(ii)

Motor carrier failed to include required user identification data in ELD account

Hours-of-Service Compliance1Non-OOS· SMS Appendix A v3.20

395.22(b)(2)(ii) is a Other Log/Form & Manner violation under 49 CFR §395.22(b)(2)(ii). It falls in the Hours-of-Service Compliance BASIC with a severity weight of 1/10. Nationally it was cited 1,708 times in the last five years, with an OOS rate of 0.0%.

📊

National roadside inspection stats

as of 6/20/2026

Inspections

1,674

that found this code

Violations

1,708

total written

OOS rate

0.0%

0 OOS

Source: FMCSA roadside inspection data (last 5 years). The OOS rate is the share of these violations that led the officer to mark the driver or vehicle out of service.

Violation group: Other Log/Form & Manner
Regulation §: 395.22(b)(2)(ii)
Severity weight: 1
Used in SMS: Yes
Status: Active
Updated: 6/20/2026

Last updated June 2026

⚡

Think this violation was written incorrectly?

Generate a polished DataQs challenge letter for 395.22(b)(2)(ii) in about 5 seconds. AI quotes the CFR, predicts your grant chance.

⚡ Draft a challenge →

Notes

DSMS: N | Comment: Added in 3.13 | Footnote: This violation was added to SMS with the December 31, 2021 snapshot.

📚

Challenging 395.22(b)(2)(ii) through FMCSA DataQs

If this violation was written incorrectly, here are the angles trucking-safety managers use to contest it. Playbook: Hours of Service.

Relevant 49 CFR49 CFR § 395.22

Motor carrier responsibilities — ELDs

“A motor carrier must ensure that its drivers use an ELD to record the driver's record of duty status, except for drivers permitted to use paper records of duty status or grandfathered AOBRDs in accordance with §395.8.”

Common ways to challenge this code

ELD malfunction or edit-history defect
The ELD device produced or recorded incorrect duty-status data because of a malfunction, time-zone defect, or edit-history that overwrites driver entries.
Evidence that wins
- ✓ELD malfunction report (date stamped)
- ✓ELD edit history export covering the day of inspection
- ✓Manufacturer support ticket or replacement record
Time was Personal Conveyance, not driving
The duty time the officer flagged was actually Personal Conveyance under FMCSA Regulatory Guidance, and qualifies as off-duty.
Evidence that wins
- ✓ELD record showing Personal Conveyance status
- ✓Trip context (driver heading home / to lodging after relief)
- ✓Carrier Personal Conveyance policy
Adverse driving conditions exception
Driving time exceeded the 11-hour limit because adverse driving conditions extended the maximum driving window by up to 2 hours under §395.1(b)(1).
Evidence that wins
- ✓Weather report or road-closure record for the route
- ✓Driver's contemporaneous note in the log
- ✓Dispatch / load record showing planned arrival before adverse conditions
Sleeper-berth split timing
A 7/3 or 8/2 sleeper-berth split was correctly applied and resets the 14-hour driving window, but was scored as a continuous driving violation.
Evidence that wins
- ✓ELD record showing the two sleeper berth periods
- ✓Time-stamped duty-status changes

Common pitfalls — avoid these

⚠Submitting screenshots instead of the official ELD-mandated data file export
⚠Not asking for the ELD-edit-suggestions log that the driver may have rejected

⚡ Draft a challenge for 395.22(b)(2)(ii) →Read the DataQs guide first

More codes in Hours-of-Service Compliance

Same BASIC category — ranked by national citation volume

View all Hours-of-Service Compliance codes →

Other Other Log/Form & Manner codes

Codes under the same FMCSA violation group

❓

Frequently asked questions about 395.22(b)(2)(ii)

What does violation 395.22(b)(2)(ii) mean?

395.22(b)(2)(ii) is the FMCSA roadside-inspection violation code for "Motor carrier failed to include required user identification data in ELD account", part of the Other Log/Form & Manner group, cited under 49 CFR §395.22(b)(2)(ii).

What BASIC does 395.22(b)(2)(ii) affect?

395.22(b)(2)(ii) falls under the Hours-of-Service Compliance BASIC in the FMCSA Safety Measurement System (SMS).

What is the CSA severity weight of 395.22(b)(2)(ii)?

395.22(b)(2)(ii) carries a severity weight of 1 out of 10. Higher weights indicate violations more closely tied to crash risk, and they count more toward a carrier's Hours-of-Service Compliance score.

Is 395.22(b)(2)(ii) an out-of-service (OOS) violation?

No. 395.22(b)(2)(ii) is not an out-of-service violation, so on its own it does not trigger an out-of-service order at the roadside.

How many CSA points does 395.22(b)(2)(ii) add to a carrier's score?

The point contribution of 395.22(b)(2)(ii) depends on its severity weight (1/10) multiplied by a time weight of 3, 2, or 1 based on how recent the inspection is. You can calculate the exact contribution with the CSA points calculator.

Can 395.22(b)(2)(ii) be challenged through DataQs?

Yes. If you believe 395.22(b)(2)(ii) was recorded in error, you can file a Request for Data Review (RDR) through the FMCSA DataQs system with supporting evidence. A successful challenge can remove or correct the violation on your record.

Keep going

CSA points calculator How to challenge a violation Draft a DataQs letter for 395.22(b)(2)(ii)Hours-of-Service Compliance BASIC Carrier CSA lookup CSA glossary

395.22(b)(2)(ii)

National roadside inspection stats

Challenging 395.22(b)(2)(ii) through FMCSA DataQs

ELD malfunction or edit-history defect

Time was Personal Conveyance, not driving

Adverse driving conditions exception

Sleeper-berth split timing