Skip to main content

Route

Everett → Medford

PAEEverettSeattle Paine Field International Airport
MFRMedfordRogue Valley International-Medford Airport
Distance
383 mi
Estimated flight time
~1h 15m

Same local time in Everett and Medford.

No nonstop connection observed

Our route data contains no observed nonstop flight from Everett to Medford. That does not rule out a one-stop journey; see the direct destinations of Everett for the options.

About this route

  • Domestic route: both airports are in the same country.
  • Direct destinations observed from Everett: 41.
  • Direct destinations observed from Medford: 17.

The airports on this route

Seattle Paine Field International Airport

Everett, United StatesPAE / KPAE

Regional airport · 41 direct destinations · 2 runways · longest runway 9,009 ft

75 °F · ClearSource: METAR observation via the NOAA Aviation Weather Center

Rogue Valley International-Medford Airport

Medford, United StatesMFR / KMFR

Regional airport · 17 direct destinations · 1 runway · longest runway 8,799 ft

80 °F · ClearSource: METAR observation via the NOAA Aviation Weather Center

Alternative airports for this journey

Same journey, a different airport nearby - with an observed direct connection.

About the route from Everett to Medford

The distance between Seattle Paine Field International Airport (PAE) and Rogue Valley International-Medford Airport (MFR) is approximately 383 mi; no direct connection has been observed in our route data.

Frequently asked questions about this route

How far is Everett from Medford by air?
The great-circle distance between Seattle Paine Field International Airport and Rogue Valley International-Medford Airport is approximately 383 mi.
Is there a direct connection from Everett to Medford?
No direct connection between PAE and MFR has been observed in our route data. That does not rule out a one-stop journey.
What is the current time difference between Everett and Medford?
Same local time in Everett and Medford.

Where this data comes from

The route data comes from the flight archive (ADS-B, adsb.lol): which connections actually flew over the last twelve full months and who flew them, combined with our own airport, runway, and airline datasets. It is reference data about observed routes - not a current timetable and no claim about bookability.

The flight archive of the last twelve months has nothing for this route, so we say nothing about frequency.

Route data updated on October 11, 2026.