Washington, DC Metropolitan Area Special Flight Rules Area; Technical Amendment, 13410-13411 [2018-06335]

Download as PDF 13410 Federal Register / Vol. 83, No. 61 / Thursday, March 29, 2018 / Rules and Regulations KS; INT Liberal 137° and Will Rogers, OK, 284° radials; Will Rogers; INT Will Rogers 113° and Okmulgee, OK, 238° radials; to Okmulgee. From Brickyard, IN; Muncie, IN; to Rosewood, OH. From Revloc, PA; INT Revloc 096° and Harrisburg, PA, 285° radials; Harrisburg; Lancaster, PA; INT Lancaster 095° and Yardley, PA, 255° radials; to Yardley. * * * * * V–221 [Amended] From Bible Grove, IL; Hoosier, IN; Shelbyville, IN; Muncie, IN; Fort Wayne, IN; to INT Fort Wayne 016° and Goshen, IN, 092° radials. * * * * * V–232 [Amended] From Keating, PA; Milton, PA; INT Milton 099° and Solberg, NJ, 299° radials; Solberg; INT Solberg 137° and Colts Neck, NJ, 263° radials; to Colts Neck. V–233 [Amended] From Spinner, IL; INT Spinner 061° and Roberts, IL, 233° radials; Roberts; Knox, IN; Goshen, IN; to Litchfield, MI. From Mount Pleasant, MI; INT Mount Pleasant 351° and Gaylord, MI, 207° radials; Gaylord; to Pellston, MI. * * * V–493 [Amended] From Livingston, TN; Lexington, KY; York, KY; INT York 030° and Appleton, OH, 183° radials; to Appleton. From Menominee, MI; to Rhinelander, WI. * * * * * * * V–522 [Removed] V–523 [Removed] * * * * * * * V–542 [Amended] From Tidioute, PA; Bradford, PA; INT Bradford 078° and Elmira, NY, 252° radials; Elmira; Binghampton, NY; Rockdale, NY; Albany, NY; Cambridge, NY; INT Cambridge 063° and Lebanon, NH, 214° radials; to Lebanon. * * * * * V–584 [Removed] Issued in Washington, DC, on March 22, 2018. Rodger A. Dean Jr., Manager, Airspace Policy Group. [FR Doc. 2018–06268 Filed 3–28–18; 8:45 am] * * BILLING CODE 4910–13–P * * DEPARTMENT OF TRANSPORTATION * * Federal Aviation Administration * * * * * * * * * * * * * * * * V–297 [Removed] * * * V–353 [Removed] * * * V–383 [Removed] * * * 14 CFR Part 93 [Docket No. FAA–2004–17005; Amdt. No. 93–91A] V–396 [Removed] * * * RIN 2120–AI17 V–406 [Removed] * * * Washington, DC Metropolitan Area Special Flight Rules Area; Technical Amendment V–416 [Removed] * * * Federal Aviation Administration, DOT. ACTION: Final rule; technical amendment. AGENCY: V–418 [Removed] * * * V–426 [Removed] * * * * * * V–443 [Removed] * * * V–450 [Amended] From Escanaba, MI; Menominee, MI; Green Bay, WI; Muskegon, MI; INT Muskegon 094° and Flint, MI, 280° radials; to Flint. rmajette on DSKBCKNHB2PROD with RULES * * * * * * * * * * * V–464 [Removed] * * * V–467 [Removed] * * * V–486 [Removed] * * * VerDate Sep<11>2014 15:09 Mar 28, 2018 Currently, FAA regulations require all pilots operating aircraft to or from College Park Airport, Potomac Airfield or Washington Executive/Hyde Field Airport to file instrument flight rules (IFR), DC Flight Restricted Zone (FRZ), or DC Special Flight Rules Area (SFRA) flight plans with the Washington Hub Flight Service Station (FSS). The FAA is transferring the responsibility for processing flight plans within the DC FRZ from the Washington Hub FSS to the Washington Air Route Traffic Control Center (ARTCC). This document revises the regulations by updating the organization responsible for processing the flight plans and by updating the flight plans required for flight operations in the DC FRZ. SUMMARY: V–435 [Removed] Jkt 244001 PO 00000 Frm 00036 Fmt 4700 Sfmt 4700 Effective on March 29, 2018. FOR FURTHER INFORMATION CONTACT: Scott Rosenbloom, Airspace and Rules, AJV–113, Federal Aviation Administration, 800 Independence Avenue SW, Washington, DC 20591; telephone (202) 267–3783; email scott.rosenbloom@faa.gov. SUPPLEMENTARY INFORMATION: Good Cause for Immediate Adoption Without Prior Notice V–525 [Removed] * DATES: Section 553(b)(3)(B) of the Administrative Procedure Act (APA) (5 U.S.C. 551 et seq.) authorizes agencies to dispense with notice and comment procedures for rules when the agency for ‘‘good cause’’ finds that those procedures are ‘‘impracticable, unnecessary, or contrary to the public interest.’’ Under this section, an agency, upon finding good cause, may issue a final rule without seeking comment prior to the rulemaking. Section 553(d)(3) of the Administrative Procedure Act requires that agencies publish a rule not less than 30 days before its effective date, except as otherwise provided by the agency for good cause found and published with the rule. This document revises § 93.343(a) of title 14 of the Code of Federal Regulations (14 CFR) by updating the organization responsible for processing IFR and FRZ flight plans from/to College Park, Potomac Airfield, and Washington Executive/Hyde Field airports. This revision will not impose any additional restrictions on the persons affected by these regulations. Furthermore, any additional delay in revising the regulations would be contrary to the public interest because it would create confusion among pilots operating in the DC SFRA including the DC FRZ. Accordingly, the FAA finds that (i) public comment on this change prior to promulgation is unnecessary and contrary to public interest, and (ii) good cause exists to make this rule effective in less than 30 days. Background Currently, § 93.343(a) requires pilots to file IFR, DC FRZ, or DC SFRA flight plans with the Washington Hub FSS for each departure and arrival from/to College Park, Potomac Airfield, and Washington Executive/Hyde Field Airports, whether or not the aircraft makes an immediate stop. An objective of the Administrator’s Flight Service National Airspace System (NAS) Efficient Streamlined Services Initiative is to realign activities through more efficient delivery of services. As part of this initiative, the FAA is E:\FR\FM\29MRR1.SGM 29MRR1 Federal Register / Vol. 83, No. 61 / Thursday, March 29, 2018 / Rules and Regulations transferring the responsibility for processing IFR and DC FRZ flight plans within the Washington DC Flight Restricted Zone from the Washington Hub FSS to the Flight Data Unit (FDU) at Washington ARTCC. This transition will occur on March 29, 2018. As a result, the FAA is updating § 93.343(a) to reflect the change in responsibility.1 Also as a result of the transition, the FAA is removing from §§ 93.341(d) and 93.343(a)(2) the references to the DC SFRA flight plan. Both regulations govern flight operations within the DC FRZ, which require a DC FRZ flight plan. Because a single entity was responsible for processing both DC SFRA and DC FRZ flight plans, the FAA has effectively construed any request for a DC SFRA flight plan to/from a location within the DC FRZ as a DC FRZ flight plan. Once the responsibilities for processing DC SFRA and DC FRZ flight plans are divided between two entities, however, the FAA will no longer be able to re-characterize a DC SFRA flight plan as a DC FRZ flight plan. The FAA is, therefore, removing the references to the DC SFRA from §§ 93.341(d) and 93.343(a)(2) to make clear that a pilot must file either an IFR or DC FRZ flight plan when operating to or from the DC FRZ. Furthermore, the FAA notes that it has communicated with the Transportation Security Administration (TSA) about a corresponding technical amendment that must be made to 49 CFR 1562.3(g)(1) to include the new organization responsible for processing IFR and DC FRZ flight plans. Technical Amendment In this technical amendment, the FAA is revising § 93.343(a)(2) and (3) by removing the references to the Washington Hub FSS. In their place, the FAA is inserting references to the Washington ARTCC, which is the new organization responsible for processing the flight plans. Furthermore, the FAA is revising §§ 93.341(d) and 93.343(a)(2) by removing the references to the DC SFRA flight plan. rmajette on DSKBCKNHB2PROD with RULES List of Subjects in 14 CFR Part 93 Air traffic control, Airports, Navigation (air), Reporting and recordkeeping requirements. The Amendment In consideration of the foregoing, the Federal Aviation Administration 1 The FAA notes that this change in responsibility will also generate a change in the dedicated phone number used for pilots to confirm their flight plan. Therefore, the FAA is also revising its Orders to update the phone number and organization responsible for filing IFR and DC FRZ flight plans. VerDate Sep<11>2014 15:09 Mar 28, 2018 Jkt 244001 amends chapter I of title 14, Code of Federal Regulations as follows: PART 93—SPECIAL AIR TRAFFIC RULES 1. The authority citation for part 93 continues to read as follows: ■ Authority: 49 U.S.C. 106(f), 106(g), 40103, 40106, 40109, 40113, 44502, 44514, 44701, 44715, 44719, 46301. 2. Amend § 93.341 by revising paragraph (d) to read as follows: ■ § 93.341 Aircraft operations in the DC FRZ. * * * * * (d) Before departing from an airport within the DC FRZ, or before entering the DC FRZ, all aircraft, except DOD, law enforcement, and lifeguard or air ambulance aircraft operating under an FAA/TSA airspace authorization must file and activate an IFR or a DC FRZ flight plan and transmit a discrete transponder code assigned by an Air Traffic Control facility. Aircraft must transmit the discrete transponder code at all times while in the DC FRZ or DC SFRA. 3. Amend § 93.343 by revising paragraphs (a)(2) and (a)(3) to read as follows: ■ § 93.343 Requirements for aircraft operations to or from College Park Airport, Potomac Airfield, or Washington Executive/ Hyde Field Airport. (a) * * * (2) Before departing, the pilot files an IFR or DC FRZ flight plan with the Washington Air Route Traffic Control Center for each departure and arrival from/to College Park, Potomac Airfield, and Washington Executive/Hyde Field airports, whether or not the aircraft makes an intermediate stop; (3) When filing a flight plan with the Washington Air Route Traffic Control Center, the pilot identifies himself or herself by providing the assigned pilot identification code. The Washington Air Route Traffic Control Center will accept the flight plan only after verifying the code; and * * * * * Issued under the authority of 49 U.S.C. 106(f) and (g) and 40103 in Washington, DC. Lirio Liu, Executive Director, Office of Rulemaking. [FR Doc. 2018–06335 Filed 3–28–18; 8:45 am] BILLING CODE 4910–13–P PO 00000 Frm 00037 Fmt 4700 Sfmt 4700 13411 DEPARTMENT OF TRANSPORTATION Federal Aviation Administration 14 CFR Part 97 [Docket No. 31184; Amdt. No. 3791] Standard Instrument Approach Procedures, and Takeoff Minimums and Obstacle Departure Procedures; Miscellaneous Amendments Federal Aviation Administration (FAA), DOT. ACTION: Final rule. AGENCY: This rule establishes, amends, suspends, or removes Standard Instrument Approach Procedures (SIAPs) and associated Takeoff Minimums and Obstacle Departure Procedures (ODPs) for operations at certain airports. These regulatory actions are needed because of the adoption of new or revised criteria, or because of changes occurring in the National Airspace System, such as the commissioning of new navigational facilities, adding new obstacles, or changing air traffic requirements. These changes are designed to provide safe and efficient use of the navigable airspace and to promote safe flight operations under instrument flight rules at the affected airports. DATES: This rule is effective March 29, 2018. The compliance date for each SIAP, associated Takeoff Minimums, and ODP is specified in the amendatory provisions. The incorporation by reference of certain publications listed in the regulations is approved by the Director of the Federal Register as of March 29, 2018. ADDRESSES: Availability of matters incorporated by reference in the amendment is as follows: SUMMARY: For Examination 1. U.S. Department of Transportation, Docket Ops-M30, 1200 New Jersey Avenue SE, West Bldg., Ground Floor, Washington, DC, 20590–0001. 2. The FAA Air Traffic Organization Service Area in which the affected airport is located; 3. The office of Aeronautical Navigation Products, 6500 South MacArthur Blvd., Oklahoma City, OK 73169 or, 4. The National Archives and Records Administration (NARA). For information on the availability of this material at NARA, call 202–741–6030, or go to: http://www.archives.gov/ federal_register/code_of_federal_ regulations/ibr_locations.html. E:\FR\FM\29MRR1.SGM 29MRR1

