IRELAND · IAA / EASA · SORA 2.5 · OSO & CSP
Example of OSO Evidence and a Comprehensive Safety Portfolio for Drone Operators in Ireland
In the SORA 2.5 methodology, it is insufficient to merely select a low, medium, or high risk level for the Operational Safety Objectives (OSOs). For each OSO, it must be clear which requirement applies, where the procedure is documented, what evidence supports its implementation, and how this evidence is managed. The Comprehensive Safety Portfolio (CSP) makes this line verifiable and traceable, which is essential for Specific category operations that require a recognised risk analysis.
Building an Evidence Line for Each OSO
Each Operational Safety Objective (OSO) has a specific robustness level based on the Specific Assurance and Integrity Level (SAIL), derived using the SORA 2.5 risk tables. It is crucial not only to describe general safety measures but to underpin them with precise references to operational procedures, standards, tests, declarations, or logs.
To manage this effectively, use unique evidence IDs that enable clear assignment, traceable updates, and audit facilitation. This practice boosts transparency and ensures that all documentation amendments remain clearly trackable over time.
In Ireland, the Irish Aviation Authority (IAA) is the competent authority responsible for oversighting UAS operations. Operators must consult the IAA’s official material for any specific local requirements or recommendations related to OSOs and CSPs.
- OSO ID and the required robustness level according to the SAIL
- Status of the OSO: Open, Substantiated, or Not Applicable
- Precise section in the Operations Manual (OM) or procedure identifier
- Evidence ID including document title, version, date, and responsible individual or department
- Any open corrective actions and acceptance criteria
Example of a Strong Evidence Reference
A weak statement such as ‘The pilots are trained’ lacks detail on the content, evidential support, and responsible party.
A robust example reads: 'Section 6.3 of the Operations Manual details initial and recurrent training; evidence document EV-TR-004 contains the validated crew competency matrix; register REG-02 records current flight experience and recency; the Safety Manager verifies these records before every deployment.'
This level of specification clarifies the content, supporting evidence, and responsible roles or functions, creating a robust foundation for the OSO. Such clarity aligns with EASA’s strong emphasis on accountability and traceability.
Operators should also refer to the IAA’s official documentation for country-specific templates and guidelines concerning evidence referencing.
- Specify the exact location in the Operations Manual or Concept of Operations (ConOps)
- Refer to formal controlled documents with unique reference codes
- Identify who is responsible for monitoring and verifying the evidence
Assembling the Comprehensive Safety Portfolio
The Comprehensive Safety Portfolio (CSP) acts as a central index and repository for all evidence pertinent to demonstrating compliance with the SORA OSOs. It must integrate all required elements, including the Concept of Operations (ConOps), risk assessment, Operations Manual, Emergency Response Plan (ERP), technical documentation, crew qualifications, test results, maps, registers, and declarations.
Before finalising the CSP, operators must ensure that all documentation is current, operational boundaries are accurately defined, and all evidence references are consistent and verifiable. No OSO should rely solely on unverified assertions. A well-maintained CSP supports the establishment of the Ground Risk Class (GRC) and facilitates operational approvals by national authorities such as the IAA.
Refer to the IAA’s official guidance for up-to-date requirements and best practices concerning the CSP.
- Centralised index linking all layers of evidence
- Maintain strict version control and ensure documents are up to date
- Avoid unsupported claims for any OSO
- Supports the submission and ongoing compliance of the Specific category Emergency Response Plan (ERP)
Frequently asked questions
Must each evidence document be consolidated into a single PDF file?
No, consolidation into a single PDF is not required. A well-managed Comprehensive Safety Portfolio with stable, clearly structured references to separate documents is generally more practical. However, all referenced files must be accessible, current, and clearly identifiable.
Can an OSO be designated as 'Not Applicable'?
Yes, but only if the methodology by which the OSO was determined explicitly allows for this and if the non-applicability is substantiated in a traceable manner within the documentation.
What is the difference between OSO and SAIL in SORA?
Operational Safety Objectives (OSOs) specify the concrete safety requirements arising from the risk analysis, while the Specific Assurance and Integrity Level (SAIL) indicates the required robustness level of those OSOs, ranging from low to high depending on the evaluated risks.
How does DroneManual support compiling the CSP?
DroneManual offers clear structural guidance and illustrative examples for assembling a Comprehensive Safety Portfolio, enabling drone operators to organise their documentation effectively and in full compliance with EASA SORA requirements.
What national rules apply in Ireland alongside SORA?
The Irish Aviation Authority (IAA) is the competent authority in Ireland responsible for applying European SORA rules and, where applicable, enforcing additional national procedures. Operators should regularly consult the latest IAA publications and directives for current local regulatory obligations.