TruckCodex
Hubs

Crash Record KY0072677052

FMCSA crash record in SPRINGFIELD on Aug 30, 2021.

Injury Federal Recordable

What happened

On August 30, 2021, FMCSA recorded an injury crash with one person hurt in SPRINGFIELD, Kentucky. The vehicle was operated by TLD LOGISTICS SERVICES INC (USDOT 1820774). Recorded conditions: 1 / 1 / 1 pavement. Reported by TLD LOGISTICS SERVICES INC, FMCSA reference KY0072677052.

Carrier pattern note

This is the carrier's 45 crashes in the past 24 months — above the typical pattern (median 0) for fleets of 51–500 power units.

Fatalities
0
Injuries
1
Vehicles
1
Carrier
TLD LOGISTICS SERVICES INC
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
45
2 fatal · 15 injury
Crashes per 100 power units (24 mo)
3.4
17 crashes · 495 units
Days since prior carrier crash
10
Last on Aug 20, 2021
Vs fleet-size peers
above the median
Cohort median 0.0 · 26,863 carriers

Geographic context

How this crash sits in its setting.

Within SPRINGFIELD, Kentucky, 14 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

Contributing factors

What the responding officer recorded.

Light
1
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 #:
KY0072677052
Date:
Aug 30, 2021
Time:
0902
State:
Kentucky
City:
SPRINGFIELD
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No
Vehicles:
1
Carrier (USDOT):
TLD LOGISTICS SERVICES INC (1820774)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 6 3AKJGEDR1JSJM8810 Y469HZ (TN) TLD LOGISTICS SERVICES INC 3 No

Crash event

Event sequence description.

2:18:COLLISION INVOLVING FIXED OBJECT

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cmtwgme1g002hpmiy55cqqueu Sep 4, 2026 NC Tow-Away 0 0
cr_5097952 Jan 28, 2026 OH Tow-Away 0 0
cr_5046591 Oct 6, 2025 OH Tow-Away 0 0
cr_5027892 Sep 12, 2025 TN Tow-Away 0 0
cr_5025443 Aug 20, 2025 IN Tow-Away 0 0
cr_5009819 Aug 12, 2025 TN Tow-Away 0 0
cr_5002032 Aug 7, 2025 MO Tow-Away 0 0
cr_5009890 Aug 1, 2025 TN Tow-Away 0 0
cr_5009133 Jul 22, 2025 SC Fatal 2 10
cr_4993202 Jun 10, 2025 GA Tow-Away 0 0

Related records

Vehicle
2018 FREIGHTLINER Cascadia
NHTSA recalls and complaints for this make/model/year.
Recall
23V073000
ELECTRONIC STABILITY CONTROL (ESC)
Recall
22V817000
FORWARD COLLISION AVOIDANCE: ADAPTIVE CRUISE CONTROL
Recall
20V567000
EXTERIOR LIGHTING:BRAKE LIGHTS
Carrier
TLD LOGISTICS SERVICES INC
USDOT 1820774 · 288 crashes · 685 inspections
Vehicle
VIN: 3AKJGEDR1JSJM8810
Decode this VIN for make, model, year, and recall data.
State
Crashes in Kentucky
Statewide crash records.
Agency
TLD LOGISTICS SERVICES INC
Crashes reported by this law-enforcement agency.
City
Crashes in SPRINGFIELD, KY
All crashes on file for this city.
Index
All Crash Records
Browse FMCSA commercial vehicle crash records.
Database
Roadside Inspections
Inspection history and violation details.
Database
NHTSA Recalls
Active recall campaigns.

Frequently asked questions about FMCSA crash records

What does this crash report tell me about the carrier? ▾
An individual FMCSA crash record tells you that a commercial vehicle operated by this carrier was involved in a reportable crash on the date listed, along with the severity (fatalities / injuries / tow-away) and the responding agency. A single crash record does not tell you whether the carrier was at fault, whether the driver was cited, or how the crash affected the carrier's safety scores. To evaluate the carrier, compare the full multi-year crash history against the carrier's fleet size, miles driven, and cohort peers.
Was this crash the carrier's fault? ▾
FMCSA crash records do not assign fault. Fault attribution requires reviewing the police report, any litigation outcome, and FMCSA's preventability determination if one was requested. If you need a fault determination, request the underlying state police crash report (PAR) — the carrier or its insurer can pull this through standard channels.
How does this crash affect the carrier's safety scores? ▾
Crash records feed FMCSA's Crash Indicator BASIC inside the Safety Measurement System (SMS). Each FMCSA-reportable crash counts for two years from the crash date and is weighted by severity (fatal / injury / tow-only). The Crash Indicator score is normalized against the carrier's power-unit count and exposure, so larger fleets need more crashes to score the same percentile as smaller ones. Non-reportable crashes do not enter the score.
Will this crash show up on the carrier's CSA SMS scores? ▾
If the federal_recordable flag on this record is true, yes — it will appear in the carrier's Crash Indicator BASIC for two years from the crash date. Crashes flagged state-only (state_recordable) are visible on the public crash file but do not enter the federal score.
How do I check the carrier's full crash history? ▾
Click through to the carrier profile (the USDOT link near the top of this page). The carrier's profile lists every crash on file, severity counts, and links into the SMS detail when an MC docket is on record. You can also visit FMCSA's SAFER and SMS portals directly using the carrier's USDOT number.
What if details look wrong — how do I correct an FMCSA crash record? ▾
FMCSA's DataQs system handles corrections to crash records. Either the carrier or an interested third party can file a Request for Data Review (RDR) with supporting documentation (police report, court records, witness statements). Corrections are processed by the originating state agency and propagate to the federal file within roughly 60–120 days when accepted.