Watch
Send carrier packetSend packetOnboard this carrier with a branded, e-signable packet
Carrier profile · USDOT 806674 · Updated 06/13/2026

CHAD CRIPE

DBA CRIPE EARTH SERVICES

1 power unitsHUNTINGTON, IN
AUTHORITY STATUS UNKNOWNUNDELIVERABLE ADDRESS
Verified linksFMCSA SAFERCall
Observed fleet · trailing 24 mo daily
1Power units
Self-reported · MCS-150
Trailers seen
None observed · 24 mo
Avg age (yr)
Awaiting decode
USDOT registration27 yr registered
Authority not on file
Insurance (BIPD) unknown
No filing on record
Vehicle OOS · 24-mo
No inspections · 24 mo
Crashes · fatal
No crash record
Vektor intelligence · beyond the federal recordProprietary signals computed from VIN-decoded inspections & daily FMCSA snapshots
Fleet typeIdentity

Owner-operator

1 power units. Brokers price each fleet type apart.

Fleet age vs peersDecoding

Awaiting VIN decode

Identity stabilityStable

27 yr unchanged

Same registration since 1999 — no chameleon / reincarnation signal.

AI readCarrier, 27-yr registration unrated.Full read

Is CHAD CRIPE safe to work with?

Is CHAD CRIPE safe to load? CHAD CRIPE (USDOT 806674) is an inactive owner-operator motor carrier based in HUNTINGTON, IN, operating 1 power unit and 2 drivers. Operating authority has been active 27 years (past the 24-month broker-confidence threshold). FMCSA has not assigned a safety rating. Vektor does not assign this carrier a safety score — there is not enough federal record to assess it. Verify authority and insurance directly. Source: FMCSA SAFER/MCMIS, last updated 2026-06-13.

FMCSA fields + Vektor analysis · updated 2026-06-13
Loading full carrier record…
02

Frequently asked

What is CHAD CRIPE's USDOT number?

CHAD CRIPE's USDOT number is 806674.

Is CHAD CRIPE authorized to operate?

As of 2026-06-13, CHAD CRIPE is inactive in the FMCSA register.

How big is CHAD CRIPE's fleet?

CHAD CRIPE operates 1 power unit and 2 drivers per its most recent MCS-150 filing.

Where is CHAD CRIPE based?

CHAD CRIPE is based in HUNTINGTON, IN.

03

Similar carriers

Peer comparison temporarily unavailable

We could not retrieve a reliable peer set for this profile right now.