RAE(F) and the Rise of SAIL Marks

The introduction of the Recognised Assessment Entity for Flightworthiness (RAE(F)) under CAP 722J represents a substantive structural development within the UK Specific category framework.

While much discussion around UK SORA has focused on containment methodology, OSO robustness and SAIL allocation, the RAE(F) model alters something more fundamental: how technical compliance is evidenced and by whom.

For operators conducting, or intending to conduct, SAIL III and above operations, this development warrants careful attention.

Regulatory Context

Under Article 11 of UK Regulation (EU) 2019/947, operators in the Specific category must conduct a risk assessment and demonstrate that the operation can be conducted safely .

The UK SORA methodology, aligned with SORA 2.5 , determines a Specific Assurance and Integrity Level (SAIL) based on intrinsic ground and air risk.

As SAIL increases, so too does the required robustness of Operational Safety Objectives (OSOs), containment performance, and system integrity evidence.

Historically, the operator bore responsibility for assembling and presenting the full compliance basis — including technical substantiation relating to aircraft design, reliability assumptions and containment mechanisms — regardless of aircraft type or manufacturer.

The RAE(F) model introduces a different architecture.

The Function of an RAE(F)

A Recognised Assessment Entity for Flightworthiness is a CAA-recognised organisation authorised to conduct technical assessments of unmanned aircraft systems against defined UK SORA requirements .

Where appropriate, the RAE(F) may issue evidence in support of a SAIL Mark certificate. The SAIL Mark identifies specific UK SORA requirements that have been satisfied at aircraft or system level.

This does not replace the Operational Authorisation, which remains issued to the operator. Nor does it remove operator accountability for safe conduct. Rather, it permits certain technical compliance elements to be evidenced independently of the individual operator.

In effect, aircraft-level assurance can be modularised.

Practical Implications for Operators

The impact of this development varies by SAIL.

For lower SAIL operations (I–II), the practical effect may be limited. Many such operations do not require deep technical substantiation beyond basic system integrity and procedural controls.

At SAIL III and above, however, the evidential burden increases significantly. Operators must demonstrate robust compliance with OSOs, including containment integrity and system reliability commensurate with the assessed risk level.

Without RAE(F) involvement, operators must independently gather and present:

• Technical design data

• Reliability arguments

• Functional performance substantiation

• Verification and validation evidence

With an RAE(F)-assessed platform, some of these elements may already be addressed within the scope of the SAIL Mark. The operator’s compliance matrix can then reference that evidence directly.

This reduces duplication and may improve clarity during assessment. However, it also introduces dependencies.

Operators must ensure that:

• The aircraft configuration matches that assessed by the RAE(F)

• Operational use remains within the conditions attached to the SAIL Mark

• Modifications are managed carefully, particularly where they may affect containment or integrity assumptions

Failure to maintain alignment between configuration and certification scope risks invalidating reliance on the SAIL Mark evidence.

Compliance Architecture and Accountability

The RAE(F) framework creates a clearer separation between aircraft design assurance and operational safety management.

This is not equivalent to Certified category approval. However, it does introduce structured third-party scrutiny into the Specific category, particularly for higher SAIL operations.

Operators remain accountable for:

• Conducting the SORA

• Defining the operational environment

• Implementing procedures and mitigations

• Ensuring safe conduct

• 
  

The SAIL Mark supports compliance. It does not transfer responsibility.

The distinction is material.

Strategic Considerations

For operators planning SAIL III+ operations, early engagement with aircraft manufacturers regarding RAE(F) status and SAIL Mark scope is now prudent.

Procurement decisions may increasingly consider:

• Whether the aircraft has been assessed by a recognised RAE(F)

• Which UK SORA requirements are covered

• The configuration control framework in place

• The implications for future modifications

  
  

Similarly, manufacturers may view RAE(F) assessment as a route to scalable market access, reducing the need for repetitive technical substantiation across multiple customers.

Over time, this may lead to a more structured product-level compliance ecosystem within the Specific category.

The introduction of RAE(F) and SAIL Mark policy is not an administrative refinement. It reflects the continued maturation of the UK UAS regulatory framework.

For lower-risk operations, the impact may be marginal. For higher SAIL operations, it alters the evidential model and introduces a more modular compliance structure.

Operators who understand how aircraft-level assurance integrates with operational risk assessment will be better positioned to manage both regulatory scrutiny and commercial scalability.

The Specific category is becoming more structured. RAE(F) is a significant part of that development.

I