RoadsideProof 
FMCSA roadside violation code
395.22H4 — Driver failed to maintain supply of blank drivers records of duty status graph-grids
Raw code: 39522H4. Description, BASIC, weights, and appearance count below come from the public SMS violations snapshot dated 2026-07-31.
What this code counts in
- Raw FMCSA code
- 39522H4
- Description
- Driver failed to maintain supply of blank drivers records of duty status graph-grids
- Group
- EOBR Related
- BASIC
- Hours-of-Service Compliance
- Observed severity weight
- 1. Public FMCSA SMS violations file, snapshot 2026-07-31.
- Observed out-of-service addition
- 0, 2. Public FMCSA SMS violations file, snapshot 2026-07-31.
- Appearances in this file
- 6,341 violation rows. Public FMCSA SMS violations file, snapshot 2026-07-31.
The out-of-service addition varies between records in this file. Use the addition recorded for the violation being calculated.
How time changes the weight
SMS uses a 24-month inspection window. The time weight is ×3 through 6 months back from the snapshot date, ×2 for more than 6 through 12 months back, and ×1 for more than 12 through 24 months back. Older inspections are outside that snapshot's calculation window.
These bands are measured back from the snapshot date in calendar months. At a band boundary, the inspection remains in the more recent band. This describes snapshot calculations, not a promised date for a record to disappear.
Method and band numbers: SMS methodology used for snapshot 2026-07-31; calculation sources and explanation.
The inspection cap
Within each inspection and BASIC, severity weights including any out-of-service additions are summed, capped at 30, and only then multiplied by the time weight. Violations in other BASICs do not enter that cap.
If the sum still reaches the 30-point cap after a violation is removed, the inspection's contribution is unchanged. The effect of removing a violation is the difference between the measure with it and the measure without it, keeping the other snapshot data fixed.
Cap and order of operations: SMS methodology used for snapshot 2026-07-31; how it works.
A worked example for 395.22H4
Illustration using the most frequent observed pair for this code: severity 1 and out-of-service addition 0, recorded together in 6,324 violation rows in snapshot 2026-07-31. Assume no other violations in this BASIC on the inspection. Other records can have different weights.
Inspection severity total: min(30, 1 + 0) = 1. At time weight ×3 it contributes 1 × 3 = 3 to the BASIC numerator; at ×2, 1 × 2 = 2; at ×1, 1 × 1 = 1. These are derived example values using the method for snapshot 2026-07-31.
Pair counts preserve joint observations from the public SMS violations file; they do not identify a carrier or inspection. Formula source: FMCSA SMS methodology v3.21, June 2026, sections 3 and Appendix A.
These example weighted numerator points are not a change in the BASIC measure or estimated position. A reference code does not establish support for a personal report. The measure also depends on its denominator and the other inspections. Read how a violation moves the measure.
Related codes in EOBR Related
- 395.22H4ELDBRODS — HOS (ELD) - In-Vehicle Information - Failing to have a supply of blank driver's records of duty status graph-grids sufficient to record the driver's duty status and other related information for a minimum of 8 days.
- 395.22GELDMFV — HOS (ELD) - A portable ELD is not mounted in a fixed position and visible to the driver when seated in the normal driving position.
- 395.22H2ELDNISDT — HOS (ELD) Driver failing to have instruction sheet describing the data transfer mechanisms supported by the ELD and step-by-step instructions for the driver to produce and transfer the driver's hours of service records to an authorized safety official
- 395.22H1ELDNUM — HOS (ELD) - In-Vehicle Information - No user's manual for the driver describing how to operate the ELD. (May be electronic)
Related codes use the same group and BASIC in snapshot 2026-07-31, ordered by appearances in that file.