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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>Guidance</strong> concerning <strong>Air</strong> Navigation in and above the <strong>NAT</strong> <strong>MNPS</strong>A CHAPTER 8Leaving the Rampa) checking the distance from the ramp position to the first waypoint. Some systems willaccount for the track distance involved in an ATC SID; in others, an appropriate allowancefor a SID may have to be made to the great circle distance indicated in order to match that inthe Master <strong>Doc</strong>ument. If there is significant disagreement, rechecking initial position andwaypoint co-ordinates may be necessary.b) selecting track waypoint 1 to waypoint 2 and doing the following:- checking accuracy of the indicated distance against that in the Master <strong>Doc</strong>ument;- checking, when data available, that the track displayed is as listed in the Master <strong>Doc</strong>ument.(This check will show up any errors made in lat/long designators (i.e. N/S or E/W).)c) similar checks should be carried out for subsequent pairs of waypoints and any discrepanciesbetween the Master <strong>Doc</strong>ument and displayed data checked for possible waypoint insertionerrors. These checks can be co-ordinated between the two pilots checking against theinformation in the Master <strong>Doc</strong>ument.d) when each leg of the flight has been checked in this manner it should be annotated on theMaster <strong>Doc</strong>ument by means of a suitable symbology as previously suggested (See "The Useof a Master <strong>Doc</strong>ument” above).e) some systems have integral navigation databases and it is essential that the recency of thedatabase being used is known. It must be recognised that even the co-ordinates of waypointpositions contained in a data base have been keyed in at some point by another human. Thepossibility of input errors is always present. Do not assume the infallibility of navigationdatabases and always maintain the same thorough principles which are applied in thechecking of your own manual inputs.8.3.19 The aircraft must not be moved prior to the navigation mode being initiated, otherwiseinertial navigation systems must be realigned. Prior to leaving the ramp Zero Ground Speed indications fromthe LRNS should be confirmed. Any excessive Ground Speeds noted while on chocks should be resolved bychecking fault codes, the currency of data bases and RAIM (if GPS is employed).8.3.20 After leaving the ramp, inertial groundspeeds should be checked (a significantly erroneousreading may indicate a faulty or less reliable inertial unit). A check should be made on any malfunctioncodes whilst the aircraft is stopped but after it has taxied at least part of the way to the take-off position; anysignificant ground-speed indications whilst stationary may indicate a faulty inertial unit such as a tiltedplatform. Prior to take-off, operators with an avionic fit which employs an electronic map display shouldconfirm that the derived position indicates that the aircraft is at the start of the runway.8.3.21 Many modern aircraft are equipped with FMS navigation systems (i.e. Flight ManagementComputers fed by multiple navigation sensors.). Once the FMS is put into 'Nav' mode, the system decideson the most appropriate (i.e. accurate) navigation sensors to use for position determination. If GPS is part ofthe solution, then the position is normally predominantly based on GPS inputs with the IRS/INS in asupporting role. It may therefore be difficult to know exactly what component of the navigation solution(IRS, GPS, DME etc) is being used to derive position at any one time. With an FMS-based system, or a GPSstand-alone system, the “Leaving the Ramp” checks should be designed to provide assurance that thenavigation information presented is indeed 'sensible'.<strong>NAT</strong> <strong>Doc</strong> <strong>007</strong> 52 Edition 2010

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

Saved successfully!

Ooh no, something went wrong!