CSA
Violation code

395.5(a)(2)

15 - hour rule violation (Passenger)

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

395.5(a)(2) is a Hours violation under 49 CFR §395.5(a)(2). It falls in the Hours-of-Service Compliance BASIC with a severity weight of 7/10.

Violation group
Hours
Regulation §
395.5(a)(2)
Severity weight
7
Used in SMS
Yes
Status
Active
Updated
5/15/2026

Last updated May 2026

⚡

Think this violation was written incorrectly?

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

⚡ Draft a challenge →

Notes

DSMS: Y

What 395.5(a)(2) means — and how to avoid it

In plain English

In plain terms, 395.5(a)(2) is cited for 15 - hour rule violation (Passenger). It falls under the FMCSA rules on hours of service and logging.

What the inspector checks

  • •Duty-status records for today and the prior 7 days
  • •ELD function and correct data entry
  • •Driving-limit compliance

How to prevent it

  • ✓Keep the ELD accurate and annotated
  • ✓Plan around available hours
  • ✓Never falsify a log

How it affects your CSA

up to 21 pts (fresh)

Severity 7/10. A fresh citation counts at the 3× time weight — up to 21 points toward the Hours-of-Service Compliance BASIC — then tapers to 2× after 6 months and 1× after a year, dropping off the score at 24 months.

General guidance from the violation’s FMCSA classification — not legal advice, and not a substitute for the inspector’s findings or 49 CFR.

📚

Challenging 395.5(a)(2) through FMCSA DataQs

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

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

More codes in Hours-of-Service Compliance

Same BASIC category — ranked by national citation volume

View all Hours-of-Service Compliance codes →
❓

Frequently asked questions about 395.5(a)(2)

What does violation 395.5(a)(2) mean?

395.5(a)(2) is the FMCSA roadside-inspection violation code for "15 - hour rule violation (Passenger)", part of the Hours group, cited under 49 CFR §395.5(a)(2).

What BASIC does 395.5(a)(2) affect?

395.5(a)(2) falls under the Hours-of-Service Compliance BASIC in the FMCSA Safety Measurement System (SMS).

What is the CSA severity weight of 395.5(a)(2)?

395.5(a)(2) carries a severity weight of 7 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.5(a)(2) an out-of-service (OOS) violation?

No. 395.5(a)(2) 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.5(a)(2) add to a carrier's score?

The point contribution of 395.5(a)(2) depends on its severity weight (7/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.

How can a driver prevent 395.5(a)(2)?

Keep the ELD accurate and annotated; Plan around available hours; Never falsify a log.

Can 395.5(a)(2) be challenged through DataQs?

Yes. If you believe 395.5(a)(2) 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

Turn this violation into a training moment

Assign training on this exact topic — and prove it

Looking up a code is step one. FleetTrained — built by the same safety manager behind VioCodes — lets you assign a video on this topic; drivers quiz and sign in their language, and you get a DOT-ready certificate so it stops happening.

Flat monthly · unlimited driversCertificates · any language
Explore FleetTrained

Field notes & comments

0 comments
Sign in to add a field note.
  • No comments yet — be the first.

Statistics

Most-cited violation codes

Ranked by roadside-inspection citation count across FMCSA public data.