83 FR 13410 - Washington, DC Metropolitan Area Special Flight Rules Area; Technical Amendment

DEPARTMENT OF TRANSPORTATION
Federal Aviation Administration

Federal Register Volume 83, Issue 61 (March 29, 2018)

Page Range		13410-13411
FR Document		2018-06335

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.

Federal Register, Volume 83 Issue 61 (Thursday, March 29, 2018)

[Federal Register Volume 83, Number 61 (Thursday, March 29, 2018)]
[Rules and Regulations]
[Pages 13410-13411]
From the Federal Register Online  [www.thefederalregister.org]
[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

Federal Register / Vol. 83, No. 61 / Thursday, March 29, 2018 / Rules and Regulations 13411

transferring the responsibility for amends chapter I of title 14, Code of DEPARTMENT OF TRANSPORTATION
processing IFR and DC FRZ flight plans Federal Regulations as follows:
within the Washington DC Flight Federal Aviation Administration
Restricted Zone from the Washington PART 93—SPECIAL AIR TRAFFIC
Hub FSS to the Flight Data Unit (FDU) RULES 14 CFR Part 97
at Washington ARTCC. This transition
[Docket No. 31184; Amdt. No. 3791]
will occur on March 29, 2018. As a ■ 1. The authority citation for part 93
result, the FAA is updating § 93.343(a) continues to read as follows: Standard Instrument Approach
to reflect the change in responsibility.1 Procedures, and Takeoff Minimums
Authority: 49 U.S.C. 106(f), 106(g), 40103,
Also as a result of the transition, the
40106, 40109, 40113, 44502, 44514, 44701, and Obstacle Departure Procedures;
FAA is removing from §§ 93.341(d) and
44715, 44719, 46301. Miscellaneous Amendments
93.343(a)(2) the references to the DC
SFRA flight plan. Both regulations AGENCY: Federal Aviation
■ 2. Amend § 93.341 by revising
govern flight operations within the DC Administration (FAA), DOT.
paragraph (d) to read as follows:
FRZ, which require a DC FRZ flight ACTION: Final rule.
plan. Because a single entity was § 93.341 Aircraft operations in the DC FRZ.
responsible for processing both DC SUMMARY: This rule establishes, amends,
* * * * *
SFRA and DC FRZ flight plans, the FAA suspends, or removes Standard
has effectively construed any request for (d) Before departing from an airport Instrument Approach Procedures
a DC SFRA flight plan to/from a location within the DC FRZ, or before entering (SIAPs) and associated Takeoff
within the DC FRZ as a DC FRZ flight the DC FRZ, all aircraft, except DOD, Minimums and Obstacle Departure
plan. Once the responsibilities for law enforcement, and lifeguard or air Procedures (ODPs) for operations at
processing DC SFRA and DC FRZ flight ambulance aircraft operating under an certain airports. These regulatory
plans are divided between two entities, FAA/TSA airspace authorization must actions are needed because of the
however, the FAA will no longer be able file and activate an IFR or a DC FRZ adoption of new or revised criteria, or
to re-characterize a DC SFRA flight plan flight plan and transmit a discrete because of changes occurring in the
as a DC FRZ flight plan. The FAA is, transponder code assigned by an Air National Airspace System, such as the
therefore, removing the references to the Traffic Control facility. Aircraft must commissioning of new navigational
DC SFRA from §§ 93.341(d) and transmit the discrete transponder code facilities, adding new obstacles, or
93.343(a)(2) to make clear that a pilot at all times while in the DC FRZ or DC changing air traffic requirements. These
must file either an IFR or DC FRZ flight SFRA. changes are designed to provide safe
plan when operating to or from the DC and efficient use of the navigable
FRZ. ■ 3. Amend § 93.343 by revising airspace and to promote safe flight
Furthermore, the FAA notes that it paragraphs (a)(2) and (a)(3) to read as operations under instrument flight rules
has communicated with the follows: at the affected airports.
Transportation Security Administration DATES: This rule is effective March 29,
(TSA) about a corresponding technical § 93.343 Requirements for aircraft 2018. The compliance date for each
amendment that must be made to 49 operations to or from College Park Airport, SIAP, associated Takeoff Minimums,
CFR 1562.3(g)(1) to include the new Potomac Airfield, or Washington Executive/ and ODP is specified in the amendatory
organization responsible for processing Hyde Field Airport.
provisions.
IFR and DC FRZ flight plans. (a) * * * The incorporation by reference of
Technical Amendment (2) Before departing, the pilot files an certain publications listed in the
regulations is approved by the Director
In this technical amendment, the FAA IFR or DC FRZ flight plan with the
of the Federal Register as of March 29,
is revising § 93.343(a)(2) and (3) by Washington Air Route Traffic Control
2018.
removing the references to the Center for each departure and arrival
Washington Hub FSS. In their place, the ADDRESSES: Availability of matters
from/to College Park, Potomac Airfield,
FAA is inserting references to the and Washington Executive/Hyde Field incorporated by reference in the
Washington ARTCC, which is the new amendment is as follows:
airports, whether or not the aircraft
organization responsible for processing makes an intermediate stop; For Examination
the flight plans. Furthermore, the FAA
(3) When filing a flight plan with the 1. U.S. Department of Transportation,
is revising §§ 93.341(d) and 93.343(a)(2)
Washington Air Route Traffic Control Docket Ops-M30, 1200 New Jersey
by removing the references to the DC
SFRA flight plan. Center, the pilot identifies himself or Avenue SE, West Bldg., Ground Floor,
herself by providing the assigned pilot Washington, DC, 20590–0001.
List of Subjects in 14 CFR Part 93 identification code. The Washington Air 2. The FAA Air Traffic Organization
Air traffic control, Airports, Route Traffic Control Center will accept Service Area in which the affected
Navigation (air), Reporting and the flight plan only after verifying the airport is located;
recordkeeping requirements. code; and 3. The office of Aeronautical
Navigation Products, 6500 South
The Amendment * * * * *
MacArthur Blvd., Oklahoma City, OK
In consideration of the foregoing, the Issued under the authority of 49 U.S.C. 73169 or,
rmajette on DSKBCKNHB2PROD with RULES

Federal Aviation Administration 106(f) and (g) and 40103 in Washington, DC. 4. The National Archives and Records
Lirio Liu, Administration (NARA). For
1 The FAA notes that this change in responsibility
Executive Director, Office of Rulemaking. information on the availability of this
will also generate a change in the dedicated phone material at NARA, call 202–741–6030,
number used for pilots to confirm their flight plan. [FR Doc. 2018–06335 Filed 3–28–18; 8:45 am]
Therefore, the FAA is also revising its Orders to
or go to: http://www.archives.gov/
BILLING CODE 4910–13–P
update the phone number and organization federal_register/code_of_federal_
responsible for filing IFR and DC FRZ flight plans. regulations/ibr_locations.html.

VerDate Sep<11>2014 15:09 Mar 28, 2018 Jkt 244001 PO 00000 Frm 00037 Fmt 4700 Sfmt 4700 E:\FR\FM\29MRR1.SGM 29MRR1

Document Created: 2018-03-29 00:26:15
Document Modified: 2018-03-29 00:26:15

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		Rules and Regulations
Action		Final rule; technical amendment.
Dates		Effective on March 29, 2018.
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]
FR Citation		83 FR 13410
RIN Number		2120-AI17
CFR Associated		Air Traffic Control; Airports; Navigation (air) and Reporting and Recordkeeping Requirements

83 FR 13410 - Washington, DC Metropolitan Area Special Flight Rules Area; Technical Amendment

DEPARTMENT OF TRANSPORTATIONFederal Aviation Administration

Federal Register Volume 83, Issue 61 (March 29, 2018)

DEPARTMENT OF TRANSPORTATION
Federal Aviation Administration