X hits on this document

421 views

0 shares

0 downloads

0 comments

36 / 145

Guidance concerning Air Navigation in and above the NAT MNPSA

CHAPTER 4

CHAPTER 4:

FLIGHT PLANNING

4.1

FLIGHT PLAN REQUIREMENTS

General

4.1.1

It is essential that care is taken when entering track information into a computer and the

information should be cross-checked before it is given to the operating crew. Crews of all NAT flights at or above FL290, even those that will transit the NAT above the MNPSA (i.e. above FL420) or through the MNPSA but are not planned to use the OTS, must be given both the organised track message and relevant amendments to it. Copies must be available on-board the aircraft. (N.B. In the event of a contingency or diversion, knowledge of the location of the OTS tracks will be useful to the crew of any NAT high level flight). Should more than one version of the daily Track Message have been issued, then crews should be issued the entire revised version together with an appropriate explanation to relate differences between versions. Each successive version will be identified by the TMI and an alphabetic suffix. e.g. 243A, 243B

etc.

4.1.2

All flights which generally route in an eastbound or westbound direction should normally be

flight planned so that specified ten degrees of longitude (20°W, 30°W, 40°W etc.) are crossed at whole degrees of latitude; and all generally northbound or southbound flights should normally be flight planned so that specified parallels of latitude spaced at five degree intervals (65°N, 60°N, 55°N etc.) are crossed at whole degrees of longitude. (N.B. For those flights that generally route in an eastbound or westbound direction, it is important that the latitude crossings of ALL oceanic ten-degree meridians be included as waypoints in the flight plan submitted to ATC. Even where “named” significant points are close to these "prime" meridians of longitude it is not appropriate to omit the ten-degree crossings from the ATC Flight

Plan.).

4.1.3 waypoints.

All flights should plan to operate on great circle tracks joining successive significant

Routings

      • 4.1.4

        During the hours of validity of the OTS, operators are encouraged to flight plan as follows:

        • in accordance with the OTS; or

        • along a route to join or leave an outer track of the OTS; or

        • on a random route to remain clear of the OTS, either laterally or vertically.

      • 4.1.5

        Nothing in the paragraph above prevents operators from flight planning through/across the

OTS. However they should be aware that whilst ATC will make every effort to clear random traffic across the OTS at published levels, re-routes or significant changes in flight level are likely to be necessary during most of the OTS traffic periods.

4.1.6

Outside of the OTS periods operators may flight plan any random routing, except that during

a period of one hour prior to each OTS period the following restrictions apply:

Eastbound flights that cross 30°W less than one hour prior to the incoming/pending Westbound OTS (i.e. after 1029 UTC), or Westbound flights that cross 30°W less than one hour prior to the incoming/pending

NAT Doc 007

20

Edition 2010

Document info
Document views421
Page views421
Page last viewedSat Dec 10 10:59:19 UTC 2016
Pages145
Paragraphs4885
Words62134

Comments