Transforming your craft from an oceanic vessel back to domestic operations is just a matter of making the right contacts, finishing some paperwork, removing SLOP (if any), and getting the cockpit ready for airways, radar contact, and full time air traffic control.
This section continues an example G450 trip from Bedford, Massachusetts (KBED) to Geneva, Switzerland (LSGG), to Tokyo, Japan (RJAA), back to Bedford. For the purpose of covering an oceanic departure, this section will focus on the KBED to LSGG leg. To view the steps required prior to oceanic airspace entry, see: Oceanic Departure. For the en route portion, see: Oceanic En Route.
Everything here is from the references shown below, with a few comments in an alternate color.
Figure: Example Plotting Chart (Arrival), from Eddie's notes.
[AC 91-70B, ¶D.2.11.3] Compare LRNS to ground-based NAVAID (as applicable depending on your equipage). 1. When departing oceanic airspace and acquiring ground-based NAVAIDs, you should note the accuracy of your LRNS compared to the position information provided by those NAVAIDs. 2. You should note discrepancies in your maintenance log.
The coast-in navigation accuracy check is conducted in the same manner as for coast-out, except that the earliest possible navigation aid is sought for the first opportunity to check navigation performance, keeping in mind the service volume of the navaid is limited.
More about this: Navigation Accuracy Check.
[AC 91-70B, ¶D.2.11.1] Remove strategic lateral offset. You must remove the strategic lateral offset prior to exiting oceanic airspace at coast-in. We recommend you include this as a checklist item.
[AC 91-70B, ¶D.2.11.2] Confirm routing beyond oceanic airspace. Before entering the domestic route structure, you must confirm your routing and speed assignment.
[AC 91-70B, ¶D.2.12.1] Transition Level. During the approach briefing, you should note the transition level on the approach plate or verify with ATC. You must reset your altimeters to QNH when descending through the transition level. You should confirm whether the altimeter setting is based on inches of mercury or hectopascals.
[ICAO Document 4444, Ch 1]
G450 Note: The FMS transition level function can be useful because it will alert you 1,000 feet after passing the transition layer.
More about this: Transition Altitude/Layer/Level.
See: Record Keeping, below.
[AC 91-70B, ¶D.2.13.1] When arriving at your destination gate, you should note any drift or circular error in your LRNS. 1. A GPS primary means system normally should not exceed 0.27 NM for the flight. 2. Some inertial systems may drift as much as 2 NM per hour.
[AC 91-70B, ¶D.2.14] You must note problems in the altimetry system, altitude alert, or altitude hold in the maintenance log.
There doesn't appear to be any written guidance on keeping records of your oceanic flights any more, now that AC 91-70A has been replaced and the newer AC 91-70B doesn't mention record keeping at all. Here is the old guidance:
[AC 91-70A, ¶3-6.t.] At the end of each flight, determine the accuracy of the navigational system to facilitate correction of performance. You may perform a check to determine the radial error at the ramp position as soon as the aircraft parks. Radial errors for INSs in excess of 2 NM per hour are generally considered excessive (part 121, appendix G). Keep records on each individual navigation system performance.
[AC 91-70A, ¶3-12.c.]
There is some guidance in ICAO NAT Doc 007:
[ICAO NAT Doc 007, ¶11.2.1] Decisions regarding the monitoring of aircraft navigation performance are largely the prerogative of individual operators. In deciding what records should be kept, operators should take into account the stringent requirements associated with the NAT HLA. Operators are required to investigate all lateral deviations of 10 NM or greater, and it is imperative, whether these are observed on ground radar, via ADS reports or by the flight crew, that the cause(s) of track deviations be established and eliminated. Therefore, it will be necessary to keep complete in-flight records so that an analysis can be carried-out.
It may be useful to carry an envelope for each planned oceanic leg, labeled with the following information:
The following items, as applicable, should be retained at the aircraft base:
There is no regulatory guidance on how long these records should be retained. We use six months.
Some online flight planning software provide nearly automatic methods of record keeping. ARINCDirect in combination with their Flight Operations Software (FOS) applications, for example, will archive just about everything done while oceanic. Job Done. But what if your software doesn't offer this capability?
You can take photos — called "screen grabs" — of everything you do on an iPad that is pertinent by pressing the "Home" and "Power" buttons simultaneously. Everything will be saved as a photo to your Photos application. From there it is a matter of sending those photos via an email or text message to whomever does your record keeping.
*Advisory Circular 91-70A, Oceanic and International Operations, 8/12/10, U.S. Department of Transportation
* This version of AC 91-70 has been superseded but it retained because it contains older guidance that helps place current guidance into perspective.
Advisory Circular 91-70B, Oceanic and International Operations, 10/4/16, U.S. Department of Transportation
ICAO Doc 4444 - Air Traffic Management, 16th Edition, Procedures for Air Navigation Services, International Civil Aviation Organization, October 2016
ICAO Nat Doc 007, North Atlantic Operations and Airspace Manual, v. 2021-1, applicable from February 2021
Copyright 2019. Code 7700 LLC. All Rights Reserved.