Route profile

Yuma (YUM) → Phoenix (PHX)

A reference for the Yuma MCAS/Yuma International Airport to Phoenix Sky Harbor International Airport route. You'll find the operators on file, the great-circle geometry, the connecting options if no nonstop fits your dates, and a short profile of each endpoint airport.

257 kmGreat-circle distance
160 miIn miles
1h 02mApprox. block time
2Operators on file

The flight from Yuma (YUM) to Phoenix (PHX) covers a great-circle distance of roughly 257 km (160 miles). Aircraft leave Yuma MCAS/Yuma International Airport on an initial east heading. As US domestic sectors go, this one sits in the short-haul bracket: long enough that most carriers run it as its own dedicated rotation, but short enough to fit inside a single crew duty period.

2 carriers file a direct YUM to PHX sector, with American Airlines and US Airways among the operators on record. A route attracting this many carriers usually points to a city pair with both leisure and business demand, or a competitive hub-to-hub link where the airline alliances overlap on the same metal.

Operators on the YUM → PHX direction

Carriers with at least one scheduled rotation on this sector in the OpenFlights dataset, ranked by the number of code-shared filings.

IATAAirlineCountryCallsign
AA American Airlines United States AMERICAN
US US Airways United States U S AIR

At well under 1,500 km this is a regional sector. Carriers typically run narrow-body aircraft from the Airbus A320 family or the Boeing 737 series, with regional jets (Embraer E-Jet, CRJ) showing up on lower-frequency rotations. Block time runs around 1h 02m. Expect a single-aisle cabin and no real meal service. A snack and a drink is usually all you get.

If a nonstop doesn't match your dates, Los Angeles (LAX), –, and – show up on both ends of the network and make the most natural connecting points. The connecting-hubs grid below extends that list to the eight strongest options, ranked by each airport's overall departure activity. That ranking is a fast proxy for how many onward flights a single stop is likely to feed.

Connecting hubs

Airports that already appear on both ends of this network. They're the natural one-stop options when no nonstop matches your dates, ranked by overall departure activity.

Both endpoints sit inside the United States, so this counts as a domestic sector for fare-bucket, baggage, and carry-on purposes. Reservations on US carriers usually pick up the standard domestic checked-bag fee unless you hold elite status, and TSA PreCheck eligibility applies at the departure airport. See the United States routes index for other domestic pairs in the same network.

On the day of operation, the YUM to PHX direction lifts off heading east, then the great-circle track curves to compensate for the Earth's rotation. The return PHX to YUM sector heads west out of the gate, with 2 operators on file for the inbound side. Combine the two operator lists for a full picture of the city pair's competitive landscape.

Endpoints

Other routes from Yuma (YUM)

Other destinations served from the same origin. Handy for combining trips or for finding an alternate first leg.

Other routes into Phoenix (PHX)

Other origins that already file scheduled service into the destination airport.

Reading this route page

The operator list reflects scheduled-route filings in the OpenFlights dataset, not real-time availability. A carrier appearing here publishes a scheduled service on this sector. It isn't a live timetable, and the actual flight numbers, frequencies, and aircraft types shift season to season. For booking and current schedules, cross-reference the airline page above with the carrier's own website.

Distance here is the great-circle arc between the two airports' published coordinates. Real flight tracks wander off that line because of wind, ATC routings, oceanic crossings, and political airspace constraints. Block time is an estimate covering ground taxi, climb, cruise at typical jet speeds, and descent. Real block times shift with aircraft type, weather, and traffic, so treat the stat-strip number as a planning indicator rather than a published flight time.