States / Arizona
West coverage
Freight shipping in Arizona
We quote from 2 origin cities in Arizona across 98 modeled lane pages that begin here, and 96 modeled lane pages that arrive here from another state. The cities named on this page are origin points the lane model prices from — not offices, terminals or staffed locations we claim to have. Every number below is derived from the lane directory at render time.
Last reviewed 2026-11-17 - Portlandia Logistics dispatch
Origin cities and modeled lanes in Arizona
One row per origin city the model prices from. The nearest and longest modeled lane in each row are the two lane pages that bracket that hub's coverage, with the planning miles and planning band the model gives them.
| Origin city the model prices from | Modeled lane pages | Nearest modeled lane | Longest modeled lane |
|---|---|---|---|
| Phoenix, AZ Residential job-site freight, equipment and distribution |
49 | Phoenix, AZ → Tucson, AZ 125 planning mi · 1-2 business days |
Phoenix, AZ → Newark, NJ 2,495 planning mi · 5-6 business days |
| Tucson, AZ Defense, mining supply and cross-border manufacturing |
49 | Tucson, AZ → Phoenix, AZ 125 planning mi · 1-2 business days |
Tucson, AZ → Newark, NJ 2,470 planning mi · 5-6 business days |
A row is a city the lane model prices from, not an office or terminal we operate. Planning miles are the model's own output (hub distance × a 1.17 road factor); the band is the model's day count plus one day for an LTL break. Both are planning figures, never a carrier commitment.
What the model records about Arizona
The lane model prices Arizona from 2 origin cities: Phoenix and Tucson. The West region of the model is where these hubs sit. The corridors the model records for them: Phoenix — I-10 and I-17 serve Phoenix; Tucson — I-10 and I-19 serve Tucson. Those are the routes the model uses to explain a lane, not equipment we operate on them.
The freight base the model records for those metros reads: Phoenix — residential job-site freight, equipment and distribution; Tucson — defense, mining supply and cross-border manufacturing. That is the market description the lane directory carries for each city, and it is the only description these pages use.
Receiving, as the model records it: Phoenix — job-site delivery often needs liftgate, curbside placement or a straight truck; Tucson — industrial sites use gate check-in and residential delivery is common. Terminal and node notes in the model: Tucson — a rail yard and the Nogales crossing to the south. Those facilities are operated by third parties; we hold no port, rail or terminal rights and claim no facility in Arizona. Seasonal constraints the model records: Phoenix — extreme summer heat, which changes packaging and driver-hour planning; Tucson — desert heat. They shape how a lane is planned, not what it costs on a given day.
The lane geometry in Arizona
The lane pages that begin in Arizona run from 125 to 2,495 planning miles, a spread of 2,370 miles between the shortest and longest card in that set; the planning band runs from 1-2 business days to 5-6 business days. They reach 50 destination cities in 26 states, and 48 origin cities outside Arizona route into it. The instant estimate uses the same model for any lower-48 ZIP pair, so a lane that has no page here is still priced from the same basis.
The same model prices the lane on the quote form: origin and destination ZIPs, weight, pallets and freight class in, and a planning range with the basis shown out. Nothing on this page is a booked rate.
Service lines quoted from this desk
The mode is chosen from the lane and the freight, not the state. Each page states where its scope ends.
| LTL and partial freight Palletized freight priced from the lane, the class and the handling you declare. |
| Full truckload 53-ft dry van and flatbed capacity arranged through third-party carriers. |
| Intermodal Rail for the long segment with a truck on each end, quoted as one lane. |
| Port and rail drayage Container moves between a terminal and the first real destination. |
| Flatbed and step-deck Securement, tarping and loading method captured before the rate is confirmed. |
| Temperature-controlled Reefer range, pre-cool and monitoring captured at booking, verified on the carrier. |
| High-value and solar Declared value checked against the carrier certificate before tender. |
| Returns pickup Pickup at a home or jobsite with visible condition documented before the truck leaves. |
| Expedited and hot-shot Time-critical ground freight quoted per load against a real ready time. |
| Warehousing and cross-dock Storage and transload coordinated at a contracted facility, never a facility we own. |
| Heavy haul and permitted Oversize and overweight moves quoted per move with permits and escorts named. |
| Drop trailer Trailer placement instead of live loading, where a dock needs the window. |
What we do not claim about Arizona
- No office, terminal, warehouse or cross-dock in Arizona. The 2 origin cities above are places the lane model prices from. We do not own tractors, trailers or chassis and we do not hold port, rail or terminal rights anywhere.
- No authority claim. Pre-launch: no broker authority is claimed and no tenders are accepted yet. Nothing on this site is an offer to arrange freight. The full record is on the authority page.
- No coverage percentage and no capacity claim. The counts on this page are the model's card counts, not a share of a market and not a promise that any particular lane will be covered on a given day.
- No transit promise. Planning miles and planning bands are model output. The firm pickup window and rate appear on a rate confirmation naming the carrier.
- No customer names and no reviews. There are no verified shipper reviews to publish yet, so none are quoted here.
- Every number is derived. This page reads lib/lanes.js at render time; add a lane to the model and the counts on this page change by themselves.
Destination cities the model reaches from Arizona
A destination list, not a service promise: each name is a city that appears as a lane destination in the model from an origin in Arizona. 50 destination cities in 26 states.
Albuquerque, NM · Atlanta, GA · Austin, TX · Baltimore, MD · Boise, ID · Charlotte, NC · Chicago, IL · Cincinnati, OH · Cleveland, OH · Columbus, OH · Dallas, TX · Denver, CO · Detroit, MI · El Paso, TX · Fresno, CA · Houston, TX · Indianapolis, IN · Jacksonville, FL · Kansas City, MO · Laredo, TX · Las Vegas, NV · Long Beach, CA · Los Angeles, CA · Louisville, KY · Memphis, TN · Miami, FL · Milwaukee, WI · Minneapolis, MN · Nashville, TN · New Orleans, LA · Newark, NJ · Oakland, CA · Oklahoma City, OK · Orlando, FL · Phoenix, AZ · Portland, OR · Raleigh, NC · Reno, NV · Sacramento, CA · Salt Lake City, UT · San Antonio, TX · San Diego, CA · Savannah, GA · Seattle, WA · Spokane, WA · St. Louis, MO · Tacoma, WA · Tampa, FL · Tucson, AZ · Tulsa, OK
Questions about freight in Arizona
Do you have an office, terminal or trucks in Arizona?
No. 2 origin cities are listed on this page because the lane model prices from them - Phoenix, AZ and Tucson, AZ. They are not Portlandia offices, terminals, warehouses, cross-docks or staffed locations. We do not own tractors, trailers or chassis and we hold no port or rail facility rights.
Which Arizona cities can you quote from?
The model carries 2 origin cities in Arizona: Phoenix, AZ and Tucson, AZ. Every one of them is a modeled origin, so the instant estimate prices a lane from those cities the same way it prices any lower-48 ZIP pair. If a city is not in the model, the ZIP pair is still priced from the same basis.
What do the miles and the band in the table mean?
Planning miles are the model's distance for the city pair (hub distance times a 1.17 road factor, rounded). The band is the model's day count plus one day for an LTL break. In Arizona the cards that begin here run from 125 to 2,495 planning miles. Both figures are planning output, not a carrier commitment.
How do I get a firm rate for a Arizona lane?
Enter the origin and destination ZIPs, the weight, the pallets and the freight class on the quote form. You get the planning range, mileage and transit before you submit; dispatch then confirms the carrier, the pickup window and the firm rate in writing on a rate confirmation. Pre-launch: no broker authority is claimed and no tenders are accepted yet. Nothing on this site is an offer to arrange freight.
Talk to dispatch
Mon–Fri 8:00am–6:00pm ET
After hours, email the lane and the pickup window; the on-call dispatcher replies for loads already in transit, and new quotes are answered the next business day.
(502) 385-3399 Email the deskAuthority status
Pre-launch: no broker authority is claimed and no tenders are accepted yet. Nothing on this site is an offer to arrange freight.
Where these numbers come from
Hub count, lane-card counts, planning miles and planning bands are computed from the lane directory in this build, not typed into this page. 2 cities in Arizona appear as origin hubs in that model.
Know the number before you commit
Send the lane from Arizona and see the mileage, the planning transit and the range before you submit anything.