World Air Ops | NAT | Doc 007 MNPS Guidance

More documents

Recommendations

Info

Guidance concerning Air Navigation in and above the NAT MNPSA CHAPTER 16route requirements in all regions. Failure to comply may result in rejected flight plans, lengthydelays and operating penalties such as in-flight re-routes and/or the flight not receivingrequested altitudes.- If (and only if) the flight is planned to operate along the entire length of one of the organizedtracks, from oceanic entry point to oceanic exit point, as detailed in the NAT track message,should the intended track be defined in Item 15 of the ICAO flight plan using the abbreviation"NAT" followed by the code letter assigned to the track.- The planned Mach number and flight level at the commencement point of the track should bespecified at the organised track commencement point.- Each point at which a change of Mach Number or flight level is requested must be specified asgeographical co-ordinates in latitude and longitude or as a named point.- For flights operating along the entire length of an OTS track, estimated elapsed times (EET/ inItem 18) are only required for the commencement point of the track and for FIR boundaries.Planning a Random Route16.6.7 A Random route is any route that is not planned to operate along the entire length of theorganised track from oceanic entry point to oceanic exit point.16.6.8 A Random route is described as follows : -- For generally East/West flights south of 70N, by significant points formed by the intersection ofhalf or whole degrees of latitude with meridians spaced at intervals of 10 degrees fromGreenwich meridian to longitude 70 degrees West.- For generally East/West flights north on 70N, by significant points formed by the intersection ofparallels of latitude expressed in degrees and minutes with meridians spaced at intervals of 20degrees from the Greenwich meridian to longitude 60 degrees West.- For generally North/South flights, formed by the intersection of half or whole degrees oflongitude with specified parallels of latitude which are separated at 5 degrees interval from 20degrees North to 90 degrees North.16.6.9 Random routes can be planned anywhere within MNPS Airspace but the dispatcher shouldsensibly avoid those routes that conflict directly with the OTS. Examples of sensibly planned random routesinclude routes that:- Remain clear of the OTS by at least 1 deg;- Leave or join outer tracks of the OTS;- Are above or below the OTS flight level stratum;- Are planned on track co-ordinates before/after valid OTS times.16.6.10 Care should be taken when planning random routes and it would be prudent to plansufficient fuel to allow for potential re-routes or non-optimum altitudes. The following examples illustrateparticular issues to consider.Examples:- Flights planned to initially operate below MNPS Airspace/RVSM flight levels at FL280 onroutes that pass under the OTS should not plan to climb until 1 degree clear of the OTS.- Planning to join an outer track is allowable. However, the dispatcher should be aware that theclearance may not be given due to the adverse impact on track capacity. Leaving an outer trackNAT Doc 007 96 Edition 2010
Guidance concerning Air Navigation in and above the NAT MNPSA CHAPTER 16is seldom a problem as long as at least 1 degree of separation is subsequently maintained fromother tracks.- Random routes paralleling the OTS 1 or 2 degrees north or south can be as busy as the OTSitself.16.6.11 Dispatchers planning NAT flights originating in south Florida or the Caribbean shouldconsider the effect of traffic from South America operating north eastwards to the USA, when deciding onflight levels. Although the dispatcher should plan optimum flight levels, adequate fuel should be carried sothat a NAT flight can accept a lower altitude (FL260 or FL280) until east of 70 ˚W.16.6.12 Any flight planning to leave an OTS track after the oceanic entry point must be treated as arandom route. The track letter must not be used to abbreviate the route description.16.6.13 Flights operated against the peak traffic flows should plan to avoid the opposite directionOTS. Even if operating outside of the validity periods of the OTS some restrictions on routings may apply.These can affect Eastbound traffic crossing 30W at 1030 UTC or later; and Westbound traffic crossing 30Wat 2400 UTC and later (See Chapter 4, paragraph 4.1.6). If in any doubt it would be prudent to co-ordinateany such routes directly with appropriate OACs.Flight Levels16.6.14 Flight Dispatchers should be aware of the North Atlantic Flight Level Allocation Scheme(FLAS). This is subject to change and the current FLAS is published in the UK and Canadian AIPs andshown at Attachment 6.16.6.15 Chapters 2 and 4 contain details on RVSM flight level guidance. Since virtually all airspaceadjoining MNPS airspace is now RVSM, transition problems are no longer a major issue for ATC ordispatchers. Nevertheless dispatchers should be aware that some “opposite direction” levels, which may beflight planned for the NAT segment of a flight, may not be similarly allowed in adjacent domestic areas.Guidance for RVSM flight procedures in MNPS airspace can be found in Chapter 9 of this Manual.16.6.16 RVSM allows more flight levels for planning and therefore provides better opportunity to flycloser to an optimum route/profile. As aircraft fly towards their destination they become lighter as fuel onboardis consumed and they are then able to climb to more fuel efficient altitudes. It is acceptable to planand/or request step climbs within the OTS but because of traffic volumes and the difference in aircraftperformance it is wise to plan conservatively. Climbs on random routes that are totally north or south of thetrack system are more readily approved. If a flight is planned without profiling a climb crews should beencouraged to request a climb as aircraft decreasing weight permits.Communications16.6.17 The availability of functioning HF ATS communications is mandatory for flights through theShanwick OCA. Many States of Registry insist on two functioning long range communications systems forflights in Oceanic or Remote areas. Some States of Registry will allow their operators to substituteSATCOM Voice for one HF system. Dispatchers should ensure that they are fully aware of their State ofRegistry requirements in this regard. VHF communications (freq 123.45 or 121.5) can be used as to relayair-ground ATS communications as backup in case of en route HF failure.16.6.18 Many operators now use ADS-C (automatic dependent surveillance) and CPDLC (controllerpilot data link communications) for oceanic position reporting and clearance updating. These featuresimprove position reporting speed and accuracy. They also reduce the chance of errors. Advancedregistration with the ATS Providers may be required if ADS/CPDLC are to be used in the NAT Region.NAT Doc 007 97 Edition 2010
Page 1 and 2:
www.worldairops.comThis document is
Page 3:
Guidance concerning Air Navigation
Page 7 and 8:
Page 9 and 10:
Page 11 and 12:
Page 13 and 14:
Page 15 and 16:
Page 17 and 18:
Page 19 and 20:
Page 21:
Page 25:
Page 28 and 29:
Page 30 and 31:
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
Page 43 and 44:
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62: Guidance concerning Air Navigation
Page 111: Guidance concerning Air Navigation
Page 145: www.worldairops.comThis document is
show all

World Air Ops | NAT | Doc 007 MNPS Guidance

Create successful ePaper yourself

Delete template?

Save as template?