When Assumption Becomes the Enemy: Lessons from a Helicopter’s Hard Landing

Image of the crashed helicopter courtesy of ATSB

On 5 October 2025, a Schweizer 269C-1 helicopter departed Lake Macquarie Airport for what should have been a simple ferry flight to Duri, New South Wales. The pilot had just collected the aircraft after its annual service. This was to be a routine flight, one they’d done many times before.

Before take-off, the pilot looked at the fuel gauge: 92 litres. The number matched expectations, and the aircraft had just come from maintenance, so it seemed reliable. Normally, the pilot used a dipstick to physically verify the fuel level. But this time, trusting the indication, and the recent maintenance, felt reasonable.

It was a small assumption. And as with so many accidents, that’s where the story began.

En route, about halfway through the flight, the pilot noticed something the fuel seemed to be burning faster than expected. The calculations didn’t match what they were seeing. They didn’t ignore it, they recognised it and decided to act. The pilot told their passenger they’d make a precautionary landing to inspect the fuel situation.

That decision was a good one. Unfortunately, the engine stopped producing power before they could land. At 2,500 feet, the helicopter ran out of fuel and the pilot executed a skilled autorotation, guiding the powerless helicopter to a hard but survivable landing beside a railway line. Both occupants walked away. As you can see from the image at the top, the helicopter did not.

The official cause of this accident was fuel exhaustion. But, as with every aircraft accident, the deeper story is one of assumption, attention, and the complexity of rules designed to prevent exactly this kind of event.

Lesson 1: The Pilot Did the Right Thing — And That Matters

It’s easy to read “fuel exhaustion” and picture carelessness. However, that’s not the full story of what happened here. The pilot noticed something was wrong and took steps to manage it. That’s not failure, that’s actually resilience in action. The decision to conduct a precautionary landing came too late to prevent engine failure, but the thinking was sound: recognise the anomaly, act conservatively, prioritise safety.

In a world obsessed with outcomes, we often overlook good decisions that just came a fraction too late. But those moments show the mindset we should all strive for: adaptability, awareness, and humility.

Business takeaway: on’t measure decision quality purely by outcomes. Reward people who speak up, pause, or act on uncertainty, even if the result isn’t perfect. They’re the ones building safety into your culture. Encouraging and promoting this kind of thinking creates organisations that catch errors early, instead of punishing them late.

Lesson 2: When We Stop Verifying, We Start Guessing

The pilot’s small assumption of trusting the gauge instead of checking with a dipstick seems trivial. In safety-critical systems, verification is often the last defence against error.

In this case, that skipped check wasn’t laziness; it was made consciously. After all, the aircraft had just come from professional maintenance. It felt safe to assume it was right.

This is a good example of authority bias: our tendency to trust experts and systems over our own senses. In aviation, that bias can turn routine into risk. In business, it can do the same:

• Teams assume reports are accurate because “finance signed off.”

• Managers assume compliance is handled because “it’s in the policy.”

• Leaders assume systems will flag problems automatically.

Each assumption erodes a layer of safety.

Business takeaway: Verification is discipline, not distrust. Double-checking is how professionals stay professional. If verifying something feels unnecessary, that’s usually the moment it matters most.

Lesson 3: Rules Alone Don’t Create Safety

This is a bit of a tangent but worthy of highlighting given the context of this accident. Australia’s Civil Aviation Safety Authority (CASA) publishes an Advisory Circular on aircraft fuel requirements that runs to 44 pages.

Forty-four pages. On fuel.

It’s a perfect example of how safety can become its own complexity trap. Each new rule, clarification, and sub-clause is added to prevent the next accident. Paradoxically, the web eventually becomes so dense that it’s impossible for any human to keep it all in working memory.

We do this in every industry. Something goes wrong, and instead of simplifying the system to make it easier to do the right thing, we add another layer of regulation, process, or policy.

The result is the more rules we create, the harder safety becomes to achieve.

Business takeaway: Rules on their own don’t create safety, understanding does. Focus on clarity, not complexity. When systems, manuals, or compliance frameworks become unmanageable, they stop protecting people and start trapping them.

Lesson 4: Fuel Isn’t the Only Thing That Runs Out

This accident wasn’t just about fuel; it was about time and attention which are two resources that deplete faster than we realise. The pilot did the maths mid-flight, recognised the issue, and made the right call to land. But by the time that decision became an action, the window had closed.

It’s the same pattern seen across industries. Teams notice warning signs but underestimate how quickly their margin for recovery is shrinking. They wait for one more data point, one more confirmation, one more meeting, until it is too late, and suddenly the problem has outpaced them.

Business takeaway: Encourage early action, not perfect timing. It’s far better to pause too early than too late. In aviation, the phrase is “land while you still have options.” In business, you might instead say “change course while you still can.”

Lesson 5: Design Systems for Real Humans

Aviation safety is built not on perfect behaviour, but on systems that assume imperfection.

What if the helicopter had a simple “low fuel” interlock after maintenance? Or if the maintenance paperwork clearly highlighted, “Fuel level not verified post-service”? Small design changes like these catch predictable human errors before they become catastrophic.

The same principles can be applied to business. If success depends on everyone following every rule perfectly every time, your system is already fragile. People get distracted. Pressure builds. Context changes. These things are normal so we need to build systems to cope with them.

Business takeaway: Build systems that trap small errors before they escalate. This could be the use of prompts, peer checks, and simplified workflows to make the right action easy and the wrong action hard.

Final Thoughts: The Thin Line Between Routine and Risk

The pilot of the Schweizer helicopter didn’t fail out of carelessness. They actually did almost everything right, they noticed a problem, made a good decision, and executed a safe emergency landing.

But they were also flying inside a system where verification depended on memory, safety depended on complexity, and success depended on perfect attention. That’s not a human problem, it's a design problem. And it’s one every organisation faces.

When rules multiply, assumptions grow, and “normal” feels too comfortable, risk hides in plain sight.

Safety, in the air or in business, doesn’t come from doing more things right. It comes from designing systems where doing the right thing is simple, obvious, and normal.

-----------------------------------------------------------------------------------------------------------------------------------------------------

Mike Mason and Sam Gladman are the co-founders of On Target, a leadership and team development company that brings elite fighter pilot expertise into the corporate world. With decades of combined experience in high-performance aviation, they specialise in translating critical skills such as communication, decision-making, and teamwork into practical tools for business. Through immersive training and cutting-edge simulation, Mike and Sam help teams build trust, improve performance, and thrive under pressure—just like the best flight crews in the world.

If you'd like to learn more about how On Target can help your team, contact Mike and Sam at info@ontargetteaming.com