Crash Record MS6102250042
FMCSA crash record in FLORENCE on Jan 21, 2025.
What happened
On January 21, 2025, FMCSA recorded a tow-away crash with no reported injuries in FLORENCE, Mississippi. The vehicle was operated by PILOT TRAVEL CENTERS LLC (USDOT 91805). Recorded conditions: 2 / 1 / 1 pavement. Reported by SARATOGA, FMCSA reference MS6102250042.
Carrier pattern note
This is the carrier's 124 crashes in the past 24 months — above the typical pattern (median 0) for fleets of 500+ power units.
This carrier's crash pattern
Derived from the carrier's full crash history.
Geographic context
How this crash sits in its setting.
Within FLORENCE, Mississippi, 11 other commercial vehicle crashes have been recorded in the past 24 months.
Agencies most active in this area:
- RANKIN COUNTY SCHOOL DISTRICT · 2 reports
- LACEY'S DIGGING SERVICE INC · 1 reports
- KRJ TRANSPORT LLC · 1 reports
Contributing factors
What the responding officer recorded.
- Light
- 2
- Weather
- 1
- Road surface
- 1
Conditions are mixed. The data does not assign causation; this section reports only what was recorded by the responding officer.
Crash details
Key facts from the FMCSA crash record.
- Report #:
- MS6102250042
- Date:
- Jan 21, 2025
- Time:
- 0401
- State:
- Mississippi
- City:
- FLORENCE
- Fatalities:
- 0
- Injuries:
- 0
- Tow-Away:
- Yes
- HazMat:
- No
- Vehicles:
- 2
- Carrier (USDOT):
- PILOT TRAVEL CENTERS LLC (91805)
Vehicles / units involved
1 commercial motor vehicle(s) in this crash.
| # | Config | Cargo Type | VIN | Plate | Carrier | GVW | HazMat |
|---|---|---|---|---|---|---|---|
| 1 | 8 | 12 | 1XKYDP9X7RJ.45943 | S3636HY (TN) | SARATOGA | 3 | No |
Crash event
Event sequence description.
1:20:COLLISION INVOLVING OTHER MOVABLE OBJECT
Other crashes by this carrier
10 additional crash record(s) on file.
| Record | Date | State | Severity | Fatalities | Injuries |
|---|---|---|---|---|---|
| cmqt2c387002fp84g4x0i42xa | Jun 17, 2026 | VA | Tow-Away | 0 | 0 |
| cmpoujjv3004lr2048vc15j1e | May 20, 2026 | NC | Tow-Away | 0 | 0 |
| cmouyr2u40065nu1klf04gm53 | Apr 29, 2026 | KY | Tow-Away | 0 | 0 |
| cmodru16y0055nvfd9i54z0at | Apr 19, 2026 | TN | Injury | 0 | 3 |
| cr_5127134 | Mar 27, 2026 | IA | Tow-Away | 0 | 0 |
| cr_5125414 | Mar 17, 2026 | TX | Tow-Away | 0 | 0 |
| cr_5123578 | Mar 14, 2026 | PA | Tow-Away | 0 | 0 |
| cr_5124947 | Mar 14, 2026 | TX | Tow-Away | 0 | 0 |
| cr_5116621 | Mar 11, 2026 | TN | Tow-Away | 0 | 0 |
| cr_5121469 | Feb 22, 2026 | GA | Tow-Away | 0 | 0 |
Related records
How to evaluate a carrier's crash record
- Look at frequency, not any single crash. A single crash record rarely tells you anything decisive about a carrier. Pull the carrier's full multi-year crash list and look at the rate over time — clusters and trends matter more than any one event.
- Calculate crashes per power unit when data is available. Divide the 24-month crash count by the carrier's reported power units. A rate of one crash per power unit per year is high; a rate of one crash per ten power units per year is closer to industry baseline. Skip this step when power_units is missing or zero — the rate is meaningless without it.
- Filter for fault-attributed crashes. FMCSA crash records do not flag fault. To distinguish preventable from non-preventable, check whether the carrier requested a Preventability Determination through DataQs and what FMCSA ruled. Only the preventable crashes are a clean signal of carrier or driver behavior.
- Compare against fleet-size peers. Crash counts cannot be compared directly between fleets of different sizes. Use the SMS Crash Indicator percentile, or compare the carrier's crashes-per-power-unit rate against the median for its fleet-size cohort. A 50-truck carrier with 4 crashes in 24 months looks very different from a 5-truck carrier with the same count.
- Cross-reference with the SMS BASIC Crash Indicator. FMCSA's Safety Measurement System publishes a Crash Indicator percentile when the carrier has enough crashes and exposure to score. A score in the 65th percentile or higher triggers federal intervention thresholds. Always sanity-check raw crash counts against the percentile before drawing conclusions.