Radar Vectors
FAA Order Cancelled Issued Aug 9, 2004 AFS-400 17 pages Copy saved Nov 18, 2026

Order 8260.26D Establishing and Scheduling Standard Instrument Procedure Effective Dates

This document is cancelled. Cancelled by 8260.26E. Check the official source before relying on it.

Official source ↗ Open PDF

Distribution: A-W(ND/AS/FS/AT/AF)-3; ATA-110 (15 Cys); AVN-503 (75 Cys) Initiated By: AFS-420 AVN-100 (150 Cys); AMA-200 (80 Cys); A-X(FS/AT/AF/AS)-3; A-FFS-4 (ALL); ZVN-826; Special Military and Public Addressees

ORDER U.S. DEPARTMENT OF TRANSPORTATION

FEDERAL AVIATION ADMINISTRATION 8260.26D

FEDERAL AVIATION ADMINISTRATION 8260.26D

8/9/04

SUBJ: ESTABLISHING AND SCHEDULING CIVIL PUBLIC-USE STANDARD

INSTRUMENT PROCEDURE EFFECTIVE DATES 1. PURPOSE. This order provides policy for establishing public use standard instrument approach procedure (SIAP) and obstacle departure procedure (ODP) effective dates. It ensures that aeronautical 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 on the charts are correct and confirmed by flight inspection. It provides guidance regarding designation of associated controlled airspace for instrument procedures, including those based on area navigation (RNAV). It further ensures that the FAA will not assign an effective date for a procedure until all necessary action, including flight inspection, has been completed. 2. DISTRIBUTION.

SUBJ: ESTABLISHING AND SCHEDULING CIVIL PUBLIC-USE STANDARD

This order is distributed in Washington headquarters to the branch level in the Offices of Communications, Navigation, and Surveillance Systems and Airport Safety and Standards; to Flight Standards, Air Traffic, and Airway Facilities Services; to the National Flight Data Center (ATA-110); to the National Aeronautical Charting Office, Requirements and Technology Staff (AVN-503); to the National Flight Procedures Office (AVN-100) and to the Regulatory Standards Division (AMA-200) at the Mike Monroney Aeronautical Center; to the branch level in the regional Flight Standards, Air Traffic, Airway Facilities, and Airports Divisions; to all Flight Inspection Offices; International Flight Inspection Office; special mailing list ZVN-826; and Special Military and Public Addressees. 3. CANCELLATION. Order 8260.26C, Establishing and Scheduling Standard Instrument Procedure Effective Dates, dated March 12, 1999, is canceled. 4. EXPLANATION OF CHANGES. a. Added information to the functional area distribution codes and responsibilities to reflect organizational changes. b. Paragraph 1.

Reworded the purpose paragraph to quote the Administrator’s comments of November 20, 1972, in support of the original order. c. Paragraph 5. Expanded the background paragraph to provide a more inclusive history of and rationale for the order. d. Paragraph 7a(1). Added a reference to Order 8260.43, Flight Procedures Management Program (latest version).

e. Paragraph 7a(3). Added a note to clarify that original SIAPs may be effective on a Change Notice date.

f. Paragraph 7a(4). Changed the .26 message date to provide 38 days lead time vice 31 days to accommodate development of the FAA National Flight Database (NFD). Additionally, a note has been added to define en route charting changes.

g. Paragraph 7a(5). Changed this paragraph to specify textual obstacle departures.

h. Paragraph 7b. Expanded this paragraph to include the regional National Airspace System (NAS) Implementation (ANI) Divisions’ responsibilities.

i. Paragraph 7b(5). Added a reference to Order 7900.2, Reporting of Electronic Navigation Aids and Communications Facilities Data to the National Flight Data Center (latest version).

j. Paragraph 7f(5). Changed the flight inspection lead-time to 39 days vice 32 days to accommodate the revised .26 message lead-time.

k. Paragraph 7f(6). Revised the .26 message process to allow use of the AVN File Transfer Protocol (FTP) site. Additionally, the .26 message content has been expanded to include a statement that flight inspection has been completed.

l. Paragraph 7g(2). Added the requirement for NFDC to publish facility and fix changes for proposed procedures not later than the Thursday following receipt of a .26 message.

m. Paragraph 7g(3). Added the requirement for NFDC to promulgate proposed procedures and associated changes not later than the Friday following receipt of a .26 message

NOTE: Changes to paragraphs 7g(2) and 7g(3) are as agreed to by all at the January 14, 2004 Aeronautical Information Services Working Group (AISWG) meeting.

n. Paragraph 7g(4). Added the requirement for National Flight Data Center to publish facility-commissioning NOTAMs received from the regional OCC.

o. Paragraph 9. Added AFS-400 as the approval authority for deviations other than charting suspense dates. p. Extended the Instrument Procedures/Airspace Processing Schedules in appendix 1 to include Aeronautical Information Regulation and Control (AIRAC) charting dates and associated submission cutoff dates through the year 2010. 5. BACKGROUND. a. Prior to the original order, when a facility was not commissioned as scheduled, the SIAP could be published but required a Flight Data Center (FDC) Notice to Airmen (NOTAM) on the effective date specifying that the procedure not be authorized. In some cases, the NOTAM remained in effect for extended periods before the facility was eventually commissioned, or a determination was made that the facility would never be commissioned. Consequently, the

8/9/04 8260.26D

Par 5 Page 3

