A civil drone business does not scale by hiring more pilots.
It scales when someone can run the UAS operator capability in a repeatable way:
Authorisation frame. Safety. Operations manual. Operational control. B2B delivery inside those limits.
At Beyond Chiefs we call this the Operator-File Test.
Christian Pobbig and Beyond Chiefs work from Hamburg on AI Executive Search in DACH. “Head of UAS Operations” is not a statutory post. It is one organisational name for the function that holds that operating capability.
The real question:
Is there an operator organisation behind the title — or only a box on the org chart?
In the specific category the UAS operator is the regulatory starting point.
Legal persons register in the EASA Member State of their principal place of business.
For specific-category operations the operator generally needs an operational authorisation from the competent national aviation authority — unless the operation falls under a standard scenario or is covered by LUC privileges.
The authorisation sets the conditions under which the operator may fly.
It is not a single-flight permission. Inside its scope it can cover many operations.
The operator is not building a flight log.
They are building an operating capability.
The authorisation architecture includes the operations manual.
It does not only describe the aircraft.
It describes how the organisation actually operates:
Procedures.
Responsibilities.
People.
Safety measures.
Operating limits.
Emergency processes.
Depending on the authorisation path, risk assessment and compliance evidence sit with it.
An operations manual written only for the application is worthless.
The test:
Does the company actually fly the system it described to the authority?
EASA separates UAS operator and remote pilot.
The operator must create suitable procedures, put qualified people in place, and designate a remote pilot for each operation.
The remote pilot owns their concrete tasks before and during the flight.
That split matters.
A pilot can fly well.
Set flight standards.
Train other pilots.
That still does not mean they hold the operator organisation.
An internal title like Chief Pilot does not change that.
If a company uses that title, we would expect four things.
Which operations may the company actually fly?
Not:
What does sales want to sell?
But:
What does the existing regulatory frame carry?
Operational authorisation, STS, or where relevant a LUC must match real operations.
Who keeps the operating safety architecture working?
Not documentation alone.
Procedures, responsibilities, training, incident handling, changes, and evidence.
The system must work when nobody expects an inspection.
Can the same kind of operation be run by several teams under the same rules?
Named remote pilots.
Qualifications.
Records.
Mission procedures.
Pre-flight and contingency processes.
Change management.
A drone business scales only when operations no longer depend on one pilot’s implicit knowledge.
The customer may only get what the operator can deliver safely and inside the rules.
This is where the role becomes commercial.
Sales can win work.
Operations must answer:
Can we actually run this order inside our existing operating envelope?
If not:
Do we need a new authorisation?
A change?
More mitigations?
Or must we simply not sell that order in this form?
UAS operations sits between regulation and revenue.
A Light UAS Operator Certificate is not mandatory for every drone company.
It is an extra organisation and maturity step.
With a LUC, depending on privileges granted, the operator may self-authorise certain operations.
Requirements on organisation, management system, and operational control rise with that.
Here the accountable manager appears as a defined responsibility inside the safety management system.
That does not mean:
Accountable manager = CEO.
And not:
Accountable manager = Head of UAS Operations.
The functions can sit in one person.
They do not have to.
In designated U-space the UAS operator remains responsible for the operation.
Mandatory U-space services must be used.
The provider delivers services.
They do not simply take the operator’s responsibility for safe flight.
A software contract or USSP subscription is not an operations function.
Civil only: inspection, survey, logistics, infrastructure. No weapons. No military use.
A “Head of UAS Operations” is a real leadership seat when that person can hold an organisation that operates repeatably inside its approved frame.
Not only pilots.
Not only aircraft.
Not only documents.
But:
Authorisation frame.
Safety system.
Operations manual.
Operational control.
Commercial delivery inside those limits.
If that capability is missing, the title is probably larger than the function.
No.
A Chief Pilot can own flight standards and flying quality.
The operator organisation is a different layer.
No.
A LUC raises organisational maturity, requirements, and potentially privileges.
It does not automatically define the internal post “Head of UAS Operations”.
No.
In the LUC context the accountable manager is a relevant safety-management function.
How that maps to CEO, COO, or Head of UAS Operations is the company’s call.
The title is secondary.
What matters is who actually holds the operating system.
Anyone staffing the operator organisation, not only the pilot title, buys the AI Executive Search mandate.
.webp)
