Skip to Content

Proposed Rule

Proposed Establishment of Area Navigation Routes (RNAV), FL

Document Details

Information about this document as published in the Federal Register.

Published Document

This document has been published in the Federal Register. Use the PDF linked in the document sidebar for the official electronic format.

Start Preamble Start Printed Page 6376

AGENCY:

Federal Aviation Administration (FAA), DOT.

ACTION:

Notice of proposed rulemaking (NPRM).

SUMMARY:

This action proposes to establish eight area navigation (RNAV) routes in Florida in support of the High Altitude Redesign (HAR) project. The FAA is proposing this action to enhance safety and to improve the efficient use of the navigable airspace.

DATES:

Comments must be received on or before March 24, 2005.

ADDRESSES:

Send comments on this proposal to the Docket Management System, U.S. Department of Transportation, Room Plaza 401, 400 Seventh Street, SW., Washington, DC 20590-0001. You must identify FAA Docket No. FAA-2004-19667 and Airspace Docket No. 04-ASO-13, at the beginning of your comments. You may also submit comments on the Internet at http://dms.dot.gov.

Start Further Info

FOR FURTHER INFORMATION CONTACT:

Paul Gallant, Airspace and Rules, Office of System Operations and Safety, Federal Aviation Administration, 800 Independence Avenue, SW., Washington, DC 20591; telephone: (202) 267-8783.

End Further Info End Preamble Start Supplemental Information

SUPPLEMENTARY INFORMATION:

Comments Invited

Interested parties are invited to participate in this proposed rulemaking by submitting such written data, views, or arguments, as they may desire. Comments that provide the factual basis supporting the views and suggestions presented are particularly helpful in developing reasoned regulatory decisions on the proposal. Comments are specifically invited on the overall regulatory, aeronautical, economic, environmental, and energy-related aspects of the proposal.

Communications should identify both docket numbers (FAA Docket No. FAA-2004-19667 and Airspace Docket No. 04-ASO-13) and be submitted in triplicate to the Docket Management System (see ADDRESSES section for address and phone number). You may also submit comments through the Internet at http://dms.dot.gov.

Commenters wishing the FAA to acknowledge receipt of their comments on this action must submit with those comments a self-addressed, stamped postcard on which the following statement is made: “Comments to FAA Docket No. FAA-2004-19667 and Airspace Docket No. 04-ASO-13.” The postcard will be date/time stamped and returned to the commenter.

All communications received on or before the specified closing date for comments will be considered before taking action on the proposed rule. The proposal contained in this action may be changed in light of comments received. All comments submitted will be available for examination in the public docket both before and after the closing date for comments. A report summarizing each substantive public contact with FAA personnel concerned with this rulemaking will be filed in the docket.

Availability of NPRMs

An electronic copy of this document may be downloaded through the Internet at http://dms.dot.gov. Recently published rulemaking documents can also be accessed through the FAA's Web page at http://www.faa.gov, or the Federal Register's Web page at http://www.gpoaccess.gov/​fr/​index.html.

You may review the public docket containing the proposal, any comments received, and any final disposition in person in the Dockets Office (see ADDRESSES section for address and phone number) between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays. An informal docket may also be examined during normal business hours at the office of the Regional Air Traffic Division, Federal Aviation Administration, 1701 Columbia Avenue College Park, GA 30337.

Persons interested in being placed on a mailing list for future NPRMs should contact the FAA's Office of Rulemaking, (202) 267-9677, for a copy of Advisory Circular No. 11-2A, Notice of Proposed Rulemaking Distribution System, which describes the application procedure.

Background

As part of the on-going National Airspace Redesign, the FAA has implemented the HAR program. This specific effort focuses on developing and implementing improvements in navigation structure and operating methods to allow more flexible and efficient en route operations in the high altitude airspace environment. In support of this program, the FAA is establishing RNAV routes to provide greater freedom to properly equipped users and to achieve the economic benefits of flying user selected non-restrictive routings.

The new RNAV routes will be identified by the letter prefix “Q,” followed by a number consisting of from one to three digits. The International Civil Aviation Organization (ICAO) has allocated the “Q” prefix, along with the number set 1 through 499, for use by the U.S. for designating domestic RNAV routes.

Related Rulemaking

On April 8, 2003, the FAA published the Designation of Class A, B, C, D, and E Airspace Areas; Air Traffic Service Routes, and Reporting Points rule in the Federal Register (68 FR 16943). This rule adopted certain amendments proposed in Notice No. 02-20, Area Navigation and Miscellaneous Amendments. The rule revised and adopted several definitions in FAA regulations, including Air Traffic Service Routes, to be in concert with ICAO definitions; and reorganized the structure of FAA regulations concerning the designation of Class A, B, C, D, and E airspace areas, airways, routes, and reporting points. The purpose of the rule was to facilitate the establishment of RNAV routes in the National Airspace System (NAS) for use by aircraft with advanced navigation system capabilities.

On May 9, 2003, the FAA published the Establishment of RNAV final rule in the Federal Register (68 FR 24864). This rule, which supports Phase I of the Start Printed Page 6377HAR, established 11 new RNAV routes along high-density air traffic tracks in the western and north central U.S. The eight new RNAV routes being proposed in this notice would further support the HAR effort by extending the benefits of RNAV routing to the Florida area.

The Proposal

