11.07.2015 Views

World Air Ops | NAT | Doc 007 MNPS Guidance

World Air Ops | NAT | Doc 007 MNPS Guidance

World Air Ops | NAT | Doc 007 MNPS Guidance

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>Guidance</strong> concerning <strong>Air</strong> Navigation in and above the <strong>NAT</strong> <strong>MNPS</strong>A CHAPTER 6(see also “HF Management <strong>Guidance</strong> Material for the <strong>NAT</strong> Region”). However, it must beappreciated that pending further system developments and facility implementations thecapability for Ground(ATC)-initiated calls varies between different <strong>NAT</strong> OACs3. If the aircraft is not equipped with SATCOM Voice then the pilot should attempt to use VHF tocontact any (other) ATC facility or another aircraft, inform them of the difficulty, and requestthat they relay information to the ATC facility with which communications are intended.4. The inter-pilot air-to-air VHF frequency, 123.45 MHz, may be used to relay position reports viaanother aircraft. (N.B. The emergency frequency 121.5 MHz should not be used to relay regularcommunications, but since all <strong>NAT</strong> traffic is required to monitor the emergency frequency, itmay be used, in these circumstances, to establish initial contact with another aircraft and thenrequest transfer to the inter-pilot frequency for further contacts).5. In view of the traffic density in the <strong>NAT</strong> Region, pilots of aircraft experiencing a two-way ATScommunications failure should broadcast regular position reports on the inter-pilot frequency(123.45 MHz) until such time as communications are re-established.Communications Procedures for Use in the Event of an On-board HF Equipment Failure6.6.6 Use SATCOM Voice communications, if so equipped. (See General Provisions 2. above).6.6.7 If not SATCOM Voice equipped try VHF relay via another aircraft (See General Provisions3. & 4. above).Communications Procedures for Use during Poor HF Propagation Conditions6.6.8 Poor HF propagation conditions are the result of ionospheric disturbances. These are usuallycaused by sun-spot or solar flare activity creating bursts of charged particles in the solar wind which canspiral down around the Earth’s magnetic lines of force and distort or disturb the ionised layers in thestratosphere which are utilised to refract HF radio waves. As with the Aurora Borealis, which is of similarorigin, these ionospheric disturbances most commonly occur in regions adjacent to the Magnetic Poles.Since the Earth’s North Magnetic Pole is currently located at approximately 80N 110W, flights through theNorth Atlantic and Northern Canada regions can, on occasion, experience resulting HF communicationsdifficulties.6.6.9 SATCOM Voice communications are unaffected by most ionospheric disturbances.Therefore, when so equipped, an aircraft may use SATCOM Voice for ATC communications (See GeneralProvisions 2 above).6.6.10 If not SATCOM Voice equipped, in some circumstances it may be feasible to seek theassistance, via VHF, of a nearby SATCOM Voice equipped aircraft to relay communications with ATC (SeeGeneral Provisions 3. & 4. above).6.6.11 Whenever aircraft encounter poor HF propagation conditions that would appear to adverselyaffect air-ground communications generally, it is recommended that all pilots then broadcast their positionreports on the air-to-air VHF frequency 123.45 MHz. Given the density of traffic in the <strong>NAT</strong> Region and thefact that in such poor propagation conditions ATC will be unable to maintain contact with all aircraft, it isimportant that even those aircraft that have been able to establish SATCOM Voice contact also broadcasttheir position reports.6.6.12 If for whatever reason SATCOM Voice communications (direct or relayed) are not possible,then the following procedures may help to re-establish HF communications. Sometimes these ionospheric<strong>NAT</strong> <strong>Doc</strong> <strong>007</strong> 37 Edition 2010

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!