ORD → FOEChicago to Topeka

live

Direct flights from Chicago (ORD) to Topeka (FOE) run nonstop between the two airports. The nonstop covers 737 km, an estimated 1 hour 27 minutes in the air.

ORD Chicago smooth · +0
FOE Topeka tracking
737 km · ~1h 27m est.
Under pressure · 0 airlines · nonstop
69 / 100

route health from live ORD and FOE delay boards

Flight time~1h 27mestimated from route distance

Airports right now

live boards
ORDChicago +0 min smooth ⛅ overcast · SSE 8 kt Full ORD delay board →
FOETopeka tracking Full FOE delay board →

How the Chicago to Topeka route actually runs

Pro Flight Search records official board updates for nonstop ORD to FOE flights through the day: schedules, estimates, gate pushes and actual departures. The verdict above comes from operated flights, so it reflects what this route does rather than what the timetable promises.

Planning around a delay? Live airport delays · Weather delay risk map · Will a delayed flight be cancelled? · Do planes make up time in the air? · How we measure

Cite this data

Journalists, bloggers, and researchers may cite this page with attribution and a link to Pro Flight Search.

Suggested citation

Pro Flight Search: Chicago (ORD) to Topeka (FOE) route reliability, measured from operated flights on official airport boards.

Canonical URL
https://proflightsearch.com/search-flights/ORD-FOE
How we measure this →

ORD to FOE questions

Is ORD–FOE running on time right now?

Mostly on schedule. Both endpoints currently score the same, route health score 69/100. The airports section above carries the live status and delay window at both ends.

How long is the flight from ORD to FOE?

Great-circle distance is 737 km. With typical jet cruise speed plus taxi, climb and descent, expect roughly 82–93 min gate-to-gate on this route.

What does the route health score measure?

A blend of departure-side delay at ORD and arrival-side delay at FOE, computed from rolling delay windows (refreshed every 40 minutes) with a daily-rollup fallback. Current MVFR, IFR, or LIFR endpoint weather caps the score when flight rules can limit throughput. Higher is healthier: 100 means operations are clean at both ends.