procedure, although published, was never authorized and subsequently had to be canceled. This directive was originally developed in response to National Transportation Safety Board recommendation A-71-19 to ensure that instrument approach procedure charts associated with new navigational aid (NAVAID(s)) commissioning will not be released to the public until it is known that the supporting NAVAID(s) perform satisfactorily and that all procedural data are correct and have been confirmed by flight inspection.

b. This order was also developed to provide procedure specialists, flight inspection personnel, charting agents, and aircrews a shorter response time to publish and use procedures after flight inspection. However, it must be remembered that the en route charting cycle is tied to airspace actions and is not as dynamic as the cycle for terminal data. En route data, including airways, NAVAIDs, airspace, fixes, graphic departure procedures (DPs), standard terminal arrivals (STARs), and digital aeronautical information must be effective on a preestablished 56-day international AIRAC cycle date. This data is also used to develop the Digital Aeronautical Chart Supplement (DACS) which is the source document for the National Airspace System (NAS). The DACS is used to develop instrument flight rule (IFR) en route charts and air traffic control radar video maps, to program Air Route Traffic Control Center (ARTCC) computers, and is the source for the development of avionics databases.

The lead-time for these products will not accommodate the 38-day suspense allowed for terminal procedures under this order. Adherence to this order will ensure improved service to the user and more complete and accurate approach charts. c. This order was expanded in 1999 to include instrument procedures that are not dependent on ground-based NAVAIDs. It was also expanded to include any procedure submitted as “Proposed” under Order 8260.19, Flight Procedures and Airspace (latest version), which did not impact en route charting. Submission schedules were revised to include cutoff dates for instrument flight procedure (IFP) types other than SIAPs. Additionally, guidance for controlled airspace designation was provided. 6. SCOPE. This order affects the FAA's regional operating divisions; the National Flight Data Center (NFDC), ATA-110; the National Flight Procedures Office (NFPO), AVN-100; the National Aeronautical Charting Office (NACO), AVN-500; and the Flight Inspection Operations Division, AVN-200.

It provides guidance relating to flight inspection of new/relocated NAVAIDs and new/amended instrument flight procedures, components of the NAS, and policy for processing and publishing instrument flight procedures. 7. PROCEDURES. a. General. (1) The development and/or modification of instrument procedures must be a closely coordinated process both within and outside of the affected FAA Regional Office. Order 8260.43A, Flight Procedures Management Program, as well as this order should be followed to ensure the coordinated, timely publication of proposed procedures. The Regional Airspace and Procedures Team (RAPT) and the National Airspace and Procedures Team (NAPT) are the established coordination mediums to assist in this effort. (2) The effective date for commissioning, decommissioning, or altering a component of the NAS having a direct bearing on the IFR capability of the facility or system, must coincide with one of the pre-established international AIRAC charting dates – see

appendix 1. Establishment of a procedure effective date must be coordinated through the RAPT between the NFDC and the NFPO. Commissioning notices and all information related to proposed commissioning dates of NAVAIDs must also be coordinated between NFDC and the NFPO. For advance notification requirements to NFDC, refer to Order 7900.2, Reporting of Electronic Navigation Aids and Communication Facilities Data. (3) Government produced procedure charts are published every 56 days as a set of terminal procedures publication (TPP) volumes, with a change notice (CN) printed on the intermediate 28th day (except for Alaska). Both publications contain civil and military SIAPs and DPs effective on the date of the publication; however, graphic ODPs, standard instrument departures (SIDs), and STARs may only be effective on TPP dates.

NOTE: An original SIAP may be assigned a CN effective date provided the procedure does not require en route charting changes, the airport information is published in the Airport/Facility Directory (AFD), and all currently published SIAPs for the airport are in the Volpe format. (4) Any SIAP may be submitted to NFDC as “proposed,” under Order 8260.19, and assigned an effective date via message (.26 message) provided the SIAP requires no en route charting changes. The .26 message must be received at NFDC and NACO not later than 38 days prior to the desired effective date – see appendix 1. The message must indicate that flight inspection has been completed.

NOTE: En route chart changes are those changes that require modification of an IFR En route Chart, graphic DP, STAR, or the DACS; e.g., adding a new fix, changing the location of a currently charted fix, adding DP or STAR charting, etc. Amending a Form 8260-2 that does not affect the aforementioned chart and digital products; e.g., adding a currently charted en route fix to an instrument approach procedure chart is not considered an en route chart change and is acceptable under this order. (5) A textual ODP (FAA Form 8160-15A) may also be assigned an effective date via a .26 message provided it has been submitted to be effective “concurrent” with a proposed SIAP (see Order 8260.19, chapter 8).

NOTE: Graphic ODPs, SIDs, and STARs are controlled by en route charting submission and effective dates and may not be assigned an effective date by a .26 message. (6) On those occasions where a .26 message must be used to assign an effective date for an approach that requires en route charting changes (new or re-located feeder fixes, airspace changes, new NAVAID, etc.), the flight inspection of the en route items must be completed and the applicable forms submitted to NFDC at least nine weeks prior to the effective date. A .26 message may be used to assign an instrument approach procedure effective date only after the en route charting items are in place and have been promulgated. These procedures must be effective on TPP dates only. b. Regional Airway Facilities (AF) and/or NAS Implementation (NI) Divisions must: (1) Establish a schedule of proposed commissioning dates through the RAPT for new and/or restoration dates for relocated or modified NAVAIDs in the NAS. Give full consideration to equipment delivery dates, site availability, procedure development time, installation schedules, seasonal weather factors, flight inspection scheduling, and contractor's

8/9/04 8260.26D

Par 7 Page 5

