UK SORA Compliance
From OSC to SORA, without losing your Operational Authorisation nor scope.
A structured transition pathway for UK operators moving from a legacy Operating Safety Case to a SORA-based authorisation. SORA is different, and securing the same authorisations may be challenging. For UK Specific category operators with existing scope to protect.
The CAA is moving every Specific category operator from the legacy OSC framework to SORA under CAP722K. The methodology is different.
Transition
What's actually changing
Operational Authorisations in the Specific category are gradually moving from the legacy OSC framework to SORA under AMC and GM to Article 11 (ORS9 Decision No. 46).
The SORA Framework
The risk assessment methodology is different. The evidence the CAA wants is different.
Operational Continuity Guaranteed
Operational Authorisations in the Specific category are gradually moving from the legacy OSC framework to SORA under AMC and GM to Article 11 (ORS9 Decision No. 46).
The risk assessment methodology is different. The evidence the CAA wants is different.
Securing Operational Continuity
We help you secure and replicate your scope under SORA, and when possible extending your scope or adding flexibility.
Lock in your flight scope
Transition
Transition
The CAA is moving every Specific category operator from the legacy OSC framework to SORA under CAP722K. The methodology is different.
The CAA is moving every Specific category operator from the legacy OSC framework to SORA under CAP722K. The methodology is different.
Shaping OSC to SORA transition work.
How we run your transition
01
Rebuild
We translate your concept of operations into SORA language. New GRC and ARC, derived SAIL, OSO compliance pack, refreshed containment strategy, and an Operations Manual amendment that align with SORA and CAA findings.
02
Verify
Securing regulatory alignment through rigorous pre-submission checks, ensuring your evidence portfolio matches SORA requirements criteria before the final Civil Aviation Authority assessment begins.
03
Engage
We help you submit the new application, manage all CAA correspondence and response to findings, and protect your existing operational scope through the dialogue.
04
Authorise
Obtaining your official Operational Authorisation. We remain available for minor modifications, or for an application for a variation as your mission requirements continue to grow.
Built for operators with something to protect
The transition from legacy OSC to the new SORA framework is more than a paperwork update. For example, risk to uninvolved people is approached differently. It is a shift in how risk is justified to the CAA to maintain your Operational Authorisation.
AVOIDING TRANSITION RISKS
Protect scope
How does a legacy OSC reduced distance mitigation translate into SORA's GRC scoring?
In SORA, reduced distance from uninvolved people is addressed through the intrinsic ground risk class GRC and population density inputs rather than a standalone mitigation. Overflight is possible, yet the ground risk scale is challenging. Your legacy OSC separation distances need to be reframed as a strategic ground risk mitigation with a defined robustness level, supported by evidence in your ConOps and Operations Manual.
Protecting your operational continuity: what is the best approach to secure the transition from OSC to SORA?
Start early, invest time in building a thorough ConOps that accurately reflects your actual operations, and treat the OSOs as a structured safety narrative rather than a checklist. Working with experienced consultants who know the CAA's expectations can significantly reduce iteration time and approval risk.
What are the common pitfalls in the transition process from OSC to SORA?
Many operators underestimate the shift from the OSC model to SORA's evidence-based safety case approach. The most frequent mistakes are an underdeveloped ConOps and underestimating OSO robustness requirements. Without precise translation into the new evidence framework, you risk lengthy delays and iteration in your approval process.