Order 8260.60C Special Procedures
This order provides policy, guidance, and standardization for requesting, maintaining, and processing special procedures and Area Navigation (RNAV) Visual Flight Procedures (RVFPs) that are not prescribed under Title 14, Code of Federal Regulations (14 CFR), part 71, part 95, or part 97.
Distribution: Electronic Initiated By: AFS-400
SUBJ: Special Procedures
This order provides the policy, guidance, and standardization for requesting, maintaining, and processing special procedures that include Special Instrument Flight Procedures (IFPs) and Area Navigation (RNAV) Visual Flight Procedures (RVFPs).
For Hugh J. Thomas Executive Director Flight Standards Service
fNRA
Effective Date: National Policy
ORDER 8260.60C
09/18/2026
LEISHA M BELL
Digitally signed by LEISHA M BELL Date: 2026.09.18 07:49:14 -04'00'
i
Table of Contents
Chapter 1. General Information … 1-1
Section 1-1. Administrative … 1-1
1-1-1. Purpose of This Order … 1-1 1-1-2. Audience … 1-1 1-1-3. Where to Find This Order … 1-1 1-1-4. What This Order Cancels … 1-1 1-1-5. Required Forms … 1-1 1-1-6. Explanation of Policy Changes … 1-1 1-1-7. Background … 1-1
Section 1-2. General Guidance … 1-2
1-2-1. Area Navigation Visual Flight Procedures … 1-2 1-2-2. Special Procedures … 1-2
Section 1-3. Special Procedure Requests and Processing … 1-3
1-3-1. Initiating a Request for Special Procedures … 1-3
Chapter 2. Roles and Responsibilities … 2-1
Section 2-1. Processing … 2-1
2-1-1. Special Procedures … 2-1 2-1-2. Special Procedure Package Contents … 2-2 2-1-3. Service Provider Requirements … 2-4 2-1-4. Transferring Special Procedure Maintenance Responsibilities … 2-5 2-1-5. Cancellation of Special Procedures … 2-6 2-1-6. Issuance of Special Procedures … 2-6 2-1-7. Charting … 2-7
Chapter 3. RNAV Visual Flight Procedures … 3-1
Section 3-1. General Information … 3-1
3-1-1. RNAV Visual Flight Procedure … 3-1 3-1-2. Considerations … 3-1 3-1-3. Preliminary Concept Request … 3-1 3-1-4. General Design and Charting Guidelines … 3-2 3-1-5. Completion of FAA Form 8260-19 … 3-4 3-1-6. RVFP Validation … 3-8 3-1-7. RVFP Training/Attention All Users Page … 3-8 3-1-8. Processing Documentation … 3-9 3-1-9. Issuance of RVFPs … 3-9 3-1-10. Maintenance … 3-10
ii
Appendix A. Administrative Information … A-1
1. Distribution … A-1 2. Acronyms, Abbreviations, Definitions, and Related Publications … A-1 3. Suggestion for Improvements … A-1
Appendix B. Directives Feedback Information … B-1
Section 1-1. Administrative › 1-1-7. Background.
Chapter 1. General Information
Section 1-1. Administrative
1-1-1. Purpose of This Order. This order provides policy, guidance, and standardization for requesting, maintaining, and processing special procedures and Area Navigation (RNAV) Visual Flight Procedures (RVFPs) that are not prescribed under Title 14, Code of Federal Regulations (14 CFR), part 71, part 95, or part 97.
1-1-2. Audience. All personnel who are responsible for requesting, designing, amending, and/or maintaining special procedures and RVFPs.
1-1-3. Where to Find This Order. You can find this order on the public Federal Aviation Administration (FAA) website under Orders & Notices and the FAA Dynamic Regulatory System (DRS).
1-1-4. What This Order Cancels. FAA Order 8260.60B, Special Instrument Procedures, dated 12/11/2020.
1-1-5. Required Forms. FAA Form 8260-19, RNAV Visual Flight Procedures.
1-1-6. Explanation of Policy Changes. Significant areas of new direction, guidance, policy, and criteria are as follows:
• Updated administrative changes throughout the document.
• Updated page and paragraph numbers in the Table of Contents.
• Updated area navigation visual flight procedures guidance.
1-1-7. Background. Historically, special procedures were limited in both quantity and use. Improvements in navigation methods, aircraft performance systems, and a growth in private aviation have increased the need for special procedures that are tailored to a specific user(s). This has led to the creation of commercial, non-FAA service providers that design special procedures tailored to locations, performance characteristics, and specific users.
1-2-2. Special Procedures (Instrument and Visual Flight Procedures). › f. For the current inventory of special IFPs, see the Special…
Section 1-2. General Guidance
1-2-1. Area Navigation Visual Flight Procedures.
a. RVFPs are not instrument flight procedures but follow the submission and distribution process used for special instrument flight procedures.
b. Chapter 3 explains RVFP-specific requirements. (FAA service providers and non-FAA service providers will herein be referred to as “service providers” unless otherwise specified).
1-2-2. Special Procedures (Instrument and Visual Flight Procedures).
a. Special procedures may be designed based on unique aircraft performance/equipment or flight crew training requirements. They may also require the use of airports, landing aids, communications, or weather services and issued to authorized users only.
b. Special procedures require specific processing, are reviewed and authorized by the Flight Technologies and Procedures Division (AFS-400), who may have specified aircraft performance/equipment requirements, special crew training, airport facility equipment, waivers from published standards, proprietary criteria, and restricted access.
c. Special procedures are not published in the Federal Register and are often promulgated at the request of private individuals, operators, or private airport/heliport owners. These procedures may be aircraft-specific, have unique designs, or specific requirements. Special procedures that serve the public interest may be funded by the FAA. The FAA Order 8260.43, Flight Procedures Management Program, requires specific approval of the appropriate Instrument Flight Procedure (IFP) Validation Team prior to FAA-funded special procedure design.
d. Special procedures may require non-government funding for design and maintenance.
e. Requests for any information relating to the development of special procedures, or the approved procedures, made in accordance with the provisions of the Freedom of Information Act (FOIA), 5 U.S.C. 552, will be handled separately in accordance with the FOIA and FAA Order 1270.1, Freedom of Information Act Program. Responses to such requests will be coordinated through AFS-400, and release determination will be made case-by-case.
f. For the current inventory of special IFPs, see the Special Instrument Flight Procedure List.
Section 1-3. Special Procedure Requests and Processing
1-3-1. Initiating a Request for Special Procedures.
a. To request a special procedure, the proponent/operator has the following options:
1-3-1. Initiating a Request for Special Procedures. › d. If the proponent elects to utilize a non-FAA service provider, the…
(1) Contact the FAA for special procedure design,
(2) Design their own special procedure (as a non-FAA service provider), or
(3) Select a non-FAA service provider for special procedure design.
NOTE 1: If the proponent contracts with the FAA, then the FAA service provider will process the request.
NOTE 2: A lead operator (typically an air carrier) may design and submit an RVFP to the Flight Technologies and Procedures Division’s Flight Procedure and Airspace Group (AFS-420).
b. Proponents/operators that would like the FAA to design a special procedure may initiate requests by filling out an Instrument Flight Procedures Request Process form or contacting the applicable Operations Support Group’s Flight Procedures Team (OSG FPT).
c. If the proponent would like to design their own special procedure (proponent as a non-FAA service provider), the proponent will follow the guidance in this order and FAA Order 8260.43 for documentation submission to AFS-420’s appropriate service area section. Refer to the Service Center Area Division of Work Map.
d. If the proponent elects to utilize a non-FAA service provider, the non-FAA service provider will follow the guidance in this order and FAA Order 8260.43 for documentation submission to AFS-420’s appropriate service area section. Refer to the Service Center Area Division of Work Map.
NOTE: For additional information see the Non-FAA Service Provider Contact List.
2-1-1. Special Procedures. › b. Flight Technologies and Procedures Division.
Chapter 2. Roles and Responsibilities
Section 2-1. Processing
2-1-1. Special Procedures.
a. Service provider.
(1) Designs and amends procedures using applicable FAA directives or other criteria approved by the FAA.
(2) Forwards all new, amended, abbreviated amendments, and cancellation procedure packages to the AFS-420 for authorization and coordination.
(3) Completes waiver request(s) in coordination with the proponent and forwards it to AFS-420 for further action.
(4) Performs quality assurance (QA) review of special procedures prior to submission to AFS-420 for authorization.
(5) Coordinates with the FAA Instrument Flight Procedures Validation Team and service center airspace offices by completing the AFS-420 Validation/Airspace request forms prior to submitting procedures (except for RVFPs).
(6) Coordinates, documents, and performs flight inspection/flight validation of the procedures (when applicable) and provides the required forms and associated data to AFS-420.
(7) Maintains a complete procedure package file for each special procedure designed and/or maintained. Contents of this file, at a minimum, must contain all applicable 8260-series FAA forms, maps, and all other relevant documents related to the design of the procedure (see paragraph 2-1-2 for procedure package content requirements).
(8) Performs periodic reviews in accordance with FAA Order 8260.19, Flight Procedures and Airspace, (except for RVFPs). If a service provider intends to transfer the responsibility for periodic reviews (procedure maintenance) to another service provider, see paragraph 2-1-4.
(9) When the service provider will no longer maintain a special procedure, and the procedure will not be transferred from or to another service provider; the service provider must notify AFS-420, initiate Notice to Airmen (NOTAM) action, or initiate cancellation of the procedure as appropriate (see paragraph 2-1-5). The service provider must maintain the procedure until the procedure is canceled or removed from service by NOTAM.
(10) Signs “Approved By” and “Reviewed By” lines on 8260-series FAA forms certifying the special IFP was developed in accordance with applicable policies, directives, standards, and criteria and is approved for further processing .
b. Flight Technologies and Procedures Division.
Section 2-1. Processing › 2-1-2. Special Procedure Package Contents.
(1) Reviews and approves non-FAA service provider proprietary criteria to support requests for special procedures in accordance with FAA Order 8260.19, section 2-12.
(2) Conducts oversight of non-FAA service providers in accordance with FAA Order FS 8260.57, Oversight of Non-FAA Instrument Flight Procedure Service Providers.
(3) Coordinates with other Flight Standards (FS) Divisions and other FAA organizations on special procedure packages, if needed.
(4) Identifies specific operational and/or training requirements relative to any unique and/or local environmental conditions and documents on FAA Form 8260-7B, Special Instrument Approach Authorization.
(5) Establishes and communicates an effective date of all special procedures (including cancellations) on the appropriate 8260-series FAA forms as soon as possible within 224 days of the approved by signature date on FAA Form 8260-7B. The effective date must coincide with Aeronautical Information Regulation and Control (AIRAC) cycle dates and should meet the appropriate AIRAC cutoff dates. The effective date may exceed 224 days with AFS-420 Manager’s approval.
(6) Distributes special procedure packages as appropriate.
(7) Provides oversight and tracking for issuance, amendment, cancellation, suspension, and revocation of special procedures. Maintains records of all current, amended, and canceled special procedure packages in accordance with Agency directives.
(8) Coordinates with the principal operator inspector (POI) regarding the operators' meeting specific procedure requirements. Authorizes the issuance of special procedures to additional requesters through the Safety Assurance Office (SAO)/POI.
(9) Evaluates waivers and approval requests for instrument flight procedures in accordance with FAA Order 8260.19.
NOTE: FAA Form 8260-7B will accompany all special procedures and be incorporated as an amendment to the operations specifications of the certificate holder. The form may also be issued with a Letter of Authorization (LOA) to part 91 operators. A separate FAA Form 8260-7B is required for issuance of each special obstacle departure procedure (ODP) and/or standard instrument departure (SID). The requirements documented on this form will be developed and approved by AFS-400. See FAA Order 8260.19, appendix I for details.
c. Other FS divisions and FAA organizations. Assist with evaluating special procedure packages, including participation at Flight Technologies and Procedures Division’s Procedure Review Board (PRB), when requested.
2-1-2. Special Procedure Package Contents. Service providers must submit a single “standalone” package (see FAA Orders 8260.19 and 8260.46, Departure Procedure (DP) Program, as appropriate). For RVFP package contents, see chapter 3. For FAA, see FAA-AFS Memorandum of
Agreement (MOA) between Flight Standards and Mission Support Services on Specials, Waivers, and Approvals Processing, dated 06/26/2023 (available on DRS).
(14) Documentation of the following (unless the service provider has an… › (c) The identity of the proponent (if different from the airport…
a. A complete special procedure package (original and full amendments) must contain the documents listed below in the following order:
(1) Cover letter explaining the request to include any waiver(s) and/or approval(s) and any documentation that is not included in the package;
(2) Applicable 8260-series FAA forms (see FAA Order 8260.19), including all required signatures;
(3) FAA Form 8260-2, Radio Fix & Holding Data Record, and/or FAA Form 8260-2 Data Worksheets (if applicable) in alphabetical order;
(4) Documentation for waiver and/or approval requests, if any;
(5) Existing instrument approach chart (if applicable) or graphic portrayal of the procedure;
(6) Maps with identifying scale, graphically depicting obstacles in relation to the obstacle evaluation areas (OEAs). Each obstacle will be identified by a number that corresponds with the submitted form for the procedure;
(7) Flight inspection/validation forms;
(8) Missed approach/departure climb gradient calculations for manually built procedures;
(9) Distance measuring equipment (DME)/DME assessments (if applicable);
(10) Temporary NOTAM (T-NOTAM);
(11) Appropriate environmental review process documentation in accordance with FAA Order 1050.1, FAA National Environmental Policy Act Implementing Procedures. Service providers need documentation signed by an Environmental Protection Specialist unless covered under a memorandum of agreement;
(12) Stamped information (INFO) copies of all existing waivers/approval (if applicable);
(13) Other Supporting Documentation as required and
(14) Documentation of the following (unless the service provider has an FAA-accepted process to retain these records):
(a) Acceptance of the procedure by all affected Air Traffic Control (ATC) facilities,
(b) Airport/Heliport owner/manager acceptance of special procedure design,
(c) The identity of the proponent (if different from the airport owner/manager),
b. The service provider is responsible for providing the following… › (1) The service provider must identify a point-of-contact as the focal…
(d) The identity of the operator(s) expected to use the procedure, and
(e) Documentation that the proponent and airport/heliport owner(s) have granted permission to the proposed operator(s) to use the procedure. Non-FAA service providers may act as an agent for the proponent in granting this permission.
b. Abbreviated Amendments. An abbreviated amendment contains the documents listed below in the following order:
(1) A cover letter including a brief description of the changes to include any waiver(s) and/or approval(s) and any documentation that is not included in the package.
(2) New FAA Form 8260-7A, Special Instrument Approach Procedure, and/or 8260-15 departure procedure series FAA forms (as applicable) in accordance with FAA Order 8260.19, chapter 8.
(3) Appropriate environmental review process documentation in accordance with FAA Order 1050.1. Service providers need documentation signed by an Environmental Protection Specialist unless covered under a memorandum of agreement.
c. Any package submitted without the information listed in paragraph 2-1-2.a, may be returned to the submitter along with the reason it was returned, with no action taken. Documentation exceptions may be authorized by the AFS-420 Manager or designee.
(1) The service provider must communicate these omissions in the cover letter. If these items are not included in the submission, the procedure may be reviewed at the PRB but not authorized until all required documentation is submitted to AFS-420.
(2) Where circumstances require immediate NOTAM action, the service provider must issue a Flight Data Center (FDC) T-NOTAM to initiate the change. An amended FAA Form 8260-7A/8260-15 departure series FAA forms (as applicable) amendment must be submitted and processed within 224 days of NOTAM issuance (see FAA Order 8260.19 and FAA Order JO 7930.2, Notice to Airmen). If the processing deadline cannot be met, a NOTAM extension must be submitted to FS.
2-1-3. Service Provider Requirements (Procedure Maintenance Plan).
a. In addition to the completion of applicable 8260-series FAA forms (see paragraph 2-1-2), certain levels of coordination, maintenance, protection, and periodic review are required.
b. The service provider is responsible for providing the following actions and plans for the procedure to AFS-420 for review at the PRB [service providers with accepted maintenance plans on file with AFS-420 are exempt from paragraphs 2-1-3].
(1) The service provider must identify a point-of-contact as the focal point for the organization’s maintenance activities. AFS-420 will determine whether the applicant possesses the expertise and qualifications to conduct procedure maintenance.
b. If the transfer is approved, the service providers must address the… › (2) Coordinate transfer of documentation files to include all…
(2) The service provider will document a method for conducting periodic reviews, which must comply with the requirements in FAA Order 8260.19 to include a process for ensuring that a review is conducted within the allotted timeframe and action taken (NOTAM, amendments) to correct safety/criteria compliance issues.
(3) The service provider will establish an Obstruction Evaluation (OE) Study Plan and utilize the automated Obstruction Evaluation/Airport Airspace Analysis (OE/AAA) program. Document a process for receiving notifications and conducting evaluations of all OE studies in a time-sensitive manner. Provide information to show that a method is in place to identify obstruction evaluation/nonrulemaking airspace cases that may have an aeronautical effect due to the obstacle’s height and proximity to the instrument procedure(s), along with a specific process for taking appropriate action.
(4) The service provider will establish a NOTAM Plan. The National Flight Data Center (NFDC) NOTAM process is used to disseminate NOTAMs on special procedures in accordance with FAA Order JO 7930.2.
(5) The service provider will establish a plan to comply with periodic flight validation requirements as specified in FAA Order 8200.1, U.S. Standard Flight Inspection Manual (USSFIM), and FAA Order 8900.1 Volume 11, Chapter 12, Section 1, Requirements to Conduct an Instrument Flight Procedure Validation.
(a) Document a method for ensuring the validation can be conducted within the allotted timeframe, who to contact, and/or what to do if periodic dates are not met.
(b) Provide documentation indicating appropriate airspace requirements have/will be met in accordance with FAA Order 8260.19 (see chapters 4 and 5 as applicable).
(6) When a special procedure has not been or can no longer be maintained in accordance with the provisions of this order and FAA Order 8260.19, the service provider will notify the AFS-420 and immediately discontinue use (NOTAM may be required). If maintenance cannot be restored within 60 calendar-days, a complete procedure review must be conducted before reissuance, or the procedure must be canceled (see paragraph 2-1-5).
2-1-4. Transferring Special Procedure Maintenance Responsibilities. Special procedures may be transferred from one service provider to another for maintenance after the following requirements have been met:
a. The receiving service provider submits a written request to AFS-420 seeking approval to assume maintenance responsibilities from the current service provider. This request must indicate how the requirements specified in paragraph 2-1-3.b will be met.
b. If the transfer is approved, the service providers must address the following:
(1) Establish the transfer date as agreed to by all parties.
(2) Coordinate transfer of documentation files to include all applicable 8260-series FAA forms (see paragraph 2-1-2 for procedure package contents) and general correspondence that
a. Safety Assurance Offices/POI. › (4) Guidance for Powered-lift aircraft special issuance, in accordance…
pertains to the procedure(s). This includes documentation on periodic reviews, NOTAMs, OE studies, and periodic flight inspection/validation as applicable.
(3) Once procedures are accepted by the receiving service provider, they become their responsibility. The receiving service provider must ensure that transferred procedures are current and acceptable. The receiving service provider may need to issue NOTAMs against the transferred procedures until the identified issues are resolved.
2-1-5. Cancellation of Special Procedures.
a. When a special procedure will no longer be maintained and responsibility for it will not be transferred, it must be canceled.
b. The provider will send the cancellation package to AFS-420 for processing, to include:
(1) A cover letter including a brief description of the reason for cancellation and
(2) Documents from paragraph 2-1-2.a(2) (as applicable) (in accordance with FAA Order 8260.19).
NOTE 1: AFS-420 will coordinate and document the effective date after authorization of cancellation.
NOTE 2: The service provider will continue to maintain the procedure until canceled or removed from service by NOTAM, with the concurrence of AFS-420.
c. If a special procedure(s) is/are planned to be canceled and replaced by a new procedure(s) concurrently, both the replacement procedure(s) and canceled procedure(s) must be submitted to AFS-420 at the same time. AFS-420 will ensure that both procedures share the same effective date.
2-1-6. Issuance of Special Procedures.
a. Safety Assurance Offices/POI.
(1) Airplane Special procedures issuance process and guidance. See FAA Order 8900.1 Volume 3, Chapter 18, Section 5, Part C Operations Specifications – Airplane Terminal Instrument Procedures and Airport Authorization and Limitations.
(2) Helicopter Special procedures issuance process and guidance. See FAA Order 8900.1 Volume 3, Chapter 18, Section 7, Part H Helicopter Terminal Instrument Procedures and Airport Authorizations and Limitations.
(3) Part 129 Operators Special procedures issuance process and guidance. See FAA Order 8900.1 Volume 12, Chapter 4, Section 4, Title 14 CFR Part 129 Part C Operations Specifications – Airplane Terminal Instrument Procedures and Airport Authorizations and Limitations.
(4) Guidance for Powered-lift aircraft special issuance, in accordance with 14 CFR Part 194 194, Special Federal Aviation Regulation (SFAR) No. 120 – Powered-Lift: Pilot Certification
Section 2-1. Processing › 2-1-7. Charting.
and Training, Operations Requirements, and any associated guidance for Operations Specifications (OpSpecs).
(5) Foreign-Registered Aircraft (Not 14 CFR Part 129) and Foreign Civil Aircraft (14 CFR Part 375), Special procedures issuance process and guidance. See FAA Order 8900.1, Volume 12, Chapter 3, Section 9, Letters of Authorization.
b. Flight Technologies and Procedures Division. See FAA Order 8900.1 Volume 3, Chapter 18, Sections 5, Part C Operations Specifications – Airplane Terminal Instrument Procedures and Airport Authorizations and Limitations (OpSpec C081 and C381) and Volume 3, Chapter 18, Section 7, Part H Helicopter Terminal Instrument Procedures and Airport Authorizations and Limitation (OpSpec H122).
2-1-7. Charting. Charts must include all relevant information from the applicable 8260-series FAA forms. Charts should adhere to standard approach charting conventions, but may be tailored as necessary to meet user needs.
NOTE: For “Special” procedures charted by the proponent or agent hired by the proponent, the procedure design authority may decide where to place chart notes.
Figure 2-1–1. Special Procedures Processing Flow Diagram
Chapter 3. RNAV Visual Flight Procedures
Section 3-1. General Information
a. Contents. Include the following information (as applicable): › (1) Verification that no Part 97 IAP(s) serve the runway or that…
3-1-1. RNAV Visual Flight Procedure. An RVFP is a special visual flight procedure flown on an instrument flight rule (IFR) flight plan. It is flown in visual conditions and clear of clouds must be maintained. An RVFP is flown using an approved RNAV system to maintain published lateral and vertical paths to runways without an instrument approach procedure. It requires an ATC-clearance and may begin at other points along the path of the charted procedure when approved by ATC. An RVFP is not published in the Federal Register for public use and the operator is required to have a specific OpSpec approval. Required ceiling and visibility minima are published on the procedure chart. An RVFP does not have a missed approach procedure and is not evaluated for obstacle protection.
3-1-2. Considerations.
a. Performance Based Navigation (PBN) Instrument Approach Procedures (IAPs) should be the first and primary strategy for approaches, even in visual conditions. PBN IAPs ensure consistent, repeatable flight paths.
(1) If a PBN IAP is not feasible, the FAA would prefer an Instrument Approach with a Visual Guidance Fix (VGF). This is an instrument required navigation performance (RNP) approach (APCH) procedure with a VGF.
(2) If a PBN IAP or IAP with a VGF are not feasible, consider an RVFP.
b. RVFPs promote flight path repeatability, may reduce air traffic communications, and enhance safety by providing prescribed lateral and vertical guidance to a runway.
c. RVFPs are neither Charted Visual Flight Procedures nor IFPs. RVFPs are not authorized for Simultaneous Independent Parallel Instrument Approaches, Simultaneous Close Parallel instrument approaches, Simultaneous Offset Instrument Approaches, or Established on RNP operations.
d. RVFPs must be designed to serve the maximum number of operators and are not exclusive to a single operator
NOTE: RVFPs designed by proponents/non-FAA service providers do not require SPECIAL IFP validation (see paragraph 2-1-1.a).
3-1-3. Preliminary Concept Request. During project initiation (before design and procedure submittal to the AFS-420), the proponent must review the existing IFPs and the need for the proposed RVFP. The request must provide justification and ATC acceptance of the preliminary concept for the requested RVFP.
a. Contents. Include the following information (as applicable):
(1) Verification that no Part 97 IAP(s) serve the runway or that existing IAP(s) are not operationally suitable;
3-1-4. General Design and Charting Guidelines. › b. RVFPs are not IAPs, are not designed with prescribed Terminal…
(a) Justify why a Part 97 or non-Part 97 (Special) IAP has not been requested.
(b) Provide the estimated publication date for the Part 97 IAP that is being designed or requested if applicable.
(2) The standard navigation capability for the RVFPs is RNAV 1 with the Global Positioning System (GPS) as the navigation sensor and track-to-fix (TF) turn construction.
(a) If radius-to-fix (RF) turns are required, then the alternate navigation capability is RNP 1 with GPS as the navigation sensor.
(b) Provide the required navigation capability used for the RVFP path design.
(3) Include a flight safety analysis that explains the safety concerns an RVFP will mitigate. Examples of this data include:
(a) Improvements to stabilized approaches,
(b) De-identified data from Flight Operations Quality Assurance; Aviation Safety Action Program, and
(c) Aviation Safety Information Analysis and Sharing or air traffic track data may be used to provide evidence of an existing safety concern that an RVFPs may mitigate.
(4) Prototype Chart;
(5) Environmental benefits and operational efficiency benefits may also be included. These benefits are not a substitute for the flight safety analysis.
(6) Other work products [i.e., Terminal Area Route Generation Evaluation and Traffic Simulation (TARGETS) package] or other design software products may be included.
b. Submission. After completing the above, submit the preliminary concept request to AFS-420. The request will be routed to the AFS-420 Aviation Safety Inspector (ASI), who will coordinate the review and provide FS acceptance of the preliminary concept request for further design of the RVFPs.
3-1-4. General Design and Charting Guidelines.
a. Design RVFPs to emulate existing visual approach paths. These procedures must include all normal operational and/or desired altitude and speed restrictions. Proper coordination between the lead operator and/or their representative, the local ATC facility, and the Flight Technologies and Procedures Division will ensure procedural design requirements are satisfied.
b. RVFPs are not IAPs, are not designed with prescribed Terminal Instrument Procedures (TERPS) criteria and do not provide obstacle protection. Any RVFP design and related ATC facility directives for procedural use must consider these facts.
c. To assess RVFP flyability, a design tool such as TARGETS can be used during the RVFP design process to evaluate coded flight paths (lateral and advisory vertical.
3-1-4. General Design and Charting Guidelines. › j. Identification of RVFPs. RVFPs must be uniquely identified to permit…
d. A runway served by an RVFP should be equipped with a visual glideslope indicator (VGSI). If there is a VGSI, the coded advisory vertical path provided should be coincident (descent angles within 0.20 degrees) or steeper than the guidance provided by the VGSI.
e. Missed approach procedures will not be published; however, expected go-around instructions may be published with FS approval. These expected go-around instructions should be limited to a heading flown and altitude to maintain. Use of waypoints (WPs) in the published, expected go-around instruction is not authorized.
f. Weather Requirements. The ceiling and visibility minimums required to conduct these procedures must equal or exceed for visual approach operations and meet applicable 14 CFR requirements, ATC standards (reference FAA Order JO 7110.65, Air Traffic Control) and any local ATC facility policies. Ceiling and visibility minimums must be coordinated between the lead operator and local ATC facility and approved by FS.
g. Charts must include all relevant information from FAA Form 8260-19, RNAV Visual Flight Procedures. Charts should adhere to standard charting conventions; and may be tailored as necessary to meet user needs. Use only dashed lines to depict the RVFP flight segments.
NOTE: As FAA Form 8260-19 does not have PBN and Equipment Requirements boxes, RVFPs built with RF legs must include the chart note “RF Required.”
h. PBN Equipment Requirements. PBN Navigation Specifications (NavSpec) and sensor requirements will be defined on FAA Form 8260-7B. While there is no requirement to include the PBN NavSpec and sensor requirements on the RVFP chart, they may be printed on the chart or the Attention All Users Page (AAUP).
(1) A standard RVFP with TF-TF turn construction should require RNAV 1 as the navigation capability with GPS. This must be documented on FAA Form 8260-7B as “RNAV 1 – GPS.”
(2) An alternate turn construction using RF functionality must require RNP 1 with the navigation sensor GPS. When RF functionality is required anywhere on the RVFP, this must be documented on FAA Form 8260-7B as “RNP 1 – GPS, RF.”
i. RVFPs with Concurrent RF/TF Legs. RVFPs with concurrent RF and TF legs have been built in various locations in the National Airspace System (NAS). RVFPs are considered to have concurrent RF and TF legs when the constructed ground tracks for each version are so similar that any small differences can’t be distinguished by ATC. RVFPs with concurrent RF and TF legs may be processed in one package, utilizing one FAA Form 8260-19.
j. Identification of RVFPs. RVFPs must be uniquely identified to permit differentiation on charts/publications, airborne equipment displays, and during ATC communications. The RVFP must be named using the following format: “RNAV VISUAL RWY XX.” The procedure name must be
a. Basic information. › (6) Touchdown Zone Elevation (TDZE).
included in all correspondence and documentation. The following items must be included on the chart:
(1) Procedure name as documented on FAA Form 8260-19. The procedure name coded in the aircraft avionics navigation database should match the procedure name on the chart and be retrievable by name (i.e., line-selectable). Pilots are not authorized to build these procedures manually.
(2) Operators with different Flight Management System (FMS) databases on single or multiple-type airframes that cannot code the name the same in the database must annotate the procedure name for each airframe on the chart.
NOTE: Both versions of an RVFPs with concurrent RF and TF legs will be identified on their respective charts with the same identification “RNAV VISUAL RWY XX.” The concurrent versions may be identified/differentiated for operator use utilizing the guidance above. ATC will be provided with both versions of the RVFP charts. Only waypoints that are depicted on both charts may be used for ATC clearance. ATC procedures for clearing an aircraft on an RVFPs that have concurrent RF and TF legs will be agreed to by ATC and the operator prior to use. ATC will note these procedures in the appropriate facility directives/guidance.
3-1-5. Completion of FAA Form 8260-19. This paragraph contains information applicable to the completion of FAA Form 8260-19. Guidance is referenced to each separate area of the form.
a. Basic information.
(1) Airport Identifier. Enter the official FAA airport identifier as derived from the National Airspace System Resource (NASR).
(2) Procedure Name. Enter procedure identification as determined by paragraph 3-1-4.i.
(3) Original/Amendment. Enter “ORIG” for an original procedure or “AMDT” with the applicable amendment number/letter.
(a) The amendment number must be advanced or the alphabetical suffix added/advanced whenever the procedure is revised in accordance with paragraph 3-1-10.
(b) When completing the FAA Form 8260-19 for an abbreviated amendment, revise the amendment number to an alphanumeric format by adding an alphabetical suffix following the amendment number (e.g., Amdt 3B; Orig-A).
(4) City and State. Enter the associated city name and state name as derived from NASR. Use the official two-letter state abbreviations.
(5) Airport Elevation. Enter the official airport elevation as derived from NASR.
(6) Touchdown Zone Elevation (TDZE). Enter TDZE [as stated in the AIRNAV/NASR databases, rounded to the nearest foot] for the runway designated in the procedure title.
b. Terminal Routes. This information is used to design the planview of… › (6) Altitude column. Enter the altitude authorized for each leg.
(7) Superseded. Enter the identification of the superseded procedure.
(8) Original/Amendment. If the procedure is original, enter “None”; otherwise, enter “Orig” or amendment number as appropriate.
(9) Dated. If the procedure is original, leave blank; otherwise, enter the previous amendment date.
(10) Magnetic variation. Enter the magnetic variation value of the aerodrome of intended landing upon which the procedure design and documentation is based.
(11) Epoch Year. Enter the epoch year of the variation value as designated by Aeronautical Information Services. Enter this value in four digits; e.g., 2015.
(12) Facility. Enter RNAV.
(13) Effective Date. The actual effective date of the procedure will be entered by AFS-400, which must coordinate with the affected ATC facility to ensure adequate time to train controllers and incorporate the procedure into electronic data systems before implementation. Effective dates must be based on 28-day AIRAC cycle dates (or 56-day AIRAC cycle dates if en route chart changes are required) as published in FAA Order 8260.26, Establishing Submission Cutoff Dates for Civil Instrument Flight Procedures. When the actual effective date of the procedure is assigned, the AFS-400 representative will provide FAA Forms 8260-7B and 8260-19 to the service provider.
(14) Cancel. If applicable, indicate if the procedure is being canceled.
b. Terminal Routes. This information is used to design the planview of the RVFP chart. Document all legs of the procedure.
(1) Enter the name of the “FROM” and “TO” waypoints.
(2) Enter the RNAV leg type.
(3) Enter the waypoint type [Fly-Over (FO) or Fly-By (FB)].
(4) Enter the actual magnetic course to the hundredth of a degree. For RF leg types, document the radius, direction (clockwise or counter-clockwise), and the computer navigation fix (CNF) point used to define this arc segment followed by the arc distance in the following manner: (4.72 NM RADIUS CW (CFYUQ).
NOTE: The arc radius, direction, and CNF used to make up the RF leg will not be published on the chart. This information is provided for database use only. Only the RF track distance and altitude will be published on an RF turn.
(5) Enter the distance to the hundredth of a nautical mile.
(6) Altitude column. Enter the altitude authorized for each leg.
d. Notes. Enter notes pertaining to conditional use of the procedure,… › (6) When night operations are not allowed enter note as follows
(a) The altitude authorized for any terminal route must be no lower than the altitude authorized for succeeding segments. Where more than one segment joins at a common waypoint, a common altitude should be selected.
(b) When mandatory or maximum altitudes are an operational necessity, document the limitations in “Additional Flight Data.”
NOTE: When an RVFPs with concurrent RF and TF legs will be processed in one package, check the “ADD ROUTE” box to the right of the “TERMINAL ROUTES” header on the form to activate a function which will allow both RF and TF leg route versions to be noted on the form.
c. Profile. This information is used to design the profile view of the RVFP chart.
(1) Line 1. Enter the waypoint at which the profile view is to start in the following manner: “Profile starts at BOSTN.”
(2) Line 2 – FAC: Enter the Final Approach Course (FAC) established by the service provider computation to a hundredth of a degree.
(3) Line 3 – MIN ALT: Enter waypoints and minimum altitudes that are to be depicted on the profile view as follows: “HARLY 5000, AUSTN 3000.”
(4) Line 4 - MSA FROM: Enter the appropriate runway identifier followed by the minimum altitude as follows: “RW16R 7700.”
NOTE: When an RVFP with concurrent RF and TF legs will be processed in one package and different profile views are necessary, check the “ADD PROFILE” box to the right of the “PROFILE” header on the form to activate a function which will allow both RF and TF leg profile versions to be noted on the form.
d. Notes. Enter notes pertaining to conditional use of the procedure, notes restricting the use of the procedure, and other notes required for procedure clarification.
(1) Do not duplicate Attention All Users Page notes.
(2) Unless specified as “Chart planview note” or “Chart profile note,” all notes will be charted in the briefing strip, “Notes” section, of the procedure chart.
(3) When multiple notes are required, they may be combined under a single heading: e.g., “Chart planview notes,” “Chart profile notes,” or “Chart notes” followed by the actual notes.
(4) An AAUP chart note must be established for all RVFPs as follows: “CHART PLANVIEW NOTE: SEE ADDITIONAL REQUIREMENTS ON AAUP.”
(5) RVFPs built with RF legs shall include the chart note “RF Required.”
(6) When night operations are not allowed enter note as follows: “CHART NOTE: PROCEDURE NA AT NIGHT.”
3-1-5. Completion of FAA Form 8260-19. › h. Submitted by. Enter the name, signature, company name, and date…
(7) Limitation notes required on the use of special procedures. Where there are no private aspects to a special procedure, the following statement must be added to FAA Form 8260-7As restricting the use of that procedure; use: “CHART NOTE: USE OF THIS PROCEDURE REQUIRES SPECIFIC AUTHORIZATION BY FAA FLIGHT STANDARDS.”
e. Additional Flight Data. When additional information or data is essential to clarify the charting of RVFPs or when the procedures specialist wants information charted, but does not want it to appear on the chart as a note, the necessary information/data must be entered in the “Additional Flight Data” section. Preface specific items to be charted with the term “Chart.” Specific instructions to chart data must be held to a minimum.
(1) Vertical descent angle (VDA)/Threshold Crossing Height (TCH). Enter the descent angle for the appropriate waypoint in the final approach leg, and the appropriate TCH: KNSAS to RW15: 3.26/55.
(2) Where descent angles and/or TCH values are not coincident with published VGSI values, use “CHART PROFILE NOTE: VGSI AND DESCENT ANGLES NOT COINCIDENT (VGSI ANGLE {ANGLE}/TCH {FEET}).”
NOTE: Do not enter the VGSI angle/TCH numerical values; this information will be obtained by chart producers from the applicable source.
(3) When speed restrictions are needed at a waypoint enter the waypoint followed by type (MAN, MAX, MIN, REC) of restriction and speed in knots indicated airspeed (KIAS) as follows: “CHART PROFILE VIEW NOTE: JUBOL: MAX 230 KIAS.”
(4) Speed restrictions must be noted on the chart as follows: “CHART SPEED ICON IN PLANVIEW AT LUCIG: MAX 190 KIAS.” For an RF turn, specify the point where the restriction starts and the point at which the restriction is no longer required. Use “CHART PLANVIEW NOTE AT NILCI: DO NOT EXCEED 200 KIAS UNTIL HIVUD.”
(5) Enter charting instructions for maximum, mandatory or block altitudes; e.g., “Chart mandatory 5000 at DAVID,” or “Chart at or below 14000 and at or above 12000 at CATTS.” Maximum or mandatory altitudes should be avoided where possible.
f. Weather Minimums. Document the ceiling (in whole 100-ft increments above the airport elevation) and visibility (in whole statute miles) requirements as agreed with ATC as follows: 5000 - 6.
g. Changes and Reasons. The purpose of these entries is to keep charting agencies and coordinating offices advised of major procedural changes. The listing of changes must include all revisions (except clerical) and the reasons should contain sufficient details so that the cause for the procedural amendment will be clear to the reviewing offices.
h. Submitted by. Enter the name, signature, company name, and date authorized by the nongovernmental entity that designated the procedure.
(2) Briefing Points: › (b) By accepting an RVFP clearance, pilots accept the requirements and…
i. Flight Validated By. Enter the name, signature, and company name of the individual who conducted the flight validation and the date the flight validation was completed.
j. Developed by. Enter the name, signature, and company name of the individual responsible for developing the procedure, as well as the date developed.
k. Recommended by. Enter the name, signature, and company name of the individual who certifies that the flight procedure was developed in accordance with applicable policies, directives, standards, and criteria.
l. Approved by. Enter the name and signature of the FAA AFS-420 manager who certifies that the flight procedure was developed in accordance with applicable policies, directives, standards, and criteria and is approved for further processing.
3-1-6. RVFP Validation. An FAA-qualified Flight Simulation Training Device (FSTD) or aircraft must be used to validate the procedure design. Information on simulator capabilities is available from 14 CFR part 60 and from the FAA National Simulator Program. Flight validation of an RVFP in an aircraft is not required. However, if an aircraft is used for validation, the RVFP must be flown in visual meteorological conditions.
3-1-7. RVFP Training/Attention All Users Page. An AAUP must be created for all RVFPs.
a. An AAUP will be established and processed in tandem with an original RVFP. If RVFPs are amended, a revised AAUP will also be processed if necessary. These AAUPs will be included in the package sent to AFS-420 for processing. The Flight Technologies and Procedures Division will evaluate these AAUPs as part of the PRB review process.
b. In special circumstances, a new or amended AAUP may be established and processed without a related procedure amendment (i.e., AAUP being established where none existed originally, or AAUP contents being revised to meet current guidance). In these special instances, the AAUPs don’t require PRB approval and may be approved by the designated ASI.
c. Operators must train their pilots on RVFPs. This training must include RVFP phraseology, procedures, and requirements.
d. The AAUP will contain the following information:
(1) Procedure Name
(2) Briefing Points:
(a) Prescribed TERPS obstacle clearance is not provided for RVFPs.
(b) By accepting an RVFP clearance, pilots accept the requirements and responsibilities associated with a visual approach clearance (e.g., visibility minimums and cloud clearances). Pilots are responsible for remaining clear of terrain and obstacles while navigating on the RVFP track.
3-1-9. Issuance of RVFPs. › a. Safety Assurance Offices/POIs, apply paragraph 2-1-6.a(1) and…
(c) Pilots must fly the published RVFP route, unless otherwise cleared by ATC.
(d) Comply with charted mandatory altitudes and speeds.
(e) RVFPs can only be used if available in the navigation database. RVFPs must be retrieved by name from the FMS. Manual construction of RVFPs are not authorized.
(f) A statement requiring pilots to request the RVFP on initial contact with the controlling ATC facility or established communication agreed upon by operator and ATC for assigning RVFP.
(g) To receive clearance, advise ATC “Airport or Preceding Aircraft in Sight.”
(3) If expanded procedure guidance is desired, AAUPs may also contain:
(a) Weather Information (Specific Guidance).
(b) Glide Path Navigation (Specific Guidance).
(c) Additional Airport Information (Specific Guidance, if applicable).
3-1-8. Processing Documentation. All RVFP packages submitted (original and full/abbreviated amendments) to AFS-420 must contain the following:
a. Original and Full Amendments:
(1) AAUP (if applicable)
(2) AFS-420’s preliminary concept request acceptance documentation (for originals, as well as full amendments where the RVFP route/track has been changed).
(3) All documentation from paragraph 2-1-2.a. except 2-1-2.a(6), and 2-1-2.a(8).
b. Abbreviated amendments:
(1) AAUP (if applicable).
(2) A cover letter including a brief description of the changes.
(3) New FAA Form 8260-19.
(4) Appropriate environmental review process documentation in accordance with FAA Order 1050.1. Service providers need documentation signed by an Environmental Protection Specialist unless covered under a memorandum of agreement.
3-1-9. Issuance of RVFPs.
a. Safety Assurance Offices/POIs, apply paragraph 2-1-6.a(1) and 2-1-6.a(3).
3-1-10. Maintenance. › g. Cancellation. Apply paragraph 2-1-5.
b. Flight Technologies and Procedures Division, see paragraph 2-1-6.b.
3-1-10. Maintenance. Coordination for all amendments must be completed with AFS-420 in a timely manner.
a. Apply paragraphs 2-1-3.b(4) and 2-1-3.b(6).
b. RVFPs should be reviewed biennially and amended or canceled as needed. This review should include the viability of an IFP replacing the RVFP. The results of the review should be documented by the lead proponent as part of their recordkeeping.
c. Review for capability of an IFP replacing the RVFP.
d. Where circumstances require immediate NOTAM action, FDC T-NOTAM must be issued.
e. An amendment/abbreviated amendment must be submitted and processed within 224 days of issuance of a NOTAM (see FAA Order JO 7930.2). If the processing deadline can’t be met, a NOTAM extension must be submitted to FS.
f. Coordination must be completed with the affected ATC facility Airspace and Procedures Specialist for all new fix/waypoint names.
g. Cancellation. Apply paragraph 2-1-5.
3. Suggestion for Improvements. › b. Flight Technologies and Procedures Division at…
Appendix A. Administrative Information
1. Distribution. This order is distributed electronically only.
2. Acronyms, Abbreviations, Definitions, and Related Publications. Users of this order can refer to FAA Order 8260.3, United States Standard for Terminal Instrument Procedures, for an alphabetical listing of frequently used acronyms, abbreviations, definitions, and related publications.
a. Approved Procedure. An RVFP or special procedure developed and agreed upon by the lead operator, respective ATC facility and AFS-400.
b. Area Navigation Visual Flight Procedure. A procedure that capitalizes on an RNAV System technology to promote stabilized visual approaches to a designated runway.
c. FAA Service Provider. The FAA office that develops and maintains public and special procedures.
d. Lead Operator. An operator who acts as a proponent for the development, coordination, and implementation of a RVFP.
e. Operators. Individuals or companies (including airlines) that own/operate aircraft. These entities may develop (as a non-FAA service provider) or contract to have special procedures or an RVFP-developed for them.
f. Proponent. A company, organization, or person requesting a special procedure.
3. Suggestion for Improvements. Please forward all comments on deficiencies, clarifications, or improvements regarding the contents of this order to:The Directives Management Officer at 9- [email protected] or
b. Flight Technologies and Procedures Division at [email protected].
Your suggestions are welcome. Form 1320-19, Directives Feedback Information, is available in appendix C for your convenience.
Appendix B. Directives Feedback Information
Appendix B. 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: FAA Order 8260.60C, Special Procedures
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:
(attach separate sheet if necessary)
In a future change to this order, please include coverage on the following subject:
(briefly describe what you want to be 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