Use this skill when a crash has been incorrectly classified as DOT-recordable when it shouldn't be. Covers the § 390.5 criteria, common misclassifications, and challenge process.
Scanned 9/11/2026
Install to Claude Code
npx -y skills add x3allamerican/skills --skill dataq-crash-classification --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Dataq Crash Classification?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/x3allamerican-dataq-crash-classification)More formats (shields.io, HTML) on the badges page.
---
name: dataq-crash-classification
description: |
Use this skill when a crash has been incorrectly classified as DOT-recordable when it shouldn't be. Covers the § 390.5 criteria, common misclassifications, and challenge process.
---
# DataQ Filing for Crash Classification Errors
Per § 390.5, a DOT-recordable crash requires: fatality, bodily injury requiring medical treatment off-scene, OR disabling damage requiring tow-away. Crashes missing these triggers are NOT recordable. Challenge them.
## Common misclassification scenarios
- **Crash with no injuries** but tow-away (this IS recordable; not a challenge target)
- **Crash with minor injuries** where first aid was given on scene only — NOT recordable
- **Crash with damage** but vehicles were drivable — NOT recordable (tow-away requires inability to drive)
- **Crash with passenger pre-existing condition** — depends on what triggered medical treatment
- **Crash where parties drove away** but later sought medical treatment — typically NOT recordable (treatment must be away from scene immediately)
## Evidence needed
- Police report (often shows injury status, tow-away status)
- Photos of damage
- Witness statements
- Medical records (if available, can show no immediate off-scene treatment)
- Vehicle inspection results
- Insurance claim records
## Filing steps
1. Go to fmcsa.dot.gov/DataQ
2. Search for the crash record
3. Challenge category: "Crash Classification"
4. Subcategory: "Not DOT-recordable"
5. Narrative explaining why crash does not meet § 390.5 triggers
6. Upload evidence
## Success rate
- Documentation clearly shows no qualifying trigger: ~70%
- Officer reasonably classified given on-scene info: ~30%
## Compass support
Compass Accidents module:
- Cross-references your crash records against § 390.5 criteria
- Flags potentially non-recordable crashes
- Builds the DataQ challenge with evidence package
- Tracks reversal
## CFR citations
- **49 CFR § 390.5**
- **FMCSA DataQ User Guide**
## How Compass surfaces this
Searchable in Compass Ask. Runs against the carrier's actual 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=dataq-crash-classification
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!