Agencies

[Federal Register Volume 83, Number 61 (Thursday, March 29, 2018)]
[Rules and Regulations]
[Pages 13410-13411]
From the Federal Register Online via the Government Publishing Office [www.gpo.gov]
[FR Doc No: 2018-06335]


-----------------------------------------------------------------------

DEPARTMENT OF TRANSPORTATION

Federal Aviation Administration

14 CFR Part 93

[Docket No. FAA-2004-17005; Amdt. No. 93-91A]
RIN 2120-AI17


Washington, DC Metropolitan Area Special Flight Rules Area; 
Technical Amendment

AGENCY: Federal Aviation Administration, DOT.

ACTION: Final rule; technical amendment.

-----------------------------------------------------------------------

SUMMARY: Currently, FAA regulations require all pilots operating 
aircraft to or from College Park Airport, Potomac Airfield or 
Washington Executive/Hyde Field Airport to file instrument flight rules 
(IFR), DC Flight Restricted Zone (FRZ), or DC Special Flight Rules Area 
(SFRA) flight plans with the Washington Hub Flight Service Station 
(FSS). The FAA is transferring the responsibility for processing flight 
plans within the DC FRZ from the Washington Hub FSS to the Washington 
Air Route Traffic Control Center (ARTCC). This document revises the 
regulations by updating the organization responsible for processing the 
flight plans and by updating the flight plans required for flight 
operations in the DC FRZ.

