Detroit by Mid-Morning, Columbus by Dinner

The industry is organised around campuses that are hours apart by road and awkward by air. Engineers making that trip weekly are the clearest case in business aviation for flying rather than driving. Columbus to Detroit is 156 nautical miles of it, and 3 h 25 m by car in conditions that rarely hold.

Wheels up at 07 45 puts you on site in Detroit by 09 01, with 7 h 43 m on the ground before the aircraft goes back. Home by 18 30. That is about as easy as a there-and-back day gets — no hotel, no overnight bag, and no second day of anyone's time.

The realistic alternative here is driving, and 3 h 25 m each way is the sort of number that gets quietly accepted until someone adds it up. Two of those in a day is most of a working day spent in a car, arriving for the meeting already tired. The scheduled-airline option on a pair this length is usually worse rather than better once you count the drive to the airport, the screening queue, and the connection a route this short often requires.

Both The Ohio State University Airport and Oakland County 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.