Skip to main content

Route

Bristol → Cincinnati

TRIBristolTri-Cities Regional TN/VA Airport
LUKCincinnatiCincinnati Municipal Airport Lunken Field
Distance
212 mi
Estimated flight time
~55m

Same local time in Bristol and Cincinnati.

No nonstop connection observed

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

About this route

  • Domestic route: both airports are in the same country.
  • Direct destinations observed from Bristol: 11.
  • Direct destinations observed from Cincinnati: 32.

The airports on this route

Tri-Cities Regional TN/VA Airport

Bristol, United StatesTRI / KTRI

Regional airport · 11 direct destinations · 2 runways · longest runway 7,999 ft

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

Cincinnati Municipal Airport Lunken Field

Cincinnati, United StatesLUK / KLUK

Regional airport · 32 direct destinations · 3 runways · longest runway 6,102 ft

53 °F · RainSource: 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 Bristol to Cincinnati

The distance between Tri-Cities Regional TN/VA Airport (TRI) and Cincinnati Municipal Airport Lunken Field (LUK) is approximately 212 mi; no direct connection has been observed in our route data.

Frequently asked questions about this route

How far is Bristol from Cincinnati by air?
The great-circle distance between Tri-Cities Regional TN/VA Airport and Cincinnati Municipal Airport Lunken Field is approximately 212 mi.
Is there a direct connection from Bristol to Cincinnati?
No direct connection between TRI and LUK has been observed in our route data. That does not rule out a one-stop journey.
What is the current time difference between Bristol and Cincinnati?
Same local time in Bristol and Cincinnati.

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.