DATES: Effective on March 29, 2018.

FOR FURTHER INFORMATION CONTACT: Scott Rosenbloom, Airspace and Rules, 
AJV-113, Federal Aviation Administration, 800 Independence Avenue SW, 
Washington, DC 20591; telephone (202) 267-3783; email 
[email protected].

SUPPLEMENTARY INFORMATION: 

Good Cause for Immediate Adoption Without Prior Notice

    Section 553(b)(3)(B) of the Administrative Procedure Act (APA) (5 
U.S.C. 551 et seq.) authorizes agencies to dispense with notice and 
comment procedures for rules when the agency for ``good cause'' finds 
that those procedures are ``impracticable, unnecessary, or contrary to 
the public interest.'' Under this section, an agency, upon finding good 
cause, may issue a final rule without seeking comment prior to the 
rulemaking.
    Section 553(d)(3) of the Administrative Procedure Act requires that 
agencies publish a rule not less than 30 days before its effective 
date, except as otherwise provided by the agency for good cause found 
and published with the rule.
    This document revises Sec.  93.343(a) of title 14 of the Code of 
Federal Regulations (14 CFR) by updating the organization responsible 
for processing IFR and FRZ flight plans from/to College Park, Potomac 
Airfield, and Washington Executive/Hyde Field airports. This revision 
will not impose any additional restrictions on the persons affected by 
these regulations. Furthermore, any additional delay in revising the 
regulations would be contrary to the public interest because it would 
create confusion among pilots operating in the DC SFRA including the DC 
FRZ. Accordingly, the FAA finds that (i) public comment on this change 
prior to promulgation is unnecessary and contrary to public interest, 
and (ii) good cause exists to make this rule effective in less than 30 
days.