performance requirements. Proposed commissioning dates must be selected to coincide with an international AIRAC 56-day cycle and must be coordinated with NFDC and the Flight Inspection Central Operations Office (FICO). Additionally, concurrence must be obtained from the regional Air Traffic and Airports Divisions and the regional Flight Procedures Office (FPO). The regional AF Division concurrence must also be obtained if ANI has scheduled oversight. (2) Distribute proposed commissioning dates, including non-Federal navigation facilities (14 CFR Part 171) and Airport Improvement Program (AIP) projects, to the FICO and all interested offices within the affected region. Keep them advised of any anticipated delays that might be encountered in the installation of individual system components that will impact published procedures. (3) Direct the appropriate Operational Control Center (OCC) to contact the FICO to coordinate a flight inspection no later than 10 days prior to the requested date.

Note that the appropriate Flight Inspection Office (FIO) must complete a satisfactory flight inspection of the facility and the SIAP/textual departure at least 39 days prior to the estimated date of commissioning. After a successful flight inspection, notify the FPO and the regional Flight Standards and Air Traffic Divisions that the facility is ready for commissioning. (4) Issue a commissioning or facility restoral NOTAM at 0901Z on the effective date agreed upon. (5) Provide site survey data on new, relocated, or modified facilities to NFDC, the FPO, and the Flight Inspection Technical Support Branch, AVN-210, not later than 120 days prior to the anticipated completion of such activity. See Order 7900.2, Reporting of Electronic Navigation Aids and Communications Facilities Data, to the National Flight Data Center. c.

Regional Airports Divisions must: As requested, and on a case-by-case basis, provide regional Air Traffic and Airway Facilities Divisions and the FPO a copy of the airport drawing accompanying an Airport Improvement Plan (AIP) request, a drawing accompanying the Notification of Change of Airport Status for Non-AIP Proposals, or the latest Airport Master Record. These drawings will be used by charting agencies to determine runway length, width, and alignment, as well as taxiway configuration, terminal complex, control tower, and hangar layout. These data should be submitted prior to final flight inspection so that charting agencies might properly depict airport configuration. d. Regional Air Traffic Divisions must: (1) Take the necessary action to establish airways, routes, SIDs.and STARs to be effective on the proposed facility commissioning date.

(2) Complete the necessary rulemaking process to ensure that controlled airspace is available for the protection of planned procedures and airways, and will be effective on the planned facility commissioning date or proposed SIAP effective date (see Order 8260.19C, paragraph 402 and chapter 5, section 2). (3) Coordinate with the FPO through the RAPT process on all matters affecting proposed flight procedures and airspace action requests.

(4) A requirement for minor adjustment to existing controlled airspace to fully encompass an instrument procedure does not necessarily form the basis for withholding procedure publication. An approach procedure may be published prior to obtaining the optimum configuration of controlled airspace when the following conditions exist: (a) The centerline of all terminal routes is located within existing controlled airspace. (b) The procedure turn area, out to and including the specified completion distance, is contained within existing controlled airspace. (c) The final approach fix is contained within existing controlled airspace. e. Regional Flight Standards Divisions must: When there is an expressed interest regarding a proposed procedure, coordinate with the appropriate FPO through the RAPT process to ensure the actions of the concerned divisions will culminate in meeting the publication date agreed upon. f. Aviation Systems Standards (AVN) must: (1) Coordinate the development of a proposed procedure through the RAPT process based on the planned facility location.

Obtain sufficient airport data and details to enable complete procedure development and determination of controlled airspace requirements (see Order 8260.19). (2) Review the status of proposed procedures through the RAPT process to determine those procedures that can be published in the appropriate TPP or CN. The effective date of a procedure is the same date as the publication date. (3) Forward requests for airspace action through the FPO to the regional Air Traffic Division for appropriate action to ensure the airspace is designated on or before the proposed commissioning date of the facility. (4) Forward the proposed original, amended, or canceled SIAP, based on the new, relocated, or decommissioned facility, to NFDC for final administrative review and publication in the transmittal letter (TL). Submit proposed procedures to arrive in NFDC a minimum of ten weeks before the SIAP proposed effective date. (5) Complete a commissioning flight inspection of the facility and a flight inspection of proposed SIAPs at least 39 days before the planned commissioning/desired effective date.

Complete the flight inspection of items that require en route changes to allow all procedural information to be submitted to NFDC at least nine weeks before the proposed commissioning/ desired effective date. (6) Notify NFDC and NACO via the AVN File Transfer Protocol (FTP) site, or other appropriate means, of the effective date of the procedure. If a “canceled” procedure is concurrent with an “original” procedure, include the effective date for the canceled procedure in the message. Include in the notification any final changes to the procedure that are required as a result of a flight inspection. If changes are substantial, e.g., requiring re-submission of the

8/9/04 8260.26D

Par 7 Page 7

