What "Approved" Doesn't Mean

On Saturday, two Airlink jets flew a low-level flyover of Cape Town Stadium ahead of the Springboks and All Blacks test. Flight tracking data suggests one aircraft came within roughly 50 feet of the stadium roof. Footage of the moment spread fast, and so did the debate. Airlink's position is that both aircraft stayed within approved and rehearsed safety limits. Several aviation observers watching the same footage have publicly disagreed, arguing the margin looked considerably tighter than that statement suggests. Whether Airlink's safety margin was in fact adequate is a live, contested question that this piece is not trying to settle.

What is useful, regardless of how that specific dispute resolves, is the distinction sitting underneath it, one that matters just as much inside a founder-led business as it does above a packed stadium: "approved" describes a decision that was made. It says nothing, by itself, about how much room for error existed once that decision met reality.

Approval is a signature, not a safety margin

A plan gets approved when the right person signs off on it. That process answers one question: did someone with authority say yes. It does not automatically answer a second, more important question: what happens if this plan is executed even slightly imperfectly. Those are different questions, and founder-led businesses routinely treat the first as if it answers the second.

Critics of the Cape Town flyover argue the margin left little room for a gust of wind, a timing delay, or a misjudged descent, a claim Airlink disputes. If the critics are right, then approval alone did not make that plan safe, it just meant nobody stopped it beforehand. If Airlink is right, the plan had more room in it than it looked like from the ground. Either way, the general point holds: an approved plan and a plan with a real margin for error are not automatically the same plan, and it is worth knowing which one you actually have before it is tested in public.

Where founder-led businesses make the same bet

The pattern shows up constantly at the $1M-$20M stage, usually with far less spectacle and far more financial exposure. A contract gets approved by whoever happened to be in the room, not by whoever actually understood the liability inside it. A hiring plan gets approved against last quarter's revenue, with no real test of what happens if this quarter comes in soft. A delivery timeline gets approved because a client wanted to hear yes, without anyone checking how much slack exists if a supplier is late or a key person is out sick for a week.

Each of these decisions was, technically, approved. Few of them had a margin deliberately built in for the ordinary, predictable ways that plans go slightly wrong. That is the useful parallel the Cape Town flyover debate offers an entire country's worth of business owners at once: a plan can clear every approval step and still turn out, in hindsight, to have had less room in it than anyone checked for.

Building the margin in, not bolting it on afterward

Good governance is not the question "did we get this approved." It is the question "what happens if this plan is even a little bit wrong on the day," asked before the plan runs, not after something goes sideways. For a founder-led business, that means a cash flow forecast that survives a slower month, not just a good one. A contract review that catches the clause nobody in the room understood. A delivery commitment with enough slack that one delay does not cascade into a client relationship.

None of this is about being risk-averse. Airlink still flew the flyover, and most businesses should still take the bold client, the aggressive hire, the ambitious timeline. The difference between a bold move and a reckless one is rarely visible in the plan itself. It is visible in how much room the plan leaves for reality to be slightly less cooperative than the rehearsal.