Prevention FAQ — FMCSR 390.17

390.17 covers the use of electronic devices and record-keeping methods that must comply with prescribed formats and systems. Inspectors examine whether required forms, logs, or electronic records meet the regulatory format — not just whether they exist, but whether they conform to the method specified.

Enforcement is geographically concentrated. Our inspection records show that in the last 180 days, North Carolina alone generated 152 citations, far ahead of second-ranked Arizona at 66. Ohio (64), Iowa (50), and Texas (39) round out the top five. If your fleet operates regularly through NC, AZ, or OH corridors, inspectors in those states are actively looking for 390.17 deficiencies. Build region-specific awareness into driver briefings for runs through these states.

Add a dedicated compliance-format verification step before dispatch. Drivers should confirm:

• ELD functionality: Device is logging using the method prescribed — not switching between modes improperly.
• Record format: Any paper backup logs or supporting documents are on the correct form version.
• Device sync: ELD data is current and not showing unresolved errors or uncertified logs.
• Supporting documents on board: Last 7 days of records are accessible and in the correct format.

The pre-trip check for 390.17 is less about physical condition and more about data integrity. Build a 60-second "compliance format check" into your dispatch release process. Flag any driver who can't confirm clean ELD status before wheels roll.

Drivers must have on board:

• Current and previous 7-day ELD records in the format prescribed — accessible for display to an inspector on demand.
• Any required paper backup logs if the ELD malfunctions, completed on approved forms.
• ELD malfunction documentation if applicable, including the date the malfunction was reported to the carrier.

Carriers must retain driver records of duty status (RODS) for a minimum of 6 months. Critically, the format and method of those retained records must match what was prescribed at the time of operation — not a reconstructed or reformatted version. Our database shows 390.17 has accumulated 3,805 all-time citations, none of which resulted in an OOS, but every citation still generates a CSA event record.

Our inspection data from the last 90 days shows clear co-occurrence patterns that point to three systemic issues:

1. 395.8A1-HOSP appeared in 18 shared inspections — failing to have a RODS using the prescribed method. This suggests drivers are logging, but not in the correct format. Root cause: inadequate ELD training or improper mode selection.

2. 396.17C-PI appeared in 15 shared inspections — no proof of periodic inspection. This pairing suggests a broader documentation discipline failure, not just an ELD issue. Drivers who don't carry inspection records also tend to have record-format problems.

3. 395.24 appeared in 13 shared inspections — ELD form and manner violations. This trifecta (390.17 + 395.8A1 + 395.24) almost always points to a fleet whose ELD onboarding process is incomplete or whose drivers are using workarounds. Address ELD training at the fleet level, not driver by driver.

390.17 is an administrative/records violation — it carries a 0.0% OOS rate across all 3,805 citations in our database, so vehicles aren't parked. But the corrective action still requires verification before the driver's next dispatch.

The safety manager or compliance officer should:

• Confirm the ELD device is operating in the correct prescribed mode and logging properly.
• Review and certify any corrected logs through your ELD portal before the next trip begins.
• Document the correction with a timestamp — who fixed it, what was wrong, and what was done.
• Have the driver acknowledge the correction in writing or via your fleet management system.

Do not simply clear the event and move on. The correction record becomes your defense in a DataQs challenge if the citation is later disputed.

Run a structured three-part review within 5 business days of the citation:

1. Individual driver review: Pull the driver's ELD records for the 72 hours surrounding the citation. Identify what format deviation triggered the violation. Was it a mode error, an uncertified log, or a missing supporting document?

2. Fleet-wide pattern check: Our data shows the last 12 months produced 1,172 citations nationally — an average of nearly 98 per month. If one driver was cited, audit the same record format across your entire active fleet. One citation often means others are at risk.

3. Carrier benchmark review: The top carriers in our records — including Swift Transportation (27 citations), FedEx (23), and UPS (23) — all accumulated citations despite mature compliance programs. Use your event as a trigger to review your ELD configuration settings fleet-wide, not just for the cited driver.

390.17 falls under the General/Admin category of FMCSR and is not OOS-eligible — it carries a 0.0% OOS rate across all 3,805 citations in our database, compared to the all-FMCSR average OOS rate of 31.4%. The citation will not shut down a vehicle or driver, but it does post as a violation to your CSA inspection record.

390.17 is ranked #401 out of 3,036 FMCSR codes by citation volume — it's not rare. Each citation adds to your carrier's violation count and can affect your Safety Measurement System (SMS) scores depending on your inspection volume and the time-weight of recent events. For high-frequency fleets where 390.17 is appearing repeatedly, the cumulative CSA impact is real even without OOS weight behind individual events.

Our vehicle make data shows FRHT (560 citations) and FREIGHTLIN (543 citations) are the top two makes cited under 390.17 all-time, followed by Volvo variants at 234 and 199 citations. These are the dominant power units in large national fleets, which means 390.17 training gaps are fleet-wide problems, not equipment-specific ones.

Target these training modules:

• ELD mode selection: Drill on when personal conveyance, yard move, and driving modes are appropriate — misuse is a primary trigger.
• Log certification procedure: Many drivers skip certifying logs daily. Build this into end-of-shift habit training.
• Paper backup protocol: Drivers must know exactly what form to use and how to complete it if the ELD malfunctions.
• Supporting document management: Pair this with the periodic inspection training, since 396.17C-PI co-occurred in 15 of the same inspections as 390.17 in the last 90 days.

Challenge when you have clear documentation that the driver's records were in the correct prescribed format and the citing officer made a factual error. Specific grounds:

• ELD system logs (timestamped) show the correct mode was active during the inspection period.
• The citation references a form or method the driver was not required to use under their operating authority.
• The driver was on a qualifying short-haul exemption and was not required to maintain ELD records for that segment.

Do not challenge simply because the citation didn't result in OOS. The 0.0% OOS rate is expected for this code — it doesn't signal the citation was improper. Your challenge must be documentation-based. File within 60 days of the inspection date and attach ELD portal exports, not driver-reconstructed summaries.

Our inspection records show the last 90 days produced 312 citations, while the full last 12 months produced 1,172. That's roughly 293 citations per 90-day period as an annual average — meaning the most recent 90-day period (312) is running above average. The monthly trend also shows an uptick: citations climbed from 88/month in mid-2025 to 152 in December 2025, 143 in March 2026, and 120 in February 2026.

This trend justifies a monthly internal audit cadence, not quarterly. Specifically:

• Pull a random 10% sample of driver logs each month and verify format compliance against ELD system records.
• After any month where your fleet's 390.17 citations exceed your baseline, trigger a 100% audit for the following 30 days.
• Track audit results in your corrective action log — inspectors in NC, AZ, and OH are actively writing this code, and self-audits are your primary early-warning system.