Detroit by Mid-Morning, Pittsburgh by Dinner

Automotive programme work moves between engineering centres, tier-one suppliers, and assembly plants on a cadence set by the launch calendar. Missing a build review is not a scheduling inconvenience; it is a programme risk. The Pittsburgh–Detroit pair is a clean example: 209 nm apart, and awkward by every scheduled option.

Wheels up at 07 45 puts you on site in Detroit by 09 11, with 7 h 23 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 4 h 35 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.

Neither end of this leg constrains the aircraft. That means short-notice departures are realistic and a schedule change on the day is usually absorbable rather than a rebooking exercise.

Halcyon quotes the Vision Jet and nothing else, which is why we know which operators run it well and which fields it likes. The aircraft carries a whole-airframe parachute and Garmin Safe Return emergency autoland — neither of which exists on any other jet in production. Flights are operated by FAA Part 135 certificate holders.