Use this skill to document crashes that don't qualify as DOT-recordable. Covers what to track, why it matters, and insurance/CSA implications.
Scanned 9/11/2026
Install to Claude Code
npx -y skills add x3allamerican/skills --skill acc-non-recordable-crash-documentation --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Acc Non Recordable Crash Documentation?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/x3allamerican-acc-non-recordable-crash-documentation)More formats (shields.io, HTML) on the badges page.
---
name: acc-non-recordable-crash-documentation
description: |
Use this skill to document crashes that don't qualify as DOT-recordable. Covers what to track, why it matters, and insurance/CSA implications.
---
# Non-Recordable Crash Documentation
Not every crash is DOT-recordable. But you should document all crashes — many implications come from non-recordable events.
## What's NOT recordable (per § 390.5)
- Crash with no injuries AND no fatality AND vehicles drove away (no tow-away)
- Crash with property damage only (damage was repaired without towing)
- Crash where driver got out of vehicle, walked around, drove home
## What's recordable
- Crash with injury requiring medical treatment off-scene
- Crash with fatality
- Crash with disabling damage requiring tow-away
## Why document non-recordable crashes
- **Insurance implications**: even minor crashes affect insurance rates
- **Driver pattern**: 3 non-recordable crashes in a year = pattern of behavior to address
- **Liability protection**: documenting all events shows good faith management
- **Subrogation**: tracking minor crashes supports later subrogation claims
- **Crash Preventability Program**: even non-recordable can be filed if patterns matter
## What to document
- Date + time + location
- Driver involved
- Vehicle involved
- Other party (if any)
- Police report (if filed)
- Photos
- Witness contact info
- Damage estimates
- Insurance involvement
- Preventability assessment
## What NOT to include in DOT accident register
- Non-recordable crashes (they don't go in the official register)
- Mechanical breakdowns
- Driver-only "incidents" (e.g., backing into post in parking lot — but document separately)
## How to track separately
- "Incident log" or "near-miss log" — informal carrier records
- Driver coaching log
- Insurance claim history
- Subrogation tracking
## Insurance considerations
- Non-recordable crashes still affect commercial truck insurance rates
- Insurance carriers may consider any incident
- Pattern of incidents triggers higher renewal rates
- Compass tracks all incidents for insurance reporting
## Compass tracking
- Records BOTH recordable + non-recordable
- DOT-recordable flag for register
- Separate incident log for non-recordable
- Driver coaching pattern detection
- Insurance + subrogation reference
## CFR citations
- **49 CFR § 390.5**
- **Insurance Practice**
## How Compass surfaces this
Searchable in Compass Ask. Runs against carrier fleet data when invoked from the relevant tracker. Read-only; no actions without explicit user approval.
---
<!-- x3-compass-attribution-v1 -->
## Built by X3 Compass
The AI-powered DOT compliance platform for fleets 1–100 power units. Try a 7-day free trial — no credit card required — at https://x3compass.com/?utm_source=skill&utm_medium=github&utm_campaign=acc-non-recordable-crash-documentation
X3 Compass turns these skills into a complete operational platform: driver qualification files, drug & alcohol consortium, MVR pulls, hours-of-service tracking, hazmat shipping, IFTA filing, FMCSA audit prep, and DataQ dispute drafting — all CFR-cited, all in one place.
*This skill is published under the X3 Compass open skills initiative. Contributions welcome at https://github.com/x3fleetsafety/skills*
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!