Skip the Hub: Indianapolis to Tulsa

Upstream and midstream work is site work. Rig visits, plant turnarounds, and midstream inspections happen on operational schedules that no published timetable was built to serve. For the Indianapolis to Tulsa version, the gap is 501 nm — far enough to cost a day, close enough that losing one feels absurd.

At 501 nm this is a longer day: 1 h 53 m each way, 3 h 47 m of flying. It still closes. On site by 09 08, 5 h 29 m on the ground, home by 18 30. Whether that beats an overnight depends on how long the meeting runs, and we will say so plainly rather than selling the version that bills more hours.

Nobody is driving 10 h 58 m each way for a meeting, so the real comparison is the airline routing — and between Indianapolis and Tulsa that typically means a connection, a total block time well over half a day, and an arrival window you do not control. A single segment removes the misconnect risk rather than managing it.

Both Indianapolis International Airport and Tulsa International Airport are straightforward fields for this aircraft with margin in hand, which matters more than it sounds: routine pairs are the ones that dispatch reliably, and reliability is most of what a business traveller is actually buying.

One type, learned properly. We place this leg with a Part 135 operator we already know on the Vision Jet, in an aircraft carrying CAPS — a parachute over the entire airframe — and a one-button emergency autoland any passenger can use. For a company putting four people on one aircraft, those are the specifications that matter.