Background

    Currently, Sec.  93.343(a) requires pilots to file IFR, DC FRZ, or 
DC SFRA flight plans with the Washington Hub FSS for each departure and 
arrival from/to College Park, Potomac Airfield, and Washington 
Executive/Hyde Field Airports, whether or not the aircraft makes an 
immediate stop.
    An objective of the Administrator's Flight Service National 
Airspace System (NAS) Efficient Streamlined Services Initiative is to 
realign activities through more efficient delivery of services. As part 
of this initiative, the FAA is

[[Page 13411]]

transferring the responsibility for processing IFR and DC FRZ flight 
plans within the Washington DC Flight Restricted Zone from the 
Washington Hub FSS to the Flight Data Unit (FDU) at Washington ARTCC. 
This transition will occur on March 29, 2018. As a result, the FAA is 
updating Sec.  93.343(a) to reflect the change in responsibility.\1\
---------------------------------------------------------------------------

    \1\ The FAA notes that this change in responsibility will also 
generate a change in the dedicated phone number used for pilots to 
confirm their flight plan. Therefore, the FAA is also revising its 
Orders to update the phone number and organization responsible for 
filing IFR and DC FRZ flight plans.
---------------------------------------------------------------------------

    Also as a result of the transition, the FAA is removing from 
Sec. Sec.  93.341(d) and 93.343(a)(2) the references to the DC SFRA 
flight plan. Both regulations govern flight operations within the DC 
FRZ, which require a DC FRZ flight plan. Because a single entity was 
responsible for processing both DC SFRA and DC FRZ flight plans, the 
FAA has effectively construed any request for a DC SFRA flight plan to/
from a location within the DC FRZ as a DC FRZ flight plan. Once the 
responsibilities for processing DC SFRA and DC FRZ flight plans are 
divided between two entities, however, the FAA will no longer be able 
to re-characterize a DC SFRA flight plan as a DC FRZ flight plan. The 
FAA is, therefore, removing the references to the DC SFRA from 
Sec. Sec.  93.341(d) and 93.343(a)(2) to make clear that a pilot must 
file either an IFR or DC FRZ flight plan when operating to or from the 
DC FRZ.
    Furthermore, the FAA notes that it has communicated with the 
