slide1 n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
PP 49-2 Summary table PowerPoint Presentation
Download Presentation
PP 49-2 Summary table

Loading in 2 Seconds...

play fullscreen
1 / 3

PP 49-2 Summary table - PowerPoint PPT Presentation


  • 99 Views
  • Uploaded on

PP 49-2 Summary table. PP 49-2 Proposed Resolution for states.  PR#S1 : SDF shall be unnamed when the procedure is promulgated with a chart having a continuous descent path and a dist/alt table to MAPt/RW.

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'PP 49-2 Summary table' - bayard


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
pp 49 2 proposed resolution for states
PP 49-2 Proposed Resolution for states

PR#S1: SDF shall be unnamed when the procedure is promulgated with a chart having a continuous descent path and a dist/alt table to MAPt/RW.

PR#S2: SDF should be preferably named when the procedure is promulgated with a chart having a continuous descent path or a dive and drive profile and without a dist/alt table to MAPt/RW.

PR#S3: IFPP should consider an amendment to the PANS OPS to request the publication of a distance/Altitude table to MAPt/RW for all “LNAV approaches”.

pp 49 2 proposed resolution for navigation database suppliers
PP 49-2 Proposed Resolution for Navigation Database Suppliers

PR#NDB1: Navigation Database supplier should not code unnamed SDF in their NDB when the chart includes a dist/alt table to MAPt/RW.

PR#NDB2: Navigation Database supplier should code named SDF in their NDB.

PR#NDB3: Navigation Database supplier should code unnamed SDF in their NDB when the chart doesn’t include a dist/alt table to MAPt/RW.

PR#NDB4: Navigation Database supplier should consider an ARINC 424 amendment to reflect PR#NDB1, PR#NDB2 and PR#NDB3 resolutions.