Introduction
Flying over the ocean is a different beast. No radar coverage, no immediate ATC contact, vast distances between alternates, and traffic flowing in organized streams at similar levels. When something goes wrong — a pressurization failure, a medical emergency, a nav system degrading — the margin for error shrinks dramatically.
ICAO Doc 4444 (PANS-ATM), Section 15.2, lays out the framework for handling in-flight contingencies in oceanic airspace. Whether you're preparing for a type rating, a long-haul line check, or a technical interview, knowing these procedures cold is non-negotiable.
This article breaks them down clearly, straight from the source.
1. The Three Main Contingency Scenarios
Section 15.2.1.1 identifies the most frequent cases these procedures are designed to address:
- Inability to comply with ATC clearance due to weather (meteorological conditions)
- En-route diversion across the prevailing traffic flow — e.g., a medical emergency requiring an immediate track change
- Loss or significant degradation of navigation capability — or a pressurization failure
Note: Degraded navigation procedures are also covered separately in Chapter 5, Section 5.2.2.
One key principle runs through everything: the pilot's judgement determines the sequence of actions, having regard to prevailing circumstances. ATC shall render all possible assistance — but the crew leads.
2. General Procedures (Section 15.2.2) — Non-Weather Contingencies
Step 1: Try to Get a Clearance First
If the aircraft cannot continue in accordance with its ATC clearance, a revised clearance shall be obtained whenever possible, prior to initiating any action (15.2.2.1). Don't just deviate — talk to ATC first.
Step 2: If No Clearance Can Be Obtained
This is where it gets operational. The aircraft should be flown at an offset level and on an offset track to minimize the likelihood of encountering other traffic.
Specifically (15.2.2.2):
a) Lateral offset — 5.0 NM
Turn at least 30 degrees left or right to establish a parallel, same-direction track offset by 5.0 NM (9.3 km).
The direction of turn should consider:
1. Aircraft position relative to any organized track or ATS route system
2. Direction of flights and flight levels on adjacent tracks
3. Direction to alternate airport
4. Any strategic lateral offset (SLOP) being flown
5. Terrain clearance
b) Traffic watch — ACAS
Maintain a visual and ACAS watch. Keep ACAS in RA mode at all times (unless aircraft limitations dictate otherwise).
c) Exterior lights
Turn on all exterior lights (within operating limitations).
d) Transponder / ADS
Keep SSR transponder on. When able, squawk 7700. If equipped with ADS-B or ADS-C, select the appropriate emergency functionality.
e) Notify ATC as soon as practicable
Advise ATC of any deviation from assigned clearance.
f) Communication means
Use voice and/or CPDLC as appropriate.
g) Voice distress/urgency signals
If voice is used:
- MAYDAY (distress) or PAN PAN (urgency) — preferably spoken three times
h) CPDLC emergency
If communicated via CPDLC, the controller may respond via CPDLC but will also attempt to make voice contact.
i) Broadcast on guard / inter-pilot frequency
Broadcast on 121.5 MHz (or backup: 123.45 MHz) at suitable intervals:
- Aircraft identification
- Nature of distress condition
- Pilot's intention
- Position (ATS route designator or track code)
- Flight level
3. Actions Once Offset from Track (Section 15.2.3)
Once established on the 5.0 NM parallel, same-direction offset, the pilot faces a key decision.
The note in 15.2.3 is important: factors to consider include whether you're in a parallel track system, the potential for UPRs (User Preferred Routes) parallel to your route, the nature of the contingency, and weather at lower flight levels (e.g., convective activity).
15.2.3.1 — Maintain Flight Level If Possible
If possible, maintain the assigned flight level until established on the offset. If unable, minimize the rate of climb/descent to the extent operationally feasible.
15.2.3.2 — Once on the 5 NM Offset: Two Options
Option A — Descend below FL 290 (15.2.3.2 a)
Descend below FL 290 and establish a 150 m (500 ft) vertical offset from normally-used flight levels. Proceed as required by the operational situation or per ATC clearance if obtained.
Note 1: "Normally used flight levels" are those in Annex 2 — Rules of the Air, Appendix 3.
Note 2: Descent below FL 290 is considered particularly applicable when there is a predominant traffic flow (e.g., east-west) or a parallel track system where your diversion path will likely cross adjacent tracks. It reduces the risk of conflict, ACAS RA events, and clearance delays.
Option B — Remain above FL 290 (15.2.3.2 b)
Establish and maintain a 150 m (500 ft) vertical offset from normally-used flight levels (or 300 m / 1000 ft if above FL 410). Proceed as required.
Note: Altimetry System Errors (ASE) may result in less than 500 ft of actual vertical spacing (less than 1000 ft above FL 410) when this procedure is applied.
4. Weather Deviation Procedures (Section 15.2.4)
Weather deviations follow a slightly different logic, because the deviation is driven by avoidance — not emergency per se.
15.2.4.1 — General
When a weather deviation is required, initiate communications with ATC via voice or CPDLC. To get a rapid response:
- State "WEATHER DEVIATION REQUIRED" to get priority on the frequency, or
- Send a CPDLC lateral deviation request
If necessary, use the urgency call "PAN PAN" (preferably three times) or a CPDLC urgency downlink.
Important: The pilot shall inform ATC when the weather deviation is no longer required, or when the aircraft has returned to its cleared route.
15.2.4.2 — When Comms with ATC Are Established
The pilot requests clearance, advising the extent of deviation needed.
ATC will either:
- Issue clearance (if separation can be applied), or
- Advise the pilot of conflicting traffic and inability to clear, and request the pilot's intentions
The pilot then either:
- Complies with the ATC clearance, or
- Advises ATC of intentions and proceeds per 15.2.4.3
15.2.4.3 — If No Revised ATC Clearance Can Be Obtained
This section invokes the pilot-in-command authority (Annex 2, 2.3.1). If deviation is required to avoid weather and no clearance is available, an ATC clearance shall be obtained at the earliest possible time. Until then:
a) Deviate away from organized track/ATS route system if possible
b) Broadcast on 121.5 MHz (or 123.45 MHz backup)
At suitable intervals: aircraft ID, flight level, position (ATS route or track code), and intentions.
c) Watch for conflicting traffic — visual and ACAS
d) Turn on all exterior lights
e) Deviations < 5.0 NM from cleared track
Remain at the ATC-assigned level.
f) Deviations ≥ 5.0 NM from cleared track
When approximately 9.3 km (5.0 NM) from track, initiate a level change per Table 15-1:
| Cleared Track Direction |
Deviation Direction |
Level Change |
| EAST (000°–179° magnetic) |
Left |
Descend 90 m (300 ft) |
| EAST (000°–179° magnetic) |
Right |
Climb 90 m (300 ft) |
| WEST (180°–359° magnetic) |
Left |
Climb 90 m (300 ft) |
| WEST (180°–359° magnetic) |
Right |
Descend 90 m (300 ft) |
💡 Memory tip — SAND: South deviation → Ascend | North deviation → Descend
Regardless of your track direction, just think about which side of the route you're going to. Deviating towards the South → climb. Deviating towards the North → descend. This mirrors the semi-circular rule logic: northerly tracks use odd levels, southerly tracks use even levels — so deviating north puts you into an odd-level environment (climb), deviating south into an even one (descend). SAND gives you the answer instantly, without reconstructing the table.
g) If partial clearance obtained then lost
If you had clearance for a specified distance but cannot extend it, apply the Table 15-1 altitude offset before deviating beyond the cleared distance.
h) Returning to track
Be at your assigned flight level when within approximately 5.0 NM of the centreline.
i) Continue attempting to contact ATC throughout.
5. Quick Reference — Key Numbers to Remember
| Parameter |
Value |
| Initial turn angle off track |
At least 30° |
| Lateral offset |
5.0 NM (9.3 km) |
| Vertical offset (standard) |
150 m / 500 ft |
| Vertical offset above FL 410 |
300 m / 1000 ft |
| Descent trigger (non-weather) |
Below FL 290 |
| Weather deviation level change at ≥5 NM |
90 m / 300 ft |
| Guard frequency |
121.5 MHz |
| Inter-pilot air-to-air frequency |
123.45 MHz |
| Emergency squawk |
7700 |
6. Interview Tip — The Logic Behind the Procedures
If you're asked about oceanic contingency procedures in a technical interview, examiners aren't just checking memory — they want to see that you understand why:
- The 30° initial turn gets you off track quickly, with minimum delay, while the 5 NM offset keeps you clear of adjacent traffic streams.
- The 500 ft vertical offset creates separation from normally-used flight levels where other traffic will be.
- Descent below FL 290 is preferred when crossing traffic streams because it removes you from the busy semi-circular rule altitudes and reduces ACAS RA conflicts.
- Table 15-1 logic mirrors the semi-circular rule — eastbound traffic steps down on left, up on right; westbound reverses — to avoid opposite-direction conflict at the point of offset establishment.
Understanding the intent of each element shows operational maturity, and that's what airlines look for.
Summary
In oceanic airspace, there is no radar, no immediate backup, and no margin for improvisation. These procedures exist because the environment demands a pre-loaded response — not a discussion.
Get clear. Stay separated. Keep talking. And never forget: the pilot leads, ATC supports.
References: ICAO Doc 4444 PANS-ATM, Section 15.2 — Special Procedures for In-Flight Contingencies in Oceanic Airspace