Order 8260.43D Flight Procedures Management Program
This order describes how to request an Instrument Flight Procedure (IFP), including original, amendment, cancellation, or suspension, and defines the Federal Aviation Administration (FAA) process for coordinating, approving, and prioritizing each request. This order contains guidance that is pertinent to Title 14, Code of Federal Regulations, Part 97, Standard Instrument Procedures, while containing other guidance that is administrative in nature.
7. IFP Request Process › a. The IFP Request Process differs depending upon the service provider.…
Distribution: Electronic Only Initiated By: AFS-400
National Policy
ORDER 8260.43D
SUBJ: Flight Procedures Management Program
1. Purpose of This Order. This order describes how to request an Instrument Flight Procedure (IFP), including original, amendment, cancellation, or suspension, and defines the Federal Aviation Administration (FAA) process for coordinating, approving, and prioritizing each request. This order contains guidance that is pertinent to Title 14, Code of Federal Regulations, Part 97, Standard Instrument Procedures, while containing other guidance that is administrative in nature.
2. Audience. The primary audience for this order is all stakeholders involved in the IFP program management. The secondary audience is any service provider, individuals, or organizations interested in requesting or amending an IFP.
3. Where To Can Find This Order. You can find this order on the MyFAA Employee website under Orders & Notices and on the public FAA.gov website under Orders & Notices.
4. What This Order Cancels. FAA Order 8260.43C, Flight Procedures Management Program, dated April 9, 2019.
5. Explanation of Policy Changes. The significant changes include:
• Updated the IFP Request Process, based on the incorporation of policy waivers contained in a superseded policy memo.
• Updated Figure B-1 to reflect the current IFP Request Process with FAA as the service provider.
6. Background. Increasing demand for new IFPs requires continuous process improvement efforts to realize necessary efficiencies in the IFP development process. Order 8260.43A, Flight Procedures Management Program, established the Regional Airspace and Procedures Team (RAPT), providing a single point of contact for the initiation of new or modification of existing IFPs. This order redefined and renamed the roles of the RAPT and National Airspace and Procedures Team and added executive oversight and decision making. This effort established a national prioritization of workload and added emphasis on production capacity within the National Airspace System (NAS) while striving to reserve bandwidth to fast-track minor changes.
7. IFP Request Process
a. The IFP Request Process differs depending upon the service provider. The procedure proponent has the option of contracting with the FAA or with a non-FAA service provider for development of the IFP. If the procedure proponent selects the FAA as the service provider, see
Effective Date:
08/05/2026
b. IFP Validation (see figure B-1). Each service center will establish… › (2) IFP Validation Team objective.
paragraph 7a(1). If the procedure proponent selects a non-FAA service provider, see paragraph 7a(2).
(1) FAA as the service provider (see figure B-1): Submit a request for the creation, amendment, or cancellation of the IFP using the IFP Information Gateway. The IFP Information Gateway is your centralized IFP data portal, providing a single source for:
(a) Charts: All published, volume, and type;
(b) IFP Production Plan: Current IFPs under development or amendments with tentative publication date and status;
(c) IFP Coordination: All coordinated developed/amended procedure forms forwarded to Flight Program Operations or Charting for publication; and
(d) IFP Documents: Navigation Database Review (NDBR), repository, and source documents used for data validation of coded IFPs.
(2) Non-FAA Service Provider: A Non-FAA Service Provider Contacts List is available on the FAA.gov website. The procedure proponent will reach out to the non-FAA service provider directly. The non-FAA service provider will coordinate the procedure requests through Flight Standards. Flight Standards provides a list of these procedure requests to the IFP Validation Team for awareness only. The non-FAA service provider has the same coordination requirements as the FAA and will be the sole point of contact for development and maintenance of the procedure.
b. IFP Validation (see figure B-1). Each service center will establish and maintain an IFP Validation Team. The teams will validate all IFP requests within the service area. Permanent Notice to Airmen and abbreviated amendments as defined by Order 8260.19, Flight Procedures and Airspace, are submitted to the IFP Validation Team for awareness and coordination only. The service center may include additional experts on the IFP Validation Team as required to provide unique knowledge or skills relevant to a particular IFP.
(1) IFP Validation Team members. The members (or representatives) must include:
(a) Service Center Representatives;
1. Flight Procedures Team (FPT) manager (Team Lead); and
2. Air Traffic Representative.
(b) Flight Procedures and Airspace Group Representative; and
(c) Office of Airports Representative.
(2) IFP Validation Team objective. The team’s objective is to ensure efficient use of FAA resources to benefit the NAS. It is not intended for the authority of the IFP Validation
(5) Validate IFP request for policy compliance and NAS benefits. › (a) Alignment with PBN NAS Navigation Strategy;
Team to supersede organizational authorities and responsibilities of individual FAA lines of business as established by current directives.
(3) IFP request review. The IFP Validation Team will analyze the request and determine the FAA’s response. If the request is not approved, the IFP Validation Team will document the reasons, notify the proponent, and not forward it to the IFP Prioritization Team. For approved IFP requests whose development requires FAA resources (public or special), the IFP request will be forwarded to the IFP Prioritization Team.
(a) Consult with Advisory Circular 150/5300-13 (current edition), Airport Design, for standards and requirements in the design of civil airports. For example, the Approach or Departure Reference Code (APRC or DPRC) describes the combination of aircraft and visibility scenarios that allows concurrent operations on the runways and taxiways without generating airport (e.g., PPR) or ATC operational controls (i.e., wingspan limitations, taxiway movement restrictions, etc.). Normally, the IFP should be designed to support up to category D minimums where possible. While an airport sponsor may request that an IFP be published without a given line of minima, the committee will only concur with this request when it's necessary to mitigate a specific surface safety risk that outweighs the flight safety benefits of the line of minima. The team will document any exclusion of the approach category, stating the reason(s) for the exclusion.
(b) Identify IFPs with a known safety issue and those associated with a hard publication date [i.e., magnetic variation, airport construction, etc.]. Submit valid IFP requests to the IFP Prioritization Team.
(c) Review existing IFPs at the airport where the request is being made to determine if any should be canceled. Every effort should be made to eliminate IFPs that no longer serve a valid use or has/will be replaced by a Performance-Based Navigation (PBN) procedure.
(d) Maintain a record of coordination/decision. After the IFP Validation Team has reached a decision, each team member must sign the IFP Validation Checklist (see figure B-2) to document the decision. If the team approves the request, the signed IFP Validation Checklist provides assurance that all appropriate FAA lines of business are aware of the IFP development, amendment, suspension, or cancellation. The checklist will be included in the package submitted to the IFP Prioritization Team. If the IFP Validation Team does not approve the request, the reasons for disapproval will be documented on the IFP Validation Checklist and relayed to the proponent.
(4) The IFP Validation Team will establish a process (electronic preferred) to meet the coordination requirements listed.
(5) Validate IFP request for policy compliance and NAS benefits. This should include, but not be limited to, consideration of the following:
(a) Alignment with PBN NAS Navigation Strategy;
(b) Establish and maintain an IFP Production Schedule for: › 1. Procedures requiring hard publication date (i.e., runway…
(b) Comprehensive review of airport IFP services to ensure a comparable IFP is not currently available;
(c) Compatibility with national initiatives;
(d) Enhancement of operational efficiency;
(e) Alignment with AC 150/5300-13 (current edition) guidance; and
(f) Feasibility study to include navigational aid availability, Air Traffic Control Services, airspace analysis, environmental considerations, etc.
(6) Appeal process. If the IFP request is denied, the proponent may appeal the decision to the IFP Validation Team through the Flight Procedures Team Manager with additional justification. If the denial is sustained, the appeal will be forwarded to the IFP Prioritization Team for final determination. The IFP Validation Team will notify the proponent of the final determination.
c. IFP Prioritization (see figure B-1). The IFP Prioritization Team prioritizes all valid IFP requests received from the IFP Validation Team and establishes the national production schedule. IFP action to support the safety and integrity of the NAS is the team’s highest priority. The Air Traffic Organization’s (ATO) Vice President of Mission Support Services will appoint the team chair.
(1) IFP Prioritization Team members (or representative):
(a) Director, Office of Airport Safety and Standards (AAS-1);
(b) Manager, Flight Technologies and Procedures Division (AFS-400);
(c) Director, Policy (AJV-P);
(d) Director, Aeronautical Information Services (AJV-A);
(e) Service Center Director (AJV-W/C/E); and
(f) Director, Aircraft Operations (AJF-1).
(2) IFP Prioritization Team responsibilities:
(a) Establish and maintain a National IFP Prioritization List of validated requests subject to this order.
(b) Establish and maintain an IFP Production Schedule for:
1. Procedures requiring hard publication date (i.e., runway construction, magnetic variation, etc.); and
d. IFP Oversight. The IFP Oversight Committee provides broad direction… › (3) The IFP Oversight Committee will meet as necessary.
2. National initiatives and other projects as defined by the Oversight Committee.
(c) Establish a three-chart cycle publication window for those procedures on the priority list publishing within three years, excluding those identified in paragraph 7.c(2)(b).
Note: ATO/Mission Support will assign a publication date based on the projected publication window.
(d) Provide final determination of IFP request appeals submitted by IFP Validation Teams.
(e) Return IFP requests that require additional justification to the IFP Validation Team.
(f) Establish a process (i.e., electronic or meeting) to meet the above responsibilities and coordination requirements.
d. IFP Oversight. The IFP Oversight Committee provides broad direction and oversight of the Flight Procedures Management Program and the resolution of conflicting national initiatives of the NAS. For additional details, including the IFP Validation Checklist, see appendix B, paragraph 3.b, and figure B-2.
(1) IFP Oversight Committee members:
(a) Director, Office of Airport Safety and Standards (AAS-1);
(b) Director, Office of Safety Standards (AFS-1);
(c) Vice President, Air Traffic Services (AJT-0); and
(d) Vice President, Mission Support Services (AJV-0) (Chair).
(2) IFP Oversight Committee responsibilities:
(a) Ensure the policy/practices of the subordinate teams are executed in a manner that maintains the safety and integrity of the NAS;
(b) Provide guidance on national initiatives; and
(c) Provide resolution of competing initiatives.
(3) The IFP Oversight Committee will meet as necessary.
Bryan Bedford Administrator
1. Distribution. This order is electronic only. › 2. Suggestions for Improvements.
08/05/2026 8260.43D Appendix A
Appendix A. Administrative Information
1. Distribution. This order is electronic only.
2. Suggestions for Improvements. Please forward all comments on deficiencies, clarifications, or improvements regarding the contents of this order to the Directives Management Officer at [email protected] and [email protected]. Your suggestions are welcome. FAA Form 1320-19, Directives Feedback Information, is available at the link provided as well as located at the end of this document for your convenience.
3. IFP Validation Checklist. › Note
Appendix B. Supplemental Information
1. General. This appendix contains a process flow diagram that shows how an IFP request progresses through the FAA. The appendix also contains an IFP validation checklist, which may be used to document the approval or disapproval of an IFP request.
2. Process Flow. The Process Flow Diagram (see figure B-1) outlines the process for publishing an IFP.
3. IFP Validation Checklist.
a. Each line of business will provide justification (as needed) to support the validation of the project request.
b. When completing the validation checklist (see figure B-2), each member is responsible for providing justification/information that supports the requested procedure (as needed). The justification/information must detail the benefits of the procedure to the NAS, along with the criteria used to validate the request.
Note: If the justification/information is not provided, the project will not be reviewed by the IFP Validation Team.
Figure B-1. Process Flow Diagram
Figure B-2. IFP Validation Checklist
Airport ID Airport Name Airport Location (City, ST) Requested by: Procedure(s) Description:
Request Outcome (provide justification comments on page 2): Validated Denied
Request Tracking Number:
Approach Categories:
A B C D E (If less than D, enter justification in the comments below) Comments:
Requested Pub Date: (enter justification in the comments above)
Hard Date Required: Yes No
Service Center Flight Procedures Team Objection No Objection
Service Center Air Traffic Operations Support - Objection No Objection
Flight Standards Division Objection No Objection
Regional Airports Division Objection No Objection
Validation or denial justification must be included by one or more core members below. Flight Procedures Team Comments:
Air Traffic Comments:
Airports Comments:
Flight Standards Comments:
Appendix C. Directives Feedback Information
08/05/2026 8260.43D Appendix C
Appendix C. Directives Feedback Information
Please submit any written comments or recommendations for improving this directive or suggest new items or subjects to be added to it. Also, if you find an error, please tell us about it. Subject: Order
To: Directive Management Officer,
(Please mark all appropriate line items)
☐ An error (procedural or typographical) has been noted in paragraph on
page .
☐ Recommend paragraph on page be changed as follows: (attached separate sheet if necessary) ☐ In a future change to this order, please include coverage on the following subject:
(briefly describe what you want added): ☐ Other comments: ☐ I would like to discuss the above. Please contact me. Submitted by: Date:
Telephone Number: Routing Symbol: FAA Form 1320-19 (11/23) Supersedes Previous Edition