8260 series forms, coordinate with NFDC and the regional Air Traffic and Airway Facilities Divisions, etc. to establish a later effective date for the procedure. Effective date messages must be received in NFDC not later than 38 days before the desired procedure effective date. Format the message as follows: To: ATA-110 From: AVN-100 IN ACCORDANCE WITH FAA ORDER 8260.26 (latest version), THE FOLLOWING IS SUBMITTED: BLUE RIDGE, MARTINSVILLE, VA LOC RWY 30 ORIG. FLIGHT INSPECTION COMPLETE. PROCEDURE EFFECTIVE 19 FEB 04 WITH THE FOLLOWING CHANGES: AIRPORT ELEVATION 942. DISTANCE FAF TO MAP: 5.03 THLD 5.03. CIRCLING HAA 618 ALL CATS. DME MINIMUMS CIRCLING HAA 618 ALL CATS. SDF RWY 30 AMDT 2A CANCELED EFFECTIVE 19 FEB 04. NAME MANAGER, AVN-XXX (7) When changes are required, include only the one affected procedure in the .26 message including any procedure cancellations. If no changes are required, you may include multiple procedures in a single .26 message. (8) Publish the procedure(s) in the U.S. Government TPP or CN on the designated effective date as specified in the TL. g. The National Flight Data Center (NFDC), ATA-110, must: (1) Publish the proposed procedure in the TL at least seven weeks prior to the proposed effective date. (2) Publish the original/revised facility and fix data in the National Flight Data Digest (NFDD) as soon as possible, but not later than the Thursday following receipt of the .26 message. (3) When notified by the NFPO via the .26 message, publish the procedure, along with any revisions indicated in the message, in the TL on the Friday following receipt of the .26 message.

(4) Publish commissioning and/or restoral NOTAMs initiated by the regional OCC. 8. NON-FEDERAL FACILITIES. The procedure for commissioning facilities and establishing SIAPs should be identical for non-Federal facilities approved in accordance with 14 CFR Part 171, including those established under the AIP. The regional Airway Facilities Divisions have primary responsibility for monitoring the installation progress for non-Federal facilities, including facilities installed under AIP. The FPO, through the RAPT, must ensure that all

regional Airway Facilities Division requirements are satisfied prior to commissioning and establishing a SIAP on a non-Federal facility. 9. DEVIATIONS. Every attempt should be made to successfully coordinate the development of a complete and accurate instrument approach procedure prior to the selection of a publication date. Requests for deviation from the charting suspense dates must be minimal and made to the Manager, Aeronautical Information Division, ATA-100. The request must be made by the branch manager (or higher) level with convincing justification for the deviation. Other deviations to this order require approval of the Flight Technologies and Procedures Division, AFS-400, through the Flight Procedure Standards Branch, AFS-420. 10. SCHEDULE. Appendix 1 contains a listing of the submission and publication schedules for aeronautical products. When the specified "cutoff date" falls on a holiday, products must arrive at NFDC not later than the last workday preceding the holiday.

The scheduled dates have been adjusted to account for known holidays at the time the appendix was developed. ATA-100 is responsible for ensuring that temporary changes to the scheduled dates are promulgated to all concerned agencies. The Flight Procedure Standards Branch, AFS-420, must coordinate all permanent changes to the schedules with the NACO, the NFPO, and with the NFDC. 11. INFORMATION UPDATE. For your convenience, FAA Form 1320-19, Directive Feedback Information, is included at the end of this order to note any deficiencies found, clarifications needed, or suggested improvements regarding the contents of this order. When forwarding your comments to the originating office for consideration, please use the "Other Comments" block to provide a complete explanation of why the suggested change is necessary. James J. Ballough Director, Flight Standards Service

Page 1 (and 2)

APPENDIX 1. INSTRUMENT PROCEDURE/AIRSPACE

APPENDIX 1. INSTRUMENT PROCEDURE/AIRSPACE

PROCESSING SCHEDULES

2004 (LY) CUTOFF DATES 2005 CUTOFF DATES 2006 CUTOFF DATES 2007 CUTOFF DATES 2008 (LY) CUTOFF DATES 2009 CUTOFF DATES 2010 CUTOFF DATES

2004 (LY) CUTOFF DATES (1)

TEXTUAL DPs EN ROUTE

INST APPROACH PROC MTR SIAP TRANSMITTAL

EFFECTIVE CUTOFF FOR .26 MSG PREF RTS GRAPHIC DPs LETTER

EFFECTIVE CUTOFF FOR .26 MSG PREF RTS GRAPHIC DPs LETTER

DATE SUBMISSION (PROP IAP) ARTCC BND STARS NUMBER DATE

(2) (3) (4) (5) (6)

25 Dec 03 16 Oct 03 20 Nov 03 23 Oct 03 16 Oct 03 03-25 7 Nov 03

* 22 Jan 04 13 Nov 03 15 Dec 03 N/A N/A 04-01 5 Dec 03

19 Feb 04 11 Dec 03 12 Jan 04 18 Dec 03 11 Dec 03 04-03 2 Jan 04

19 Feb 04 11 Dec 03 12 Jan 04 18 Dec 03 11 Dec 03 04-03 2 Jan 04

* 18 Mar 04 8 Jan 04 9 Feb 04 N/A N/A 04-05 30 Jan 04

15 Apr 04 5 Feb 04 8 Mar 04 12 Feb 04 5 Feb 04 04-07 27 Feb 04

* 13 May 04 4 Mar 04 5 Apr 04 N/A N/A 04-09 26 Mar 04

10 Jun 04 1 Apr 04 3 May 04 8 Apr 04 1 Apr 04 04-11 23 Apr 04

* 8 Jul 04 29 Apr 04 28 May 04 N/A N/A 04-13 21 May 04

5 Aug 04 27 May 04 28 Jun 04 3 Jun 04 27 May 04 04-15 18 Jun 04

5 Aug 04 27 May 04 28 Jun 04 3 Jun 04 27 May 04 04-15 18 Jun 04

* 2 Sep 04 24 Jun 04 26 Jul 04 N/A N/A 04-17 16 Jul 04

