Skip to main content
TruckCodex
Hubs

Crash Record MD23A1007205

FMCSA crash record in Maryland on Feb 27, 2023.

Injury Federal Recordable

What happened

On February 27, 2023, FMCSA recorded an injury crash with one person hurt in Maryland. The vehicle was operated by LEYENDA LTD (USDOT 893562). Recorded conditions: 3 / 2 / 2 pavement. Reported by LEYENDA LTD, FMCSA reference MD23A1007205.

Carrier pattern note

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

Fatalities
0
Injuries
1
Vehicles
2
Carrier
LEYENDA LTD
USDOT 893562
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
4
2 injury · 3 tow-away
Crashes per 100 power units (24 mo)
14.3
1 crashes · 7 units
Days since prior carrier crash
151
Last on Sep 29, 2022
Vs fleet-size peers
above the median
Cohort median 0.0 · 315,866 carriers

Geographic context

How this crash sits in its setting.

Within Maryland, 3,731 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
3
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 #:
MD23A1007205
Date:
Feb 27, 2023
Time:
1949
State:
Maryland
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
LEYENDA LTD (893562)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 6 3 1FUJA6AV45LU05727 NV6649 (NC) LEYENDA LTD 3 No

Crash event

Event sequence description.

2:98:OTHER;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
cr_5029201 Jun 17, 2025 VA Tow-Away 0 0
cr_4675259 Nov 30, 2023 DE Tow-Away 0 0
cr_4446821 Sep 29, 2022 CT Injury 0 1
cr_4364833 May 17, 2022 MD Tow-Away 0 0
cr_4148920 Mar 18, 2021 NY Tow-Away 0 0
cr_3262481 Jul 18, 2016 MA Injury 0 1
cr_3220348 May 20, 2016 CT Tow-Away 0 0
cr_3128230 Oct 20, 2015 CT Tow-Away 0 0
cr_3123987 Sep 4, 2015 CT Tow-Away 0 0
cr_3042220 May 10, 2015 VA Tow-Away 0 0

Carrier booking & risk tools

Check booking and risk signals for USDOT 893562 — tools open pre-filled.

Book / don't book Insurance check Cancel desk Chameleon check Safety benchmark

Related records

Carrier
LEYENDA LTD
USDOT 893562 · 21 crashes · 37 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Vehicle
VIN: 1FUJA6AV45LU05727
Decode this VIN for make, model, year, and recall data.
State
Crashes in Maryland
Statewide crash records.
Agency
LEYENDA LTD
Crashes reported by this law-enforcement agency.
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.