PBN Helicopter Operations

PBN Helicopter Operations

Helicopter operations, including HEMS, SAR, police, offshore and governmental missions, are operationally critical and are frequently conducted in demanding environments such as low‑level airspace, complex terrain and urban areas. In this context, Performance‑Based Navigation (PBN) has emerged as the key enabler for safe, predictable and all‑weather helicopter IFR operations across Europe.

Why PBN Matters

PBN enables IFR access to hospitals, heliports and remote locations where conventional navigation aids are not available. It supports the establishment of low‑level helicopter route networks that are essential for time‑critical missions and significantly improves safety, availability and operational predictability, particularly in adverse weather conditions. Without PBN, many critical helicopter operations would be severely constrained or, in some cases, not feasible at all.

Current Operational Model

RNP 0.3 is the primary navigation specification used for helicopter en‑route and terminal operations, including dedicated low‑level route networks. For approach operations, RNP APCH is increasingly applied to helicopters, often through shared use of CAT A aeroplane procedures, replacing dedicated CAT‑H designs where these provide limited additional operational benefit. Point‑in‑Space (PinS) procedures play a crucial role in enabling access to hospitals and remote sites; however, their implementation remains uneven across States. Overall, while helicopter PBN operations are well established and operationally mature, they are not yet fully harmonised at the European level.

Regulatory

The PBN Implementing Rule primarily addresses ATS routes and instrument runway ends. Many helicopter‑specific operations, including low‑level routes, hospital access and PinS procedures, fall outside the direct scope of the Implementing Rule. Consequently, States rely on national safety cases, approvals and exemptions, which has resulted in inconsistent implementation across Europe.

GNSS Dependency

Helicopter PBN operations are highly dependent on GNSS. This dependency is exacerbated by the limited availability of conventional alternates and the short fuel endurance typical of helicopter operations, which together amplify operational risk. Contingency solutions, such as the use of conventional navigation back‑ups, are not uniformly achievable across fleets and States, in part due to avionics limitations.

Helicopter Operations in the ICAO PBN Manual (Doc 9613)

Helicopter PBN operations are addressed within ICAO Doc 9613 – Performance‑based Navigation (PBN) Manual, which provides global implementation guidance for RNAV and RNP operations. The manual does not contain a standalone “helicopter chapter” but explicitly accommodates rotorcraft operations through specific navigation specifications and application guidance, particularly within Volume I (Concept and Implementation) and Volume II (Implementing RNAV and RNP Operations).

Applicability to Helicopter Operations

The PBN Manual recognises that helicopter operations differ from fixed‑wing operations due to their low‑level flight profiles, operation in obstacle‑rich environments, and frequent need for IFR access to non‑runway sites such as hospitals or offshore installations. As a result, ICAO includes provisions allowing PBN navigation specifications to be applied to helicopter‑specific operational concepts, subject to appropriate safety assessment and State approval. [pbnportal.eu]

Key Navigation Specifications for Helicopters

RNP 0.3 - ICAO Doc 9613 identifies RNP 0.3 as the navigation specification most used for helicopter operations. It is applicable to departure, en‑route, arrival, initial and intermediate approach segments, as well as missed approach segments. RNP 0.3 supports helicopter low‑level route networks and operations in constrained or obstacle‑rich environments by providing reduced containment areas and onboard performance monitoring and alerting. [skybrary.aero]

RNP APCH - The PBN Manual confirms that RNP APCH is applicable to helicopter approach operations. It may be used either through helicopter‑specific procedures or via shared use of fixed‑wing CAT A procedures, provided operational suitability is ensured. RNP APCH enables IFR access in environments where conventional approach aids may not be available or cost‑effective. [pbnportal.eu], [icao.int]

Point‑in‑Space (PinS) - ICAO recognises PinS as a helicopter‑specific application of PBN, enabling instrument procedures to a defined point in space rather than a runway threshold. PinS procedures typically consist of an instrument segment followed by a visual segment and are particularly relevant for hospital heliports, offshore platforms and remote sites. ICAO Doc 9613 includes PinS within its PBN framework while leaving detailed operational approval and implementation to States. [caa.co.uk]

Regulatory and Implementation Perspective

ICAO Doc 9613 is guidance material, not a regulatory instrument. It allows flexibility for States to implement helicopter PBN operations in line with national airspace concepts, fleet equipage and operational needs. As a result, helicopter PBN implementation—particularly for PinS and low‑level routes—varies significantly between States, even though the underlying navigation specifications are globally harmonised.

Safety Support EUROCONTROL

EUROCONTROL has developed a set of generic helicopter safety cases to support the safe implementation of PBN‑based helicopter operations in Europe, particularly where operations take place at low level, to/from non‑runway sites, or outside conventional ATS route structures. These safety cases are intended to be adapted locally by States, ANSPs, helicopter operators and heliport operators

Safety cases for helicopter low‑level route operations

EUROCONTROL has developed a generic safety case and guidance material for IFR helicopter operations on Low‑Level Routes (LLR) that supports the local deployment of helicopter operations, including routes designed using RNP 0.3 or RNP 1. It covers the full operational lifecycle, from concept and design through implementation, transition from VFR to IFR operations, and ongoing service provision. The guidance highlights that LLRs can connect PinS approaches and departures, existing ATS routes, or other terminal procedures, thereby forming an integrated helicopter IFR network..

Safety case for helicopter low‑level route operations is available here

Safety cases for PinS procedures

The Safety Case for deployment of Helicopter PinS provides guidance to support local safety assessments for helicopter PinS approach operations. It explains how to tailor to a specific operational environment and addresses all affected domains, including GNSS, flight procedure design, aeronautical information services, meteorological services, air traffic services, heliport operations and helicopter operations.

Safety cases for PinS procedures is available here