TruckCodex

Crash Record NJ0006902476

FMCSA crash record in BOUND BROOK on Jun 11, 2025.

Tow-Away Federal Recordable Bus

What happened

On June 11, 2025, FMCSA recorded a tow-away crash with no reported injuries in BOUND BROOK, New Jersey. The vehicle was operated by KENSINGTON BUS CO (USDOT 1229309). Recorded conditions: 1 / 1 / 1 pavement. Reported by KENSINGTON BUS CO, FMCSA reference NJ0006902476.

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.

Fatalities
0
Injuries
0
Vehicles
1
Carrier
KENSINGTON BUS CO
Vehicle Type
Bus
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
4
1 injury · 3 tow-away
Crashes per 100 power units (24 mo)
3.6
3 crashes · 84 units
Days since prior carrier crash
182
Last on Dec 11, 2024
Vs fleet-size peers
above the median
Cohort median 0.0 · 26,285 carriers

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 #:
NJ0006902476
Date:
Jun 11, 2025
Time:
0756
State:
New Jersey
City:
BOUND BROOK
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
1
Carrier (USDOT):
KENSINGTON BUS CO (1229309)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 3 1 1GB6G5BG7D1168316 C537S1 (NJ) KENSINGTON BUS CO 2 No

Crash event

Event sequence description.

1:2:NONCOLLISION:JACKKNIFE

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_4878998 Dec 11, 2024 NJ Tow-Away 0 0
cr_4857137 Sep 10, 2024 NJ Injury 0 1
cr_4902238 Dec 8, 2023 NJ Tow-Away 0 0
cr_4914218 Jun 2, 2023 NJ Injury 0 2
cr_4572231 Mar 21, 2023 NJ Tow-Away 0 0
cr_4901957 Feb 16, 2023 NJ Tow-Away 0 0
cr_4576355 Jan 24, 2023 NJ Injury 0 1
cr_4358269 Mar 31, 2022 NJ Tow-Away 0 0
cr_4389994 Mar 9, 2022 NJ Tow-Away 0 0
cr_4389939 Feb 10, 2022 NJ Tow-Away 0 0

Related records

Vehicle
2013 CHEVROLET Express
NHTSA recalls and complaints for this make/model/year.
Recall
18V267000
EQUIPMENT
Recall
13V544000
EQUIPMENT:OTHER:LABELS
Recall
14V614000
ELECTRICAL SYSTEM
Carrier
KENSINGTON BUS CO
USDOT 1229309 · 60 crashes · 35 inspections
Vehicle
VIN: 1GB6G5BG7D1168316
Decode this VIN for make, model, year, and recall data.
State
Crashes in New Jersey
Statewide crash records.
Agency
KENSINGTON BUS CO
Crashes reported by this law-enforcement agency.
City
Crashes in BOUND BROOK, NJ
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.

How to evaluate a carrier's crash record

  1. Look at frequency, not any single crash. A single crash record rarely tells you anything decisive about a carrier. Pull the carrier's full multi-year crash list and look at the rate over time — clusters and trends matter more than any one event.
  2. Calculate crashes per power unit when data is available. Divide the 24-month crash count by the carrier's reported power units. A rate of one crash per power unit per year is high; a rate of one crash per ten power units per year is closer to industry baseline. Skip this step when power_units is missing or zero — the rate is meaningless without it.
  3. Filter for fault-attributed crashes. FMCSA crash records do not flag fault. To distinguish preventable from non-preventable, check whether the carrier requested a Preventability Determination through DataQs and what FMCSA ruled. Only the preventable crashes are a clean signal of carrier or driver behavior.
  4. Compare against fleet-size peers. Crash counts cannot be compared directly between fleets of different sizes. Use the SMS Crash Indicator percentile, or compare the carrier's crashes-per-power-unit rate against the median for its fleet-size cohort. A 50-truck carrier with 4 crashes in 24 months looks very different from a 5-truck carrier with the same count.
  5. Cross-reference with the SMS BASIC Crash Indicator. FMCSA's Safety Measurement System publishes a Crash Indicator percentile when the carrier has enough crashes and exposure to score. A score in the 65th percentile or higher triggers federal intervention thresholds. Always sanity-check raw crash counts against the percentile before drawing conclusions.

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.

Data sources & freshness

TruckCodex aggregates official public-sector datasets. See the Source registry for dataset-level coverage and the Freshness log for last-import timestamps.

FMCSA

Census, SAFER, SMS, Licensing & Insurance (L&I), roadside inspections, crashes, and authority history.

Refreshed daily.
NHTSA

Vehicle recall campaigns, defect investigations, and consumer safety complaints (SCRS).

Refreshed daily.
EIA

Retail diesel and gasoline price history and state fuel-tax tables.

Refreshed weekly.
Transport Canada

Cross-border carrier registry and Canadian recall campaigns where applicable.

Refreshed weekly.

TruckCodex is an independent aggregator; it is not affiliated with FMCSA, NHTSA, EIA, or Transport Canada. Always verify compliance-critical information directly with the originating agency.