CHAPTER 1. INSTRUMENT FLIGHT PROCEDURE VALIDATION (IFPV) OVERVIEW
.1-1
1.1 Process1-1
1.2 Authorization1-1
1.3 Notification of Planned IFPV Activity1-2
1.4 Record Data Format1-2
1.5 Data Accuracy and Sources1-2
1.6 Library1-2
1.7 Records1-2
CHAPTER 2. SERVICE PROVIDER REQUIREMENTS2-1
2.1 Operational Guidance2-1
2.2 Safety Management System (SMS)/Operational Safety Assessment (OSA)2-3
CHAPTER 3. INSTRUMENT FLIGHT PROCEDURE VALIDATION (IFPV)3-1
3.1 Process3-1
3.2 Requirements3-3
3.3 Flight Validation of Space Based Augmentation System (SBAS)/ Ground Based
Augmentation System (GBAS) WAAS IFP3-5
CHAPTER 4. IFPV EVALUATOR TRAINING REQUIREMENTS4-1
4.1 Initial Training Requirements for IFPV Authorization4-1
4.2 Recurrent Training Requirements4-3
APPENDIX A. ADMINISTRATION INFORMATIONA-1
APPENDIX B. EXAMPLE OF BRIEFING FOR NON-IFPV AUTHORIZED PILOTS .. B-1 iii
CHAPTER 1. INSTRUMENT FLIGHT PROCEDURE VALIDATION (IFPV) OVERVIEW
1.1 General.
This AC describes the process for safely and efficiently adding a new or revised, nonpart 97, satellite based PBN IFP [e.g., area navigation (RNAV) SID/STAR/Route and approach procedures titled RNAV (GPS) or RNAV (RNP)] through the Instrument Flight Procedures Validation (IFPV) process. The term “Flight Validation” is part of the Procedure Validation process and is concerned with factors other than the performance of the navigation aid or system that may affect the suitability of the procedure for publication. Flight Validation is a flight assessment of a new or revised instrument flight procedure to confirm that the procedure is operationally acceptable for safety, including required obstacle clearance, flyability, navigation database ARINC-424 coding, design accuracy, and required infrastructure (i.e., runway markings, approach lights, communications, runway lights, charting, etc.) with all supporting documentation.
1.2 Process.
IFPV is a series of actions involving several distinct elements including:
• Ground Validation,
• Pre-flight Validation, and
• Flight Validation.
Figure 1-1. IFPV Overview
1.3 Authorization.
Non-FAA service providers must be authorized by the FAA prior to conducting IFPV activities. Approval to conduct IFPV activities consists of approved training and surveillance, by a Flight Procedures Airspace Group (FPAG) Oversight Unit approved ASI, of IFPV activities completed in accordance with the company’s IFPV manual.
Specific Flight Procedures Airspace Group’s authorization is required for Ground 1-1
Obstacle Assessment (GOA), Simulator Validation (SV), Airborne Obstacle Assessment (AOA), and Flight Validation (FV). See FAA Order 8900.1, Flight Standards Information Management System (FSIMS), Volume 11, Chapter 12 for examples of IFPV Letters of Authorization (LOAs).
1.4 Notification of Planned IFPV Activity.
Non-FAA service providers must notify the Flight Technologies and Procedures Division’s representative by Knowledge Services Network (KSN) Activity Tracker or email 9-amc-fsifp-oversight@faa.gov 14 calendar days prior to conducting any IFPV activity. Upon receipt of the entry/email, an FPAG Oversight Unit approved ASI will notify the non-FAA service provider of the level of oversight for that activity.
1.5 Record Data Format.
Records submitted pursuant to this AC must be in an electronic format.
1.6 Data Accuracy and Sources.
Satellite-based PBN IFP [e.g., RNAV SID/STAR and approach procedures titled RNAV (GPS) or RNAV (RNP)] require highly accurate data based on the World Geodetic System 1984 (WGS84). This requires all survey data used in the flight procedure meet FAA Order 8260.19, Flight Procedures and Airspace, standards. It is mandatory that the non-FAA service provider must maintain a quality assurance system covering all domains of data collection (surveys), processing, publication, and navigation database development. Terrain, obstacle, and aeronautical data, including the source, type, date, version, and resolution of the data must be documented in accordance with FAA Order 8260.19.
1.7 Library.
A current copy of all relevant FAA documents (print or electronic), FAA-accepted IFPV operations manuals, publications, and correspondence pertinent to IFPV must be maintained by the non-FAA service provider. At a minimum, this library must contain the publications listed in Appendix A, paragraph A.2.
1.8 Records.
The non-FAA service provider must maintain records of the items listed below for two years after an IFP is canceled and must make them available to the FAA for audit purposes upon request. The non-FAA service provider must maintain the records for five years in cases where the IFP was involved in any mishap.
1.8.1 Obstacle assessment records.
1.8.2 Detailed survey reports.
1-2
1.8.3 Autonomous Global Positioning System Recording System (AGRS) recordings from GOA and/or AOA and FV activities.
1.8.3.1 Furnish the AGRS electronic file (compatible with FAA computer systems) from both the obstacle assessment and the FV to FS.
1.8.3.2 Submit the report in conjunction with the procedure package. The report must contain, at a minimum, the following elements:
• Processing data and time;
• Maximum number of satellites;
• Minimum number of satellites;
• Average Position Dilution Of Precision (PDOP);
• Vertical Protection Level (VPL) [WAAS procedures only];
• Maximum Observed Horizontal DOP (HDOP) [WAAS procedures only];
• Horizontal Protection Level (HPL) [WAAS procedures only];
• Maximum observed Vertical DOP (VDOP) [WAAS procedures only];
• For each segment, the maximum and minimum altitude, ground speed, climb rate, and climb gradient; and
• A printed graphic of sufficient detail that depicts the flight track flown referenced to the desired track of the approach procedure, including procedure fixes.
1.8.4 Helicopter IFP utilizing Final Approach Segment (FAS) data block SBAS/GBAS (WAAS). A documented analysis of the FAS data in relation to the landing threshold point or desired Point-in-Space (PinS) for lateral and vertical path, and the Cyclic Redundancy Code (CRC).
1.8.5 All IFPV activities. Use FAA Forms 8260-30.1, Simulator Validation Checklist;
8260-30.2, Obstacle Assessment Checklist, and 8260-30.3, Flight Validation Checklist.
1. The IFPV evaluator will use FAA Forms 8260-30.1, 8260-30.2, and 8260-30.3 for SV, obstacle assessment, and FV respectively.
2. Include all the original forms in the initial procedure package submitted to FS.
1-3
3. Forward signed copies of FAA Form 8260-30.2 to FS upon the completion of a periodic (540-day) obstacle assessment in the inspection window. Digital signatures will be accepted.
4. Forms are in FAA Order 8900.1, Flight Standards Information Management System (FSIMS), Volume 11, Chapter 12, Section 1, Table 11-1, and Figures 11-30 through
11-32. Additionally, you can contact FS for current editions.
1.8.6 Personnel training records including initial, recurrent, and supplemental training documentation related to IFPV.
1.8.7 Individual and company IFPV LOAs.
1.8.8 Any additional items listed in the non-FAA Service Provider’s Operation Manual.
1-4
Figure 1-2. IFPV Process Flow Note: Some of the steps may not be required or may be accomplished in a different order.
1-5
CHAPTER 2. SERVICE PROVIDER REQUIREMENTS
2.1 Operational Documentation.
The non-FAA service provider must submit documentation describing the processes and policies followed for the Administrator’s acceptance documentation describing the processes and policies followed when conducting IFPV activities. FPAG will review the documentation and coordinate Administrator’s acceptance the non-FAA service provider must follow when conducting IFPV activities. The documentation must, at a minimum, contain the following:
2.1.1 General information containing:
1. Contact person(s) in charge of all saved records and method of accessing those records.
2. List of individuals authorized to conduct IFPV and person(s) able to access their relevant endorsements (simulator evaluation, GOA, AOA, and FV).
3. Process for periodic internal audits.
4. Process for communicating and coordinating with appropriate FAA offices to include the transfer of data, forms, and documents.
5. Process for acquiring and maintaining regulatory guidance material associated with each authorized function, to include processes for maintaining the currency of all reference material.
6. Process to ensure all personnel authorized to perform IFPV activities are current and trained in accordance with current IFPV guidance.
7. Training attendance, including initial, and recurrent and supplemental training documentation.
8. Process for ensuring that all IFPV processes have been accepted and remain current.
9. Procedures for revising the operations manual including a revision tracking system.
2.1.2 Ground Validation information. PBN IFP Quality Assurance (QA) review process (describe the formal internal review process).
2.1.3 Pre-flight Validation information containing:
2.1.3.1 SV process (if applicable).
2.1.3.1.1 QA review process of the Flight Management System (FMS) navigation database for correct coding of the PBN IFP (describe the formal internal review process used to compare and ensure matching data).
2-1
2.1.3.1.2 Simulator use requirements (i.e., methodology as to when a simulator check would be completed or required).
2.1.3.2 Obstacle assessment process, to include accuracy codes, achievable using company-specific equipment, and process.
2.1.3.2.1 GOA information (if applicable) containing:
1. Complete equipment list (hardware) to include type, make, model, software version, and revision if applicable.
2. Complete equipment list (software) used to post-process recorded GPS data, to include software manufacturer, title, version, and purpose.
3. Step-by-step process for obstacle verification.
4. Process for ensuring any new or different obstacles identified during GOA are documented and IFP re-evaluated, if necessary.
2.1.3.2.2 AOA information (if applicable) containing:
1. Complete equipment list (hardware) to include type, make, model, software version, and revision if applicable.
2. Complete equipment list (software) used for in-flight referencing of controlling obstacles and recording obstacle assessment tracks, to include software manufacturer, title, version, and purpose.
3. Step-by-step process for obstacle verification.
4. Company-specific Obstacle Evaluation Area (OEA) evaluation processes, if applicable.
5. Process for ensuring any new or different obstacles identified during an AOA are documented and IFP re-evaluated, if necessary.
6. Process for briefing pilots, without IFPV authorization, on AOA mission (e.g., briefing the helicopter operator’s pilot) [see Appendix B].
2.1.4 FV information containing:
1. QA review process of IFP chart, FAA Order 8260-series forms comparison with navigation database (describe the formal internal review process used to compare and ensure matching data).
2. Complete FV equipment list (hardware) and software version and revision if applicable.
2-2
3. Complete equipment list (software) used for recording flight tracks, to include software manufacturer, title, version, and purpose.
4. Process for addressing issues concerning obstacles or flyability discovered during flight validation.
5. Process for assessing airport/heliport infrastructure.
2.2 Safety Management System (SMS).
Service providers should define the safety policies, processes, and practices for all aspects of IFPV design, validation, and maintenance. Service providers should have technical processes and procedures in place to identify hazards and to mitigate risk. AC 120-92 (as amended), Safety Management Systems for Aviation Service Providers, may be used as guidance.
2-3
CHAPTER 3. INSTRUMENT FLIGHT PROCEDURE VALIDATION (IFPV)
3.1 Process.
IFPV consists of three elements: Ground Validation, Pre-flight Validation, and Flight Validation.
3.1.1 Ground Validation is a quality assurance review of the entire IFP package. The purpose is to identify areas with the potential to negatively affect the flyability and safety of the IFP (e.g., ARINC 424 coding errors, obstacles, Obstruction Evaluation/Airport Airspace Analysis (OE/AAA) and charting). The IFPV evaluator should address issues identified during the ground validation phase prior to the Pre-flight Validation phase.
3.1.2 Pre-flight Validation must include an obstacle assessment and may include a simulator evaluation. Address any issue identified during the Pre-flight Validation phase prior to Flight Validation.
3.1.2.1 Determine any special operational issues specific to the IFP (e.g., climb gradients, proximity to restricted areas, speed restrictions, etc.).
3.1.2.2 Although encouraged for all fixed wing procedures, simulator evaluations are required whenever there is a request for a waiver or request for FS-approval for deviations from standard criteria for Special RNAV (RNP) Authorization Required (AR) Instrument Approach Procedures (IAPs). Simulator evaluations are a valuable tool to test the procedure flyability and to compare database coding. They can test the procedure at the design limit and should be used where factors such as challenging terrain or specific operational considerations exist. All areas listed on FAA Form 8260-30.1 should be evaluated. Provide feedback to the procedure designer who, if feasible, should be involved in the simulator evaluation.
The simulator evaluation must be conducted in a FAA-qualified Level “C” or Level “D” flight simulator capable of flying the procedure. Information on simulator capabilities is available in 14 CFR part 60 and from the FAA National Simulator Program.
Note: For Special PBN IFP designed for a specific make/model/series and specific FMS, software part number, software version, and revision, the simulator evaluation must be flown in an FAA-qualified Level “C” or Level “D” simulator with the exact configuration specified.
3.1.2.2.1 Verify the navigation database for correct coding of the PBN IFP.
3.1.2.2.2 Comparisons must be made between the area navigation (RNAV) or FMS navigation data as displayed on the control display unit and the applicable FAA 8260-series forms, and the Flight Inspection Graphic (FIG).
Additionally, any notes and/or charted requirements and restrictions such as altitudes, speeds, and courses must be validated.
3-1
3.1.2.3 Conduct an obstacle assessment verifying the height and location of the documented controlling obstacle for each segment of the IFP. Perform a visual inspection of the OEA to determine the presence of undocumented or inaccurately documented obstacles. Obstacle assessment must be performed in accordance with FAA Order 8200.1 and must be documented on FAA Form 8260-30.2.
3.1.2.3.1 A GOA may produce the most accurate results; however, circumstances may prevent ground obstacle access.
3.1.2.3.2 GOA may be used to satisfy the requirement of periodic (540-day) inspections.
3.1.2.3.3 An AOA provides easier access to obstacles and OEA boundaries.
Airborne obstacle assessments can be flown in any type of approved aircraft; however, assessments performed in helicopters or slow moving/small category aircraft are preferred. Obstacle-assessment flight activities must comply with the flight rules contained in 14 CFR part 91.
Any deviation from a 14 CFR rule during an obstacle assessment must be authorized by the geographically respective Flight Standards District Office. Consistent with FAA Order 8260.19, an AOA will result in an accuracy code of 4D being assigned to that obstacle.
3.1.2.3.4 Document incorrect obstacle data such as obstacles that no longer exist or obstacle data that is inaccurate or is missing from the FAA obstacle databases. This information must be documented on the FAA Forms 8260-30.2 and 8260-9 and provided to the IFP designer so that complete, accurate data is used for IFP evaluation. All supporting information including photos and survey data must be retained by the organization.
Obstacle data inaccuracies, of any type, must be documented and accuracy codes assigned in accordance with FAA Order 8260.19.
3.1.2.3.5 If desired, a lower accuracy code specific to the process used by the IFPV provider may be coordinated with FS. This authorization is specific to both the company and the individual performing the obstacle assessment.
This accuracy code determination will be based upon the type of equipment used, its specifications, and a determination of process effectiveness.
3.1.3 Flight Validation (FV).
1. Review the results of the simulator and obstacle evaluations, and review any specific training, operational, or equipment requirements. Review the PBN IFP package per guidelines established in FAA Order 8200.1.
2. Compare the aircraft navigation database, appropriate FAA Order 8260-series forms, and the FIGs.
3-2
3. Assess flyability to determine that all segments of the procedure can be safely flown considering required speeds, climb gradients, descent gradients, coded flight path/glide path angles, and bank angles. Conduct FV per guidelines established in FAA Order 8200.1 and company operations manual and flown at or below the maximum intended speed on the developed lateral and vertical flight path. FV must be accomplished in an aircraft capable of flying the complete (instrument and visual portions) procedure as designed.
4. Conduct a controlling obstacle verification to provide the final assurance that the controlling obstacle has been correctly identified for each segment.
5. Verify that all airport/heliport infrastructures, such as markings, lighting, and communications are in place and operative, except locations without lighting (such as NA at night and Proceed Visual).
6. Evaluate other operational factors, such as aircraft equipment (e.g., TAWS/EGPWS), performance limitations such as minimum and maximum temperature limits, and human factors/flight deck workload.
7. Document the FV on the FAA Form 8260-30.3.
8. Conduct FV in an aircraft during non-revenue operations.
3.2 Requirements.
3.2.1 Pre-flight Validation.
3.2.1.1 Personnel.
3.2.1.1.1 Simulator evaluation (fixed wing only). In order to conduct a simulator evaluation, the designated IFPV evaluator must hold an LOA for simulator evaluation. To receive an LOA, simulator evaluation pilots must have similar qualifications as those required of an FV evaluator as specified in paragraph 3.2.2.1.2. For Special IFPs designed for a particular airframe, FMS, software part number, software version, and revision, the pilot assisting in that evaluation must have experience in that particular aircraft and its flight guidance and navigation system.
3.2.1.1.2 Ground Obstacle Assessment (GOA). In order to conduct a GOA, the designated evaluator must hold an LOA for GOA. Use of a remotely operated system for obstacle assessment that meets the requirements of AC 150/5300-17 (General Guidance and Specifications for Aeronautical Survey Airport Imagery Acquisition and Submission to the National Geodetic Survey) will be considered a GOA and must be documented in an accepted operation manual.
3.2.1.1.3 Airborne Obstacle Assessment (AOA). In order to conduct an AOA, the designated evaluator must hold an LOA for AOA. If the designated 3-3