IRELAND · SORA 2.5 · OSO & CSP
Example of OSO Evidence and a Comprehensive Safety Portfolio for Drone Operators
In the SORA 2.5 methodology, simply selecting a low, medium, or high risk level for Operational Safety Objectives (OSOs) is not enough. For each OSO, it must be explicit which requirement applies, where the procedure is documented, what evidence supports its implementation, and how this evidence is managed. The Comprehensive Safety Portfolio (CSP) structures this alignment into a verifiable and traceable format, which is essential for Specific category operations requiring an approved risk assessment under the oversight of the Irish Aviation Authority (IAA).
Building an Evidence Line for Each OSO
Each Operational Safety Objective (OSO) corresponds to a robustness level derived from the Specific Assurance Integrity Level (SAIL), as determined by the SORA 2.5 risk tables. It is imperative not only to describe the general mitigating measures but to back these up with precise references to documented procedures, technical standards, tests, formal statements, or maintained records.
To manage this effectively, assign fixed evidence identifiers (IDs) to each supporting document or record. This approach facilitates traceability, streamlines revisions and audits, and improves transparency, making it straightforward to track any changes in your documentation over time.
- OSO identifier and corresponding required robustness level per the SAIL
- Status of each OSO: Open, Substantiated, or Not Applicable
- Exact paragraph or section in the Operations Manual (OM) or procedure document
- Evidence IDs with document title, version, date, and responsible person or department
- Any outstanding actions along with acceptance criteria
Example of a Strong Evidence Reference
A weak evidence statement might be: ‘The pilots are trained.’ This lacks detail on the scope of training, underlying proof, or responsible staff.
A robust alternative is: ‘Section 6.3 of the Operations Manual describes initial and recurrent drone pilot training; document EV-TR-004 holds the current competency matrix; record REG-02 details recent experience and recency; the Safety Manager verifies these documents before every flight.’
This detailed approach clarifies what the evidence consists of, where it can be found, and who is responsible for oversight, aligning well with EASA’s emphasis on traceability and accountability in the Specific category.
- Specify the precise location in the Operations Manual or Concept of Operations (ConOps)
- Reference formally controlled documents with unique identifiers
- Identify the person accountable for monitoring and verifying the evidence
Assembling the Comprehensive Safety Portfolio
The Comprehensive Safety Portfolio (CSP) functions as a central repository and index connecting all evidence necessary to demonstrate compliance with the SORA OSOs. It should encompass related documents such as the Concept of Operations (ConOps), SORA risk assessment, Operations Manual, Emergency Response Plan (ERP), technical files, pilot certificates, test results, charts, registers, and formal declarations.
Before submitting the CSP, ensure all documents are up to date, operational limits are correctly stated, and all evidence references are consistent and verifiable. No OSO should be supported solely by unsubstantiated claims. A well-maintained CSP supports the defined Ground Risk Class (GRC) and facilitates operational approval processes administered by authorities such as the IAA.
- Maintain a central index linking all layers of evidence
- Implement version control and confirm document currency
- Avoid unsupported assertions for any OSO
- Supports obtaining and maintaining Specific category operational approvals and ERP compliance
Frequently asked questions
Does each evidence document need to be combined into a single PDF?
No, consolidating all documents into one PDF is not required. A well-managed Comprehensive Safety Portfolio with stable, logically structured references to separate documents is often more practical. However, all referenced documents must be readily accessible, current, and easily identifiable.
Can an OSO be classified as 'Not applicable'?
Yes, but only if the SORA methodology under which the OSO was determined explicitly allows for such classification, and the documentation substantiates and traces the justification for this non-applicability in a clear and verifiable manner.
What is the difference between OSO and SAIL in the SORA framework?
Operational Safety Objectives (OSOs) are specific safety requirements that derive directly from the risk assessment process. The Specific Assurance Integrity Level (SAIL) reflects the required robustness or reliability level for these OSOs, ranging from low to high based on the assessed risk.
How does DroneManual assist in building a CSP?
DroneManual offers structured guidance and practical examples for constructing a Comprehensive Safety Portfolio, helping drone operators organize their documentation in a clear, consistent, and audit-ready fashion aligned with EASA SORA standards and IAA expectations.
What national procedures apply in Ireland alongside SORA?
The Irish Aviation Authority (IAA) is responsible for enforcing European SORA regulations within Ireland and may implement additional national processes as needed. Operators should always consult the current IAA guidance and procedures to ensure full compliance with Irish regulatory requirements.