30 Sep 04 22 Jul 04 23 Aug 04 29 Jul 04 22 Jul 04 04-19 13 Aug 04

* 28 Oct 04 19 Aug 04 20 Sep 04 N/A N/A 04-21 10 Sep 04

25 Nov 04 16 Sep 04 18 Oct 04 23 Sep 04 16 Sep 04 04-23 8 Oct 04

25 Nov 04 16 Sep 04 18 Oct 04 23 Sep 04 16 Sep 04 04-23 8 Oct 04

* 23 Dec 04 14 Oct 04 15 Nov 04 N/A N/A 04-25 5 Nov 04

*Denotes Change Notice (CN). NOTE: There is no CN for Alaskan procedures. NOTES: (1) Data must be received by NFDC not later than the specified “CUTOFF” date to ensure publication on the desired effective date. (2) 10 weeks prior to desired effective date - Order 8260.26. (3) 38 days prior to desired effective date - Order 8260.26. If IAP has NAVAID or fixes affecting en route charts, apply Note (4). (4) 9 weeks prior to desired effective date - Order 7031.20. Preferred routes - Order 7210.3. 90 days for ARTCC boundaries - Order 7900.1. (5) 10 weeks prior to desired effective date - Order 8260.46 (DP), Order 7100.9 (STAR), Order 8260.40 (FMS). (6) Even numbered Transmittal Letters are for NFDC internal use. All Orders – Latest Versions.

8260.26D 8/9/04 Appendix 1

2005 CUTOFF DATES (1)

2005 CUTOFF DATES (1)

TEXTUAL ODPs EN ROUTE

INST APPROACH PROC MTR SIAP TRANSMITTAL

EFFECTIVE CUTOFF FOR .26 MSG PREF RTS GRAPHIC DPs LETTER

DATE SUBMISSION (PROP IAP) ARTCC BND STARS NUMBER DATE

(2) (3) (4) (5) (6)

* 23 Dec 04 14 Oct 04 15 Nov 04 N/A N/A 04-25 5 Nov 04

20 Jan 05 10 Nov 04 13 Dec 04 17 Nov 04 10 Nov 04 05-01 3 Dec 04

20 Jan 05 10 Nov 04 13 Dec 04 17 Nov 04 10 Nov 04 05-01 3 Dec 04

* 17 Feb 05 9 Dec 04 10 Jan 05 N/A N/A 05-03 31 Dec 04

17 Mar 05 6 Jan 05 7 Feb 05 13 Jan 05 6 Jan 05 05-05 28 Jan 05

* 14 Apr 05 3 Feb 05 7 Mar 05 N/A N/A 05-07 25 Feb 05

12 May 05 3 Mar 05 4 Apr 05 10 Mar 05 3 Mar 05 05-09 25 Mar 05

* 9 Jun 05 31 Mar 05 2 May 05 N/A N/A 05-11 22 Apr 05

7 Jul 05 28 Apr 05 27 May 05 5 May 05 28 Apr 05 05-13 20 May 05

7 Jul 05 28 Apr 05 27 May 05 5 May 05 28 Apr 05 05-13 20 May 05

* 4 Aug 05 26 May 05 27 Jun 05 N/A N/A 05-15 17 Jun 05

1 Sep 05 23 Jun 05 25 Jul 05 30 Jun 05 23 Jun 05 05-17 15 Jul 05

* 29 Sep 05 21 Jul 05 22 Aug 05 N/A N/A 05-19 12 Aug 05

27 Oct 05 18 Aug 05 19 Sep 05 25 Aug 05 18 Aug 05 05-21 9 Sep 05

27 Oct 05 18 Aug 05 19 Sep 05 25 Aug 05 18 Aug 05 05-21 9 Sep 05

* 24 Nov 05 15 Sep 05 17 Oct 05 N/A N/A 05-23 7 Oct 05

22 Dec 05 13 Oct 05 14 Nov 05 20 Oct 05 13 Oct 05 05-25 4 Nov 05

* Denotes Change Notice (CN). NOTE: There is no CN for Alaskan procedures. NOTES: (1) Data must be received by NFDC not later than the specified “CUTOFF” date to ensure publication on the desired effective date. (2) 10 weeks prior to desired effective date - Order 8260.26. (3) 38 days prior to desired effective date - Order 8260.26. If IAP has NAVAID or fixes affecting en route charts, apply Note (4). (4) 9 weeks prior to desired effective date - Order 7031.20. Preferred routes - Order 7210.3. 90 days for ARTCC boundaries - Order 7900.1. (5) 10 weeks prior to desired effective date - Order 8260.46 (DP), Order 7100.9 (STAR), and Order 8260.40 (FMS). (6) Even numbered Transmittal Letters are for NFDC internal use. All Orders – Latest Versions.

2006 CUTOFF DATES (1)

2006 CUTOFF DATES (1)

TEXTUAL ODPs EN ROUTE

INST APPROACH PROC MTR SIAP TRANSMITTAL

EFFECTIVE CUTOFF FOR .26 MSG PREF RTS GRAPHIC DPs LETTER

DATE SUBMISSION (PROP IAP) ARTCC BND STARS NUMBER DATE

(2) (3) (4) (5) (6)

22 Dec 05 13 Oct 05 14 Nov 05 20 Oct 05 13 Oct 05 05-25 4 Nov 05

22 Dec 05 13 Oct 05 14 Nov 05 20 Oct 05 13 Oct 05 05-25 4 Nov 05

* 19 Jan 06 10 Nov 05 12 Dec 05 N/A N/A 06-01 2 Dec 05

