CSA
UnknownUSDOT 4305045· CARRIER· EIN 99-5004700
⬇ PDF report

AA LLC

7845 E RIVER RD APT 309, FRIDLEY, MN, 55432-2451(602) 768-7331transportaallc@gmail.comMOHAMMED MOHAMMED
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
1 hold a CDL
Annual mileage
0M mi
reported 2023
Recordable crash rate
per million miles
How far they run · drivers by operating lane
  • Intrastate · <100 mi1 drivers
Company officer
MOHAMMED MOHAMMED
Operation
Intrastate (Non-Hazmat)
Registered since
2024-10-03
Last MCS-150 update
2024-10-25
Census status
Active

Fleet: 1 trucks · 1 owned tractors · 1 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.

Connections

carrier graph

This carrier shares phone numbers or officers with 10 other carriers — review the connections below as part of your vetting.

10
Connected carriers
0
Fleet-transfer links
0
Most shared VINs
9
Strong links
Possible reincarnation pattern: FLY EAGLE LOGISTICS LLC (USDOT 3987214, registered 2022) is inactive, shares this carrier’s officer, and predates it — worth checking whether this carrier re-registered to shed a prior record.
Strong· 9
1
FLY EAGLE LOGISTICS LLC
USDOT 3987214Inactive· PHOENIX, AZ
Strong
Officer
2
GBM TRANSPORT LLC
USDOT 3719766Active· WEST VALLEY, UT
Strong
Officer
3
KALEB TRANSPORTATION LLC
USDOT 3910440Active· FORT WORTH, TX
Strong
Officer
4
LOVE 4 LOGISTIC LLC
USDOT 3133965Inactive· CLIFTON, NJ
Strong
Officer
5
M&Z ATL HOTSHOTS LLC
USDOT 3652161Inactive· NORCROSS, GA
Strong
Officer
6
MAWI TRANS LLC
USDOT 3062595Inactive· ROCHESTER, NY
Strong
Officer
7
MOHAMMED A MOHAMMED
USDOT 2800822Inactive· SEATAC, WA
Strong
Officer
8
RIGHT EXPRESS LLC
USDOT 4239355Active· DETROIT, MI
Strong
Officer
9
SPEEDY EXPRESS LLC
USDOT 3778899Active· KANSAS CITY, MO
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. 10/25/2024MCS-150 update filed

    0.0M mi reported (2023)

  2. 10/03/2024Registered with FMCSA

    PRIVATE PROPERTY

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

🚛

Operations

Classification

  • PRIVATE PROPERTY

Area served

  • Intrastate (Non-Hazmat)

FMCSA safety rating

Rating
Not rated
Type
Rated
Last review
📄

MCS-150 registration

Form date
2024-10-25
Reported mileage
1 mi (2023)

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 24, 2026, 3:48 PM. VioCodes is not affiliated with FMCSA. To dispute incorrect data, file a DataQs Request for Data Review.