Crash Record MN0212320087

FMCSA crash record in DULUTH on Aug 20, 2021.

Injury Federal Recordable Bus

What happened

On August 20, 2021, FMCSA recorded an injury crash with 2 people hurt in DULUTH, Minnesota. The vehicle was operated by DULUTH TRANSIT AUTHORITY (USDOT 1106666). Recorded conditions: 1 / 1 / 1 pavement. Reported by DULUTH TRANSIT AUTHORITY, FMCSA reference MN0212320087.

Carrier pattern note

This is the carrier's 4 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: 43 crashes occurred in the same city in the past 24 months.

Fatalities

Injuries

Vehicles

Carrier

DULUTH TRANSIT AUTHORITY

Vehicle Type

Bus

Severity

Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)

2 injury · 2 tow-away

Crashes per 100 power units (24 mo)

8.3

6 crashes · 72 units

Days since prior carrier crash

121

Last on Apr 21, 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 DULUTH, Minnesota, 43 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

DULUTH TRANSIT AUTHORITY · 7 reports
WAYNE TRANSPORTS INC · 3 reports
DULUTH PUBLIC SCHOOLS - ISD 709 · 2 reports

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 #:: MN0212320087
Date:: Aug 20, 2021
Time:: 1354
State:: Minnesota
City:: DULUTH
Fatalities:: 0
Injuries:: 2
Tow-Away:: No
HazMat:: No
Vehicles:: 1
Carrier (USDOT):: DULUTH TRANSIT AUTHORITY (1106666)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
1	4	2	15GGD2712D1181365	19908B (WI)	DULUTH TRANSIT AUTHORITY	3	No

Other crashes by this carrier

10 additional crash record(s) on file.

Record	Date	State	Severity	Injuries
cmryiu0xy003npehrkrsisltb	Jul 17, 2026	MN	Tow-Away	0
cr_5100113	Feb 4, 2026	MN	Injury	1
cr_5103986	Jan 4, 2026	MN	Injury	1
cr_4956498	Jun 13, 2025	MN	Tow-Away	0
cr_4918302	Mar 31, 2025	MN	Injury	1
cr_4863072	Nov 14, 2024	MN	Tow-Away	0
cr_4706412	Feb 26, 2024	MN	Injury	1
cr_4672352	Dec 26, 2023	MN	Injury	1
cr_4474412	Dec 6, 2022	MN	Tow-Away	0
cr_4409175	Aug 26, 2022	MN	Injury	1

Related records

Carrier

DULUTH TRANSIT AUTHORITY

USDOT 1106666 · 53 crashes · 0 inspections

Vehicle

VIN: 15GGD2712D1181365

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

State

Crashes in Minnesota

Statewide crash records.

Agency

DULUTH TRANSIT AUTHORITY

Crashes reported by this law-enforcement agency.

City

Crashes in DULUTH, MN

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.