There is a strange thing that happens towards the end of a long test day.
Nothing about the aircraft has necessarily changed. The procedures are the same, the operating limits haven’t moved, and the weather may still technically be acceptable. Yet somehow the decisions being made at four o’clock in the afternoon can feel very different from the decisions that would have been made at nine that morning.
I’ve seen versions of this throughout my career, and I suspect anyone who has spent enough time around operational environments will recognise it.
The team has travelled a long way to get there. The aircraft is finally behaving itself. Perhaps you’ve lost part of the morning to a technical problem that turned out to be frustratingly simple. The weather forecast suggests tomorrow will be worse, the customer is expecting progress, and there is one test point left that everyone would really like to complete.
Individually, none of those things should affect whether the aircraft flies.
Collectively, they absolutely can.
This is one of the things I find fascinating about operational decision-making. We spend a great deal of time defining limits around aircraft, systems and environments, yet considerably less time thinking about what happens to the people making decisions as pressure begins to build.
The wind limit hasn’t changed because the customer is watching.
The battery hasn’t gained capacity because the team has driven three hours to the test site.
The communications link doesn’t become more reliable because this is the last opportunity to fly before a demonstration.
And yet our willingness to operate closer to those limits can change remarkably quickly.
Usually, nobody announces that this is happening.
There isn’t a meeting where somebody says, “Right, we’re under a bit of pressure now, so let’s quietly accept more risk.”
It happens much more subtly than that.
Language begins to change.
“It’s still within limits.”
“We’ve flown in worse.”
“Let’s just get this one done.”
“It should be fine.”
“We’re here now.”
None of those statements are inherently reckless. In the right circumstances, every one of them might be completely reasonable. What interests me is why they tend to appear when the cost of saying no has started to increase.
That’s an important distinction.
We often think of operational decisions as a balance between risk and capability. In reality, there is frequently a third force in the room: consequence.
Not the consequence of flying.
The consequence of not flying.
A delayed programme. A disappointed customer. Another day of travel. A missed demonstration. A team that has spent hours preparing for an operation that now won’t happen. Sometimes simply the frustration of packing everything away having achieved less than we hoped.
Those consequences are real. Pretending they don’t influence people would be naïve.
The problem begins when they influence us without being acknowledged.
A decision made under pressure can still be the correct decision. Experienced operators make those judgements every day. Operational maturity isn’t about removing pressure from the system; that would be impossible. It’s about recognising when pressure has entered the decision and making sure it doesn’t quietly become part of the safety argument.
I’ve found one of the simplest ways of exposing this is to ask:
Would we make the same decision if there was no consequence to saying no?
It’s an uncomfortable question.
Imagine the customer wasn’t watching.
Imagine the team hadn’t travelled.
Imagine tomorrow’s weather was perfect.
Imagine there was no demonstration next week.
Imagine nobody cared whether that final test point was completed today.
Would you still fly?
If the answer is yes, that’s useful.
If the answer suddenly becomes less certain, that’s useful too.
It doesn’t automatically mean the original decision was wrong. It simply reveals that something other than the operation itself has entered the judgement.
Once it’s visible, it can be managed.
When it’s invisible, it becomes much more dangerous.
This is also why procedures and operating limits, while essential, can never completely replace judgement. A limit gives us a boundary, but it doesn’t necessarily tell us how sensible it is to operate close to that boundary when several other things are simultaneously moving in the wrong direction.
Imagine the wind is within limits, but only just. The crew is tired but technically within duty limits. Battery performance is acceptable but slightly lower than expected. The communications link is working but has shown occasional degradation during the day.
Every individual element remains acceptable.
The operation may therefore appear acceptable.
But the system is telling you something.
This is where the gap between compliance and judgement becomes important.
Compliance asks whether each individual condition remains within an acceptable boundary.
Judgement asks what those conditions mean together.
That difference matters enormously in complex operations because risk rarely arrives neatly packaged as a single red condition on a checklist. More often, it appears as several amber conditions that individually look manageable.
This is also where our previous ideas begin to connect again.
The Four Questions help expose what we believe about the situation.
Evidence tells us whether that belief is supported.
Assumptions reveal what we’re taking for granted.
Operational drift tells us whether small changes have quietly become normal.
Readiness asks whether the whole system, not merely the aircraft, is prepared for what we’re asking it to do.
Pressure sits across all of them.
It doesn’t necessarily change any of the answers.
It changes how much we want those answers to be true.
And that may be one of the most important human factors in operational decision-making.
The best operators I’ve worked with aren’t immune to pressure. Far from it. They want the mission completed, the test point achieved and the customer satisfied just as much as everybody else.
What distinguishes them is that they recognise when those desires have entered the decision.
Sometimes they still fly.
Sometimes they modify the operation.
Sometimes they wait.
And occasionally they pack everything away and go home.
That last decision can feel remarkably unsatisfying.
There is no successful flight to celebrate. No useful test data. No photograph of the aircraft in the air. From the outside, it can look like nothing happened.
But sometimes the best operational decision of the day is the flight that never took place.
Not because somebody was afraid to fly.
Because somebody understood why they wanted to.
Operational Law No. 3
Pressure rarely changes the limits. It changes how willing we are to approach them.
Related
Discover more from sUAS News
Subscribe to get the latest posts sent to your email.
