This research page turns Phoenix Auto Dispatch’s maintained public route matrix into a transparent, reusable planning dataset. It summarizes the corridors Phoenix currently maintains, how those routes are distributed by distance and state pair, and whether both directions of a city-to-city corridor are maintained.
This is not shipment-volume, pricing, market-share or live carrier-capacity data. A maintained route means Phoenix has chosen to keep a public planning page for that direction because it has usable route evidence and customer-planning value.
Download the CSV snapshot Research & content standardsGo beyond the raw CSV. This data-derived report analyzes distance distribution, interstate share, endpoint connectivity, bidirectional coverage and state-pair coverage across the same maintained route snapshot—with explicit limitations so coverage is not confused with customer demand.
Read the 2026 analysis →Distance is a planning input, not a quote. The bands below summarize the numeric distance values already maintained in Phoenix’s route records.
| Planning distance band | Maintained routes |
|---|---|
| Under 500 miles | 312 |
| 500–999 miles | 114 |
| 1,000–1,499 miles | 64 |
| 1,500–1,999 miles | 28 |
| 2,000+ miles | 61 |
| No numeric distance | 0 |
Median numeric planning distance: approximately 410 miles across routes with parseable distance evidence.
These labels describe how a route entered or is maintained in Phoenix’s public route set. They are editorial/data-governance classifications, not measures of booking volume.
| Classification | Routes |
|---|---|
| Maintained curated corridor | 447 |
| Market-backed maintained corridor | 108 |
| Evidence-led maintained corridor | 24 |
Coverage is not popularity. This table only shows which state pairs have the most maintained Phoenix route directions in this snapshot.
| State pair | Maintained directional routes |
|---|---|
| FL ↔ TX | 17 |
| AZ ↔ CA | 13 |
| CA ↔ NV | 11 |
| CA ↔ TX | 10 |
| FL ↔ GA | 10 |
| MN ↔ WI | 10 |
| FL ↔ FL | 9 |
| CA ↔ CA | 8 |
| CA ↔ FL | 8 |
| FL ↔ NY | 8 |
| IL ↔ IN | 8 |
| IL ↔ TX | 8 |
Phoenix Auto Dispatch. “Maintained Auto Transport Route Planning Dataset.” Snapshot August 28, 2026. https://phoenixautodispatch.com/research/Citation and analytical reuse are welcome with attribution to Phoenix Auto Dispatch and a link to this canonical research page. Reuse should preserve the limitation that the dataset measures Phoenix’s maintained planning coverage—not shipment volume, price, popularity or live capacity.
The U51 dataset and U52 analysis now include reusable visuals for route-distance distribution and endpoint connectivity. Every chart is generated from the same maintained 579-route snapshot and keeps the distinction between Phoenix planning coverage and actual shipment demand.
Google’s Preferred Sources feature lets eligible readers choose a domain they want highlighted more often in supported Google Search experiences. Google controls source eligibility and where preferred-source highlighting appears; this is an audience preference feature, not a general ranking guarantee.
If the interactive control is unavailable, open Google source preferences. Availability is determined by Google.
Use this page as the primary source for Phoenix’s maintained route-planning dataset, methodology, downloadable data and related research assets. The wording below is a recommended plain-language reference, not a claim of academic publication, independent validation or third-party endorsement.
Phoenix Auto Dispatch. “Auto Transport Route Planning Dataset & Research.” Phoenix Dispatch LLC. Maintained 579-route planning dataset; CSV snapshot dated August 28, 2026. https://phoenixautodispatch.com/research/