16 Feb 06 8 Dec 05 9 Jan 06 15 Dec 05 8 Dec 05 06-03 30 Dec 05

* 16 Mar 06 5 Jan 06 6 Feb 06 N/A N/A 06-05 27 Jan 06

13 Apr 06 2 Feb 06 6 Mar 06 9 Feb 06 2 Feb 06 06-07 24 Feb 06

* 11 May 06 2 Mar 06 3 Apr 06 N/A N/A 06-09 24 Mar 06

8 Jun 06 30 Mar 06 1 May 06 6 Apr 06 30 Mar 06 06-11 21 Apr 06

8 Jun 06 30 Mar 06 1 May 06 6 Apr 06 30 Mar 06 06-11 21 Apr 06

* 6 Jul 06 27 Apr 06 26 May 06 N/A N/A 06-13 19 May 06

3 Aug 06 25 May 06 26 Jun 06 1 Jun 06 25 May 06 06-15 16 Jun 06

* 31 Aug 06 22 Jun 06 24 Jul 06 N/A N/A 06-17 14 Jul 06

28 Sep 06 20 Jul 06 21 Aug 06 27 Jul 06 20 Jul 06 06-19 11 Aug 06

28 Sep 06 20 Jul 06 21 Aug 06 27 Jul 06 20 Jul 06 06-19 11 Aug 06

* 26 Oct 06 17 Aug 06 18 Sep 06 N/A N/A 06-21 8 Sep 06

23 Nov 06 14 Sep 06 16 Oct 06 21 Sep 06 14 Sep 06 06-23 6 Oct 06

* 21 Dec 06 12 Oct 06 13 Nov 06 N/A N/A 06-25 3 Nov 06

* Denotes Change Notice (CN). NOTE: There is no CN for Alaskan procedures. NOTES: (1) Data must be received by NFDC not later than the specified “CUTOFF” date to ensure publication on the desired effective date. (2) 10 weeks prior to desired effective date - Order 8260.26. (3) 38 days prior to desired effective date - Order 8260.26. If IAP has NAVAID or fixes affecting en route charts, apply Note (4). (4) 9 weeks prior to desired effective date - Order 7031.20. Preferred routes - Order 7210.3. 90 days for ARTCC boundaries - Order 7900.1. (5) 10 weeks prior to desired effective date - Order 8260.46 (DP), Order 7100.9 (STAR), and Order 8260.40 (FMS). (6) Even numbered Transmittal Letters are for NFDC internal use. All Orders – Latest Versions.

23 Nov 06 14 Sep 06 16 Oct 06 21 Sep 06 14 Sep 06 06-23 6 Oct 06

8260.26D 8/9/04 Appendix 1

2007 CUTOFF DATES (1)

TEXTUAL ODPs EN ROUTE

INST APPROACH PROC MTR SIAP TRANSMITTAL

EFFECTIVE CUTOFF FOR .26 MSG PREF RTS GRAPHIC DPs LETTER

DATE SUBMISSION (PROP IAP) ARTCC BND STARS NUMBER DATE

(2) (3) (4) (5) (6)

* 21 Dec 06 12 Oct 06 13 Nov 06 N/A N/A 06-25 3 Nov 06

18 Jan 07 9 Nov 06 11 Dec 06 16 Nov 06 9 Nov 06 07-01 1 Dec 06

18 Jan 07 9 Nov 06 11 Dec 06 16 Nov 06 9 Nov 06 07-01 1 Dec 06

* 15 Feb 07 7 Dec 06 8 Jan 07 N/A N/A 07-03 29 Dec 06

15 Mar 07 4 Jan 07 5 Feb 07 11 Jan 07 4 Jan 07 07-05 26 Jan 07

* 12 Apr 07 1 Feb 07 5 Mar 07 N/A N/A 07-07 23 Feb 07

10 May 07 1 Mar 07 2 Apr 07 8 Mar 07 1 Mar 07 07-09 23 Mar 07

10 May 07 1 Mar 07 2 Apr 07 8 Mar 07 1 Mar 07 07-09 23 Mar 07

* 7 Jun 07 29 Mar 07 30 Apr 07 N/A N/A 07-11 20 Apr 07

5 July 07 26 Apr 07 25 May 07 3 May 07 26 Apr 07 07-13 18 May 07

* 2 Aug 07 24 May 07 25 Jun 07 N/A N/A 07-15 15 Jun 07

30 Aug 07 21 Jun 07 23 Jul 07 28 Jun 07 21 Jun 07 07-17 13 Jul 07

* 27 Sep 07 19 Jul 07 20 Aug 07 N/A N/A 07-19 10 Aug 07

25 Oct 07 16 Aug 07 17 Sep 07 23 Aug 07 16 Aug 07 07-21 7 Sep 07

25 Oct 07 16 Aug 07 17 Sep 07 23 Aug 07 16 Aug 07 07-21 7 Sep 07

* 22 Nov 07 13 Sep 07 15 Oct 07 N/A N/A 07-23 5 Oct 07

20 Dec 07 11 Oct 07 9 Nov 07 18 Oct 07 11 Oct 07 07-25 2 Nov 07

