DEPLOYDatabase

Deployment

Aurora Driver on International LT (2nd-gen) at El Paso–Phoenix Corridor, USA

Aurora's second-generation driverless hardware kit on the International LT (Navistar) platform, the basis for fully observer-free operation targeted for Q2 2026 (produced via Roush). Distinct from the current PACCAR fleet, which still carries an OEM-requested observer.

Aurora Driver on International LT (2nd-gen) by Aurora Innovation · Catalog entry · 1 source · not yet field-verified · Trucks

Recent coverage

See all coverage →


Aurora expanded its driverless trucking network to include the El Paso–Phoenix corridor, forming a continuous 1,000-mile multi-state driverless route. This is part of Aurora's 10-route network spanning the Sun Belt.

Key facts

Corridor
El Paso–Phoenix (1,000-mile continuous route)
Operator
Aurora Innovation
Milestone
100,000+ driverless miles completed

Safety record

No incidents on record for Aurora Driver on International LT (2nd-gen) at El Paso–Phoenix Corridor, USA.

Only active incidents are counted. Retracted incidents are excluded from this summary but remain reachable at their canonical URLs.

Trust tier
Catalog entry · 1 source · not yet field-verifiedhow tiers work →
Last updated
2026-08-09
Status
operational
First seen
2026-01-01
ID
8454315b-c3d7-42c0-b610-58d28328b2ea

Timeline

  1. Jan 2026
    First recorded
    Aurora Driver on International LT (2nd-gen) first documented operating at El Paso–Phoenix Corridor, USA.
  2. Aug 2026
    Current status: operational, reviewed
    Latest recorded state. New status transitions append here as the deployment-status recorder produces them.

On the deployment map

Operates worldwide

Aurora Driver on International LT (2nd-gen) is deployed globally rather than at a single verified site, so there is no map pin.

Free to use on your site, with a link back to DEPLOY.

Aurora Driver on International LT (2nd-gen) operates in El Paso–Phoenix Corridor, USA. Explore the full verified map:

Sources (1)

  1. Aurora Triples Driverless Network to 10 Routes and Prepares to Expand Across U.S. Sun Belt · https://ir.aurora.tech/news-events/press-releases/detail/132/aurora-triples-driverless-network-to-10-routes-and-prepares-to-expand-across-u-s-sun-belt · 2026-01-01
Methodology: Verified · 1 source (1 primary) · last reviewed 2026-08-09

Verification posture

Verified

High confidence

Review state

Stable

Last reviewed 2026-08-09

Maturity + lifecycle

Maturity stage: pilot

Lifecycle: active

Architectural position

Cohort: truck

Sources by quality tier

1
primary-company-ir
Company IR disclosure

The framework is documented at /methodology. Corrections at /corrections. Reviewer: DEPLOY editorial team.

Methodology surface for Aurora Driver on International LT (2nd-gen) at El Paso–Phoenix Corridor, USA.

Common questions

What is the Aurora Driver on International LT (2nd-gen) deployment at El Paso–Phoenix Corridor, USA?
Aurora Driver on International LT (2nd-gen), built by Aurora Innovation, is recorded as a deployment at El Paso–Phoenix Corridor, USA on the DEPLOY registry. Aurora Innovation operates the deployment directly.
Who operates Aurora Driver on International LT (2nd-gen) at El Paso–Phoenix Corridor, USA?
Aurora Innovation, the manufacturer of Aurora Driver on International LT (2nd-gen), operates this deployment directly. This is a maker-deploys-its-own-product arrangement rather than a customer pilot.
When did the Aurora Driver on International LT (2nd-gen) deployment at El Paso–Phoenix Corridor, USA go live?
The deployment is recorded as starting January 1, 2026 on the DEPLOY registry. Earlier activity may exist but is not yet sourced.
Have there been incidents at the Aurora Driver on International LT (2nd-gen) deployment at El Paso–Phoenix Corridor, USA?
No active incidents affecting this deployment are recorded on the DEPLOY registry. Absence of recorded incidents is not a guarantee no incident occurred; DEPLOY records only sourced incidents and suppresses retracted ones.

Deploy Watch

Track this deployment.

We notify you when status changes against primary-source evidence, contract events surface, or a related incident is filed.

Machine-readable surfaces