SORA 2.5 · OSO & CSP
Example of OSO Evidence and a Comprehensive Safety Portfolio for Drone Operators
In the UK SORA 2.5 methodology, it is insufficient to merely assign a low, medium, or high risk level to the Operational Safety Objectives (OSOs). For each OSO, operators must clearly identify the applicable requirement, where it is documented, the evidence supporting its implementation, and how this evidence is maintained. The Comprehensive Safety Portfolio (CSP) ensures this process is verifiable and traceable, which is a critical component for Specific Category operations requiring an approved risk assessment under UK CAA oversight.
Building an Evidence Line for Each OSO
Each Operational Safety Objective (OSO) in the UK SORA framework has a designated robustness level based on the Specific Assurance Integrity Level (SAIL), determined using the SORA 2.5 risk tables. Operators must go beyond general descriptions and substantiate each OSO with precise references to procedures, standards, tests, declarations, or records.
To manage this effectively, it is recommended to use fixed evidence identifiers. This practice supports responsibility assignment, facilitates document revisions, streamlines audits, and enhances traceability. Clear tracking of documentation amendments aligns with the UK CAA’s focus on accountability and operational transparency.
For example, an OSO related to training might be detailed as follows:
- OSO-ID: OSO-001
- Robustness Level: Medium (SAIL 2)
Example of a Strong Evidence Reference
An insufficient reference such as ‘The pilots are trained’ does not specify the content, evidence, or accountability behind the claim. This weak formulation risks undermining demonstration of compliance.
A strong evidence reference example reads: ‘Section 6.3 of the Operations Manual details initial and recurrent training; Evidence EV-TR-004 contains the current competency records of the crew; Register REG-02 tracks latest experience and recency; the Safety Manager verifies this evidence before each deployment.’
This level of detail clarifies exactly what is required, where to find documented proof, and who is responsible for its verification. This practice aligns with the UK CAA’s emphasis on traceability, documentation management, and safety accountability.
Providing such detailed references improves confidence in the safety management system and supports the operator’s application for a Specific Category Operational Authorisation.
Assembling the Comprehensive Safety Portfolio
The Comprehensive Safety Portfolio (CSP) acts as the central index and repository for all evidence related to compliance with SORA OSOs under UK CAA requirements. Operators should ensure it contains all vital components, including the Concept of Operations (ConOps), risk assessment, Operations Manual, Emergency Response Plan (ERP), technical documentation, crew certifications, test results, charts, registers, and declarations.
Before CSP submission or audit, it is critical to verify all documents are current, operational limits are correct, and evidence references are consistently applied. No OSO should be supported merely by unsubstantiated statements; every claim must be traceable and verifiable.
A well-maintained CSP facilitates the establishment of Ground Risk Class (GRC) and supports the UK CAA’s evaluation of the operator’s application for Specific Category permission. Maintaining an up-to-date CSP demonstrates professional safety management and regulatory compliance, significantly easing the approval and ongoing oversight process.
Frequently asked questions
Must each evidence item be collected in a single PDF?
No, UK operators are not expected to compile all evidence into a single PDF file. Maintaining a well-structured Comprehensive Safety Portfolio with stable references to separate documents is often more practical. However, all documents must be accessible, up to date, and clearly identified to facilitate verification.
Can an OSO be marked as 'Not Applicable'?
Yes, within the UK SORA framework, an OSO may be designated 'Not Applicable' only if the applicable method or risk assessment explicitly permits this and if the reason is clearly documented and traceable within the CSP and risk assessment documents.
What is the difference between OSO and SAIL in SORA?
Operational Safety Objectives (OSOs) specify safety requirements derived from the risk assessment. The Specific Assurance Integrity Level (SAIL) defines the required robustness for these OSOs—ranging from low to high—based on the level of risk identified. Both elements work together to tailor safety objectives to the operation’s risk profile.
How does DroneManual assist in building the CSP?
DroneManual offers structured guidance and examples tailored to the UK context for compiling a Comprehensive Safety Portfolio. It helps drone operators organise their dossiers efficiently, ensuring traceability and verifiability in line with UK SORA requirements, supporting smoother interactions with the UK CAA.
What national rules apply in the United Kingdom besides SORA?
The UK Civil Aviation Authority (CAA) is the competent authority responsible for implementing SORA and regulating Specific Category drone operations in the UK. While UK SORA aligns closely with the European methodology, the UK CAA maintains national procedures and requirements. Operators must consult the latest UK CAA guidance documents on their official website to ensure full compliance with local rules.