* Denotes Changes Notice (CN). NOTE: There is no CN for Alaskan procedures. NOTES: (1) Data must be received by NFDC not later than the specified “CUTOFF” date to ensure publication on the desired effective date. (2) 10 weeks prior to desired effective date - Order 8260.26. (3) 38 days prior to desired effective date - Order 8260.26. If IAP has NAVAID or fixes affecting en route charts, apply Note (4). (4) 9 weeks prior to desired effective date - Order 7031.20. Preferred routes - Order 7210.3. 90 days for ARTCC boundaries - Order 7900.1. (5) 10 weeks prior to desired effective date - Order 8260.46 (DP), Order 7100.9 (STAR), and Order 8260.40 (FMS). (6) Even numbered Transmittal Letters are for NFDC internal use. All Orders – Latest Versions.

2008 (LY) CUTOFF DATES (1)

2008 (LY) CUTOFF DATES (1)

TEXTUAL ODPs EN ROUTE

INST APPROACH PROC MTR SIAP TRANSMITTAL

EFFECTIVE CUTOFF FOR .26 MSG PREF RTS GRAPHIC DPs LETTER

DATE SUBMISSION (PROP IAP) ARTCC BND STARS NUMBER DATE

(2) (3) (4) (5) (6)

20 Dec 07 11 Oct 07 9 Nov 07 18 Oct 07 11 Oct 07 07-25 2 Nov 07

20 Dec 07 11 Oct 07 9 Nov 07 18 Oct 07 11 Oct 07 07-25 2 Nov 07

* 17 Jan 08 8 Nov 07 10 Dec 07 N/A N/A 08-01 30 Nov 07

14 Feb 08 6 Dec 07 7 Jan 08 13 Dec 07 6 Dec 07 08-03 28 Dec 07

* 13 Mar 08 3 Jan 08 4 Feb 08 N/A N/A 08-05 25 Jan 08

10 Apr 08 31 Jan 08 3 Mar 08 7 Feb 08 31 Jan 08 08-07 22 Feb 08

* 8 May 08 28 Feb 08 31 Mar 08 N/A N/A 08-09 21 Mar 08

5 Jun 08 27 Mar 08 28 Apr 08 3 Apr 08 27 Mar 08 08-11 18 Apr 08

5 Jun 08 27 Mar 08 28 Apr 08 3 Apr 08 27 Mar 08 08-11 18 Apr 08

* 3 Jul 08 24 Apr 08 23 May 08 N/A N/A 08-13 16 May 08

31 Jul 08 22 May 08 23 Jun 08 29 May 08 22 May 08 08-15 13 Jun 08

* 28 Aug 08 19 Jun 08 21 Jul 08 N/A N/A 08-07 11 Jul 08

25 Sep 08 17 Jul 08 18 Aug 08 24 Jul 08 17 Jul 08 08-09 8 Aug 08

25 Sep 08 17 Jul 08 18 Aug 08 24 Jul 08 17 Jul 08 08-09 8 Aug 08

* 23 Oct 08 14 Aug 08 15 Sep 08 N/A N/A 08-21 5 Sep 08

20 Nov 08 11 Sep 08 10 Oct 08 18 Sep 08 11 Sep 08 08-23 3 Oct 08

* 18 Dec 08 9 Oct 08 10 Nov 08 N/A N/A 08-25 31 Oct 08

* Denotes Changes Notice (CN). NOTE: There is no CN for Alaskan procedures. NOTES: (1) Data must be received by NFDC not later than the specified “CUTOFF” date to ensure publication on the desired effective date. (2) 10 weeks prior to desired effective date - Order 8260.26. (3) 38 days prior to desired effective date - Order 8260.26. If IAP has NAVAID or fixes affecting en route charts, apply Note (4). (4) 9 weeks prior to desired effective date - Order 7031.20. Preferred routes - Order 7210.3. 90 days for ARTCC boundaries - Order 7900.1. (5) 10 weeks prior to desired effective date - Order 8260.46 (DP), Order 7100.9 (STAR), and Order 8260.40 (FMS). (6) Even numbered Transmittal Letters are for NFDC internal use. All Orders – Latest Versions.

20 Nov 08 11 Sep 08 10 Oct 08 18 Sep 08 11 Sep 08 08-23 3 Oct 08

8260.26D 8/9/04 Appendix 1

2009 CUTOFF DATES (1)

TEXTUAL ODPs EN ROUTE

INST APPROACH PROC MTR SIAP TRANSMITTAL

EFFECTIVE CUTOFF FOR .26 MSG PREF RTS GRAPHIC DPs LETTER

DATE SUBMISSION (PROP IAP) ARTCC BND STARS NUMBER DATE

(2) (3) (4) (5) (6)

* 18 Dec 08 9 Oct 08 10 Nov 08 N/A N/A 08-25 31 Oct 08

15 Jan 09 6 Nov 08 8 Dec 08 13 Nov 08 6 Nov 08 09-01 28 Nov 08

15 Jan 09 6 Nov 08 8 Dec 08 13 Nov 08 6 Nov 08 09-01 28 Nov 08

* 12 Feb 09 4 Dec 08 5 Jan 09 N/A N/A 09-03 26 Dec 08

12 Mar 09 31 Dec 08 2 Feb 09 8 Jan 09 31 Dec 09 09-05 23 Jan 09

* 9 Apr 09 29 Jan 09 2 Mar 09 N/A N/A 09-07 20 Feb 09

7 May 09 26 Feb 09 30 Mar 09 5 Mar 09 26 Feb 09 09-09 20 Mar 09

7 May 09 26 Feb 09 30 Mar 09 5 Mar 09 26 Feb 09 09-09 20 Mar 09

* 4 Jun 09 26 Mar 09 27 Apr 09 N/A N/A 09-11 17 Apr 09

2 Jul 09 23 Apr 09 22 May 09 30 Apr 09 23 Apr 09 09-13 15 May 09

