Crash Record PA111699400X

FMCSA crash record in PINE TOWNSHIP on Nov 23, 2021.

Tow-Away Federal Recordable

What happened

On November 23, 2021, FMCSA recorded a tow-away crash with no reported injuries in PINE TOWNSHIP, Pennsylvania. The vehicle was operated by SULTAN TRANSPORT INC (USDOT 3549771). Recorded conditions: 2 / 4 / 6 pavement. Reported by SULTAN TRANSPORT INC, FMCSA reference PA111699400X.

Carrier pattern note

This is the carrier's 4 crashes in the past 24 months — above the typical pattern (median 0) for fleets of 1–5 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

SULTAN TRANSPORT INC

Vehicle Type

Truck

Severity

Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)

1 fatal · 0 injury

Crashes per 100 power units (24 mo)

100.0

1 crashes · 1 units

Days since prior carrier crash

Last on Nov 13, 2021

Vs fleet-size peers

above the median

Cohort median 0.0 · 3,566,280 carriers

Geographic context

How this crash sits in its setting.

Within PINE TOWNSHIP, Pennsylvania, 43 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

MELY TRANSPORT INC · 2 reports
PENNDOT · 2 reports
UNITED PARCEL SERVICE INC · 2 reports

Contributing factors

What the responding officer recorded.

Light: 2
Weather: 4
Road surface: 6

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 #:: PA111699400X
Date:: Nov 23, 2021
Time:: 0211
State:: Pennsylvania
City:: PINE TOWNSHIP
Fatalities:: 0
Injuries:: 0
Tow-Away:: Yes
HazMat:: No
Vehicles:: 2
Carrier (USDOT):: SULTAN TRANSPORT INC (3549771)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
1	9	3	4V4NC9EH8KN902762	3135031 (IN)	SULTAN TRANSPORT INC	3	No

Crash event

Event sequence description.

1:20:COLLISION INVOLVING OTHER MOVABLE OBJECT

Other crashes by this carrier

10 additional crash record(s) on file.

Record	Date	State	Severity	Injuries
cr_4855839	Nov 27, 2024	WY	Tow-Away	0
cr_4820619	Sep 27, 2024	IN	Injury	1
cr_4818445	Sep 21, 2024	OH	Injury	1
cr_4821658	Sep 5, 2024	NJ	Injury	1
cr_4815729	Aug 23, 2024	CO	Injury	1
cr_4794501	Aug 9, 2024	VA	Tow-Away	0
cr_4791430	Aug 1, 2024	IN	Injury	2
cr_4792612	Jul 30, 2024	OH	Injury	3
cr_4756256	May 27, 2024	WA	Tow-Away	0
cr_4757646	May 12, 2024	NJ	Tow-Away	0

Related records

Vehicle

2019 VOLVO TRUCK VNL

NHTSA recalls and complaints for this make/model/year.

Carrier

SULTAN TRANSPORT INC

USDOT 3549771 · 30 crashes · 0 inspections

Vehicle

VIN: 4V4NC9EH8KN902762

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

State

Crashes in Pennsylvania

Statewide crash records.

Agency

SULTAN TRANSPORT INC

Crashes reported by this law-enforcement agency.

City

Crashes in PINE TOWNSHIP, PA

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.