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 16intending to also fly in this WATRS Plus airspace should ensure that its RNP approval status is included inthe flight plan. In field 18 this should be annotated as NAV/RNP10 or NAV/RNP4 (see paragraph 4.1.12).16.6 Dispatch FunctionsGeneral16.6.1 All US FAR Part 121 carriers (domestic and flag operators) and many non-US carriersemploy aircraft dispatchers or flight operations officers (hereafter referred to as dispatchers) to provide flightplanning, flight watch and/or flight monitoring services. Most of the information presented here is includedin other chapters of this manual but since this chapter deals with issues primarily important to dispatchers,the information is sometimes repeated here for emphasis and additional guidance.16.6.2 Nothing in this chapter should be construed as to take precedence over appropriategovernment regulations or individual company policy.16.6.3 The dispatcher is responsible for providing the pilot-in-command with information necessaryto conduct a flight safely and legally under appropriate State civil aviation authority regulatory requirements.ICAO Annex 6 defines the requirement for an en route aircraft, but when operating under US FAR Part 121or/and certain other State civil aviation rules, the dispatcher shares responsibility for exercising operationalcontrol with the pilot-in-command of the flight. A successful flight will always start with an intelligent,informed and conservative plan.Flight PlanningRoute Planning16.6.4 The daily published OTS tracks provide near to optimum <strong>NAT</strong> segment routings for abouthalf of all the flights between Europe and North America. For many other flights the location of the OTSstructure on the day may constrain available random routings. Consequently, the development of asuccessful <strong>NAT</strong> flight plan almost always requires consideration of the detail of the relevant OTS structure.Operators can influence the OTS construction process by providing Prefered Route Messages andparticipating in this collaborative decision making ( See Chapter 2, paragraphs 2.2.3 and 2.2.4).16.6.5 The eastbound and westbound OTS structures are the subject of separate “<strong>NAT</strong> TrackMessages” published via the AFTN. A detailed description of the <strong>NAT</strong> Track message is provided inChapter 2.Planning on an OTS Track16.6.6 Dispatchers must pay particular attention to defined co-ordinates, domestic entry and exitroutings, allowable altitudes, Track message identification number (TMI) and any other information includedin the remarks section. They must also take care to be apprised of any amendments or corrections that maybe subsequently issued. When such amendments are issued the TMI is appended with an alpha suffix (e.g.“123A”). Since track messages are often manually entered into company flight planning systems,dispatchers should verify that all waypoints on flight plans comply with the current OTS message.- It is important for dispatchers to understand that transition routes specified in the <strong>NAT</strong> Trackmessage are as important as the tracks themselves. The transition route systems in Europe – theNorth Atlantic European Routing Scheme (NERS) and in North America – the North AmericanRoutes (NARs) and the Northern Organised Track System (NOROTS) and the US East Coastroutes are described in Chapter 3. Dispatchers should comply with any specified transition<strong>NAT</strong> <strong>Doc</strong> <strong>007</strong> 95 Edition 2010

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

Saved successfully!

Ooh no, something went wrong!