* 30 Jul 09 21 May 09 22 Jun 09 N/A N/A 09-15 12 Jun 09

27 Aug 09 18 Jun 09 20 Jul 09 25 Jun 09 18 Jun 09 09-17 10 Jul 09

* 24 Sep 09 16 Jul 09 17 Aug 09 N/A N/A 09-19 7 Aug 09

22 Oct 09 13 Aug 09 14 Sep 09 20 Aug 09 13 Aug 09 09-21 4 Sep 09

22 Oct 09 13 Aug 09 14 Sep 09 20 Aug 09 13 Aug 09 09-21 4 Sep 09

* 19 Nov 09 10 Sep 09 9 Oct 09 N/A N/A 09-23 2 Oct 09

17 Dec 09 8 Oct 09 9 Nov 09 22 Oct 09 15 Oct 09 09-25 30 Oct 09

* Denotes Changes Notice (CN). NOTE: There is no CN for Alaskan procedures. NOTES: (1) Data must be received by NFDC not later than the specified “CUTOFF” date to ensure publication on the desired effective date. (2) 10 weeks prior to desired effective date - Order 8260.26. (3) 38 days prior to desired effective date - Order 8260.26. If IAP has NAVAID or fixes affecting en route charts, apply Note (4). (4) 9 weeks prior to desired effective date - Order 7031.20. Preferred routes - Order 7210.3. 90 days for ARTCC boundaries - Order 7900.1. (5) 10 weeks prior to desired effective date - Order 8260.46 (DP), Order 7100.9 (STAR), and Order 8260.40 (FMS). (6) Even numbered Transmittal Letters are for NFDC internal use. All Orders – Latest Versions.

17 Dec 09 8 Oct 09 9 Nov 09 22 Oct 09 15 Oct 09 09-25 30 Oct 09

Page 9 (and 10)

2010 CUTOFF DATES (1)

TEXTUAL ODPs EN ROUTE

INST APPROACH PROC MTR SIAP TRANSMITTAL

EFFECTIVE CUTOFF FOR .26 MSG PREF RTS GRAPHIC DPs LETTER

DATE SUBMISSION (PROP IAP) ARTCC BND STARS NUMBER DATE

(2) (3) (4) (5) (6)

17 Dec 09 8 Oct 09 9 Nov 09 22 Oct 09 15 Oct 09 09-25 30 Oct 09

* 14 Jan 10 5 Nov 09 7 Dec 09 N/A N/A 10-01 27 Nov 09

11 Feb 10 3 Dec 09 4 Jan 10 10 Dec 09 3 Dec 09 10-03 24 Dec 09

11 Feb 10 3 Dec 09 4 Jan 10 10 Dec 09 3 Dec 09 10-03 24 Dec 09

* 11 Mar 10 31 Dec 09 1 Feb 10 N/A N/A 10-05 22 Jan 10

8 Apr 10 28 Jan 10 1 Mar 10 4 Feb 10 28 Jan 10 10-07 19 Feb 10

* 6 May 10 25 Feb 10 29 Mar 10 N/A N/A 10-09 19 Mar 10

3 Jun 10 25 Mar 10 26 Apr 10 1 Apr 10 25 Mar 10 10-11 16 Apr 10

3 Jun 10 25 Mar 10 26 Apr 10 1 Apr 10 25 Mar 10 10-11 16 Apr 10

* 1 Jul 10 22 Apr 10 24 May 10 N/A N/A 10-13 14 May 10

29 Jul 10 20 May 10 21 Jun 10 27 May 10 20 May 10 10-15 11 Jun 10

* 26 Aug 10 17 Jun 10 19 Jul 10 N/A N/A 10-17 9 Jul 10

23 Sep 10 15 Jul 10 16 Aug 10 22 Jul 10 15 Jul 10 10-19 6 Aug 10

* 21 Oct 10 12 Aug 10 13 Sep 10 N/A N/A 10-21 3 Sep 10

18 Nov 10 9 Sep 10 8 Oct 10 16 Sep 10 9 Sep 10 10-23 1 Oct 10

18 Nov 10 9 Sep 10 8 Oct 10 16 Sep 10 9 Sep 10 10-23 1 Oct 10

* 16 Dec 10 7 Oct 10 8 Nov 10 N/A N/A 10-25 29 Oct 10

* Denotes Changes Notice (CN). NOTE: There is no CN for Alaskan procedures. NOTES: (1) Data must be received by NFDC not later than the specified “CUTOFF” date to ensure publication on the desired effective date. (2) 10 weeks prior to desired effective date - Order 8260.26. (3) 38 days prior to desired effective date - Order 8260.26. If IAP has NAVAID or fixes affecting en route charts, apply Note (4). (4) 9 weeks prior to desired effective date - Order 7031.20. Preferred routes - Order 7210.3. 90 days for ARTCC boundaries - Order 7900.1. (5) 10 weeks prior to desired effective date - Order 8260.46 (DP), Order 7100.9 (STAR), and Order 8260.40 (FMS). (6) Even numbered Transmittal Letters are for NFDC internal use. All Orders – Latest Versions.

FAA Form 1320-19 (8-89)

Directive 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 8260.26D, Establishing and Scheduling Civil Public-Use Standard Instrument Procedure

Effective Dates To: DOT/FAA Flight Procedure Standards Branch, AFS-420 P.O. Box 25082 Oklahoma City, OK 73125 (Please check 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 directive, 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: … FTS Telephone Number: Routing Symbol: …