
We make your regulatory compliance simpler and faster — so you can focus on growth.
Transitioning from OSC to UK SORA is not a simple update, the safety methodology is different. The safety methodology is fundamentally different — and understanding that difference is critical.

TRANSITION FROM AN OSC TO A SORA OPERATIONAL AUTHORISATION
How different is SORA?
-
Around 70% of OSC Operational Authorisations in the UK were based on reduced distances from uninvolved people. This concept does not exist under SORA. SORA quantifies ground risk probabilistically and implicitly accepts overflight.
-
OSC reduced risk to ALARP (as low as reasonably practicable). SORA requires a defined set of mitigations that bring operations to a specific Target Level of Safety — a different standard, requiring a different evidence structure.
Our core expertise
-
Transform reduced distance type OSC OA to SORA-based OA
-
BVLOS with Visual Mitigation
-
BVLOS in Atypical Air Environment
-
Test & Evaluation activities
-
Urban/dense environment
-
Containment issues
Qualification and framing of SORA application - Framing the Authorisation
-
Assessment of Ground Risk Class, Air Risk Class and SAIL level of intended operations.
-
Assessment of Containment requirements
-
Assessment of key gaps, including in terms of access to UAS documentation or functionalities
SORA Application preparation & submission to the Civil Aviation Authority
-
Documentation of each component of SORA and of each claim as the application progresses on the CAA application webportal
-
Support engagement with the regulator’s team
-
Prepare responses to CAA findings in an iterative improvement of claim documentation and safety argument
-
Document each OSOs Operational Safety Objectives applicable to the SAIL level
Operations Manual amendment
-
Amend the Operations Manual to incorporate the SORA risk assessment methodology as well as the documentation supporting each claim or safety argument in accordance with SORA







