Crash Record OK0023000081

FMCSA crash record in OKLAHOMA CITY on Jan 2, 2023.

Tow-Away Federal Recordable

What happened

On January 2, 2023, FMCSA recorded a tow-away crash with no reported injuries in OKLAHOMA CITY, Oklahoma. The vehicle was operated by TITAN TRANSPORTATION SERVICES INC (USDOT 1219854). Recorded conditions: 1 / 2 / 2 pavement. Reported by SUNSET LOGISTICS, FMCSA reference OK0023000081.

Carrier pattern note

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

Geographic note

This crash is part of an active corridor: 897 crashes occurred in the same city in the past 24 months.

Fatalities

Injuries

Vehicles

Carrier

TITAN TRANSPORTATION SERVICES INC

Vehicle Type

Truck

Severity

Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)

3 injury · 17 tow-away

Crashes per 100 power units (24 mo)

0.0

0 crashes · 90 units

Days since prior carrier crash

Last on Dec 16, 2022

Vs fleet-size peers

above the median

Cohort median 0.0 · 27,000 carriers

Geographic context

How this crash sits in its setting.

Within OKLAHOMA CITY, Oklahoma, 897 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

FEDERAL EXPRESS CORPORATION · 13 reports
CENTRAL OKLAHOMA TRANSPORTATION AND PARKING AUTHORITY · 9 reports
UNKNOWN · 9 reports

Contributing factors

What the responding officer recorded.

Light: 1
Weather: 2
Road surface: 2

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 #:: OK0023000081
Date:: Jan 2, 2023
Time:: 1334
State:: Oklahoma
City:: OKLAHOMA CITY
Fatalities:: 0
Injuries:: 0
Tow-Away:: Yes
HazMat:: No
Vehicles:: 1
Carrier (USDOT):: TITAN TRANSPORTATION SERVICES INC (1219854)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
1	9	3	3AKJHHDR5NSNN0611	3281096 (IN)	SUNSET LOGISTICS	3	No

Other crashes by this carrier

10 additional crash record(s) on file.

Record	Date	State	Severity	Injuries
cr_4616634	Sep 9, 2023	MN	Tow-Away	0
cr_4617747	Sep 6, 2023	AR	Tow-Away	0
cr_4596336	Jul 28, 2023	KY	Tow-Away	0
cr_4491431	Jan 7, 2023	NC	Tow-Away	0
cr_4487233	Jan 6, 2023	NC	Tow-Away	0
cr_4489041	Dec 16, 2022	FL	Injury	1
cr_4460115	Nov 21, 2022	VA	Injury	3
cr_4448356	Oct 21, 2022	OH	Tow-Away	0
cr_4364441	Mar 9, 2022	IL	Tow-Away	0
cr_4309126	Feb 19, 2022	IA	Tow-Away	0

Related records

Carrier

TITAN TRANSPORTATION SERVICES INC

USDOT 1219854 · 79 crashes · 0 inspections

Vehicle

VIN: 3AKJHHDR5NSNN0611

Decode this VIN for make, model, year, and recall data.

State

Crashes in Oklahoma

Statewide crash records.

Agency

SUNSET LOGISTICS

Crashes reported by this law-enforcement agency.

City

Crashes in OKLAHOMA CITY, OK

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.