Rickenbacker International Airport
Columbus, United StatesLCK / KLCK
Regional airport · 29 direct destinations · 2 runways · longest runway 12,103 ft
53 °F · RainSource: METAR observation via the NOAA Aviation Weather Center
Route
Columbus → Lansing
LCK
ColumbusRickenbacker International Airport
ColumbusRickenbacker International AirportLANLansingCapital Region International Airport
LansingCapital Region International Airport- Distance
- 222 mi
- Estimated flight time
- ~55m
Same local time in Columbus and Lansing.
No nonstop connection observed
Our route data contains no observed nonstop flight from Columbus to Lansing. That does not rule out a one-stop journey; see the direct destinations of Columbus for the options.
About this route
- Domestic route: both airports are in the same country.
- Direct destinations observed from Columbus: 29.
- Direct destinations observed from Lansing: 16.
The airports on this route
Capital Region International Airport
Lansing, United StatesLAN / KLAN
Regional airport · 16 direct destinations · 3 runways · longest runway 8,507 ft
51 °F · CloudySource: 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 Columbus to Lansing
The distance between Rickenbacker International Airport (LCK) and Capital Region International Airport (LAN) is approximately 222 mi; no direct connection has been observed in our route data.
Frequently asked questions about this route
- How far is Columbus from Lansing by air?
- The great-circle distance between Rickenbacker International Airport and Capital Region International Airport is approximately 222 mi.
- Is there a direct connection from Columbus to Lansing?
- No direct connection between LCK and LAN has been observed in our route data. That does not rule out a one-stop journey.
- What is the current time difference between Columbus and Lansing?
- Same local time in Columbus and Lansing.
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.