Crash Record NV0900028064
FMCSA crash record in LAS VEGAS on Sep 8, 2025.
Injury
Federal Recordable
Bus
What happened
On September 8, 2025, FMCSA recorded an injury crash with 2 people hurt in LAS VEGAS, Nevada. The vehicle was operated by RTC TRANSPORT LAS VEGAS LLC (USDOT 1074192). Recorded conditions: 3 / 1 / 1 pavement. Reported by RTC TRANSPORT LAS VEGAS LLC, FMCSA reference NV0900028064.
Geographic note
This crash is part of an active corridor: 261 crashes occurred in the same city in the past 24 months.
Fatalities
0
Injuries
2
Vehicles
2
Carrier
RTC TRANSPORT LAS VEGAS LLC
Vehicle Type
Bus
Severity
Injury
This carrier's crash pattern
Derived from the carrier's full crash history.
Carrier crashes (24 mo)
1
1 injury · 1 tow-away
Crashes per 100 power units (24 mo)
60.0
3 crashes · 5 units
Days since prior carrier crash
2,146
Last on Oct 24, 2019
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,566,811 carriers
Geographic context
How this crash sits in its setting.
Within LAS VEGAS, Nevada, 261 other commercial vehicle crashes have been recorded in the past 24 months.
Agencies most active in this area:
- RTC OF SOUTHERN NEVADA · 14 reports
- CLARK COUNTY SCHOOL DISTRICT · 7 reports
- LAS VEGAS PAVING CORPORATION · 5 reports
Contributing factors
What the responding officer recorded.
- Light
- 3
- 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 #:
- NV0900028064
- Date:
- Sep 8, 2025
- Time:
- 0409
- State:
- Nevada
- City:
- LAS VEGAS
- Fatalities:
- 0
- Injuries:
- 2
- Tow-Away:
- Yes
- HazMat:
- No
- Vehicles:
- 2
- Carrier (USDOT):
- RTC TRANSPORT LAS VEGAS LLC (1074192)
Vehicles / units involved
1 commercial motor vehicle(s) in this crash.
| # | Config | Cargo Type | VIN | Plate | Carrier | GVW | HazMat |
|---|---|---|---|---|---|---|---|
| 1 | 4 | 2 | 1FDFE4FS3HDC15495 | EX70087 (NV) | RTC TRANSPORT LAS VEGAS LLC | 2 | No |
Other crashes by this carrier
4 additional crash record(s) on file.
| Record | Date | State | Severity | Fatalities | Injuries |
|---|---|---|---|---|---|
| cmt5ony26005npmdm01r0kzo8 | Aug 17, 2026 | NV | Injury | 0 | 3 |
| cr_5093069 | Jan 2, 2026 | NV | Injury | 0 | 1 |
| cr_3873484 | Oct 24, 2019 | NV | Injury | 0 | 4 |
| cr_3537268 | Dec 9, 2017 | NV | Injury | 0 | 1 |
Related records
Vehicle
2017 FORD E-450
NHTSA recalls and complaints for this make/model/year.
Recall
19V466000
EQUIPMENT
Recall
19V401000
EQUIPMENT
Recall
19V342000
EXTERIOR LIGHTING:BRAKE LIGHTS
Carrier
RTC TRANSPORT LAS VEGAS LLC
USDOT 1074192 · 5 crashes · 0 inspections
Vehicle
VIN: 1FDFE4FS3HDC15495
Decode this VIN for make, model, year, and recall data.
State
Crashes in Nevada
Statewide crash records.
Agency
RTC TRANSPORT LAS VEGAS LLC
Crashes reported by this law-enforcement agency.
City
Crashes in LAS VEGAS, NV
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.