Transportation Security Administration (TSA) about a corresponding 
technical amendment that must be made to 49 CFR 1562.3(g)(1) to include 
the new organization responsible for processing IFR and DC FRZ flight 
plans.

Technical Amendment

    In this technical amendment, the FAA is revising Sec.  93.343(a)(2) 
and (3) by removing the references to the Washington Hub FSS. In their 
place, the FAA is inserting references to the Washington ARTCC, which 
is the new organization responsible for processing the flight plans. 
Furthermore, the FAA is revising Sec. Sec.  93.341(d) and 93.343(a)(2) 
by removing the references to the DC SFRA flight plan.

List of Subjects in 14 CFR Part 93

    Air traffic control, Airports, Navigation (air), Reporting and 
recordkeeping requirements.

The Amendment

    In consideration of the foregoing, the Federal Aviation 
Administration amends chapter I of title 14, Code of Federal 
Regulations as follows:

PART 93--SPECIAL AIR TRAFFIC RULES

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

    Authority:  49 U.S.C. 106(f), 106(g), 40103, 40106, 40109, 
40113, 44502, 44514, 44701, 44715, 44719, 46301.


0
 2. Amend Sec.  93.341 by revising paragraph (d) to read as follows:


Sec.  93.341   Aircraft operations in the DC FRZ.

* * * * *
    (d) Before departing from an airport within the DC FRZ, or before 
entering the DC FRZ, all aircraft, except DOD, law enforcement, and 
lifeguard or air ambulance aircraft operating under an FAA/TSA airspace 
authorization must file and activate an IFR or a DC FRZ flight plan and 
transmit a discrete transponder code assigned by an Air Traffic Control 
facility. Aircraft must transmit the discrete transponder code at all 
times while in the DC FRZ or DC SFRA.


0
 3. Amend Sec.  93.343 by revising paragraphs (a)(2) and (a)(3) to read 
as follows:


Sec.  93.343  Requirements for aircraft operations to or from College 
Park Airport, Potomac Airfield, or Washington Executive/Hyde Field 
Airport.

    (a) * * *
    (2) Before departing, the pilot files an IFR or DC FRZ flight plan 
with the Washington Air Route Traffic Control Center for each departure 
and arrival from/to College Park, Potomac Airfield, and Washington 
Executive/Hyde Field airports, whether or not the aircraft makes an 
intermediate stop;
    (3) When filing a flight plan with the Washington Air Route Traffic 
Control Center, the pilot identifies himself or herself by providing 
the assigned pilot identification code. The Washington Air Route 
Traffic Control Center will accept the flight plan only after verifying 
the code; and
* * * * *

    Issued under the authority of 49 U.S.C. 106(f) and (g) and 40103 
in Washington, DC.
Lirio Liu,
Executive Director, Office of Rulemaking.
[FR Doc. 2018-06335 Filed 3-28-18; 8:45 am]
 BILLING CODE 4910-13-P