The FAA is proposing an amendment to Title 14 Code of Federal Regulations (14 CFR) part 71 (part 71) to establish eight RNAV routes in Florida within the airspace assigned to the Jacksonville Air Route Traffic Control Center (ARTCC). These routes are proposed as part of the HAR program to enhance safety, and to facilitate the more flexible and efficient use of the navigable airspace for en route instrument flight rules (IFR) operations within the Jacksonville ARTCC area of responsibility.

The FAA has determined that this proposed regulation only involves an established body of technical regulations for which frequent and routine amendments are necessary to keep them operationally current. Therefore, this proposed regulation: (1) Is not a “significant regulatory action” under Executive Order 12866; (2) is not a “significant rule” under Department of Transportation (DOT) Regulatory Policies and Procedures (44 FR 11034; February 26, 1979); and (3) does not warrant preparation of a regulatory evaluation as the anticipated impact is so minimal. Since this is a routine matter that will only affect air traffic procedures and air navigation, it is certified that this proposed rule, when promulgated, will not have a significant economic impact on a substantial number of small entities under the criteria of the Regulatory Flexibility Act.

Start List of Subjects

List of Subjects in 14 CFR Part 71

End List of Subjects

The Proposed Amendment

In consideration of the foregoing, the Federal Aviation Administration proposes to amend 14 CFR part 71 as follows:

Start Part

PART 71—DESIGNATION OF CLASS A, B, C, D, AND E AIRSPACE AREAS; AIR TRAFFIC SERVICE ROUTES; AND REPORTING POINTS

1. The authority citation for part 71 continues to read as follows:

Start Authority

Authority: 49 U.S.C. 106(g), 40103, 40113, 40120; E.O. 10854, 24 FR 9565, 3 CFR, 1959-1963 Comp., p. 389.

End Authority
[Amended]

2. The incorporation by reference in 14 CFR 71.1 of FAA Order 7400.9M, Airspace Designations and Reporting Points, dated August 30, 2004, and effective September 16, 2004, is amended as follows:

Paragraph 2006—Area Navigation Routes

* * * * *
Q-104 DEFUN to CYY [New]
DEFUNWP(Lat. 30°48′51″ N., long. 86°07′53″ W.)
HEVVNWP(Lat. 29°49′19″ N., long. 83°53′43″ W.)
PLYERWP(Lat. 28°56′51″ N., long. 83°20′09″ W.)
MARVEWP(Lat. 28°35′16″ N., long. 83°06′31″ W.)
CYYVOR/DME(Lat. 26°09′12″ N., long. 81°46′41″ W.)
Q-106 SMELZ to GADAY [New]
SMELZWP(Lat. 28°04′59″ N., long. 82°06′34″ W.)
BULZIWP(Lat. 29°59′14″ N., long. 83°44′17″ W.)
GADAYWP(Lat. 31°02′28″ N., long. 86°08′02″ W.)
Q-108 GADAY to CLAWZ [New]
GADAYWP(Lat. 31°02′28″ N., long. 86°08′02″ W.)
CLAWZWP(Lat. 30°38′29″ N., long. 83°02′19″ W.)
Q-110 KPASA to FEONA [New]
KPASAWP(Lat. 28°10′34″ N., long. 81°54′27″ W.)
BRUTSWP(Lat. 29°30′58″ N., long. 82°58′57″ W.)
GULFRWP(Lat. 30°12′23″ N., long. 83°33′08″ W.)
FEONAWP(Lat. 31°36′11″ N., long. 84°43′51″ W.)
Q-112 DEFUN to INPIN [New]
DEFUNWP(Lat. 30°48′51″ N., long. 86°07′53″ W.)
HEVVNWP(Lat. 29°49′19″ N., long. 83°53′43″ W.)
INPINWP(Lat. 28°33′13″ N., long. 81°48′27″ W.)
Q-114 DEFUN to FORTL [New]
DEFUNWP(Lat. 30°48′51″ N., long. 86°07′53″ W.)
HEVVNWP(Lat. 29°49′19″ N., long. 83°53′43″ W.)
TEPEEWP(Lat. 28°00′01″ N., long. 82°21′59″ W.)
JOCKSWP(Lat. 27°00′33″ N., long. 81°51′13″ W.)
FORTLWP(Lat. 26°18′34″ N., long. 81°21′08″ W.)
Q-116 KPASA to CEEYA [New]
KPASAWP(Lat. 28°10′34″ N., long. 81°54′27″ W.)
BRUTSWP(Lat. 29°30′58″ N., long. 82°58′57″ W.)
GULFRWP(Lat. 30°12′23″ N., long. 83°33′08″ W.)
CEEYAWP(Lat. 31°31′32″ N., long. 84°05′32″ W.)
Q-118 KPASA to LENIE [New]
KPASAWP(Lat. 28°10′34″ N., long. 81°54′27″ W.)
BRUTSWP(Lat. 29°30′58″ N., long. 82°58′57″ W.)
LENIEWP(Lat. 31°33′58″ N., long. 83°50′50″ W.)
Start Printed Page 6378
* * * * *
Start Signature

Issued in Washington, DC, on January 31, 2005.

Edie Parish,

Acting Manager, Airspace and Rules.

End Signature End Part End Supplemental Information

[FR Doc. 05-2221 Filed 2-4-05; 8:45 am]

BILLING CODE 4910-13-P