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

CLINCH TITE CORP

DBA CTC PACKAGING

4 power unitsSANDY LAKE, PA
AUTHORITY STATUS UNKNOWN
Observed fleet · trailing 24 mo daily
4Power units
Self-reported · MCS-150
Trailers seen
None observed · 24 mo
Avg age (yr)
Awaiting decode
USDOT registration52 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

Small fleet

4 power units. Brokers price each fleet type apart.

Fleet age vs peersDecoding

Awaiting VIN decode

Identity stabilityStable

52 yr unchanged

Same registration since 1974 — no chameleon / reincarnation signal.

AI readCarrier, 52-yr registration unrated.Full read

Is CLINCH TITE CORP safe to work with?

Is CLINCH TITE CORP safe to load? CLINCH TITE CORP (USDOT 85203) is an inactive small-fleet motor carrier based in SANDY LAKE, PA, operating 4 power units and 5 drivers. Operating authority has been active 52 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 CLINCH TITE CORP's USDOT number?

CLINCH TITE CORP's USDOT number is 85203.

Is CLINCH TITE CORP authorized to operate?

As of 2026-06-13, CLINCH TITE CORP is inactive in the FMCSA register.

How big is CLINCH TITE CORP's fleet?

CLINCH TITE CORP operates 4 power units and 5 drivers per its most recent MCS-150 filing.

Where is CLINCH TITE CORP based?

CLINCH TITE CORP is based in SANDY LAKE, PA.

03

Similar carriers

Peer comparison temporarily unavailable

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