Ukrainian defence companies Culver Aerospace and GLEFA have unveiled the Behemoth, a new medium-range strike drone that has already been deployed in combat. Details of the new system, which bears visual and operational similarities to the Iranian-designed Shahed loitering munitions used extensively by Russia, emerged on May 21.
The Behemoth is capable of hitting targets up to 300km (185 miles) away and carrying a payload of up to 75kg (165lb). The drone is equipped with a tandem warhead that combines an explosively formed penetrator—also known as a shock core—with a thermobaric charge. Designed to fly at low altitudes to reduce the likelihood of detection by enemy air defences, the Behemoth can operate autonomously or in FPV mode, using the Starlink system for communication.
The development comes as Ukraine surpasses Russia in the number of long-range drone strikes conducted in a single month. Ukrainian deep-strike drones have increasingly targeted Russian oil refineries, naval infrastructure, airbases and military facilities deep within Russian territory. The developers also introduced a separate Behemoth Deepstrike version, though technical specifications for this variant have not yet been publicly disclosed.
Production and development of such systems are being significantly bolstered by international partnerships. In April, Culver Aerospace signed a cooperation agreement with the German defence firm Helsing to jointly develop and produce drones at a factory in Germany, a project funded by the German government.
Furthermore, on February 24, Culver Aerospace concluded a five-year agreement with Denmark’s Copenhagen Global A/S. This partnership, part of a broader €800m package of accords between Ukrainian and European defence manufacturers, will focus on medium-range systems of up to 400km (250 miles) and long-range strike systems capable of reaching 2,500km (1,550 miles)
Related
Discover more from sUAS News
Subscribe to get the latest posts sent to your email.
On 20 May 2026, the Law Commission published its final report on aviation autonomy. Commissioned by the Department for Transport and the Civil Aviation Authority, the review addresses the legal barriers to safely deploying highly automated and autonomous systems in aviation. It focuses on three main use cases: drones, advanced air mobility such as vertical take-off and landing aircraft (VTOLs), and air traffic management. The overarching aim is to ensure that uncrewed aircraft systems (UAS) can operate with safety levels equivalent to crewed flights.
A central element of the report is drawing a clear line between remotely piloted and autonomous operations. To ensure legal certainty regarding who is responsible for aviation safety, the commission recommends that any flight where a human pilot can intervene should be classed as remotely piloted, while any flight without this possibility is autonomous. It advises retaining the current legal definition of a remote pilot and aligning their responsibilities with those of a commander in commercial air transport operations.
For passenger-carrying remotely piloted operations, ensuring equivalent safety with crewed aircraft is paramount. The remote pilot will hold ultimate legal responsibility for flight preparation checks, such as ensuring the aircraft is airworthy and that cargo is secured. Furthermore, the remote pilot will have the responsibility to refuse transport to individuals under the influence of drink or drugs. They will also be granted the power to take reasonable measures, including authorising passenger restraint under the Civil Aviation Act 1982, to protect the aircraft and its occupants in emergency situations. Operators will be required to ensure that passengers can contact a crew member at all times.
When operations become fully autonomous, the responsibilities of the pilot will shift significantly to the UAS operator. The operator will be required to use an aircraft designed to comply with operational limitations and avoid the risk of collision. Mandatory flight data recorders are also recommended for autonomous drone and VTOL operations to facilitate accident investigations and improve long-term safety.
The report also examines civil and criminal liability when accidents happen. It states that the current strict liability system will continue to function effectively for air carriers, although product liability relating to artificial intelligence requires a broader review. In terms of criminal law, the commission recommends updating the offence of hijacking under the Aviation Security Act 1982. Recognising that uncrewed aircraft could be seized by technological means or hacking without a hijacker being present on board, the report urges the UK to implement the Beijing Protocol to expand the legal definition of hijacking.
Finally, to safely integrate uncrewed flights beyond the visual line of sight, the report calls for legislative change to accommodate the certification of uncrewed aircraft systems traffic management (UTM) providers. These services will supply vital digital information about potential hazards and weather to uncrewed aircraft, ensuring they can share the airspace safely with crewed flights.
Related
Discover more from sUAS News
Subscribe to get the latest posts sent to your email.
In 2012, the UK drone sector was still relatively small. Multirotors existed, commercial aerial work was growing, and the Civil Aviation Authority’s focus was broadly understandable: keep unmanned aircraft away from people, aircraft, congested areas and controlled airspace, and require permission for higher-risk or commercial activity.
By 2026, the picture has changed dramatically. The UK now has a layered system of registration, Flyer IDs, Operator IDs, Open/Specific/Certified categories, operational authorisations, SORA assessments, Operational Safety Objectives, containment evidence, Remote ID, UK class markings, SAIL markings, Recognised Assessment Entities for Flightworthiness, and a growing family of CAP 722 guidance documents.
The question is no longer whether drones should be regulated. They clearly should be. The real question is whether UK drone regulation has moved from proportionate safety management into a culture of compliance expansion, where each new risk produces another document, certificate, marking scheme, or approval pathway.
The early years: simple rules, clear principles
The CAA’s CAP 722 has existed since the early 2000s, but the period around 2012 was still comparatively simple. CAP 722’s revision history shows the fifth edition was published in August 2012, with updates to terms, definitions, procedures and human factors material. The major structural changes came later, particularly in 2015, when the document was completely restructured and the Operating Safety Case process became central to permissions for more complex unmanned aircraft operations. (Civil Aviation Authority)
That older approach had faults, but it had one major strength: it was relatively understandable. Operators generally knew the basics: remain visual line of sight, keep clear of people and property, stay away from airports, and seek CAA permission for commercial or higher-risk work. It was not perfect, but the compliance burden was still recognisable to small operators and manufacturers.
The 2015 introduction of the OSC process was arguably the first major paperwork escalation. It asked operators to explain their concept of operations, aircraft systems, safety mitigations and operational procedures. For serious commercial work, that made sense. But it also began the shift from “fly safely and demonstrate competence” towards “produce a large body of evidence to prove that you might fly safely.”
2018–2019: airport restrictions made sense
One of the more defensible changes was the strengthening of airport flight restriction zones. Following the increasing public concern around drones near airports, the UK introduced clearer height restrictions and restrictions around protected aerodromes. CAA guidance published in 2019 explained the 400 ft limit and the expanded Flight Restriction Zone system, including airport traffic zones and runway protection areas.
This was a sensible area for regulation. Airports are one of the few places where even a small drone can create a serious aviation hazard. The 2019 changes extended restriction zones to include runway protection extensions, commonly described as 5 km by 1 km zones from runway ends, which was aimed at protecting aircraft during take-off and landing. (GOV.UK)
Very few responsible drone operators would argue against clear airport restrictions. Flight Restriction Zones are a good example of regulation targeted at a real and obvious risk.
The problem is that this targeted logic has not always been maintained elsewhere.
2020 onwards: the European-style category system arrives
The next major shift came with the adoption of the European-style framework: Open, Specific and Certified categories. The idea was logical on paper. Low-risk operations sit in the Open Category. More complex or higher-risk operations sit in the Specific Category. Very high-risk operations fall into the Certified Category.
But the practical effect was another layer of complexity. Instead of a relatively direct permission process, operators now had to understand subcategories, registration requirements, competency requirements, operational authorisations, risk assessments, mitigations and supporting guidance.
CAP 722 itself has also become part of a much wider ecosystem. The current CAP 722 page describes it as CAA guidance and policy for unmanned aircraft system operations, but the CAA drone publications area now includes a large family of related documents, including CAP 722, CAP 722A, CAP 722D, CAP 722G, CAP 722H, CAP 722J, CAP 722K, CAP 722L and further supporting publications. (Civil Aviation Authority)
The CAA is careful to say CAP 722 is guidance rather than law. But for operators, manufacturers and consultants, guidance often becomes quasi-law. If a CAA document says something “should” be done, then in practice it can become very difficult to obtain an authorisation without doing it.
2025–2026: class marks, Remote ID, SORA and SAIL marking
By 2026, the regulatory stack becomes even heavier.
The CAA has confirmed UK class marking requirements for drones, with UK0 to UK6 classes setting product requirements such as reliability, geo-awareness, Remote ID, flashing lights, labelling and conformity assessment. The CAA says this is intended to support clearer and simpler rules, but it also introduces another product compliance layer for manufacturers and importers. (Civil Aviation Authority)
Remote ID is another example. The CAA describes Remote ID as a system that transmits identification and location information from a drone, usually by Wi-Fi or Bluetooth, to support police and enforcement activity. From 2026 and 2028, different categories of aircraft and operations become subject to Remote ID requirements, including requirements linked to UK class-marked aircraft. (Civil Aviation Authority)
Again, the purpose is understandable. Enforcement agencies need tools to identify irresponsible operators. But the practical burden falls on everyone, including responsible operators who are already registered, insured, trained and operating under permissions. RID also has technical flaws which would need addressing as currently it is to easy to Fake RID for a drone.
Then there is UK SORA. The CAA’s SORA process requires operators to assess ground risk, air risk, operational volume, contingency volume, ground risk buffer, adjacent areas, Specific Assurance and Integrity Level, Operational Safety Objectives, containment requirements and supporting evidence. (Civil Aviation Authority)
For complex operations, risk assessment is necessary. But SORA risks becoming a paperwork machine. Instead of one coherent safety case, an operator can end up managing a web of documents, evidence references, OSO compliance statements, containment arguments, aircraft evidence, operational evidence, training evidence and maintenance evidence.
The introduction of SAIL Mark certificates and Recognised Assessment Entities for Flightworthiness adds another layer again. The CAA says RAE(F)s assess technical features and flightworthiness, while SAIL Mark certificates demonstrate that a UAS meets requirements linked to UK SORA SAIL levels. (Civil Aviation Authority) CAP 722K, first issued in March 2025, sets out policy and administrative guidance for UAS designers and RAE(F)s seeking SAIL Mark certification. (Civil Aviation Authority)
This is where many manufacturers and operators start to ask whether regulation has crossed a line. If a drone already uses standard components, radio modules, electronics and systems that have their own conformity evidence, how many times should the same basic compliance be rechecked? At what point does a safety process become a market barrier?
The safety record question
The most uncomfortable question for regulators is this: where is the fatality record that justifies the scale of expansion?
The CAA’s 2024 Annual Safety Review says there were around 720,000 registered RPAS users, made up of approximately 450,000 Flyer IDs and 270,000 Operator IDs. It should be noted people that stop flying drones still have Flyer IDs for years after they have stopped flying so the answer to how many are actually operating or flying drones will be closer to 270,000 operator ID number overall.
It also reports around 2,500 operational authorisations and 21,000 remote pilots with competency qualifications. In 2024, the CAA recorded 55 RPAS accidents and serious incidents, a 31% decrease from 2023. (Civil Aviation Authority)
The same review states that fatal injury reports in 2024 represented 0.02% of all occurrence reports and that all of those fatal injury reports involved general aviation aircraft. (Civil Aviation Authority)
That does not mean drones are risk-free. A falling aircraft can injure someone. A drone near an airport can create serious consequences. The AAIB and CAA rightly require reporting of accidents and serious incidents, and the CAA says occurrence reporting is intended to support safety learning rather than blame. (Civil Aviation Authority)
But if the UK civilian multirotor sector has not produced the kind of fatality record that was once feared, then the regulatory response should be tested against real evidence. Rules should be proportionate to actual harm, not hypothetical worst-case scenarios layered on top of one another indefinitely.
Has regulation gone too far?
In some areas, no. Airport Flight Restriction Zones make sense. Basic registration makes sense. Competency tests make sense for heavier or higher-risk drones. Operational authorisations make sense for operations near people, infrastructure, controlled airspace or complex environments.
But the broader direction is harder to defend.
The UK has moved from a relatively simple safety model to a compliance stack. A responsible operator or manufacturer now faces not just operational rules, but class markings, Remote ID, SORA, SAIL, RAE(F) assessments, evidence matrices, OSO mapping, containment arguments, competency levels and a growing CAP 722 document family.
This is regulatory bloat.
The danger is that the system starts to reward paperwork more than safety. A small manufacturer can spend months producing evidence packs, paying consultants, chasing assessments and cross-referencing guidance documents, while an irresponsible operator can still buy a cheap drone and ignore the rules entirely.
That is the core failure of over-complex regulation: it burdens the compliant while doing little to stop the reckless.
Are policymakers just justifying their jobs?
It is probably too simplistic to say CAA policymakers are merely trying to justify their jobs. The CAA has statutory duties. It has to respond to government, public concern, airport disruption, international rulemaking, police enforcement needs and rapid technology change.
But it is fair to ask whether the policy culture has become self-expanding. Every new framework creates new guidance. Every guidance document creates new interpretation. Every interpretation creates a need for consultants, assessors, templates, evidence packs and further CAA review.
At some point, the process becomes its own industry.
The CAA should be challenged to answer a simple question for every new requirement: what specific risk does this reduce, and what evidence shows that the reduction is worth the cost?
If the answer is clear, the rule should stay. If the answer is vague, the rule should be simplified or removed.
A better way forward
The UK does not need deregulation. It needs proportional regulation.
Keep airport restrictions. Keep sensible height limits. Keep registration and competency where the aircraft or operation presents a real risk. Keep operational authorisations for complex work.
But reduce duplication. Stop turning every safety concern into another certificate or marking scheme. Make SORA usable by normal operators, not just consultants. Ensure SAIL marking does not become an innovation tax. Review guidance regularly and remove obsolete layers. Most importantly, measure regulatory burden against actual accident and injury data.
The drone industry has matured. The rules should mature too.
From 2012 to 2026, UK drone regulation has gone from broad safety principles to a dense compliance ecosystem. Some of that evolution was necessary. Much of it now looks excessive.
If the goal is safer skies, regulation must remain clear, targeted and evidence-led. If the result is simply more forms, more marks, more certificates and more cost, then the system is no longer just managing risk. It is manufacturing bureaucracy.
Related
Discover more from sUAS News
Subscribe to get the latest posts sent to your email.
With an extensive 30-year career as a police officer, Simon’s current tasks include delivering the programme against the force’s strategy and reducing disruption across the rail sector.
He also leads on communication with aviation, risk and regulatory contractors, and oversees work on risk quantification and the safe and responsible implementation of a BVLOS capability for the police force.
Simon has been working on Counter-Unmanned Aircraft Systems since 2019, under the NPCC Counter Drones portfolio and as an embedded member of the Home Office Counter Drones Unit, and took on his current role in April 2025.
What fundamental problem were you trying to solve when developing the drone-in-a-box programme, and how did you prioritise early use cases such as trespass, obstruction, or cable theft?
Defining the problem space was a key activity as we sought to develop a BVLOS drone capability. We identified a number of use cases and prioritised trespass and disruption, because that actually covers most of the use cases anyway.
From there we identified that the drone-in-a-box solution is really well suited to covering our trespass and disruption hotspots.
What does success look like in the next 12 months for your team? Which metrics (e.g., reduction in delays, faster incident response, cost savings, officer time released) matter most?
All of those! We have done some benchmarking of benefits and once our drone-in-a-boxes start generating data we can look at benefits realisation.
We will identify a number of key metrics and how we can measure any benefits (which may be financial or time related for example), plus be able to articulate the benefits in using the drones to pro-actively patrol these locations.
BTP is the first UK force to routinely operate under State Aircraft BVLOS provisions. How did you build a legally robust, repeatable framework around that?
Yes, although other forces also have a similar capability, all operating slightly differently. But, we are
operating at a larger scale than anyone else.
The first step for us was to obtain legal advice, which gave us the basis to proceed – we were the
first force to do this and we shared the advice with our policing colleagues. The framework we use developed the force’s already mature drone operation and processes and is based around a ‘5 Towers model’: Leadership Governance and Capability Management, Risk Management, Competency Management, Fleet and Mission Systems Management, and Flight Operations Management.
Image courtesy of the British Transport Police
How closely does your operational model align to the UK CAA’s CAP3182 Future of Flight BVLOS Roadmap?
We work closely with our biggest partner, Network Rail. They are currently progressing a SORA application for drone-in-a-box based on our processes, technology and methodology, whereas we use State Aircraft exemptions.
We operate within regulation where possible, with an acceptance that some policing operations cannot be catered for by current regulation and that’s when we need to utilise State Aircraft exemptions, with an appropriate means by which the regulator can ensure these operations are safe.
How have you approached detect-and-avoid and airspace deconfliction, especially considering possible interactions with NPAS, HEMS, or other emergency aviation assets?
NPAS and HEMS are our biggest risk, given that we are effectively conducting all our drone-in-a-box operations in an Atypical Airspace Environment, below 200 feet.
To that end, we use existing policing technology to be aware of where and when both are operating. In addition, we are working closely with Dronecloud and Network Rail on a UTM system for the railway as well as others on a form of Electronic Conspicuity using novel sensors.
We have developed a means to use transponders on all our drone-in-a-box drones, which means we can be seen. Lastly, good communication with both our own and other users is essential!
What is your strategy for dealing with critical events like GNSS disruption, C2 link loss, or EMI around railway power infrastructure?
Having a background in Counter Drones, I know that there can be some disruption, although it is less than people think. Link loss is more common, particularly at lower levels around infrastructure, so we use a mesh network to increase signal reliability and the telephony network as a failsafe.
Image courtesy of the British Transport Police
Your remote operations centre at London Bridge is impressive. How do operators coordinate drone dispatch, mission approval, and real-time decision support from the control room?
Thank you! Our operations room has been built from scratch, with no real blueprint for using multiple drone-in-a-boxes.
What we have done is to ensure we can integrate with existing operations, based around our current drone capability, using the same processes.
How is live drone data fed into incident response workflows? Who sees what, and how does drone
footage accelerate on-scene decision-making?
As mentioned, we use existing processes, so there is no real change to the way of working for us. We can get imagery to key decision-makers across both the BTP and Network Rail, but clearly we need to make sure those decision-makers understand who is the key decision-maker in any incident. There is two-way communication with the pilots as well, so the drone can be re-directed as required.
What training and competency framework did you build for BVLOS operators?
We follow the NPCC guidance on training for pilots (which does include a BVLOS element), but have developed our own training for what we do as operating drone-in-a-box is uniquely different.
Image courtesy of the British Transport Police
Was there any resistance internally, and how did you help frontline officers trust an autonomous asset arriving ahead of them?
Communication is important, particularly getting across that we’re not replacing officers or taking away options to use the drones we have, that we’re simply focussing on our trespass and disruption hotspots.
We’re also managing expectations by communicating things like the locations we have the drone-in a-box, how far we can fly and how long the drone can be airborne.
We’re in a good place as most officers are now used to working with drones and this is just an
extension of that capability.
What privacy safeguards guide how you collect, store, review, and delete drone imagery captured
near stations, homes, or public spaces?
We have very strict rules relating to data and privacy, as you would expect. We only record incidents
if there is a policing purpose, operating with a pilot and a tactical flight officer, plus a supervisor, so
the safeguards are there. In addition, we record the room (mostly for safety reasons should an accident occur), but this adds to the level of professionalism we require.
How do you secure the box, the drone, and your communications channels against tampering, interference, or cyber threats?
All our equipment goes through a cyber-assurance process. It’s not about the imagery or necessarily the data, it is about unwarranted access to our wider systems. We have layered security for our hardware, not only to prevent damage or tampering, but to prevent accidents with uninvolved persons who may be nearby.
Image from Moonrock’s visit to BTP in 2026
How do you collaborate with Network Rail, TOCs/FOCs, and infrastructure partners to ensure seamless integration between policing, rail operations, and drone data flows?
This is a really good question. We have recently begun work on a Concept of Joint Operations, supported by both the BTP Chief Constable and the CEO of Network Rail. Here we’re looking at coordinating our drone efforts across rail, using each other’s assets and sharing drone imagery whether for infrastructure inspection or searching for trespassers. There is lots to do here and for us to look at, from a National Drone Flight Operations Room to a National Drone Response Team!
What does a scalable national deployment model look like in terms of infrastructure density, maintenance, operator staffing, and cost-effectiveness?
I think there has to be a limit to the number of assets we have, the real key to this is flexibility. The ability to move assets dependent on demand has to be the most cost-effective solution. The challenge is that our assets are adding value and that we can demonstrate the benefits!
What single enabler – technical, regulatory, or organisational – would most accelerate safe, scalable BVLOS policing in the UK? And how can industry partners best support that future?
I think the first enabler I would want is an agreed regulatory model that allows us to operate within regulation where we can, but where we need to we have a framework for the use of ‘State Aircraft’
exemptions to achieve policing objectives.
This in itself presents an opportunity for industry players to partner with policing or other agencies,
which would benefit the industry more widely.
Related
Discover more from sUAS News
Subscribe to get the latest posts sent to your email.
The first person to sound the alarm was an airport employee who would later become the case’s star witness. Spotting two strange objects hovering and darting across the evening sky, she didn’t hesitate: “There are two drones. They are large. It’s not toys,” she reported up the chain. Within minutes, Danish airspace was closed to everything except emergency landings.
What she saw that night, she later described in vivid detail. One object was a large, square shape, roughly 1.5 by 1.5 metres, that reminded her of a robotic lawnmower with rounded corners and a propeller at each corner. The second was smaller, white, round, and faster. Both had bright white lights. Yet the witness was remarkably candid about her own inexperience: she had never seen a real drone in person in her entire life, only on television, in films, or in the news. “I have not seen any drones physically… but I explain from what I feel, and then it was a drone,” she told investigators. To her, the slow hover that could suddenly accelerate, the propellers, and the lights all added up.
Police, however, reached a very different conclusion. After interviewing her four times and having experts analyse the phone video filmed by her colleague, they were clear: there were no drones. The large moving light captured on the grainy footage was a school training plane from Roskilde that had been cleared to fly in the area. The small, fast-moving “zigzagging” object was simply lens flare, a common reflection inside the camera lens caused by bright external lights. When the witness watched the same video again alongside journalists from Frihedsbrevet, she herself admitted that, yes, it could easily be mistaken for a small aircraft. Police delivered the same message to several of her colleagues: what they had seen were camera artefacts, ordinary aircraft… or, in one later case, a police helicopter.
That last detail reveals a classic false-confirmation loop. Once the initial drone report went out, authorities scrambled a helicopter from the police tactical unit to hunt for the suspected intruders. A colleague who spotted the helicopter later that evening naturally assumed it was yet another drone, only to be told by police that he had actually seen their own response aircraft. The very act of sending up a helicopter in pursuit of reported drones created a new “sighting” that seemed to confirm the original alarm.
Danish public broadcaster DR this week aired a documentary titled “Droner over Danmark” that further underlined concerns about the authorities’ handling of the events, including reports (as first reported by sUAS News) of the Danish military likely mistaking a Norwegian passenger airliner for a drone and firing upon it over Billund.
You can watch the documentary here: https://www.dr.dk/drtv/program/droner-over-danmark_596478
Related
Discover more from sUAS News
Subscribe to get the latest posts sent to your email.
The UK Civil Aviation Authority’s introduction of the Recognised Assessment Entity for Flightworthiness, or RAE(F), and the associated SAIL Marking system was presented as a way to support the rollout of UK SORA and help operators demonstrate that their unmanned aircraft systems are safe for more complex Specific Category operations.
In principle, few people in the drone industry would object to proportionate safety assurance. The problem is not the intent. The problem is the way the system risks becoming another costly layer of
assessment on top of standards, certificates, declarations and component-level compliance work that manufacturers have already completed.
The CAA says RAE(F)s are approved to assess whether the technical features of a UAS meet UK SORA requirements, including design, construction and flying characteristics. It also states that designers seeking a SAIL Mark must ask an RAE(F) to assess the UAS, after which the RAE(F) advises the CAA whether the requirements have been met. (Civil Aviation Authority)
That sounds reasonable until you look at what many drone manufacturers are actually building. A modern drone is typically assembled from radios, flight controllers, GPS receivers, batteries, transmitters, electronic speed controllers and other components that already sit within an established conformity framework. Radio equipment is already subject to applicable radio and EMC requirements. CE-marked products and components are already required to demonstrate compliance with applicable Union harmonisation legislation.
EASA’s own guidance for manufacturers confirms that drones are subject to legislation such as the
Radio Equipment Directive and Machinery Directive, and that manufacturers must demonstrate compliance through the defined conformity procedures before affixing CE marking. (EASA)
So the question the industry should be asking is simple: what additional safety value is actually being created by the RAE(F) process, and what is merely a re-check of paperwork that already exists?
The SAIL Mark system is described by the CAA as optional; CAP 722K explicitly states that there is “no obligation” for a UAS designer to SAIL mark their aircraft in the UK. However, the practical reality may become very different. If operators increasingly need SAIL marked aircraft to make UK SORA applications easier, then an “optional” scheme can quickly become a commercial necessity. Once that happens, manufacturers who cannot afford the cost, delay and administrative workload of SAIL Marking may find themselves excluded from parts of the market, even when their aircraft are built from compliant, traceable and already-certified components.
This is where the system becomes problematic. The RAE(F) does not replace proper engineering by the manufacturer. It does not design the aircraft. It does not manufacture the aircraft. In many cases, it will not add meaningful physical test data beyond what the manufacturer has already generated.
CAP 722K requires the designer to submit evidence data to the RAE(F), and the RAE(F) must verify the designer’s compliance against the agreed compliance basis and approach. That is fundamentally an evidence-review model.
Evidence review has value where the aircraft is novel, high-risk, complex, or where the manufacturer is claiming safety functions that are not already proven. But it is much harder to justify when the review becomes a costly confirmation that standard components meet standards they have already been tested against. For example, CAP 722K’s C3 link requirements require data such as C3 link performance, RF spectrum and environmental conditions, plus evidence that the remote pilot can monitor C3 link performance.
Those are important issues, but for many systems the underlying radio modules, output powers,
frequency bands and conformity evidence already exist. The danger is that the RAE(F) becomes an expensive intermediary between the manufacturer’s existing technical file and the CAA’s approval process.
The CAA’s own charging structure shows the wider cost environment that manufacturers and operators now face. For 2026/27, UK SORA-based Operational Authorisation charges range from £2,422 at SAIL 1 to £17,300 at SAIL 5 and SAIL 6, with additional assessment charges possible at £346 per hour. These are CAA charges, not necessarily the full commercial cost of engaging an RAE(F), but they demonstrate the direction of travel: higher SAIL means higher cost, more documentation, more assessment and more delay. (Civil Aviation Authority) EASA’s Design Verification Report system raises similar concerns. EASA states that DVR costs are based on actual time spent assessing documentation, charged at €250 per hour, and that the duration depends heavily on system complexity and the manufacturer’s responsiveness. Again, this is a documentation-heavy model that may be appropriate for higher-risk or more novel designs, but it risks becoming disproportionate when applied too broadly. (EASA)
The strongest argument for SAIL Marking is that it allows a manufacturer to prove the technical aspects once, so operators do not have to repeat the same evidence for every Operational Authorisation. That is a valid objective. The CAA itself says that as more SAIL-marked UAS become available, operators will be able to use them to comply with certain UK SORA technical requirements. (Civil Aviation Authority)
But that benefit only materialises if the process is quick, affordable, consistent and genuinely additive. If the system is slow, expensive and mostly duplicates existing component compliance, then it will not accelerate innovation. It will tax it.
This concern is not just theoretical. In consultation feedback submitted to the CAA, the Royal Aeronautical Society warned that limited numbers of organisations providing RAE(F) services could increase industry costs, extend authorisation timelines and limit growth. The same response noted that many UK drone manufacturers are SMEs, often developing products with limited revenue, and that overly burdensome regulation can make compliance expensive and time-consuming during the critical period before a product is commercialised.
That is the core issue. The UK drone industry is not made up only of large aerospace primes with dedicated certification departments. Much of the innovation comes from small manufacturers, engineering-led start-ups and specialist operators building practical systems for real-world use cases. These companies already face costs for product development, testing, insurance, manufacturing, software, documentation, operational approvals, training, export compliance and market access. Adding another expensive assessment layer may satisfy an administrative need, but it can easily become a barrier to entry.
There is also a risk of regulatory mismatch. Drone technology evolves quickly. Components change, firmware changes, radio modules change and payloads change. A certification-style model that works for traditional aviation can become misaligned with the pace of unmanned aircraft development. The more the approval system struggles to keep up with real product cycles, the more manufacturers will either delay innovation, avoid the UK market, or design around the approval process rather than around the best technical solution.
The answer is not to abandon safety assurance. The answer is proportionality.
For low and medium-risk SAIL levels, the CAA should allow more reliance on manufacturer declarations, existing CE/UKCA/RED evidence, component certificates, conformity documentation and controlled internal test reports. RAE(F) involvement should focus on genuinely operation-specific or system-level risks: containment, failure modes, command-and-control resilience, geofencing, flight termination, software behaviour and manufacturing consistency. It should not become a paid exercise in re-reading radio module certificates and checking that standard parts already comply with standards they were built to meet.
A better model would separate “paperwork already proven elsewhere” from “system-level flightworthiness claims.” If a manufacturer uses a compliant radio module within its rated power, frequency and environmental envelope, that should not need a full reassessment. If a manufacturer claims that its drone can safely terminate flight, contain itself within a defined volume, detect C3 degradation or maintain operational control in a swarm, then that is where independent assessment can add value.
The UK has an opportunity to build a sensible, risk-based drone approval system. But if RAE(F) and SAIL Marking become too expensive, too slow, or too focused on duplicating existing standards, the result will not be a thriving ecosystem. It will be a smaller market, fewer manufacturers, slower product development and less innovation.
The CAA may see the creation of the RAE(F) system as a step forward. For parts of the industry, it may well be. But unless the system is kept proportionate, transparent and affordable, it risks becoming exactly what manufacturers fear: an expensive double-check on compliant products, paid for by the very companies the UK needs if it wants to lead in unmanned aviation.
Related
Discover more from sUAS News
Subscribe to get the latest posts sent to your email.
We are pleased to announce that Amaury Lechapelain and Iñigo H. have completed their Aero-30 test pilot training.
The Aero-30 serves as a fast-paced test & training platform, allowing our teams to continuously refine the systems and control logic powering our operational Aero-200 fleet. During the training programme, our crew gains the technical expertise necessary to safely push the boundaries of our technology in a controlled, experimental environment.
With their qualification, the number of trained test pilots and operators keeps increasing, allowing our flight activities to scale continuously. More missions can be executed in parallel, training can be expanded in a structured way, and procedures are refined continuously based on real-world feedback.
Explore more insights and updates from Dufour Aerospace: https://lnkd.in/dbzxJVkk
Related
Discover more from sUAS News
Subscribe to get the latest posts sent to your email.
At Manna, we’re changing how the world receives things — by taking delivery to the skies.
Our mission is simple but ambitious: to make high-speed suburban delivery affordable, green, and safe. We design and build our own aviation-grade drones that deliver food, coffee, groceries, and more — directly from local stores and vendors to people’s doors in just a few minutes.
We’re a team that Drive with Impact, are Safety Focused, and knows that the best ideas come from Team Players who show up as their Authentic Selves. We move fast, we are passionate about what we do, and we’re always pushing a growth mindset to be better — in everything we do.
If you want to build world-changing technology with real-world impact (and have a bit of fun while doing it), you’ll love it here.
Welcome to Manna — where we deliver the future.
Team mission
The Aircraft team is responsible for the software and firmware that runs onboard Manna aircraft and supporting hardware — including flight computers, sensors, chargers, batteries, and other critical systems. This software directly affects flight safety, aircraft reliability, and fleet scalability. We work close to hardware, real operations, and real aircraft. Engineering decisions here have immediate real-world impact.
The role
As a Software Engineer on the Aircraft team, you will contribute to delivery of core subsystems within the onboard aircraft platform. You’ll design, build, and maintain embedded and onboard software, mentor other engineers, and raise the bar on reliability and safety.
This role is ideal for an experienced engineer who enjoys working close to hardware, taking end-to-end ownership, and solving hard systems problems in a safety-critical environment.
What you’ll do
Design and build embedded and onboard software components running on aircraft and supporting hardware.
Deliver complex features: design, implementation, testing, rollout, and monitoring.
Work primarily in C++ / Embedded C/C++, with Python used for tooling, testing, and
support systems.
Collaborate closely with hardware, airspace, QA, and manufacturing teams to deliver
safe, reliable systems.
Participate in aircraft bring-up, debugging, and in-field issue resolution.
Design software with failure modes, fault tolerance, and observability in mind.
Investigate and resolve complex aircraft and hardware-adjacent issues.
Contribute to architectural discussions and influence technical direction of the
Aircraft platform.
Requirements
Required experience
Deep proficiency in C++ and Embedded C/C++.
Strong debugging skills across software 
hardware boundaries.
Familiarity with Linux-based embedded systems.
Experience collaborating closely with hardware and operations teams.
Strong professional experience building embedded, robotics, or safety-critical software in production.
Nice to have
Experience with drones, avionics, robotics, or autonomous systems.
Familiarity with flight stacks (ArduPilot/PX4), ROS/ROS2, or similar platforms.
Experience with power systems, battery management, or charging firmware.
Exposure to real-time systems, performance profiling, or low-level networking.
Experience with Python for tooling, testing, or automation
This role is based in Dublin
Related
Discover more from sUAS News
Subscribe to get the latest posts sent to your email.
The continent of Australia presents a unique logistical challenge, particularly across its vast, remote and strategically vital northern regions. For the Australian Defence Force (ADF), maintaining a continuous operational presence across such an expansive and unforgiving landscape demands highly innovative approaches to supply and support. Traditional methods of moving cargo are often stretched to their limits by the sheer scale of the geography.
Enter Project Jericho, the Royal Australian Air Force’s disruptive experimentation programme, which is pioneering the use of autonomous aerial logistics to build what military strategists term fighting depth. Central to this ambitious vision is the JabX, an uncrewed aerial system (UAS) based on the proven Jabiru 400 airframe, designed to transport heavy cargo over long distances. By automating routine cargo movements, the ADF aims to revolutionise its logistics tail, ensuring that dispersed teams remain supported without over-tasking the crewed transport fleet.
To understand the true significance of the JabX and the broader Jericho initiatives, one must consider the geographic and strategic realities of Australia. The north of the country is characterised by immense distances, sparse populations and challenging environmental conditions. Operating in this environment requires a robust and agile logistics network capable of connecting remote airbases, coastal areas and dispersed teams conducting littoral operations.
Traditional crewed aircraft are highly capable, but using them for routine supply runs across such vast distances is an inefficient use of valuable resources and personnel. The air force’s Jericho Disruptive Innovation (JDI) team is directly addressing these challenges. By focusing on autonomous aerial logistics, JDI is attempting to build fighting depth for the air force.
This concept involves creating layers of capability and resilience, ensuring that frontline forces have the continuous, uninterrupted support they need to sustain operations. When routine logistics are handled by autonomous systems, human aviators and crewed platforms are freed up to concentrate on complex decision-making, mission command and tasks that only people can perform, particularly in demanding or contested environments. As the deputy director of disruptive experimentation, Wing Commander Keirin Joyce, noted, these technologies are vital to ensuring the air force is ready for future challenges. He said: “By taking on routine logistics missions, autonomous aircraft will free up our aviators and crewed platforms for the tasks only people can do – particularly in demanding or contested conditions”.
The practical manifestation of this autonomous logistics vision is Project Camel Train, an initiative focused on prototyping and deploying UAS corridors across northern Australia. These dedicated flight corridors are intended to link remote airfields and coastal bases into a seamless, precision delivery network. The primary workhorse chosen for this ambitious undertaking is the JabX. Developed in collaboration with RFDesign, an avionics company based in Brisbane, the JabX is a heavily modified version of the popular Jabiru 400 airframe. The Jabiru 400 is already well regarded in light aviation circles, and adapting it for autonomous flight represents a pragmatic and highly efficient approach to capability development. The JabX is specifically designed for long-haul flights carrying heavy loads, featuring robust avionics, structured pre-flight and in-flight workflows, and an advanced graphical user interface that allows operators to maintain constant mission oversight.
The development process for the JabX highlights the immense benefits of using an existing, proven airframe rather than building a new design from the ground up. The director of Jabiru, Michael Halloran, explained that turning the J400 into an optionally crewed aircraft removes the vast time and resources typically required to develop a completely new platform. This approach drastically accelerates the development of autonomy systems because a safety pilot can be kept on board during the initial phases of test flying. Once the autonomous systems are fully developed, tested and proven, transitioning to a dedicated autonomous logistics platform is relatively straightforward. The final autonomous version will share 80% commonality with the crewed JU30 aircraft, meaning that production can be easily scaled up using existing commercial production lines and supply chains.
Integrating autonomous aircraft into shared airspace is not simply a technological challenge; it is a profound regulatory and safety hurdle. The Jericho team recognises that for autonomous logistics to become a reality, these robotic aircraft must navigate crowded or contested skies as safely as human pilots do. Every single component and system of the JabX is tested step by step as part of a strictly regulated pathway. This rigorous testing begins with human pilots operating in controlled settings. As the technology is proven and the regulatory framework permits, the aircraft gradually transition to higher levels of autonomy. The process is described as careful and transparent, keeping safety at the absolute centre of the programme while still enabling rapid innovation. This step-by-step methodology ensures that the ADF can build fundamental trust in the systems before deploying them for live operations across the vast northern corridors.
A critical enabler for long-range autonomous cargo operations is the ability of the uncrewed aerial vehicle (UAV) to safely separate itself from other aircraft sharing the airspace. To solve this complex problem, the Jericho team established Project Arena, a companion initiative to Project Camel Train
Related
Discover more from sUAS News
Subscribe to get the latest posts sent to your email.
Guest post from Jared Oren, Test and Evaluation Division Director at the Science and Technology Directorate’s (S&T) National Urban Security Technology Laboratory (NUSTL).
Over the past several years, NUSTL has received more inquiries about drones than almost any other technology in our laboratory’s history. We’re seeing more and more cases of public safety agencies using small unmanned aircraft systems (sUAS) in their daily operations, from providing aerial situational awareness and enhancing physical protection to supporting search and rescue efforts. The practical use cases for this technology are growing, and America’s first responders are looking for insight into how this technology can improve their safety and effectiveness.
At NUSTL, we work closely with the public safety community to understand and address their most pressing issues. We host a range of working groups, such as the Big City Fire Working Group, that focus on emerging threats and opportunities impacting first responders across the nation. Given the increased interest in sUAS we’ve seen in recent years, the lab has prioritized research and operational assessments that provide first responders with information they need to determine which solutions best fit their mission needs.
One of the latest resources available is NUSTL’s Small Unmanned Aircraft System Program Documentation for Public Safety: Recommendations and Templates. This planning tool gives responders a comprehensive methodology to safely and effectively set up their own program: administrative, operational, qualifications and training, safety, and maintenance.
We created it with collaborative inputs from urban and rural first responders across the country who have experienced the challenges firsthand of how to quickly and effectively initiate or expand a drone program. We understand responders typically don’t come from an aviation background, and we wanted to provide them with a resource that helped fill that gap. The result is a streamlined, easy-to-use template that makes it simpler than ever for responder agencies to implement policies and procedures quickly and get to the real mission at hand – saving lives.
Several factors are driving the increased adoption of sUAS for public safety agencies. Like other technologies, UAS incorporate much of the same components as other popular electronics. Batteries, cameras, and radios are all present in laptops and phones, thus the cost of manufacturing has decreased over time, making them a more affordable option than in prior years. Changes to Federal Aviation Administration regulations have also simplified the process for Drone as First Responder operations, clearing the way for more agencies to incorporate sUAS capabilities into their duties. There is also a national emphasis on expanding America’s sUAS industry, which will ensure the solutions safeguarding our skies are developed by trusted manufacturers.
It comes down to this: UAS are going to play a bigger role in first responder operations moving forward, and agencies need a trusted expert to help them find the right solutions for their unique needs. S&T and NUSTL provide that expertise, giving responders actionable insight and resources that ensure they spend less time worrying about tech specs and more time focused on the mission. I encourage you to review the sUAS Recommendations and Templates to see how your program can benefit.
For more information about the impact of NUSTL’s collaboration with first responders, listen to S&T’s Technologically Speaking podcast episode, “We Take the Load Off of Them.”
Related
Discover more from sUAS News
Subscribe to get the latest posts sent to your email.