Establishment of Helicopter Area Navigation (RNAV) Routes; Northeast United States
Transportation Department; Federal Aviation Administration · 2011
Read Establishment of Helicopter Area Navigation (RNAV) Routes; Northeast United States by Transportation Department; Federal Aviation Administration (2011) in the Tower of Babel, a free online library of public-domain works preserved in clean, searchable text. No sign-up. The full text is served as a plain-text file at a predictable URL, where text is present: https://antarctic-labs.com/tower-of-babel/uslaw-fr-2011-15885.txt.
Description
Rule published in the Federal Register on 2011-06-27 by Transportation Department; Federal Aviation Administration. Text from federalregister.gov (official edition: govinfo). [Pages 37261-37263] From the Federal Register Online via the Government Publishing Office [www.gpo.gov] [FR Doc No: 2011-15885] ----------------------------------------------------------------------- DEPARTMENT OF TRANSPORTATION Federal Aviation Administration 14 CFR Part 71 [Docket No. FAA-2011-0078; Airspace Docket No. 10-AEA-20] Establishment of Helicopter Area Navigation (RNAV) Routes; Northeast United States AGENCY: Federal Aviation Administration (FAA), DOT. ACTION:.
Catalog record
| CREATOR | Transportation Department; Federal Aviation Administration |
|---|---|
| YEAR | 2011 |
| COLLECTION | LAW |
| FORMAT | TXT |
| FILE SIZE | 14 KB |
| VERSION | 1.0 |
| LICENSE | Public Domain |
| RIGHTS | PUBLIC DOMAIN |
| SOURCE | Federal Register |
Browse the full library · About the Tower of Babel
Full text
The opening of the work, from the library's hosted text:
Establishment of Helicopter Area Navigation (RNAV) Routes; Northeast United States Citation: us:fr:2011-15885 Creator: Transportation Department; Federal Aviation Administration Year: 2011 Source-URL: https://www.federalregister.gov/documents/2011/06/27/2011-15885/establishment-of-helicopter-area-navigation-rnav-routes-northeast-united-states Context: Rule published in the Federal Register on 2011-06-27 by Transportation Department; Federal Aviation Administration. Text from federalregister.gov (official edition: govinfo). [Pages 37261-37263] From the Federal Register Online via the Government Publishing Office [www.gpo.gov] [FR Doc No: 2011-15885] ----------------------------------------------------------------------- DEPARTMENT OF TRANSPORTATION Federal Aviation Administration 14 CFR Part 71 [Docket No. FAA-2011-0078; Airspace Docket No. 10-AEA-20] Establishment of Helicopter Area Navigation (RNAV) Routes; Northeast United States AGENCY: Federal Aviation Administration (FAA), DOT. ACTION: Final rule. ----------------------------------------------------------------------- SUMMARY: This action establishes helicopter RNAV routes as part of the U.S. air traffic service route (ATS) structure and designates two helicopter RNAV routes (TK-routes) in the northeast corridor between the Washington, DC, and New York City metropolitan areas. The TK-routes are for use by helicopters having IFR-approved Global Positioning System (GPS)/Global Navigation Satellite System (GNSS) equipment. The FAA is taking this action to enhance safety and to improve the efficient use of the navigable airspace for en route IFR helicopter operations. DATES: Effective date 0901 UTC, August 25, 2011. The Director of the Federal Register approves this incorporation by reference action under 1 CFR part 51, subject to the annual revision of FAA Order 7400.9 and publication of conforming amendments. FOR FURTHER INFORMATION CONTACT: Paul Gallant, Airspace, Regulations and ATC Procedures Group, Office of Airspace Services, Federal Aviation Administration, 800 Independence Avenue, SW., Washington, DC 20591; telephone: (202) 267-8783. SUPPLEMENTARY INFORMATION: History On Tuesday, March 8, 2011, the FAA published in the Federal Register a notice of proposed rulemaking to establish two helicopter RNAV routes in Northeast United States (76 FR 12643). Interested parties were invited to participate in this rulemaking effort by submitting written comments on the proposal. Four people submitted comments on the proposal. Discussion of Comments Two commenters wrote expressing support for the proposal. Two commenters raised several issues which are discussed below. One commenter questioned the need for a new type of airway for helicopters stating that the existing system of VOR Federal airways and RNAV T- routes should be sufficient. The commenter wrote, in the past, the FAA had designated routes for helicopters in the northeast, but they were seldom available for use. Additionally, the commenter asked if the air traffic control separation standards for IFR helicopters differ from those that apply to fixed-wing aircraft; contending that, if they are the same, there is no need for helicopter airways. The past routes noted by the commenter were initiated in FAA Advisory Circular AC 73-2, ``IFR Helicopter Operations in the Northeast Corridor,'' dated June 11, 1979. AC 73-2 advised of special RNAV helicopter routes between Washington, DC, and Boston, MA. The routes were developed consistent with conventional traffic flows for use by helicopters under IFR conditions. Use of these routes was limited only to those operators that met specified criteria and were issued a letter of authorization from the FAA. Therefore, the routes were not available for general use and they were not depicted on IFR Enroute Low Altitude charts. The Advisory Circular was subsequently cancelled because the routes were designed for first generation RNAV systems which lacked the accuracy and reliability of satellite navigation and other advanced RNAV systems. Additionally, it was determined that the routes do not meet current Air Traffic Service route criteria. On March 26, 2007, the FAA issued a Letter to Airmen containing new routings to be filed with a ``fix-to-fix'' flight plan along the ``old'' IFR northeast corridor. As with the Advisory Circular routes, these routes are not depicted on IFR En route Low Altitude charts. The new TK routes in this rule approximate the former northeast corridor route [[Page 37262]] tracks. In addition, the new TK routes are public routes that will be depicted on the IFR Enroute Low Altitude charts and available for use by suitably equipped helicopters. Regarding IFR separation standards, there is no difference between IFR helicopters and IFR fixed wing aircraft. The question of establishing a new type of route for IFR helicopters was raised in response to user requests. In March 2006, the Helicopter Association International (HAI) requested that the FAA take action to develop and chart IFR RNAV airways for use by helicopters having IFR-approved GPS equipment. Of particular interest was the use of RNAV to assist IFR helicopter pilots transiting though busy terminal airspace areas while providing routes separate from fixed-wing traffic. This issue was studied by members of the Government/Industry Aeronautical Charting Forum (ACF), which is comprised of both FAA and Industry participants. The ACF supported the establishment of RNAV helicopter routes and concluded that a unique prefix should be used to identify these routes. Establishment of charted helicopter RNAV TK-routes will enhance safety and facilitate more flexible and efficient access to the NAS for IFR helicopter operations. In addition, the TK-routes will enable the designation of waypoints and feeder routes that would provide a connection between the NAS and instrument procedures serving helicopter landing/departure facilities. Among the potential benefits of these routes are more efficient and safer operations for helicopter emergency medical services flights. One commenter asked if he could file a TK-route for a flight in a Cessna 150. The answer is no, due in part to the differing missions of fixed-wing aircraft and helicopters, TK-routes may start and end at locations inappropriate for fixed wing aircraft, such as in the vicinity of hospital or other helipad locations. Due to this difference TK-routes will be designated specifically for helicopter use; therefore, only suitably equipped helicopters will be able to file for the routes. A commenter asked about the expected usage of the routes and the altitudes flown. It is anticipated the average usage rate would be around 30 to 50 flights per month for those route segments between the Philadelphia and the New York City areas. Usage of the full route between New York and Washington, DC, is expected to be about five per month. Altitude use on the routes will vary as with other ATS routes. Each TK-route will have a designated minimum en route IFR altitude (MEA). Assigned altitudes will be determined based on the requested altitude filed in the flight plan by the pilot and ATC requirements. The FAA received one request to extend the comment period. We feel that sufficient information was received to issue a final rule; therefore, an extension is not needed. One commenter questioned whether an environmental categorical exclusion (CATEX), as noted in the NPRM, was appropriate for this rule. This comment is addressed in the ``Environmental Review'' section, below. The Rule The FAA is amending Title 14, Code of Federal Regulations (14 CFR) part 71 adding low altitude helicopter RNAV routes (TK-routes) to the U.S. ATS route structure and designating the first two such helicopter RNAV routes. Helicopter RNAV routes will be identified by the International Civil Aviation Organization (ICAO) prefix ``TK'' followed by a 3-digit number. ICAO has allocated the number block 501 through 650 for U.S. use in identifying the routes. The two new routes in this rule, designated TK-502 and TK-504, will provide more direct routing for IFR helicopters in the northeast corridor between the New York City and