CSA
SearchMapNewCarriersInsightsCalculator
DataQsBeta2
Guides7
Driver CoachingAPI
LoginRegisterTry FleetTrained
UnknownUSDOT 3280924· CARRIER
⬇ PDF report

COOK'S MOTORS

Legal: TIMOTHY COOK

2050 ROUTE 541, WESTAMPTON, NJ, 08060-4411(609) 267-7911joannecook7911@outlook.comTIMOTHY COOK
Vetting snapshot
Authority
Unknown
per SAFER
Insurance
No active filing
not required
Vehicle OOS
—
no inspections
Driver OOS
—
no inspections
Crashes 24mo
0
clean
Red flags
1 flag
see details below
80
/ 100

Risk factors

Low riskVioCodes score
Possible reincarnation pattern — tied to an older inactive carrier

A weighted read of the public FMCSA signals below — authority, insurance, out-of-service, crashes, roadside OOS rates, and carrier connections. A starting point for vetting, not a guarantee.

Roadside inspection performance

Out-of-service rate vs national average. Lower is better.

Vehicle0 inspections · 0% OOS · National 22%
Driver0 inspections · 0% OOS · National 6.7%

CSA performance breakdown

FMCSA · August 28, 2026

0 inspections · 0 violations (0 OOS) · —% of inspections had an OOS finding.

0
Inspections
0
Violations
0
OOS violations
0
Distinct codes

Latest FMCSA SMS snapshot. Codes link to the lookup — severity weighting, contest angles, and the DataQs Drafter for each. Click a BASIC to filter the codes.

Company profile

FMCSA census

PRIVATE PROPERTY

Power units
1
on file (MCS-150)
Drivers
1
0 hold a CDL
Annual mileage
0M mi
reported 2021
Recordable crash rate
0.00
per million miles
How far they run · drivers by operating lane
  • Interstate · <100 mi1 drivers
Company officer
TIMOTHY COOK
Operation
Interstate · Hazmat
Registered since
2019-05-01
Last MCS-150 update
2022-06-20
Census status
I

Fleet: 1 trucks.

Source: FMCSA Company Census File (data.transportation.gov). Fleet and driver counts are self-reported on the carrier’s most recent MCS-150 filing.

Connections

carrier graph

This carrier shares officers with 8 other carriers — review the connections below as part of your vetting.

8
Connected carriers
0
Fleet-transfer links
0
Most shared VINs
8
Strong links
Possible reincarnation pattern: ANDREW JASPER (USDOT 2798480, registered 2015) is inactive, shares this carrier’s officer, and predates it — worth checking whether this carrier re-registered to shed a prior record.
Strong· 8
1
ANDREW JASPER
USDOT 2798480Inactive· RED OAK, TX
Strong
Officer
2
COOK OIL COMPANY INC
USDOT 2331992Active· HOLLY SPRINGS, MS
Strong
Officer
3
COOK'S BLACKSMITH WELDING INC
USDOT 1796560Active· BIG RAPIDS, MI
Strong
Officer
4
CORTLANDT TANK SERVICE LLC
USDOT 1146227Active· MONTROSE, NY
Strong
Officer
5
R & T EXPRESS LLC
USDOT 3118696Inactive· COMO, MS
Strong
Officer
6
RAY F LOGISTICS LLC
USDOT 4093531Inactive· BEAUMONT, TX
Strong
Officer
7
T COOK TRUCKING LLC
USDOT 1567305Active· GADSDEN, TN
Strong
Officer
8
TIMOTHY COOK CONSTRUCTION LTD
USDOT 906494Inactive· WOODSTOCK, NB
Strong
Officer

Shared VINs come from FMCSA roadside-inspection records — a vehicle inspected under more than one carrier, often a fleet transfer or trailer interchange. Other links come from the FMCSA census. Shared identifiers are common and often legitimate — treat these as leads to investigate, not proof of wrongdoing.

Activity history

2 events
  1. 06/20/2022MCS-150 update filed

    0.0M mi reported (2021)

  2. 05/01/2019Registered with FMCSA

    PRIVATE PROPERTY

Merged from FMCSA authority, insurance, out-of-service, and census records.

🚛

Operations

Classification

  • PRIVATE PROPERTY

Area served

  • Interstate
★

FMCSA safety rating

Rating
Not rated
Type
—
Rated
—
Last review
—
📄

MCS-150 registration

Form date
2022-06-20
Reported mileage
200 mi (2021)
⚡

Got a violation you want to contest?

Use the free AI-powered DataQs Drafter to generate a polished challenge letter — quotes the relevant 49 CFR, predicts your grant chance.

Open the Drafter →
ⓘ
Data sourced from public FMCSA records via safer.fmcsa.dot.gov · Latest FMCSA update: Sep 2026 · Page refreshed: Sep 21, 2026, 3:04 AM. VioCodes is not affiliated with FMCSA. To dispute incorrect data, file a DataQs Request for Data Review.