scope:

Purpose of This Order.

This order provides policy for data submission to support the promulgation and effective date assignment for both regulatory and non-regulatory public-use IFPs. It specifies the required data submission lead times to ensure that IFP charts and supporting data will not be released to the public until it is known that the supporting navigation equipment will perform satisfactorily and that all procedural data are correct and confirmed by flight inspection or flight validation. It provides guidance regarding designation of associated controlled airspace for instrument procedures, including those based on area navigation (RNAV). It further ensures that the Federal Aviation Administration (FAA) will not assign an effective date for a procedure until the underlying infrastructure is in place to support the procedure and all necessary action, including flight inspection or flight validation, have been completed. An exception is made and an effective date may be assigned in advance of flight inspection for those Standard Instrument Approach Procedures (SIAPs) and Obstacle Departure Procedures (ODPs) promulgated with "Concurrent Dates" or "Hard Dates" as specified in Order 8260.19, Flight Procedures and Airspace, chapter 8, section 8-3. This order has also been revised to provide procedure specialists, flight inspection personnel, charting specialists, and aircrews the shortest possible response time to complete necessary rulemaking actions, when required, and to publish and use procedures after completing flight inspection.

Note: Flight Validation is defined as the flight assessment of a new or revised Performance Based Navigation (PBN) IFP to confirm that the procedure is operationally acceptable for safety, flyability, and design accuracy (including obstacle and database verification) with all supporting documentation completed.