Build an offshore corridor risk assessment matrix that holds up to review

An offshore corridor can look simple on a route chart and still concentrate several risks: aircraft converging near a platform, poor weather reducing margins, or a drone operation complicating helicopter access. A useful EASA risk assessment matrix makes those hazards visible and shows how each one will be controlled.

There is no single scoring grid that makes every offshore operation EASA-compliant. The applicable requirements and method depend on the operation. In particular, a drone assessment must be built around its own regulatory pathway; a general aviation risk matrix is not a substitute for a required UAS assessment. Treat the matrix as a structured record for analysis and review, not as proof of approval.

1. Define the operation before scoring it

Write down the corridor’s purpose and boundaries in operational terms. Identify the aircraft involved, who operates them, the intended route and altitude, operating times, weather limits, launch and recovery points, and the offshore installations or vessels affected. State whether helicopters and drones will use the corridor at the same time, at different times, or under a coordination arrangement.

Keep the assessment tied to a defined concept of operations. If the route, aircraft, traffic pattern, or operating conditions change, the risk picture may change too. For a drone operation, scope the case and its evidence needs before building the detailed assessment. North Sky’s background on scoping a complex UAS compliance case before SORA is relevant when that is the operation being planned.

2. Identify hazards by phase and interface

Do not make “offshore operations” a single hazard. Break the operation into phases and ask what could go wrong at each transition: departure, transit, arrival, holding, approach, landing, launch, recovery, and contingency response. Include interfaces with platform staff, vessel crews, air traffic services where applicable, and other operators sharing airspace.

For each hazard, describe the unsafe condition and a credible consequence. Examples to test against the actual operation include:

• Helicopter and drone traffic conflict during a platform approach or departure.
• Loss of position or communications over water, leaving the crew uncertain about traffic or recovery options.
• Weather or visibility falling below the conditions assumed in the route plan.
• Emergency diversion, forced landing, or drone recovery affecting people, vessels, or infrastructure.
• A change to platform activity or route use not reaching all affected operators in time.

These are prompts, not a complete hazard register. Record the source of each hazard and the operating assumptions behind it. For shared routes, make responsibilities and traffic information explicit; the practical issues are discussed in the monthly watch for helicopter and drone teams sharing offshore airspace.

3. Choose and explain a scoring method

Use the risk method required by the applicable framework or already adopted in the operator’s safety process. Do not present a home-made score as an official EASA scale. If the assessment uses probability and severity categories, define each category in plain language and apply it consistently. State whether probability means likelihood per flight, per operating hour, or across another defined exposure period.

A practical matrix record has one row per hazard and fields for:

• Hazard and credible consequence.
• People, aircraft, assets, or operations exposed.
• Initial probability and severity, with a short rationale.
• Existing controls and the evidence that they are in place.
• Additional mitigation, its owner, and when it must be completed.
• Residual probability and severity after mitigation, with rationale.
• Acceptance decision, responsible approver, review trigger, and supporting evidence reference.

Apply the same definitions to helicopter and drone activity, but do not assume their exposure is identical. A helicopter’s crew, performance limits and operating procedures differ from a drone’s control link, containment assumptions and recovery arrangements. Record those differences rather than hiding them in a shared corridor score.

4. Select controls that change the exposure

Mitigations should address a specific causal path. Depending on the operation, consider route or time separation, defined entry and exit points, weather limits, communication and handoff procedures, traffic information, contingency routes, and a clear stop or suspend decision. For drones, consider the applicable operational limitations and what happens after loss of command or control. For helicopters, consider the established procedures and operational constraints relevant to the route.

Do not lower a probability score just because a control is listed. Identify who implements it, how crews or operators know it is active, and what record demonstrates that. If a control relies on coordination, specify the parties, information exchanged, timing, and fallback if contact fails. Then rescore the residual risk using the same definitions as the initial assessment.

5. Assemble the review pack and keep it current

Before submission or internal acceptance, check that the matrix matches the operation description, route material, procedures, training and coordination evidence. Flag open actions rather than treating planned controls as completed. The responsible safety and operational reviewers should be able to trace each rating to its reasoning and each mitigation to evidence.

Revisit the assessment when the corridor, traffic mix, aircraft, operating limits, or coordination arrangements change, and after an event or finding that challenges an assumption. A matrix is useful only while it reflects the operation actually flown. North Sky Aviation Consultancy offers risk management, drone operations and EASA and Norwegian aviation compliance advisory across European and Nordic regions. For support reviewing a defined case, contact roe.nerem@northsky.no.