The sector is held by NetJets Aviation.
Airport pair · hand carry reference
IND Indianapolis to STL St Louis
Indianapolis International, the United States, to St Louis Lambert, the United States. Computed from the scheduled network held on 2026-09-07.
- Nonstop
- 3 times a week
- Great circle
- 367 km
- Block, estimated
- 1h 02m
- Door to door
- 7h 47m
What IND to STL looks like
The IND to STL sector, the carriers on it and the flying time, before anything is promised to anybody.
Indianapolis IND to St Louis STL is a short sector of 367 km by great circle, flown nonstop 3 times a week.
At the cruise speed this site models for 367 km, 720 km an hour, and thirty minutes of taxi at the two ends, the flight blocks at about 1h 02m.
Indianapolis IND is a large airport in the network held here, 107 scheduled destinations and 171.9 departures a day. St Louis STL has 108 destinations and 229.7 departures a day.
St Louis is one hour behind of Indianapolis all year.
The pair sits inside the Americas, a corridor where the site already publishes 13 written lanes that go into customs and ground detail this page does not.
Who flies the sector, and how often
Average daily frequencies on IND to STL from the scheduled route statistics, both directions, with the operating carriers named.
| Direction | Flights a day | Flights a week | Operated by |
|---|---|---|---|
| IND to STL | 0.43 | 3 | none held |
| STL to IND | 0.14 | 1 | NetJets Aviation |
One carrier holds the sector, NetJets Aviation, so a cancellation has no second nonstop behind it and the connections below stop being theoretical.
The two directions are not level: IND to STL runs 3 times a week, the return runs about once a week, and a round trip has to be planned around the thinner of the two.
Between them the two directions put about 4 departures a week on IND to STL, which is the number that decides whether a seat can be found today or on Thursday.
The clock from collection to signature
The same ground timings the route calculator starts from, applied to the 1h 02m block time on IND to STL. Change any of them in the tool further down and the total moves with them.
| Stage | Allowed | Elapsed |
|---|---|---|
| Collection and the run to IND | 90 min | 1h 30m |
| At IND before departure | 180 min | 4h 30m |
| IND to STL in the air, estimated | 62 min | 5h 32m |
| Formalities at STL | 90 min | 7h 02m |
| Delivery run in St Louis | 45 min | 7h 47m |
| Door to door | 467 min | 7h 47m |
On the desk standard ground timings, ninety minutes to collect and reach the airport, three hours at the airport before departure, ninety minutes of arrival formalities and a forty five minute delivery run, the door to door figure for IND to STL is 7h 47m.
A courier who leaves Indianapolis at 09:00 local is on the ground in St Louis at about 09:02 local and at the door by 11:17 the same day.
Working backwards from a six in the evening handover in St Louis, the last useful departure from Indianapolis is around 15:43 local.
When the nonstop does not work
Every airport that joins the two ends, ranked by when they land, among the ones whose weaker leg is dependable enough to plan on. Connection time is allowed for the size of the hub. 38 of them join IND to STL.
| Connecting at | IND to hub, flights a day | Hub to STL, flights a day | Track, km | Estimated, gate to gate |
|---|---|---|---|---|
| Chicago MDW | 2.57 | 6.14 | 665 | 3h 29m |
| Chicago ORD | 18.14 | 16.57 | 701 | 3h 32m |
| Kansas City MCI | 1.29 | 3.14 | 1,104 | 3h 38m |
| Columbus CMH | 0.86 | 2 | 949 | 3h 39m |
| Nashville BNA | 2.71 | 4 | 838 | 3h 44m |
| Detroit DTW | 7.14 | 5.86 | 1,078 | 3h 50m |
38 airports connect the two ends on the scheduled network held here. The quickest of the dependable ones is Chicago MDW, where the weaker of the two legs still runs about twice a day.
Through MDW the routing covers 665 km against the 367 km nonstop track and takes about 3h 29m in the air and on the ground at the hub, allowing 90 minutes to connect at an airport of that size.
That is only 2h 27m more than the nonstop, which is close enough that a connection is worth taking when the nonstop is full or badly timed.
Behind it, Chicago ORD at 3h 32m and Kansas City MCI at 3h 38m hold the same connection, so a booking has three hubs to try before it has to wait for the nonstop.
The two ends are only 367 km apart in a straight line. Allowing a road track a quarter longer than that and eighty kilometres an hour, a car covers it in about 5h 44m, so a courier who misses the flight drives rather than connects, and on a short deadline the road is often the plan from the start.
Industry within reach of the two ends
Public manufacturing and research sites whose logistics run through IND or STL. Listed as industrial geography, not as customers of anyone.
- Eli Lilly, IndianapolisResearch and manufacturing at the group head office. An American cluster with European trial sites. Logistics through Indianapolis IND.
Plan Indianapolis to St Louis yourself
The same tool the dispatchers use, open to anybody and free. It is loaded with this pair already. Change either end, add a stopover or a preferred airline, and it works out the connection, the transit and the door to door clock, with the real departures underneath. Put it on your own site if it is useful to you.
min
min
min
min
Restrictions
Where this came from, and where to look next
- Carriers and frequencies: AeroDataBox scheduled route statistics, retrieved 2026-09-07. Average daily flights, not a timetable.
- Distances: great circle from published coordinates. They read short against a flown track, which is why the block time above applies a factor to them.
- Block and connection times: the same model the route calculator lower down this page runs, at the same rounding.
- Restrictions: the airport notes file, checked 2026-09-07.
- Industrial sites: public company information. Nothing here says or implies that any company named is a customer of any courier operator.
Who publishes this. OnBoard Courier is a placement desk in Dubai. An assignment is carried out by a vetted partner operator, with the desk as the single point of contact from the quote to the signature. This page exists because our own dispatchers need the answer for IND to STL in the twenty minutes before a promise is made, and a reference only one operator can read is not a reference. Free to read, quote and cite. Found an error? Tell us and we will correct it.
If you need something moved rather than looked up, the desk prices a hand carry in fifteen minutes.
More pairs through IND and STL: Atlanta to Indianapolis, Indianapolis to Chicago, Boston to Indianapolis, Detroit to Indianapolis, Indianapolis to Seattle, Indianapolis to San Francisco, New York to Indianapolis, Indianapolis to Houston.