CSA
UnknownUSDOT 1482378· CARRIER· EIN 20-4538789
⬇ PDF report

SANCHEZ EXPRESS INC

456 RUTHERFORD AVENUE, LYNDHURST, NJ, 07071(917) 657-1247LEONARDO SANCHEZ
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
Power units
0
on file (MCS-150)
Drivers
0
Annual mileage
—
Recordable crash rate
—
per million miles
Company officer
LEONARDO SANCHEZ
Registered since
2006-04-03
Last MCS-150 update
2006-04-03
Census status
I

Fleet: 0 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.

Data change history

Every FMCSA record change we’ve detected — address, fleet size, contacts, MCS-150 — newest first.

Connections

carrier graph

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

12
Connected carriers
0
Fleet-transfer links
0
Most shared VINs
12
Strong links
Possible reincarnation pattern: LEONARDO SANCHEZ (USDOT 1424225, registered 2005) is inactive, shares this carrier’s officer, and predates it — worth checking whether this carrier re-registered to shed a prior record.
Strong· 12
1
ALC LOGISTICS LLC
USDOT 3539121Active· TAYLORSVILLE, NC
Strong
Officer
2
BRS EXPRESS CORPORATION
USDOT 2024929Inactive· LYNDHURST, NJ
Strong
OfficerMailingAddress
3
FRANCES DELIVERY LLC
USDOT 3066947Inactive· NAPLES, FL
Strong
Officer
4
ILLUMINATED EXPRESS LLC
USDOT 2190442Inactive· HIALEAH GARDENS, FL
Strong
Officer
5
KME TRANSPORTATION LLC
USDOT 2948823Active· SAN JOSE, CA
Strong
Officer
6
LASA LOGISTICS INC
USDOT 4220575Active· MATTESON, IL
Strong
Officer
7
LEONARDO SANCHEZ
USDOT 1424225Inactive· HIALEAH GARDEN, FL
Strong
Officer
8
LEONARDO SANCHEZ
USDOT 1048196Inactive· PERTH AMBOY, NJ
Strong
Officer
9
LEONARDO SANCHEZ
USDOT 3022341Inactive· PEACH BOTTOM, PA
Strong
Officer
10
LEONARDO SANCHEZ
USDOT 2095995Active· FORT WORYH, TX
Strong
Officer
11
LEONARDO VINICIO SANCHEZ ABREU
USDOT 3257753Active· MIAMI, FL
Strong
Officer
12
LS TRUCKIN LLC
USDOT 4272412Active· STURGEON BAY, WI
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. 04/03/2006Registered with FMCSA
  2. 04/03/2006MCS-150 update filed

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

★

FMCSA safety rating

Rating
Not rated
Type
—
Rated
—
Last review
—
📄

MCS-150 registration

Form date
2006-04-03
Reported mileage
—
⚡

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 26, 2026, 11:01 AM. VioCodes is not affiliated with FMCSA. To dispute incorrect data, file a DataQs Request for Data Review.