Oceanic operations present a fundamentally different safety environment from domestic radar-covered routes. In oceanic airspace, there is no ground-based radar to detect off-course aircraft, separation is maintained by procedural means — agreed-upon routes, altitudes, speeds, and position reporting — and a navigation blunder or in-flight emergency can go unnoticed for an extended period unless the crew takes immediate, prescribed corrective action. Two interconnected topics anchor the knowledge requirement for ATP-level oceanic operations: the recognition and response to a Gross Navigation Error (GNE), and the proper application of oceanic in-flight contingency procedures when an emergency, meteorological hazard, or equipment failure forces a deviation from the assigned route or altitude.
Advisory Circular 91-70C, Oceanic and International Operations, is the primary FAA guidance document for these procedures. It consolidates the standards and expectations for operators and crews conducting long-range, oceanic, and polar flights, and it references ICAO documents and regional procedural supplements. Every ATP candidate and qualified crew member operating on oceanic routes must understand these procedures thoroughly — not just for the written exam, but because improper handling of an oceanic contingency is a leading contributing factor in serious oceanic incidents.
What Is a Gross Navigation Error?
A Gross Navigation Error is defined as a lateral deviation from the assigned centerline of a route that equals or exceeds 25 nautical miles (NM). This threshold is significant because oceanic lateral separation minima can be as narrow as 23–30 NM on organized track systems such as the North Atlantic Track System (NAT). A GNE therefore represents a situation where the aircraft has drifted or navigated into the lateral separation buffer of an adjacent track, creating a direct collision risk with traffic on a neighboring route — potentially at the same altitude and traveling in the same or opposite direction.
GNEs do not just happen because of failed navigation equipment. Common causes include: crew failure to load or verify the correct oceanic track or waypoints before departure; accepting an incorrect oceanic clearance without cross-checking it against the filed flight plan; failure to cross-check the Flight Management System (FMS) against independent navigation sources at oceanic entry; entering waypoints in the wrong order (waypoint transposition errors); and complacency during long cruise segments when both crew members reduce their navigation monitoring scan. The insidious danger is that on a dark oceanic crossing, the aircraft may hold heading, altitude, and speed perfectly — yet be on entirely the wrong track.
Detecting a Gross Navigation Error
Early detection is the most powerful defense. AC 91-70C reinforces that crews must conduct systematic navigation cross-checks at the oceanic entry fix and throughout the crossing. Recommended practices include:
- Pre-entry check: At the oceanic entry fix, verify the aircraft's position against the expected coordinates using all available navigation sources (FMS, GPS, ADF/VOR where available). Confirm the track angle and distance to the first oceanic waypoint.
- Cross-cockpit verification: Both pilots independently compare FMS routing against the paper or electronic oceanic clearance before entry.
- Waypoint passage checks: At each oceanic waypoint, compare the aircraft's actual position against expected latitude/longitude. A difference of more than a few tenths of a degree should trigger an investigation.
- Independent navigation source comparison: On MNPS or RVSM airspace routes, cross-check the primary FMS with an independent GPS or the second FMS. Consistent agreement is reassuring; discrepancy demands investigation.
- Track angle monitoring: The actual track angle should correspond to the charted route. A significant difference — even a few degrees sustained over time — can translate to tens of nautical miles of error at oceanic distances.
Oceanic In-Flight Contingency Procedures
When an aircraft must deviate from its assigned oceanic route, altitude, or speed — due to weather, turbulence, aircraft emergency, pressurization failure, or any other cause — the crew must immediately initiate oceanic contingency procedures. These are designed to separate the deviating aircraft from other traffic procedurally, since ATC radar surveillance is unavailable and controller intervention cannot happen in real time.
Communication First
The crew's first duty is to establish communication with the controlling oceanic ATC facility as quickly as possible. This may be via HF voice radio, SATCOM voice, or CPDLC (Controller–Pilot Data Link Communication). ATC must be informed of the emergency or deviation, the aircraft's current position, altitude, and intended action. If communication cannot be established immediately, the crew must not wait — they must act to ensure safety and continue attempting contact.
The Offset Procedure
If weather or a hazard forces a lateral deviation and immediate ATC contact is not possible, crews should apply the standard contingency offset. The widely accepted procedure, described in AC 91-70C and ICAO guidance, is to offset the aircraft by 15 NM to the right of the assigned centerline (right offset is standard because it mirrors the general convention of right-of-way in aviation and keeps the deviating aircraft clear of opposite-direction traffic on adjacent tracks to the left). This 15 NM offset is large enough to provide separation from the assigned track but keeps the aircraft from encroaching on the next assigned track in most oceanic environments.
When offsetting, the crew should also consider altitude changes if the deviation is being driven by a vertical threat (e.g., the need to descend due to pressurization failure or turbulence). The standard altitude offset to separate from other traffic at the same flight level on adjacent tracks is a 300-foot offset (climbing or descending to FL+/- 300 ft from assigned altitude) to deconflict while maneuvering. If a larger altitude change is required, the crew should attempt to reach an altitude that is odd or even thousands of feet different from the assigned altitude, consistent with the hemisphere direction-of-flight rules, and inform ATC.
Squawk and Broadcast
In conjunction with the offset, the crew should squawk 7700 (emergency) on the transponder if an emergency exists, and make a blind broadcast on 121.5 MHz (international distress frequency) and on the operational frequency in use. The blind broadcast should include the aircraft's callsign, position, altitude, nature of the contingency, and intended action. This alerts nearby aircraft monitoring those frequencies and may enable another crew or an overflying aircraft to relay the information to ATC.
Altitude Deviations for Weather
When deviating for weather in oceanic airspace, AC 91-70C reinforces that if an altitude change is required, the flight crew should request the new altitude via ATC. If unable to contact ATC and an immediate altitude change is necessary for safety, the crew takes the action and continues attempting contact. RVSM (Reduced Vertical Separation Minima) airspace, in use in most oceanic regions, uses 1,000-foot vertical separation between FL290 and FL410. Any altitude occupied by the contingency aircraft must be considered potentially occupied by another aircraft, reinforcing the importance of the 300-foot offset as a temporary measure while maneuvering through assigned levels.
Why This Matters: The Safety Case
In the North Atlantic alone, hundreds of aircraft cross simultaneously at similar altitudes, many separated by as little as one degree of latitude (approximately 60 NM) or, on popular peak-demand tracks, by only the procedural minima. A single GNE places that aircraft on a collision course with traffic it cannot see and that ATC cannot deconflict because there is no radar. Historical oceanic near-miss incidents — some with closing speeds exceeding 1,000 knots on head-on tracks — underscore that these procedures exist because the environment offers almost no margin for error and no safety net once an error occurs.
The procedures also matter for regulatory compliance. Operators authorized for oceanic and MNPS/RVSM operations are expected to train crews in these contingency procedures and document that training. Failure to follow contingency procedures — even if no collision results — can subject a crew and operator to certificate action.
Key Numbers and Rules
- 25 NM: The lateral offset defining a Gross Navigation Error.
- 15 NM right offset: The standard lateral contingency offset when deviating for weather or an emergency and immediate ATC contact is not possible.
- 300 feet: The altitude offset (above or below assigned altitude) used as an interim measure when maneuvering through RVSM-separated levels during a contingency.
- 1,000 feet: Vertical separation standard in RVSM airspace (FL290–FL410).
- 121.5 MHz: International distress frequency used for blind broadcasts during oceanic contingencies.
- Squawk 7700: Used when a genuine emergency exists; aids relay alerting from nearby aircraft.
- Position reports: Required at each oceanic waypoint; late or missing reports trigger a SLOP (Strategic Lateral Offset Procedure) or search/rescue notification process.
Common Test Traps
- Confusing 25 NM with smaller navigation error thresholds: The GNE threshold is specifically 25 NM lateral deviation; some candidates confuse this with SLOP offset values (typically 1 or 2 NM) or RVSM vertical minima.
- Assuming ATC can provide immediate radar separation oceanic: Oceanic airspace is non-radar (with the exception of some ADS-B equipped areas such as certain North Atlantic tracks). Procedural separation is the rule, not the exception.
- Forgetting the blind broadcast requirement: Many candidates know to contact ATC but omit the requirement to broadcast on 121.5 and the operational frequency to alert nearby traffic.
- Misidentifying the contingency offset direction: The offset is 15 NM to the right. A left offset would place the aircraft into opposite-direction traffic separation.
- Overlooking pre-entry cross-checks as a GNE prevention tool: Test questions may frame GNE prevention as a crew resource management or automation management issue; the answer is almost always: verify all navigation sources against the clearance at the oceanic entry fix before committing to the track.