IRON HORSE TRANSPORT AND REPAIR LLC
No authority breakdown on file.
No active policies on file.
No BOC-3 filing on file.
Carrier analysis & narrative context SEO summary, status notes, AI overview, and safety profiles
IRON HORSE TRANSPORT AND REPAIR LLC is a motor carrier based in PIMA, AZ, registered with the FMCSA under USDOT 2514670. The carrier is currently active in FMCSA's records, and has not yet received a formal FMCSA safety rating. MCS-150 self-reporting puts the fleet at 3 power units and 4 drivers, with 8 roadside inspections on file and a peak out-of-service rate of 50.0%. Use this page to verify the carrier's authority and insurance, review its inspection and crash history, and cross-reference live data on FMCSA SAFER before booking a load or onboarding a partner.
Carrier is unrated
FMCSA has not assigned this carrier a formal safety rating. Use the inspection history and BASIC scores below to assess on-road performance.
IRON HORSE TRANSPORT AND REPAIR LLC is a small fleet, operating 3 power units and 4 drivers, based in Pima, AZ. Across 7 roadside inspections in the last 24 months, the fleet recorded a 28.6% out-of-service rate, with no reportable crashes on file. no operating authority record was located.
7 roadside inspections over the last 24 months, up 600% versus the prior 24 months, concentrated in AZ (6) and NM (1), with Level 3 inspections the most common.
28.6% out-of-service rate; led by Vehicle Maintenance (84.6% of violations); top code 393.45B2-B-AIR (Brake tubing/hoses inadequate) cited 3 times.
The fleet comprises 3 power units (small fleet) and 4 drivers; Kenworth, Peterbilt, and Utility are the most-inspected makes.
Compliance & contact
Risk Signals
Out-of-Service rate vs same-size peers FMCSA roadside inspections, % placed out-of-service
Compared against 332,679 ACTIVE carriers operating 2–5 power units (±50% of this carrier's 3 unit fleet).
Inspection Analytics Monthly activity · BASIC mix · state map
Monthly Inspection Activity (24 months)
Violations by BASIC Category
Activity by State
| State | Inspections | OOS | OOS % | Last Inspection |
|---|---|---|---|---|
| Arizona (AZ) | 6 | 2 | 33.3% | Dec 4, 2025 |
| New Mexico (NM) | 1 | 0 | 0.0% | Dec 26, 2025 |
Vehicle Fleet Top makes and models observed in roadside inspections
| Make | Model | Inspections |
|---|---|---|
| Kenworth | 4 | |
| Peterbilt | 3 | |
| Utility | 2 | |
| Eagle Trai | 1 | |
| Great Dane | 1 | |
| Mack | 1 | |
| Mckt | 1 | |
| Trvs | 1 |
Recent Inspections (8 rows) View all 8 →
| Inspection # | Date ▼ | State | Level | Station | Vehicle | Violations | Top Codes | OOS |
|---|---|---|---|---|---|---|---|---|
| 86658359 | Dec 26, 2025 | NM | 3 | — |
KW TRUCK TRACTOR
|
1 | 392.2-SLLS2 | No |
| 86497306 | Dec 4, 2025 | AZ | 2 | WILLCOX AZ |
PETERBILT TRUCK TRACTOR
|
2 | 392.2-SLLMF, 393.9A-LFTSI | No |
| 86316418 | Nov 12, 2025 | AZ | 1 | SAFFORD AZ |
KENWORTH TRUCK TRACTOR
|
10 | 177.823A-HMTVMMCNID, 393.45B2-B-AIR, 393.47E | Yes |
| 86274466 | Nov 7, 2025 | AZ | 3 | DOUGLAS AZ |
PETERBILT TRUCK TRACTOR
|
0 | — | No |
| 85238466 | Jul 15, 2025 | AZ | 3 | TUCSON AZ |
WESTERN ST TRUCK TRACTOR
|
1 | 392.2-SLLTL | No |
| 85194162 | Jul 10, 2025 | AZ | 1 | SAN CARLOS AZ |
KENWORTH TRUCK TRACTOR
|
4 | 393.43A-TPV, 393.9A-LCL, 393.78A-WS | Yes |
| 83457204 | Dec 18, 2024 | AZ | 2 | BYLAS AZ |
KENWORTH TRUCK TRACTOR
|
8 | 393.9A-LCL, 393.78A-WS, 393.9A-LBL | No |
| 79330957 | Aug 3, 2023 | AZ | 1 | — |
PTRB TRUCK TRACTOR
|
1 | 393.78 | No |
Recent Crashes (6 rows)
| Report # | Date ▼ | State | Fatalities | Injuries | Tow | Hazmat | Severity |
|---|---|---|---|---|---|---|---|
| AZ0000069210 | Nov 29, 2023 | AZ | 0 | 0 | Yes | Yes | Tow |
| AZ0003977428 | Nov 26, 2022 | AZ | 0 | 0 | Yes | Yes | Tow |
| AZ0000068532 | Dec 10, 2021 | AZ | 0 | 0 | Yes | Yes | Tow |
| AZ0000062325 | Nov 9, 2021 | AZ | 0 | 1 | Yes | Yes | Injury |
| AZ0003809105 | Sep 2, 2021 | AZ | 0 | 0 | Yes | Yes | Tow |
| NM0710619235 | Apr 16, 2021 | NM | 0 | 1 | Yes | Yes | Injury |
MC Certificate Documents (1 PDF)
Authority Records (above) are FMCSA docket status and lifecycle events. MC Certificate Documents here are the archived PDF letters for each action — grants, reinstatements, revocations, name changes, and transfers. They are related but not the same dataset: one row per PDF letter, not one file per docket.
Click a row to open that specific letter. Multiple letters per docket are listed separately by action type and date.
| Date | Docket | Action | Authority | |
|---|---|---|---|---|
| Jul 31, 2014 | MC876176-C | CPL | CERTIFICATE | CPL → |
Top Stations & Violation Codes Where this carrier gets inspected and what they get cited for
Most-Inspected Stations
| Station | State | Inspections | OOS |
|---|---|---|---|
| BYLAS AZ | AZ | 1 | 0 |
| DOUGLAS AZ | AZ | 1 | 0 |
| SAFFORD AZ | AZ | 1 | 1 |
| SAN CARLOS AZ | AZ | 1 | 1 |
| TUCSON AZ | AZ | 1 | 0 |
| WILLCOX AZ | AZ | 1 | 0 |
Top Violation Codes Cited
| Code | Description | Category | Cited | OOS |
|---|---|---|---|---|
| 393.78 | Windshield condition defective | Vehicle Maintenance | 1 | 0 |
Related Records Cross-references to every adjacent page
-
Arizona carriers
All carriers based in Arizona
-
Pima carriers
Carriers based in Pima, AZ
-
Stations in Arizona
Where this carrier might be inspected
-
8 inspections
Full roadside inspection history
-
6 reportable crashes
FMCSA MCMIS crash log
-
Fleet recall search
NHTSA recalls covering this fleet's vehicle years/makes
-
File a complaint
Open the FMCSA National Consumer Complaint form for this carrier
-
Carrier comparison tool
Side-by-side vs. other carriers
-
Certificate lookup
Look up any FMCSA authority by MC/MX/FF docket number
-
All state carrier directories
Browse carriers in every US/CA/MX jurisdiction
-
How FMCSA safety ratings work
BASIC percentiles and compliance review context
-
BOC-3 process agents explained
Why every interstate carrier must file a process agent
-
FMCSA compliance filings guide
MCS-150, insurance, and authority filing requirements
-
Roadside inspection rights
What drivers and carriers can expect during a stop
How to verify IRON HORSE TRANSPORT AND REPAIR LLC
- Verify USDOT and MC numbers match the carrier's documents. Compare the USDOT number and MC docket on this page to the numbers on the carrier's invoice, rate confirmation, or load-board listing. A mismatch between the carrier's claimed numbers and the registered legal name is the single most common red flag.
- Check active operating authority and insurance status. Confirm the Authority Records show at least one ACTIVE docket for the type of operation you're booking, and that the Active Insurance card lists a current BIPD/Primary policy. A revoked authority or uninsured carrier cannot legally operate.
- Review safety rating and SMS BASIC scores. Check the carrier's FMCSA safety rating (if any) and the SMS BASIC table. A high percentile in any BASIC category — especially Unsafe Driving, HOS, or Vehicle Maintenance — is worth investigating before tendering a load.
- Examine inspection and crash history. Open the Inspection History and Crash History subpages for the full record. Look for patterns: repeat OOS findings on the same unit, multiple crashes in a short window, or violations clustered in one BASIC category.
- Cross-reference real-time data with FMCSA SAFER. For the most current snapshot — within 24 hours of any insurer filing or authority change — click through to the FMCSA SAFER lookup. TruckCodex mirrors SAFER and L&I daily; SAFER itself reflects filings within 24 hours.
Frequently asked questions about IRON HORSE TRANSPORT AND REPAIR LLC
Is IRON HORSE TRANSPORT AND REPAIR LLC an active motor carrier? ▾
What is IRON HORSE TRANSPORT AND REPAIR LLC's safety rating? ▾
How many inspections has IRON HORSE TRANSPORT AND REPAIR LLC had? ▾
What is IRON HORSE TRANSPORT AND REPAIR LLC's out-of-service rate? ▾
Where is IRON HORSE TRANSPORT AND REPAIR LLC based? ▾
Does IRON HORSE TRANSPORT AND REPAIR LLC have valid operating authority? ▾
How many trucks and drivers does IRON HORSE TRANSPORT AND REPAIR LLC operate? ▾
Has IRON HORSE TRANSPORT AND REPAIR LLC had any crashes? ▾
About FMCSA carrier records
Every commercial motor carrier operating in the United States is required to register with the Federal Motor Carrier Safety Administration (FMCSA) and obtain a USDOT number. The USDOT number is a permanent, unique identifier — once assigned, it stays with the carrier for life and is never reissued to another company. Carriers must update their registration every two years on Form MCS-150 to keep their address, fleet size, and operating data current.
Carrier safety data lives in FMCSA's Motor Carrier Management Information System (MCMIS): roadside inspections, crashes, out-of-service findings, and the seven Behavior Analysis and Safety Improvement Categories (BASICs) that make up the SMS scoring methodology. For-hire carriers must also hold operating authority — an MC, FF, or MX docket number — which is separate from the USDOT number and requires continuous insurance and BOC-3 process-agent filings to remain active.
TruckCodex mirrors FMCSA's public SAFER and L&I systems on a daily refresh cycle. Every record on this page reflects what FMCSA has on file. We do not edit or modify carrier data — for real-time confirmation immediately before a transaction, click through to the FMCSA SAFER lookup linked in the related records section above. Safety ratings, when present, come from formal compliance reviews; most active carriers have not been reviewed and are correctly listed as unrated.
Data sources & freshness
TruckCodex aggregates official public-sector datasets. See the Source registry for dataset-level coverage and the Freshness log for last-import timestamps.
Census, SAFER, SMS, Licensing & Insurance (L&I), roadside inspections, crashes, and authority history.
Vehicle recall campaigns, defect investigations, and consumer safety complaints (SCRS).
Cross-border carrier registry and Canadian recall campaigns where applicable.
TruckCodex is an independent aggregator; it is not affiliated with FMCSA, NHTSA, EIA, or Transport Canada. Always verify compliance-critical information directly with the originating agency.