80 FR 32074 - Proposed Establishment of Multiple Air Traffic Service (ATS) Routes; Western United States
DEPARTMENT OF TRANSPORTATION
Federal Aviation Administration Federal Register Volume 80, Issue 108 (June 5, 2015)
Federal Aviation Administration
Federal Register Volume 80, Issue 108 (June 5, 2015)
| Page Range | 32074-32078 | |
| FR Document | 2015-13504 |
[Federal Register Volume 80, Number 108 (Friday, June 5, 2015)] [Proposed Rules] [Pages 32074-32078] From the Federal Register Online [www.thefederalregister.org] [FR Doc No: 2015-13504] ----------------------------------------------------------------------- DEPARTMENT OF TRANSPORTATION Federal Aviation Administration 14 CFR Part 71 [Docket No. FAA-2015-1345; Airspace Docket No. 14-AWP-13] RIN 2120-AA66 Proposed Establishment of Multiple Air Traffic Service (ATS) Routes; Western United States AGENCY: Federal Aviation Administration (FAA), DOT. ACTION: Notice of proposed rulemaking (NPRM). ----------------------------------------------------------------------- SUMMARY: This action proposes to establish 13 high altitude Area Navigation (RNAV) routes (Q-routes), and one low altitude RNAV route (T-route) in the western United States. The routes would promote operational efficiencies for users and provide connectivity to current and proposed RNAV en route and terminal procedures. DATES: Comments must be received on or before July 20, 2015. ADDRESSES: Send comments on this proposal to the U.S. Department of Transportation, Docket Operations, M-30, 1200 New Jersey Avenue SE., West Building Ground Floor, Room W12-140, Washington, DC 20590-0001; telephone: (202) 366-9826. You must identify FAA Docket No. FAA-2015- 1345 and Airspace Docket No. 14-AWP-13 at the beginning of your comments. You may also submit comments through the Internet at http://www.regulations.gov. FOR FURTHER INFORMATION CONTACT: Jason Stahl, Airspace Policy and Regulations Group, Office of Airspace Services, Federal Aviation Administration, 800 Independence Avenue SW., Washington, DC 20591; telephone: (202) 267-8783. SUPPLEMENTARY INFORMATION: Authority for This Rulemaking The FAA's authority to issue rules regarding aviation safety is found in Title 49 of the United States Code. Subtitle I, Section 106 describes the authority of the FAA Administrator. Subtitle VII, Aviation Programs, describes in more detail the scope of the agency's authority. This rulemaking is promulgated under the authority described in Subtitle VII, Part A, Subpart I, Section 40103. Under that section, the FAA is charged with prescribing regulations to assign the use of the airspace necessary to ensure the safety of aircraft and the efficient use of airspace. This regulation is within the scope of that authority as it would modify the route structure in the western U.S. to preserve the safe and efficient flow of air traffic within the NAS. Background The development of new RNAV Standard Instrument Departure (SID) and Standard Terminal Arrival (STAR) routes requires incorporation of these proposed Q and T routes into the NAS Route Structure in order to maximize the benefits of increased safety in high volume en route sectors. The Los Angeles Air Route Traffic Control Center (ARTCC) currently does not have routes that join the Performance Based Navigation (PBN) arrival and departure procedures. The existing conventional jet route structure does not serve the new SID/STAR designs. Routes made up of ground based navigational aids are not capable of delivering aircraft onto the RNAV based arrival and departure procedures in an efficient manner. Developing these predictable and repeatable flight paths (Q and T routes) through a complex area confined by restricted areas will improve throughput and safety for Los Angeles ARTCC. This first phase of a two phase project will align a network of Q- Routes with the new SID's and STAR's. The Q-Route structure is projected to optimize descent/climb profiles to/from several airports in southern California and create segregated arrival/departure paths to reduce airspace complexity. 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-2015-1345 and Airspace Docket No. 14-AWP-13) and be submitted in triplicate to the Docket Management Facility (see ADDRESSES section for address and phone number). You may also submit comments through the Internet at http://www.regulations.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-2015-1345 and Airspace Docket No. 14-AWP-13.'' The postcard will be date/time stamped and returned to the commenter. All communications received on or before the specified comment closing date 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 comment closing date. 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://www.regulations.gov. 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:00 a.m. and 5:00 p.m., Monday through Friday, except Federal holidays. An informal docket may also be examined during normal business hours at the office of the Western Service Center, Operations Support Group, Federal Aviation Administration, 1601 Lind Ave SW., Renton, WA 98057. [[Page 32075]] 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. Availability and Summary of Documents for Incorporation by Reference This document proposes to amend FAA Order 7400.9Y, airspace Designations and Reporting Points, dated August 6, 2014, and effective September 15, 2014. FAA Order 7400.9Y is publicly available as listed in the ADDRESSES section of this proposed rule. FAA Order 7400.9Y lists Class A, B, C, D, and E airspace areas, air traffic service routes, and reporting points. The Proposal The FAA is proposing an amendment to Title 14, Code of Federal Regulations (14 CFR) part 71 to establish U.S. RNAV routes Q-70, Q-73, Q-74, Q-78, Q-86, Q-88, Q-90, Q-94, Q-96, Q-98, Q-114, Q-168, T-326, and Q-842, which is an extension of a current Canadian RNAV route and therefore retains the Canadian numbering. The proposed routes would connect to new SID and STAR procedures as designed in the Southern California (SoCal) Metroplex. The proposed routes are outlined below. Q-70: Q-70 is proposed from the HAILO, CA, waypoint (WP) to the SAKES, UT, WP to support departures from Los Angeles basin airports to the northeast. Q-73: Q-73 would be established from the MOMAR, CA, WP to the CORDU, ID, WP to accommodate arrivals to San Diego airport. Q-74: Q-74 is proposed from the NATEE, NV, WP to the DEANN, UT, WP and would support arrivals to John Wayne, Long Beach and Ontario airports from the northeast. Q-78: Q-78 would be established from the MARUE, NV, WP to the TOADD, AZ, WP to support arrivals to John Wayne, Long Beach and Ontario airports from the east and northeast. Q-86: Q-86 is proposed from the TTRUE, AZ, WP to the PLNDL, AZ, WP for arrivals to San Diego and Ontario airports from the east. Q-88: Q-88 would be established from the HAKMN, NV, WP to the CHESZ, UT, WP to support Los Angeles airport arrivals from the northeast. Q-90: Q-90 is proposed from the DNERO, CA, WP to the JASSE, AZ, WP and would be the primary RNAV route to Los Angeles from Denver ARTCC. Q-94: Q-94 is proposed from the WELUM, NV, WP to the ROOLL, AZ, WP to support Denver ARTCC arrivals to Burbank, Van Nuys, Camarillo, and Oxnard airports. Q-96: Q-96 would be established from the PURSE, NV, WP to the KIMMR, UT, WP to support arrivals to Burbank, Van Nuys, Camarillo, and Oxnard airports from the Salt Lake ARTCC. Q-98: Q-98 is proposed from the HAKMN, NV, WP to the PEEWE, AZ, WP to support Denver ARTCC arrivals to Los Angeles and San Diego airports. Q-114: Q-114 would extend from the NATEE, NV, WP to the BUGGG, UT, WP to support Salt Lake ARTCC arrivals to Long Beach, Ontario, and Orange County airports. Q-168: Q-168 would extend from the FNNDA, CA, WP to the JASSE, AZ, WP and would be the primary arrival route for Los Angeles airport from the Denver ARTCC. Q-842: Existing Canadian route Q-842 would extend south into U.S. airspace. The proposed route would begin at the BEALE, NV, WP and extend north to the existing TOVUM, AB, WP in Canada. This would provide routing for departures from Los Angeles, Long Beach, Ontario, and Orange County airports to airports in Calgary and Edmonton, Canada. T-326: Finally, this rule would establish low altitude RNAV route T-326, from the Mission Bay, CA, VORTAC (MZB) to the Imperial, CA, VORTAC (IPL) to transition from the San Diego area to the east, remaining south of restricted airspace R-2510 and the Kane Military Operations Area (MOA). High altitude United States RNAV routes are published in paragraph 2006, high altitude Canadian RNAV routes are published in paragraph 2007, and low altitude United States RNAV routes are published in paragraph 6011 of FAA Order 7400.9Y dated August 6, 2014, and effective September 15, 2014, which is incorporated by reference in 14 CFR 71.1. The high altitude United States RNAV routes (Q-routes), low altitude United States RNAV routes (T-routes), and high altitude Canadian RNAV routes listed in this document would be subsequently published in the Order. Regulatory Notices and Analyses 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. Environmental Review This proposal will be subject to an environmental analysis in accordance with FAA Order 1050.1E, ``Environmental Impacts: Policies and Procedures'' prior to any FAA final regulatory action. List of Subjects in 14 CFR Part 71 Airspace, Incorporation by reference, Navigation (air). The Proposed Amendment In consideration of the foregoing, the Federal Aviation Administration proposes to amend 14 CFR part 71 as follows: PART 71--DESIGNATION OF CLASS A, B, C, D, AND E AIRSPACE AREAS; AIR TRAFFIC SERVICE ROUTES; AND REPORTING POINTS 0 1. The authority citation for part 71 continues to read as follows: Authority: 49 U.S.C. 106(f), 106(g), 40103, 40113, 40120; E.O. 10854, 24 FR 9565, 3 CFR, 1959-1963 Comp., p. 389. Sec. 71.1 [Amended] 0 2. The incorporation by reference in 14 CFR 71.1 of FAA Order 7400.9Y, Airspace Designations and Reporting Points, dated August 6, 2014, and effective September 15, 2014, is amended as follows: Paragraph 2006. United States Area Navigation Routes * * * * * Q-70 HAILO, CA to SAKES, UT (New) HAILO, CA WP (Lat. 35[deg]38'14.00'' N., long. 115[deg]58'16.00'' W.) LAS, NV VOR (Lat. 36[deg]04'46.93'' N., long. 115[deg]09'35.27'' W.) [[Page 32076]] IFEYE, NV WP (Lat. 36[deg]24'56.04'' N., long. 114[deg]47'49.32'' W.) BLIPP, NV WP (Lat. 36[deg]42'41.31'' N., long. 114[deg]28'26.45'' W.) EEVUN, UT WP (Lat. 37[deg]02'52.90'' N., long. 113[deg]42'42.56'' W.) BLOBB, UT WP (Lat. 37[deg]17'45.63'' N., long. 113[deg]06'52.16'' W.) BAWER, UT WP (Lat. 37[deg]38'06.68'' N., long. 112[deg]16'45.89'' W.) SAKES, UT WP (Lat. 38[deg]50'00.51'' N., long. 110[deg]16'16.52'' W.) * * * * * Q-73 MOMAR, CA to CORDU, ID (New) MOMAR, CA WP (Lat. 33[deg]30'54.13'' N., long. 115[deg]56'40.14'' W.) CABIC, CA WP (Lat. 33[deg]46'17.01'' N., long. 115[deg]49'28.71'' W.) CHADT, CA WP (Lat. 33[deg]55'18.49'' N., long. 115[deg]45'03.26'' W.) LVELL, CA WP (Lat. 34[deg]12'37.38'' N., long. 115[deg]36'53.25'' W.) HAKMN, NV WP (Lat. 35[deg]30'28.31'' N., long. 115[deg]04'47.04'' W.) ZZYZX, NV WP (Lat. 35[deg]39'53.52'' N., long. 114[deg]51'54.99'' W.) LAKRR, AZ WP (Lat. 36[deg]05'07.72'' N., long. 114[deg]17'09.16'' W.) GUNTR, AZ WP (Lat. 36[deg]24'39.65'' N., long. 114[deg]02'11.55'' W.) ZAINY, AZ WP (Lat. 36[deg]39'24.73'' N., long. 113[deg]54'03.50'' W.) EEVUN, UT WP (Lat. 37[deg]02'52.90'' N., long. 113[deg]42'42.56'' W.) WINEN, UT WP (Lat. 37[deg]56'00.00'' N., long. 113[deg]30'00.00'' W.) CRITO, NV WP (Lat. 39[deg]18'00.00'' N., long. 114[deg]33'00.00'' W.) BROPH, ID WP (Lat. 42[deg]43'15.71'' N., long. 114[deg]52'31.80'' W.) DERSO, ID FIX (Lat. 43[deg]21'42.63'' N., long. 115[deg]08'01.66'' W.) SAWTT, ID WP (Lat. 44[deg]37'35.52'' N., long. 115[deg]43'55.55'' W.) HELLS, ID WP (Lat. 45[deg]25'07.35'' N., long. 116[deg]07'15.53'' W.) ZATIP, ID WP (Lat. 46[deg]13'17.48'' N., long. 116[deg]31'37.57'' W.) CORDU, ID WP (Lat. 48[deg]10'46.10'' N., long. 116[deg]40'21.84'' W.) Q-74 NATEE, NV to DEANN, UT (New) NATEE, NV WP (Lat. 35[deg]37'14.00'' N., long. 115[deg]22'26.00'' W.) BLD, NV VOR (Lat. 35[deg]59'44.84'' N., long. 114[deg]51'48.88'' W.) ZAINY, AZ WP (Lat. 36[deg]39'24.73'' N., long. 113[deg]54'03.50'' W.) FIZZL, AZ WP (Lat. 36[deg]56'03.37'' N., long. 113[deg]16'23.91'' W.) GARDD, UT WP (Lat. 37[deg]03'12.91'' N., long. 112[deg]37'54.38'' W.) DEANN, UT WP (Lat. 37[deg]12'34.00'' N., long. 111[deg]42'47.00'' W.) Q-78 MARUE, NV to TOADD, AZ (New) MARUE, NV WP (Lat. 35[deg]15'23.00'' N., long. 114[deg]52'55.00'' W.) DUGGN, AZ WP (Lat. 35[deg]44'06.83'' N., long. 113[deg]23'24.52'' W.) TOADD, AZ WP (Lat. 36[deg]17'45.60'' N., long. 111[deg]30'37.21'' W.) * * * * * Q-86 TTRUE, AZ to PLNDL, AZ (New) TTRUE, AZ WP (Lat. 34[deg]38'01.53'' N., long. 114[deg]23'05.05'' W.) YORRK, AZ WP (Lat. 34[deg]52'03.23'' N., long. 113[deg]55'58.14'' W.) SCHLS, AZ WP (Lat. 35[deg]14'18.55'' N., long. 113[deg]09'42.77'' W.) CUTRO, AZ WP (Lat. 35[deg]36'16.98'' N., long. 112[deg]23'00.00'' W.) VALEQ, AZ WP (Lat. 35[deg]44'01.73'' N., long. 112[deg]06'31.44'' W.) PLNDL, AZ WP (Lat. 35[deg]50'17.43'' N., long. 111[deg]52'40.71'' W.) Q-88 HAKMN, NV to CHESZ, UT (New) HAKMN, NV WP (Lat. 35[deg]30'28.31'' N., long. 115[deg]04'47.04'' W.) ZZYZX, NV WP (Lat. 35[deg]39'53.52'' N., long. 114[deg]51'54.99'' W.) LAKRR, NV WP (Lat. 36[deg]05'07.72'' N., long. 114[deg]17'09.16'' W.) NOOTN, AZ WP (Lat. 36[deg]37'32.63'' N., long. 113[deg]20'40.25'' W.) GARDD, UT WP (Lat. 37[deg]03'12.91'' N., long. 112[deg]37'54.38'' W.) VERKN, UT WP (Lat. 37[deg]23'00.05'' N., long. 112[deg]04'21.69'' W.) PROMT, UT WP (Lat. 37[deg]30'06.70'' N., long. 111[deg]52'12.94'' W.) CHESZ, UT WP (Lat. 38[deg]16'59.03'' N., long. 110[deg]02'11.31'' W.) Q-90 DNERO, CA to JASSE, AZ (New) DNERO, CA WP (Lat. 35[deg]02'07.14'' N., long. 114[deg]54'16.39'' W.) ESGEE, NV WP (Lat. 35[deg]08'00.50'' N., long. 114[deg]37'21.64'' W.) AREAF, AZ WP (Lat. 35[deg]36'31.77'' N., long. 113[deg]13'50.46'' W.) JASSE, AZ WP (Lat. 36[deg]04'15.53'' N., long. 111[deg]48'45.81'' W.) Q-94 WELUM, NV to ROOLL, AZ (New) WELUM, NV WP (Lat. 35[deg]22'56.00'' N., long. 114[deg]55'59.00'' W.) MNGGO, AZ WP (Lat. 35[deg]51'13.55'' N., long. 113[deg]28'23.59'' W.) ROOLL, AZ WP (Lat. 36[deg]27'37.93'' N., long. 111[deg]28'54.98'' W.) Q-96 PURSE, NV to KIMMR, UT (New) PURSE, NV WP (Lat. 35[deg]34'54.00'' N., long. 115[deg]11'53.00'' W.) DODDL, NV WP (Lat. 35[deg]49'28.80'' N., long. 114[deg]51'51.29'' W.) BFUNE, AZ WP (Lat. 36[deg]06'10.73'' N., long. 114[deg]28'40.09'' W.) GUNTR, AZ WP (Lat. 36[deg]24'39.65'' N., long. 114[deg]02'11.55'' W.) PIIXR, AZ WP (Lat. 36[deg]36'29.27'' N., long. 113[deg]45'02.40'' W.) FIZZL, AZ WP (Lat. 36[deg]56'03.37'' N., long. 113[deg]16'23.91'' W) [[Page 32077]] BAWER, UT WP (Lat. 37[deg]38'06.68'' N., long. 112[deg]16'45.89'' W.) ROCCY, UT WP (Lat. 37[deg]49'41.63'' N., long. 111[deg]59'59.84'' W.) SARAF, UT WP (Lat. 38[deg]36'03.84'' N., long. 110[deg]53'24.20'' W.) KIMMR, UT WP (Lat. 39[deg]13'45.24'' N., long. 109[deg]57'30.10'' W.) Q-98 HAKMN, NV to PEEWE, AZ (New) HAKMN, NV WP (Lat. 35[deg]30'28.31'' N., long. 115[deg]04'47.04'' W.) ZZYZX, NV WP (Lat. 35[deg]39'53.52'' N., long. 114[deg]51'54.99'' W.) LAKRR, NV WP (Lat. 36[deg]05'07.72'' N., long. 114[deg]17'09.16'' W.) DUZIT, AZ WP (Lat. 36[deg]24'51.20'' N., long. 113[deg]24'51.53'' W.) EEEZY, AZ WP (Lat. 36[deg]44'33.18'' N., long. 112[deg]21'40.77'' W.) PEEWE, AZ WP (Lat. 36[deg]58'08.69'' N., long. 111[deg]36'40.81'' W.) * * * * * Q-114 NATEE, NV to BUGGG, UT (New) NATEE, NV WP (Lat. 35[deg]37'14.00'' N., long. 115[deg]22'26.00'' W.) BLD, NV VOR (Lat. 35[deg]59'44.84'' N., long. 114[deg]51'48.88'' W.) ZAINY, AZ WP (Lat. 36[deg]39'24.73'' N., long. 113[deg]54'03.50'' W.) AHOWW, UT WP (Lat. 37[deg]07'14.56'' N., long. 113[deg]11'34.04'' W.) BAWER, UT WP (Lat. 37[deg]38'06.68'' N., long. 112[deg]16'45.89'' W.) BUGGG, UT WP (Lat. 38[deg]39'18.31'' N., long. 109[deg]29'48.01'' W.) * * * * * Q-168 FNNDA, CA to JASSE, AZ (New) FNNDA, CA WP (Lat. 34[deg]45'14.96'' N., long. 114[deg]45'18.49'' W.) SHIVA, AZ WP (Lat. 34[deg]58'12.28'' N., long. 114[deg]17'24.65'' W.) KRINA, AZ WP (Lat. 35[deg]28'02.52'' N., long. 113[deg]11'35.60'' W.) JASSE, AZ WP (Lat. 36[deg]04'15.53'' N., long. 111[deg]48'45.81'' W.) * * * * * Paragraph 2007. Canadian Area Navigation Routes Q-842 BEALE, NV to TOVUM, AB Canada (New) BEALE, NV WP (Lat. 36[deg]10'56.60'' N., long. 114[deg]49'34.81'' W.) BLIPP, NV WP (Lat. 36[deg]42'41.31'' N., long. 114[deg]28'26.45'' W.) WINEN, UT WP (Lat. 37[deg]56'00.00'' N., long. 113[deg]30'00.00'' W.) TABLL, UT WP (Lat. 38[deg]39'56.31'' N., long. 113[deg]10'35.15'' W.) PICHO, UT WP (Lat. 39[deg]58'00.00'' N., long. 112[deg]35'00.00'' W.) PATIO, UT WP (Lat. 41[deg]16'00.00'' N., long. 112[deg]32'00.00'' W.) PROXI, UT WP (Lat. 41[deg]58'20.81'' N., long. 112[deg]31'33.79'' W.) VAANE, ID WP (Lat. 45[deg]18'12.53'' N., long. 112[deg]44'58.36'' W.) KEETA, MT WP (Lat. 47[deg]20'39.01'' N., long. 112[deg]52'51.46'' W.) TOVUM, AB, Canada WP (Lat. 49[deg]14'29.00'' N., long. 112[deg]48'53.00'' W.) Excluding the airspace within Canada. * * * * * Paragraph 6011. United States Area Navigation Routes T-326 Mission Bay, CA to Imperial, CA (New) Mission Bay, CA (MZB) VORTAC (Lat. 32[deg]46'55.93'' N., long. 117[deg]13'31.49'' W.) HAILE, CA WP (Lat. 32[deg]46'45.70'' N., long. 117[deg]00'51.71'' W.) BLLYJ, CA WP (Lat. 32[deg]49'38.06'' N., long. 116[deg]45'56.45'' W.) STAXS, CA WP (Lat. 32[deg]52'16.70'' N., long. 116[deg]32'17.69'' W.) GILYY, CA WP (Lat. 32[deg]52'12.12'' N., long. 116[deg]21'05.24'' W.) KUMBA, CA WP (Lat. 32[deg]45'43.18'' N., long. 116[deg]03'13.37'' W.) Imperial, CA (IPL) VORTAC (Lat. 32[deg]44'55.92'' N., long. 115[deg]30'30.90'' W.) Issued in Washington, DC, on May 26, 2015. Gary A. Norek, Manager, Airspace Policy & Regulations Group. [FR Doc. 2015-13504 Filed 6-4-15; 8:45 am] BILLING CODE 4910-13-P
![32074 Federal Register / Vol. 80, No. 108 / Friday, June 5, 2015 / Proposed Rules
Group, FAA, 2601 Meacham Blvd., Fort Airspace Docket No. 14–AWP–13 at the create segregated arrival/departure paths
Worth, Texas 76137; telephone (817) 222– beginning of your comments. You may to reduce airspace complexity.
5110; email robert.grant@faa.gov. also submit comments through the
(2) For operations conducted under a 14 Comments Invited
Internet at http://www.regulations.gov.
CFR part 119 operating certificate or under Interested parties are invited to
14 CFR part 91, subpart K, we suggest that FOR FURTHER INFORMATION CONTACT:
Jason Stahl, Airspace Policy and participate in this proposed rulemaking
you notify your principal inspector, or
lacking a principal inspector, the manager of Regulations Group, Office of Airspace by submitting such written data, views,
the local flight standards district office or Services, Federal Aviation or arguments as they may desire.
certificate holding district office before Comments that provide the factual basis
Administration, 800 Independence
operating any aircraft complying with this supporting the views and suggestions
Avenue SW., Washington, DC 20591;
AD through an AMOC. presented are particularly helpful in
telephone: (202) 267–8783.
developing reasoned regulatory
(h) Additional Information SUPPLEMENTARY INFORMATION: decisions on the proposal. Comments
The subject of this AD is addressed in the are specifically invited on the overall
European Aviation Safety Agency (EASA) Authority for This Rulemaking
regulatory, aeronautical, economic,
No. 2014–0048, March 4, 2014. You may The FAA’s authority to issue rules
view the EASA AD on the Internet at environmental, and energy-related
regarding aviation safety is found in aspects of the proposal.
http://www.regulations.gov in the AD Docket. Title 49 of the United States Code. Communications should identify both
(i) Subject Subtitle I, Section 106 describes the docket numbers (FAA Docket No. FAA–
Joint Aircraft Service Component (JASC) authority of the FAA Administrator. 2015–1345 and Airspace Docket No. 14–
Code: 5300, Fuselage Structure (General). Subtitle VII, Aviation Programs, AWP–13) and be submitted in triplicate
describes in more detail the scope of the to the Docket Management Facility (see
Issued in Fort Worth, Texas, on May 26,
2015.
agency’s authority. ADDRESSES section for address and
This rulemaking is promulgated phone number). You may also submit
Lance T. Gant,
under the authority described in comments through the Internet at
Acting Directorate Manager, Rotorcraft Subtitle VII, Part A, Subpart I, Section
Directorate, Aircraft Certification Service. http://www.regulations.gov.
40103. Under that section, the FAA is Commenters wishing the FAA to
[FR Doc. 2015–13354 Filed 6–4–15; 8:45 am]
charged with prescribing regulations to acknowledge receipt of their comments
BILLING CODE 4910–13–P assign the use of the airspace necessary on this action must submit with those
to ensure the safety of aircraft and the comments a self-addressed, stamped
efficient use of airspace. This regulation postcard on which the following
DEPARTMENT OF TRANSPORTATION
is within the scope of that authority as statement is made: ‘‘Comments to FAA
Federal Aviation Administration it would modify the route structure in Docket No. FAA–2015–1345 and
the western U.S. to preserve the safe and Airspace Docket No. 14–AWP–13.’’ The
14 CFR Part 71 efficient flow of air traffic within the postcard will be date/time stamped and
NAS. returned to the commenter.
[Docket No. FAA–2015–1345; Airspace
Background All communications received on or
Docket No. 14–AWP–13]
before the specified comment closing
RIN 2120–AA66 The development of new RNAV date will be considered before taking
Standard Instrument Departure (SID) action on the proposed rule. The
Proposed Establishment of Multiple Air and Standard Terminal Arrival (STAR) proposal contained in this action may
Traffic Service (ATS) Routes; Western routes requires incorporation of these be changed in light of comments
United States proposed Q and T routes into the NAS received. All comments submitted will
Route Structure in order to maximize be available for examination in the
AGENCY: Federal Aviation the benefits of increased safety in high
Administration (FAA), DOT. public docket both before and after the
volume en route sectors. comment closing date. A report
ACTION: Notice of proposed rulemaking The Los Angeles Air Route Traffic summarizing each substantive public
(NPRM). Control Center (ARTCC) currently does contact with FAA personnel concerned
not have routes that join the with this rulemaking will be filed in the
SUMMARY: This action proposes to
Performance Based Navigation (PBN) docket.
establish 13 high altitude Area
arrival and departure procedures. The
Navigation (RNAV) routes (Q-routes), Availability of NPRMs
existing conventional jet route structure
and one low altitude RNAV route (T-
does not serve the new SID/STAR An electronic copy of this document
route) in the western United States. The
designs. Routes made up of ground may be downloaded through the
routes would promote operational
based navigational aids are not capable Internet at http://www.regulations.gov.
efficiencies for users and provide
of delivering aircraft onto the RNAV You may review the public docket
connectivity to current and proposed
based arrival and departure procedures containing the proposal, any comments
RNAV en route and terminal
in an efficient manner. Developing these received and any final disposition in
procedures.
predictable and repeatable flight paths person in the Dockets Office (see
DATES: Comments must be received on (Q and T routes) through a complex area ADDRESSES section for address and
asabaliauskas on DSK5VPTVN1PROD with PROPOSALS
or before July 20, 2015. confined by restricted areas will phone number) between 9:00 a.m. and
ADDRESSES: Send comments on this improve throughput and safety for Los 5:00 p.m., Monday through Friday,
proposal to the U.S. Department of Angeles ARTCC. except Federal holidays. An informal
Transportation, Docket Operations, M– This first phase of a two phase project docket may also be examined during
30, 1200 New Jersey Avenue SE., West will align a network of Q-Routes with normal business hours at the office of
Building Ground Floor, Room W12–140, the new SID’s and STAR’s. The Q-Route the Western Service Center, Operations
Washington, DC 20590–0001; telephone: structure is projected to optimize Support Group, Federal Aviation
(202) 366–9826. You must identify FAA descent/climb profiles to/from several Administration, 1601 Lind Ave SW.,
Docket No. FAA–2015–1345 and airports in southern California and Renton, WA 98057.
VerDate Sep<11>2014 17:42 Jun 04, 2015 Jkt 235001 PO 00000 Frm 00033 Fmt 4702 Sfmt 4702 E:\FR\FM\05JNP1.SGM 05JNP1](https://thefederalregister.org/doc/80_FR_32182/page/1.svg)
![Federal Register / Vol. 80, No. 108 / Friday, June 5, 2015 / Proposed Rules 32075
Persons interested in being placed on and would be the primary RNAV route established body of technical
a mailing list for future NPRMs should to Los Angeles from Denver ARTCC. regulations for which frequent and
contact the FAA’s Office of Rulemaking, Q–94: Q–94 is proposed from the routine amendments are necessary to
(202) 267–9677, for a copy of Advisory WELUM, NV, WP to the ROOLL, AZ, keep them operationally current.
Circular No. 11–2A, Notice of Proposed WP to support Denver ARTCC arrivals Therefore, this proposed regulation: (1)
Rulemaking Distribution System, which to Burbank, Van Nuys, Camarillo, and Is not a ‘‘significant regulatory action’’
describes the application procedure. Oxnard airports. under Executive Order 12866; (2) is not
Q–96: Q–96 would be established a ‘‘significant rule’’ under Department of
Availability and Summary of from the PURSE, NV, WP to the
Documents for Incorporation by Transportation (DOT) Regulatory
KIMMR, UT, WP to support arrivals to
Reference Burbank, Van Nuys, Camarillo, and Policies and Procedures (44 FR 11034;
This document proposes to amend Oxnard airports from the Salt Lake February 26, 1979); and (3) does not
FAA Order 7400.9Y, airspace ARTCC. warrant preparation of a regulatory
Designations and Reporting Points, Q–98: Q–98 is proposed from the evaluation as the anticipated impact is
dated August 6, 2014, and effective HAKMN, NV, WP to the PEEWE, AZ, so minimal. Since this is a routine
September 15, 2014. FAA Order WP to support Denver ARTCC arrivals matter that will only affect air traffic
7400.9Y is publicly available as listed in to Los Angeles and San Diego airports. procedures and air navigation, it is
the ADDRESSES section of this proposed Q–114: Q–114 would extend from the certified that this proposed rule, when
rule. FAA Order 7400.9Y lists Class A, NATEE, NV, WP to the BUGGG, UT, WP promulgated, will not have a significant
B, C, D, and E airspace areas, air traffic to support Salt Lake ARTCC arrivals to economic impact on a substantial
service routes, and reporting points. Long Beach, Ontario, and Orange number of small entities under the
County airports. criteria of the Regulatory Flexibility Act.
The Proposal Q–168: Q–168 would extend from the
Environmental Review
The FAA is proposing an amendment FNNDA, CA, WP to the JASSE, AZ, WP
to Title 14, Code of Federal Regulations and would be the primary arrival route This proposal will be subject to an
(14 CFR) part 71 to establish U.S. RNAV for Los Angeles airport from the Denver environmental analysis in accordance
routes Q–70, Q–73, Q–74, Q–78, Q–86, ARTCC. with FAA Order 1050.1E,
Q–88, Q–90, Q–94, Q–96, Q–98, Q–114, Q–842: Existing Canadian route Q– ‘‘Environmental Impacts: Policies and
Q–168, T–326, and Q–842, which is an 842 would extend south into U.S. Procedures’’ prior to any FAA final
extension of a current Canadian RNAV airspace. The proposed route would regulatory action.
route and therefore retains the Canadian begin at the BEALE, NV, WP and extend
numbering. The proposed routes would north to the existing TOVUM, AB, WP List of Subjects in 14 CFR Part 71
connect to new SID and STAR in Canada. This would provide routing
procedures as designed in the Southern for departures from Los Angeles, Long Airspace, Incorporation by reference,
California (SoCal) Metroplex. The Beach, Ontario, and Orange County Navigation (air).
proposed routes are outlined below. airports to airports in Calgary and The Proposed Amendment
Q–70: Q–70 is proposed from the Edmonton, Canada.
HAILO, CA, waypoint (WP) to the T–326: Finally, this rule would In consideration of the foregoing, the
SAKES, UT, WP to support departures establish low altitude RNAV route T– Federal Aviation Administration
from Los Angeles basin airports to the 326, from the Mission Bay, CA, proposes to amend 14 CFR part 71 as
northeast. VORTAC (MZB) to the Imperial, CA, follows:
Q–73: Q–73 would be established VORTAC (IPL) to transition from the
from the MOMAR, CA, WP to the San Diego area to the east, remaining PART 71—DESIGNATION OF CLASS A,
CORDU, ID, WP to accommodate south of restricted airspace R–2510 and B, C, D, AND E AIRSPACE AREAS; AIR
arrivals to San Diego airport. the Kane Military Operations Area TRAFFIC SERVICE ROUTES; AND
Q–74: Q–74 is proposed from the (MOA). REPORTING POINTS
NATEE, NV, WP to the DEANN, UT, WP High altitude United States RNAV
and would support arrivals to John routes are published in paragraph 2006, ■ 1. The authority citation for part 71
Wayne, Long Beach and Ontario airports high altitude Canadian RNAV routes are continues to read as follows:
from the northeast. published in paragraph 2007, and low
Q–78: Q–78 would be established altitude United States RNAV routes are Authority: 49 U.S.C. 106(f), 106(g), 40103,
40113, 40120; E.O. 10854, 24 FR 9565, 3 CFR,
from the MARUE, NV, WP to the published in paragraph 6011 of FAA
1959–1963 Comp., p. 389.
TOADD, AZ, WP to support arrivals to Order 7400.9Y dated August 6, 2014,
John Wayne, Long Beach and Ontario and effective September 15, 2014, which § 71.1 [Amended]
airports from the east and northeast. is incorporated by reference in 14 CFR
Q–86: Q–86 is proposed from the 71.1. The high altitude United States ■ 2. The incorporation by reference in
TTRUE, AZ, WP to the PLNDL, AZ, WP RNAV routes (Q-routes), low altitude 14 CFR 71.1 of FAA Order 7400.9Y,
for arrivals to San Diego and Ontario United States RNAV routes (T-routes), Airspace Designations and Reporting
airports from the east. and high altitude Canadian RNAV Points, dated August 6, 2014, and
Q–88: Q–88 would be established routes listed in this document would be effective September 15, 2014, is
asabaliauskas on DSK5VPTVN1PROD with PROPOSALS
from the HAKMN, NV, WP to the subsequently published in the Order. amended as follows:
CHESZ, UT, WP to support Los Angeles
airport arrivals from the northeast. Regulatory Notices and Analyses Paragraph 2006. United States Area
Q–90: Q–90 is proposed from the The FAA has determined that this Navigation Routes
DNERO, CA, WP to the JASSE, AZ, WP proposed regulation only involves an * * * * *
Q–70 HAILO, CA TO SAKES, UT (NEW)
HAILO, CA WP (Lat. 35°38′14.00″ N., long. 115°58′16.00″ W.)
LAS, NV VOR (Lat. 36°04′46.93″ N., long. 115°09′35.27″ W.)
VerDate Sep<11>2014 17:42 Jun 04, 2015 Jkt 235001 PO 00000 Frm 00034 Fmt 4702 Sfmt 4702 E:\FR\FM\05JNP1.SGM 05JNP1](https://thefederalregister.org/doc/80_FR_32182/page/2.svg)
![Federal Register / Vol. 80, No. 108 / Friday, June 5, 2015 / Proposed Rules 32077
BAWER, UT WP (Lat. 37°38′06.68″ N., long. 112°16′45.89″ W.)
ROCCY, UT WP (Lat. 37°49′41.63″ N., long. 111°59′59.84″ W.)
SARAF, UT WP (Lat. 38°36′03.84″ N., long. 110°53′24.20″ W.)
KIMMR, UT WP (Lat. 39°13′45.24″ N., long. 109°57′30.10″ W.)
Q–98 HAKMN, NV TO PEEWE, AZ (NEW)
HAKMN, NV WP (Lat. 35°30′28.31″ N., long. 115°04′47.04″ W.)
ZZYZX, NV WP (Lat. 35°39′53.52″ N., long. 114°51′54.99″ W.)
LAKRR, NV WP (Lat. 36°05′07.72″ N., long. 114°17′09.16″ W.)
DUZIT, AZ WP (Lat. 36°24′51.20″ N., long. 113°24′51.53″ W.)
EEEZY, AZ WP (Lat. 36°44′33.18″ N., long. 112°21′40.77″ W.)
PEEWE, AZ WP (Lat. 36°58′08.69″ N., long. 111°36′40.81″ W.)
* * * * *
Q–114 NATEE, NV TO BUGGG, UT (NEW)
NATEE, NV WP (Lat. 35°37′14.00″ N., long. 115°22′26.00″ W.)
BLD, NV VOR (Lat. 35°59′44.84″ N., long. 114°51′48.88″ W.)
ZAINY, AZ WP (Lat. 36°39′24.73″ N., long. 113°54′03.50″ W.)
AHOWW, UT WP (Lat. 37°07′14.56″ N., long. 113°11′34.04″ W.)
BAWER, UT WP (Lat. 37°38′06.68″ N., long. 112°16′45.89″ W.)
BUGGG, UT WP (Lat. 38°39′18.31″ N., long. 109°29′48.01″ W.)
* * * * *
Q–168 FNNDA, CA TO JASSE, AZ (NEW)
FNNDA, CA WP (Lat. 34°45′14.96″ N., long. 114°45′18.49″ W.)
SHIVA, AZ WP (Lat. 34°58′12.28″ N., long. 114°17′24.65″ W.)
KRINA, AZ WP (Lat. 35°28′02.52″ N., long. 113°11′35.60″ W.)
JASSE, AZ WP (Lat. 36°04′15.53″ N., long. 111°48′45.81″ W.)
* * * * * Paragraph 2007. Canadian Area Navigation
Routes
Q–842 BEALE, NV TO TOVUM, AB CANADA (NEW)
BEALE, NV WP (Lat. 36°10′56.60″ N., long. 114°49′34.81″ W.)
BLIPP, NV WP (Lat. 36°42′41.31″ N., long. 114°28′26.45″ W.)
WINEN, UT WP (Lat. 37°56′00.00″ N., long. 113°30′00.00″ W.)
TABLL, UT WP (Lat. 38°39′56.31″ N., long. 113°10′35.15″ W.)
PICHO, UT WP (Lat. 39°58′00.00″ N., long. 112°35′00.00″ W.)
PATIO, UT WP (Lat. 41°16′00.00″ N., long. 112°32′00.00″ W.)
PROXI, UT WP (Lat. 41°58′20.81″ N., long. 112°31′33.79″ W.)
VAANE, ID WP (Lat. 45°18′12.53″ N., long. 112°44′58.36″ W.)
KEETA, MT WP (Lat. 47°20′39.01″ N., long. 112°52′51.46″ W.)
TOVUM, AB, Can- WP (Lat. 49°14′29.00″ N., long. 112°48′53.00″ W.)
ada
Excluding the airspace within Canada. Paragraph 6011. United States Area
* * * * * Navigation Routes
T–326 MISSION BAY, CA TO IMPERIAL, CA (NEW)
Mission Bay, CA VORTAC (Lat. 32°46′55.93″ N., long. 117°13′31.49″ W.)
(MZB)
HAILE, CA WP (Lat. 32°46′45.70″ N., long. 117°00′51.71″ W.)
BLLYJ, CA WP (Lat. 32°49′38.06″ N., long. 116°45′56.45″ W.)
STAXS, CA WP (Lat. 32°52′16.70″ N., long. 116°32′17.69″ W.)
GILYY, CA WP (Lat. 32°52′12.12″ N., long. 116°21′05.24″ W.)
KUMBA, CA WP (Lat. 32°45′43.18″ N., long. 116°03′13.37″ W.)
Imperial, CA (IPL) VORTAC (Lat. 32°44′55.92″ N., long. 115°30′30.90″ W.)
Issued in Washington, DC, on May 26,
2015.
Gary A. Norek,
asabaliauskas on DSK5VPTVN1PROD with PROPOSALS
Manager, Airspace Policy & Regulations
Group.
[FR Doc. 2015–13504 Filed 6–4–15; 8:45 am]
BILLING CODE 4910–13–P
VerDate Sep<11>2014 18:57 Jun 04, 2015 Jkt 235001 PO 00000 Frm 00036 Fmt 4702 Sfmt 4702 E:\FR\FM\05JNP1.SGM 05JNP1](https://thefederalregister.org/doc/80_FR_32182/page/4.svg)
![32078 Federal Register / Vol. 80, No. 108 / Friday, June 5, 2015 / Proposed Rules
ENVIRONMENTAL PROTECTION the EPA may not be able to consider ENVIRONMENTAL PROTECTION
AGENCY your comment. Electronic files should AGENCY
avoid the use of special characters, any
40 CFR Part 52 form of encryption, and be free of any 40 CFR Part 52
[EPA–R09–OAR–2015–0228; FRL–9928–08– defects or viruses. [EPA–R03–OAR–2015–0274; FRL–9928–77–
Region 9] Docket: Generally, documents in the Region 3]
docket for this action are available
Revisions to the California State Approval and Promulgation of Air
Implementation Plan, Eastern Kern Air electronically at www.regulations.gov
Quality Implementation Plans; Virginia;
Pollution Control District, Mojave and in hard copy at EPA Region IX, 75 Prevention of Significant Deterioration;
Desert Air Quality Management District Hawthorne Street, San Francisco, Plantwide Applicability Limits for
California 94105–3901. While all Greenhouse Gases
AGENCY: Environmental Protection documents in the docket are listed at
Agency (EPA). www.regulations.gov, some information AGENCY: Environmental Protection
ACTION: Proposed rule. may be publicly available only at the Agency.
hard copy location (e.g., copyrighted ACTION: Proposed rule.
SUMMARY: The Environmental Protection
Agency (EPA) is proposing to approve material, large maps), and some may not SUMMARY: The Environmental Protection
revisions to the Eastern Kern Air be publicly available in either location Agency (EPA) is proposing to approve
Pollution Control District (EKAPCD) (e.g., CBI). To inspect the hard copy aMay 12, 2014 State Implementation
and Mojave Desert Air Quality materials, please schedule an Plan (SIP) revision submitted for the
Management District (MDAQMD) appointment during normal business Commonwealth of Virginia by the
portions of the California State hours with the contact listed in the FOR Virginia Department of Environmental
Implementation Plan (SIP). These FURTHER INFORMATION CONTACT section. Quality (VADEQ). This revision will
revisions concern volatile organic FOR FURTHER INFORMATION CONTACT: add Plantwide Applicability Limit
compound (VOC) emissions from Nancy Levin, EPA Region IX, (415) 972– (PAL) provisions for Greenhouse Gases
polyester resin operations and oil-water 3848, levin.nancy@epa.gov. (GHGs) to Virginia’s Prevention of
separators. The EPA is proposing to Significant Deterioration (PSD) program.
approve local rules that regulate these SUPPLEMENTARY INFORMATION: This This action is being taken under the
emission sources under the Clean Air proposal addresses the following local Clean Air Act (CAA).
Act (CAA or the Act). rules: EKAPCD Rule 432 Polyester Resin DATES: Written comments must be
DATES: Any comments on this proposal Operations and MDAQMD Rule 464 Oil- received on or before July 6, 2015.
must arrive by July 6, 2015. Water Separators. In the Rules and ADDRESSES: Submit your comments,
ADDRESSES: Submit comments, Regulations section of this Federal identified by Docket ID Number EPA–
identified by docket number EPA–R09– Register, the EPA is approving these R03–OAR–2015–0274 by one of the
OAR–2015–0228, by one of the local rules in a direct final action following methods:
following methods: without prior proposal because the EPA A. www.regulations.gov. Follow the
1. Federal eRulemaking Portal: believes these SIP revisions are not on-line instructions for submitting
www.regulations.gov. Follow the on-line controversial. If the EPA receives comments.
instructions. adverse comments, however, the EPA B. Email: campbell.dave@epa.gov.
2. Email: steckel.andrew@epa.gov. will publish a timely withdrawal of the C. Mail: EPA–R03–OAR–2015–0274,
3. Mail or deliver: Andrew Steckel David Campbell, Associate Director,
direct final rule and address the
(Air-4), U.S. Environmental Protection Office of Permits and Air Toxics,
comments in subsequent action based
Agency Region IX, 75 Hawthorne Street, Mailcode 3AP10, U.S. Environmental
San Francisco, CA 94105–3901. on this proposed rule. Please note that
Protection Agency, Region III, 1650
Instructions: All comments will be if the EPA receives adverse comment on
Arch Street, Philadelphia, Pennsylvania
included in the public docket without an amendment, paragraph or section of 19103.
change and may be made available this rule and if that provision may be D. Hand Delivery: At the previously-
online at www.regulations.gov, severed from the remainder of the rule, listed EPA Region III address. Such
including any personal information the EPA may adopt as final those deliveries are only accepted during the
provided, unless the comment includes provisions of the rule that are not the Docket’s normal hours of operation, and
Confidential Business Information (CBI) subject of an adverse comment. special arrangements should be made
or other information whose disclosure is The EPA does not plan to open a for deliveries of boxed information.
restricted by statute. Information that second comment period, so anyone Instructions: Direct your comments to
you consider CBI or otherwise protected interested in commenting should do so Docket ID No. EPA–R03–OAR–2015–
should be clearly identified as such and at this time. If the EPA does not receive 0274. EPA’s policy is that all comments
should not be submitted through adverse comments, no further activity is received will be included in the public
www.regulations.gov or email. docket without change, and may be
planned. For further information, please
www.regulations.gov is an ‘‘anonymous made available online at
see the direct final action.
access’’ system, and the EPA will not www.regulations.gov, including any
asabaliauskas on DSK5VPTVN1PROD with PROPOSALS
know your identity or contact Dated: May 8, 2015. personal information provided, unless
information unless you provide it in the Alexis Strauss, the comment includes information
body of your comment. If you send Acting Regional Administrator, Region IX. claimed to be Confidential Business
email directly to the EPA, your email [FR Doc. 2015–13682 Filed 6–4–15; 8:45 am] Information (CBI) or other information
address will be automatically captured whose disclosure is restricted by statute.
BILLING CODE 6560–50–P
and included as part of the public Do not submit information that you
comment. If the EPA cannot read your consider to be CBI, or otherwise
comment due to technical difficulties protected, through www.regulations.gov
and cannot contact you for clarification, or email. The www.regulations.gov Web
VerDate Sep<11>2014 18:57 Jun 04, 2015 Jkt 235001 PO 00000 Frm 00037 Fmt 4702 Sfmt 4702 E:\FR\FM\05JNP1.SGM 05JNP1](https://thefederalregister.org/doc/80_FR_32182/page/5.svg)
Document Created: 2015-12-15 15:20:49
Document Modified: 2015-12-15 15:20:49
| Category | Regulatory Information | |
| Collection | Federal Register | |
| sudoc Class | AE 2.7: GS 4.107: AE 2.106: | |
| Publisher | Office of the Federal Register, National Archives and Records Administration | |
| Section | Proposed Rules | |
| Action | Notice of proposed rulemaking (NPRM). | |
| Dates | Comments must be received on or before July 20, 2015. | |
| Contact | Jason Stahl, Airspace Policy and Regulations Group, Office of Airspace Services, Federal Aviation Administration, 800 Independence Avenue SW., Washington, DC 20591; telephone: (202) 267-8783. | |
| FR Citation | 80 FR 32074 | |
| RIN Number | 2120-AA66 | |
| CFR Associated | Airspace; Incorporation by Reference and Navigation (air) |
2025 Federal Register | Disclaimer | Privacy Policy
USC | CFR | eCFR