Prevention FAQ — FMCSR 392.2-RKD Reckless Driving

Inspectors document reckless driving as operation of a CMV in a manner that shows disregard for safety, as defined by applicable state or local law. While our inspection database shows zero citations for code 392.2-RKD across all time periods, the Unsafe Driving category contains related violations. Inspectors typically focus on speed differential relative to traffic, improper lane changes, failure to maintain safe distance, and aggressive maneuvers. Your prevention program should train dispatch and safety managers to recognize behavior patterns that precede formal citations—erratic speed changes, repeated near-miss incidents, or complaint-based observations. Establish a reporting channel for drivers and third parties to flag concerning behavior so you can intervene before a formal citation occurs.

Pre-trip checklists for reckless driving prevention focus on vehicle condition—not the violation itself, but on ensuring drivers have no mechanical excuse for unsafe maneuvers. Include: brake system function (soft pedal, uneven response), steering responsiveness, tire grip and pressure, and lighting visibility. A vehicle that brakes or steers poorly forces reactive, aggressive driving. Also add a driver fitness section: fatigue check-in, medication review, and mental/emotional state assessment. Document these checks daily in your maintenance system. Since fatigue and illness violations (392.2 variants) account for 1.7M+ citations in our database across peer codes, these pre-trip assessments double as early warning for fitness to drive—a root cause that often co-occurs with reckless behavior.

After citation, drivers must carry the citation document and court/hearing correspondence. Your fleet should retain: the original citation with inspector name and timestamp, dashcam or onboard camera footage (if equipped) from the cited incident, driver logbook entries for the date/time of citation, vehicle maintenance records for the specific unit cited, and the driver's training records up to the citation date. Create a citation file that includes the driver's response statement and any witness accounts. Maintain these for at least three years. This documentation supports DataQs challenges if the citation is factually incorrect, and provides evidence for your post-event review. Ensure your record-keeping system can be produced within 48 hours of request by FMCSA or your insurer.

Our database shows that reckless driving often correlates with violations in the Unsafe Driving category. The peer codes most frequently cited alongside unsafe driving violations are: 392.2 (Operating while ill or fatigued)—1.2M+ citations, suggesting driver fatigue or distraction masks as reckless behavior; 392.2-SLLSR (Ill or fatigued)—191K+ citations, indicating similar systemic fatigue issues; and 392.2RG (Ill or fatigued)—96K+ citations, pointing to inadequate rest or health screening. When investigating a reckless driving incident, first ask: Was the driver fatigued, medicated, or unwell? Second: Was the vehicle mechanically sound? Third: Did the driver receive adequate training on speed/distance judgment in that road/weather condition? A root-cause analysis that ignores fatigue will miss the pattern. Implement mandatory fatigue audits during post-citation review.

After a reckless driving citation, conduct a full safety inspection before the unit returns to revenue service—don't assume prior maintenance is sufficient. Focus on: brake response (test at varying speeds in a controlled lot), steering centering and play, tire tread depth and pressure, and suspension stability over bumps. Document findings with photos and technician sign-off. Have a second technician or supervisor verify critical systems independently. Any defect found should be corrected and re-tested. Create a return-to-service checklist specific to the cited vehicle and driver. This prevents the scenario where mechanical failure drove the reckless maneuver initially. Log all pre-return inspections in your fleet maintenance system with timestamps—this demonstrates due diligence if a follow-up incident occurs.

Within 5 business days of citation, schedule a structured review with the driver, a safety manager, and the driver's dispatcher. Review: the citation details (date, time, location, specific behavior), dashcam footage if available, the driver's account of what happened, vehicle condition at time of citation, driver's rest and medical history, and training records. Ask: Did mechanical failure force the maneuver? Was the driver fatigued or ill? Was the driver trained for that road condition? Document the driver's responses in writing. If the driver disputes facts, note that for a potential DataQs challenge. Develop a corrective action plan—additional training, reassignment, or fitness evaluation. Schedule a follow-up review 30 days later to confirm behavior change. This systematic approach prevents repeat citations and demonstrates to FMCSA that you have an active prevention program.

Code 392.2-RKD is classified as an Unsafe Driving violation with a CSA severity weight of 10, meaning each citation carries significant enforcement weight in your safety profile. While the citation itself lives under the Unsafe Driving category, a pattern of reckless driving citations signals to auditors that your vehicle fleet or driver training program has systemic gaps. FMCSA uses citation frequency and severity weighting to rank carriers. A single citation will impact your score modestly; multiple citations across drivers or units suggest inadequate maintenance or training oversight. Maintain a running log of all Unsafe Driving citations in your fleet to identify trends early. If you see two or more citations in a 12-month window, trigger a comprehensive audit of that driver pool or vehicle maintenance procedures. This proactive monitoring prevents escalation to enforcement action.

Core training topics: Speed and distance judgment in various road/weather conditions, with scenario-based coaching for highway merges, urban congestion, and weather degradation. Fatigue recognition and management, since our data shows fatigue violations are paired with reckless behavior patterns—teach drivers to recognize early fatigue signs and pull over. Mechanical sympathy, so drivers understand how brake, steering, and tire condition affect safe maneuvers and report defects immediately. Defensive driving and EZ Pass (or equivalent) to reduce speed-related aggression. Medication and health disclosure, with clear policy that certain medications or conditions require notification before shifts. Conduct these trainings annually and immediately after any citation. Use real footage from your fleet's dashcam system to illustrate safe vs. unsafe maneuvers in conditions your drivers actually face. Tie training completion to performance bonuses to increase engagement.

File a DataQs challenge within 90 days of citation if: (1) the citation cites the wrong code—ensure the inspector documented 392.2-RKD, not a similar code; (2) the facts in the citation are factually incorrect—your dashcam shows the cited maneuver was safe and within legal limits; (3) the driver's license or vehicle registration was valid but the inspector marked it invalid; or (4) the citation was issued outside the inspector's jurisdiction. Do not challenge based on disagreement with the inspector's judgment call alone—challenges rarely succeed on those grounds. Before filing, review your post-event investigation and dashcam footage. If your review confirms the citation is factually wrong, prepare a written statement and supporting evidence (dashcam footage, GPS data, photos) and submit within the 90-day window to your state transportation department. Even unsuccessful challenges create a record of your dispute for future audit reviews.

Conduct quarterly audits (every 90 days) of driver behavior and vehicle condition. Our inspection data shows zero citations for 392.2-RKD across all recent periods, which suggests either strong industry prevention practices or low enforcement visibility. Use this as your baseline: if any single driver receives a citation in a 12-month window, or if you observe two or more near-miss reports, escalate to monthly audits for that driver pool. Your quarterly audit should include: review of dashcam footage for unsafe maneuvers, analysis of speedometer data (if telematics-enabled), driver feedback from dispatch and customers, and vehicle pre-trip compliance rates. Document findings in a central safety database. If an entire region or vehicle class shows patterns, expand the audit to all units in that category. Link audit findings to driver scorecard ratings and tenure decisions. This cadence allows you to identify and correct behavior drift before FMCSA inspection occurs.