CSA
Not AuthorizedUSDOT 844214· MX372777· CARRIER
⬇ PDF report

HUMBERTO PERALTA L HUMBERTO PERALTA G LEONEL PERALTA GASTELUM GUADALUPE PERALTA G ANTONIO PERALTA L

CALLE 300 957 OTE, CD OBREGON, SO, MEXICO(644) 417-4717transportesperalta@hotmail.com.mxHUMBERTO PERALTA LANDAVAZO
Vetting snapshot
Authority
Inactive
operating authority
Insurance
No active filing
not required
Vehicle OOS
—
no inspections
Driver OOS
—
no inspections
Crashes 24mo
0
clean
Red flags
None
nothing flagged
45
/ 100

Risk factors

High riskVioCodes score
Operating authority is not active

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.

Authority & insurance

MX372777

Operating authority and insurance on file — from FMCSA Licensing & Insurance (L&I).

Common
Inactive
Contract
Inactive
Broker
None
Authorized for: Property
Liability (BIPD)
No active filing
not required
Cargo
Not on file
not required
Bond / surety
Not on file
not required
Authority history (10) ▾
04/04/2007FOR HIRE PROPERTYREINSTATED→ OUT OF SERVICE (08/23/2007)
04/04/2007FOR HIRE PROPERTYGRANTED→ OUT OF SERVICE (10/19/2007)
04/04/2007FOR HIRE PROPERTYGRANTED→ OUT OF SERVICE (09/07/2007)
04/04/2007FOR HIRE PROPERTYGRANTED→ OUT OF SERVICE (09/20/2007)
03/03/2007FOR HIRE PROPERTYGRANTED→ OUT OF SERVICE (02/22/2007)
04/03/2003FOR HIRE PROPERTYGRANTED→ OUT OF SERVICE (08/23/2007)
04/03/2003FOR HIRE PROPERTYGRANTED→ OUT OF SERVICE (10/19/2007)
04/03/2003FOR HIRE PROPERTYGRANTED→ OUT OF SERVICE (09/07/2007)
04/03/2003FOR HIRE PROPERTYGRANTED→ OUT OF SERVICE (09/20/2007)
02/18/2000FOR HIRE HOUSEHOLD GOODSGRANTED→ REPLACED BY PROVISIONAL AUTHORITY (03/31/2003)

Source: FMCSA Licensing & Insurance (L&I), public data. This shows the carrier’s federal insurance filings (BMC-91X liability, BMC-34 cargo) — the federally-required minimums on file for operating authority — not the carrier’s full commercial policy (its actual auto combined-single-limit, general liability, cargo, or workers’ comp, which appear on the carrier’s ACORD certificate of insurance). Always confirm current coverage with a COI from the carrier’s agent before making a vetting decision.

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

AUTHORIZED FOR HIRE

Power units
17
on file (MCS-150)
Drivers
12
12 hold a CDL
Annual mileage
0M mi
reported 2002
Recordable crash rate
0.00
per million miles
How far they run · drivers by operating lane
  • Interstate · 100+ mi10 drivers
  • Interstate · <100 mi2 drivers
Company officer
HUMBERTO PERALTA LANDAVAZO
Operation
Interstate
Registered since
1999-12-14
Last MCS-150 update
2009-11-07
Census status
I

Fleet: 17 trucks · 17 owned tractors · 17 owned trailers.

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 officers with 1 other carrier — review the connections below as part of your vetting.

1
Connected carriers
0
Fleet-transfer links
0
Most shared VINs
1
Strong links
Strong· 1
1
TRANSPORTADORA OBSON SA DE CV
USDOT 2020924Inactive· CD OBREGON, SO
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

16 events
  1. 06/28/2010Federal out-of-service order

    90 day failure to pay fine

  2. 11/07/2009MCS-150 update filed

    0.0M mi reported (2002)

  3. 12/26/2007Federal out-of-service order

    90 day failure to pay fine

  4. 10/19/2007Federal out-of-service order

    90 day failure to pay fine

  5. 09/30/2007Federal out-of-service order

    Unsatisfactory = Unfit

  6. 09/20/2007Federal out-of-service order

    90 day failure to pay fine

  7. 09/07/2007Federal out-of-service order

    90 day failure to pay fine

  8. 08/23/2007Federal out-of-service order

    90 day failure to pay fine

  9. 04/04/2007FOR HIRE PROPERTY — REINSTATED

    OUT OF SERVICE (08/23/2007)

  10. 04/04/2007FOR HIRE PROPERTY — GRANTED

    OUT OF SERVICE (10/19/2007)

  11. 03/28/2007Out-of-service order rescinded
  12. 03/03/2007FOR HIRE PROPERTY — GRANTED

    OUT OF SERVICE (02/22/2007)

  13. 02/22/2007Federal out-of-service order

    90 day failure to pay fine

  14. 04/03/2003FOR HIRE PROPERTY — GRANTED

    OUT OF SERVICE (08/23/2007)

  15. 02/18/2000FOR HIRE HOUSEHOLD GOODS — GRANTED

    REPLACED BY PROVISIONAL AUTHORITY (03/31/2003)

  16. 12/14/1999Registered with FMCSA

    AUTHORIZED FOR HIRE

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

🚛

Operations

Classification

  • AUTHORIZED FOR HIRE

Area served

  • Interstate
★

FMCSA safety rating

Rating
Unsatisfactory
Type
Compliance review
Rated
2007-09-30
Last review
2007-07-26
📄

MCS-150 registration

Form date
2009-11-07
Reported mileage
500 mi (2002)
⚡

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