aviation

Long runs are where the hard problems come loose. The first hour belongs to the body; after that the mind is free to turn over whatever the desk could not resolve. Debugging works the same way: force rarely helps, distance does, and what surfaces is usually not the fix but the wrong assumption underneath it.

The cockpit teaches the stricter version. Fly the aeroplane first, and the right problem shows itself in the time that buys. Running offers the same time without the altitude, by removing every option except patience. Which here is not a virtue but a technique, and the one that separates a patch that works from an answer that is right.

Some decisions are only arithmetic, made once the facts are in. The ones that matter come earlier, when waiting for certainty costs more than being wrong. Across flying, ultrarunning, building software, and tasting whisky, the same problem keeps appearing in different clothes: how to act on incomplete information, and how much margin to leave for the gap.

Weather is a probability dressed as a fact; a race is a bet placed hours before it pays out; code that compiles is not code that is correct; a cask is a decision no one tastes for decades. What the four teach is not courage but a better relationship with uncertainty: how much room to keep for being wrong.

The moment I arrive at the airfield, something shifts. The rush drops away. What remains is the preflight — thorough, clockwise, unhurried. Not as formality, but as foundation. On the ground you still have a choice not to go. In the air, you work with what you prepared.

The SportCruiser came my way when a flight school standardised its fleet. The alternatives didn't fit — literally. Together with a few flying friends I bought it. Not a single regret. Flying is the privilege of being above everything that was pulling at you an hour ago, provided you took the time for everything that came before.