Source: Doc. No. FAA–2004–17005, 73 FR 76213, Dec. 16, 2008, unless otherwise noted.
This subpart prescribes special air traffic rules for aircraft operating in the Washington, DC Metropolitan Area. Because identification and control of aircraft is required for reasons of national security, the areas described in this subpart constitute national defense airspace. The purpose of establishing this area is to facilitate the tracking of, and communication with, aircraft to deter persons who would use an aircraft as a weapon, or as a means of delivering weapons, to conduct an attack on persons, property, or buildings in the area. This subpart applies to pilots conducting any type of flight operations in the airspace designated as the Washington, DC Metropolitan Area Special Flight Rules Area (DC SFRA) (as defined in §93.335), which includes the airspace designated as the Washington, DC Metropolitan Area Flight Restricted Zone (DC FRZ) (as defined in §93.335).
(a) Any violation . The FAA may take civil enforcement action against a pilot for violations, whether inadvertent or intentional, including imposition of civil penalties and suspension or revocation of airmen's certificates.
(b) Knowing or willful violations . The DC FRZ and DC SFRA were established for reasons of national security under the provisions of 49 U.S.C. 40103(b)(3). Areas established by the FAA under that authority constitute “national defense airspace” as that term is used in 49 U.S.C. 46307. In addition to being subject to the provisions of paragraph (a) of this section, persons who knowingly or willfully violate national defense airspace established pursuant to 49 U.S.C. 40103(b)(3) may be subject to criminal prosecution.
For purposes of this subpart—
DC FRZ flight plan is a flight plan filed for the sole purpose of complying with the requirements for VFR operations into, out of, and through the DC FRZ. This flight plan is separate and distinct from a standard VFR flight plan, and does not include search and rescue services.
DC SFRA flight plan is a flight plan filed for the sole purpose of complying with the requirements for VFR operations into, out of, and through the DC SFRA. This flight plan is separate and distinct from a standard VFR flight plan, and does not include search and rescue services.
Fringe airports are the following airports located near the outer boundary of the Washington, DC Metropolitan Area Special Flight Rules Area: Barnes (MD47), Flying M Farms (MD77), Mountain Road (MD43), Robinson (MD14), and Skyview (51VA).
Washington, DC Metropolitan Area Flight Restricted Zone (DC FRZ) is an area bounded by a line beginning at the Washington VOR/DME (DCA) 311° radial at 15 nautical miles (NM) (Lat. 38°59'31" N., Long. 077°18'30" W.); then clockwise along the DCA 15 nautical mile arc to the DCA 002° radial at 15 NM (Lat. 39°06'28" N., Long 077°04'32" W.); then southeast via a line drawn to the DCA 049° radial at 14 NM (Lat. 39°02'18" N., Long. 076°50'38" W.); thence south via a line drawn to the DCA 064° radial at 13 NM (Lat. 38°59'01" N., Long. 076°48'32" W.); thence clockwise along the 13 NM arc to the DCA 276° radial at 13 NM (Lat.38°50'53" N., Long 077°18'48" W.); thence north to the point of beginning, excluding the airspace within a one nautical mile radius of the Freeway Airport, W00, Mitchellville, MD from the surface up to but not including flight level (FL) 180. The DC FRZ is within and part of the Washington, DC Metropolitan Area SFRA.
Washington, DC Metropolitan Area Special Flight Rules Area (DC SFRA) is an area of airspace over the surface of the earth where the ready identification, location, and control of aircraft is required in the interests of national security. Specifically, the DC SFRA is that airspace, from the surface to, but not including, FL 180, within a 30-mile radius of Lat. 38°51'34" N., Long. 077°02'11" W., or the DCA VOR/DME. The DC SFRA includes the DC FRZ.
[Doc. No. FAA–2004–17005, 73 FR 76213, Dec. 16, 2008; Admt. 93–91, 73 FR 79314, Dec. 29, 2008]
A pilot conducting any type of flight operation in the DC SFRA must comply with the restrictions listed in this subpart and all special instructions issued by the FAA in the interest of national security. Those special instructions may be issued in any manner the FAA considers appropriate, including a NOTAM. Additionally, a pilot must comply with all of the applicable requirements of this chapter.
(a) Except as provided in paragraphs (b) and (c) of this section and in §93.345, or unless authorized by Air Traffic Control, no pilot may operate an aircraft, including an ultralight vehicle or any civil aircraft or public aircraft, in the DC SFRA, including the DC FRZ, unless—
(1) The aircraft is equipped with an operable two-way radio capable of communicating with Air Traffic Control on appropriate radio frequencies;
(2) Before operating an aircraft in the DC SFRA, including the DC FRZ, the pilot establishes two-way radio communications with the appropriate Air Traffic Control facility and maintains such communications while operating the aircraft in the DC SFRA, including the DC FRZ;
(3) The aircraft is equipped with an operating automatic altitude reporting transponder;
(4) Before operating an aircraft in the DC SFRA, including the DC FRZ, the pilot obtains and transmits a discrete transponder code from Air Traffic Control, and the aircraft's transponder continues to transmit the assigned code while operating within the DC SFRA;
(5) For VFR operations, the pilot must file and activate a DC FRZ or DC SFRA flight plan by obtaining a discrete transponder code. The flight plan is closed upon landing at an airport within the DC SFRA or when the aircraft exits the DC SFRA;
(6) Before operating the aircraft into, out of, or through the Washington, DC Tri-Area Class B Airspace Area, the pilot receives a specific Air Traffic Control clearance to operate in the Class B airspace area; and
(7) Before operating the aircraft into, out of, or through Class D airspace area that is within the DC SFRA, the pilot complies with §91.129 of this chapter.
(b) Paragraph (a)(5) of this section does not apply to operators of Department of Defense aircraft, law enforcement operations, or lifeguard or air ambulance operations under an FAA/TSA airspace authorization, if the flight crew is in contact with Air Traffic Control and is transmitting an Air Traffic Control-assigned discrete transponder code.
(c) When operating an aircraft in the VFR traffic pattern at an airport within the DC SFRA (but not within the DC FRZ) that does not have an airport traffic control tower, a pilot must—
(1) File a DC SFRA flight plan for traffic pattern work;
(2) Communicate traffic pattern position via the published Common Traffic Advisory Frequency (CTAF);
(3) Monitor VHF frequency 121.5 or UHF frequency 243.0, if the aircraft is suitably equipped;
(4) Obtain and transmit the Air Traffic Control-assigned discrete transponder code; and
(5) When exiting the VFR traffic pattern, comply with paragraphs (a)(1) through (a)(7) of this section.
(d) When operating an aircraft in the VFR traffic pattern at an airport within the DC SFRA (but not within the DC FRZ) that has an operating airport traffic control tower, a pilot must—
(1) Before departure or before entering the traffic pattern, request to remain in the traffic pattern;
(2) Remain in two-way radio communications with the tower. If the aircraft is suitably equipped, the pilot must also monitor VHF frequency 121.5 or UHF frequency 243.0;
(3) Continuously operate the aircraft transponder on code 1234 unless Air Traffic Control assigns a different code; and
(4) Before exiting the traffic pattern, comply with paragraphs (a)(1) through (a)(7) of this section.
(e) Pilots must transmit the assigned transponder code. No pilot may use transponder code 1200 while in the DC SFRA.
(a) Except as provided in paragraph (b) of this section, no pilot may conduct any flight operation under part 91, 101, 103, 105, 125, 133, 135, or 137 of this chapter in the DC FRZ, unless the specific flight is operating under an FAA/TSA authorization.
(b) Department of Defense (DOD) operations, law enforcement operations, and lifeguard or air ambulance operations under an FAA/TSA airspace authorization are excepted from the prohibition in paragraph (a) of this section if the pilot is in contact with Air Traffic Control and operates the aircraft transponder on an Air Traffic Control-assigned beacon code.
(c) The following aircraft operations are permitted in the DC FRZ:
(1) Aircraft operations under the DCA Access Standard Security Program (DASSP) (49 CFR part 1562) with a Transportation Security Administration (TSA) flight authorization.
(2) Law enforcement and other U.S. Federal aircraft operations with prior FAA approval.
(3) Foreign-operated military and state aircraft operations with a State Department-authorized diplomatic clearance, with State Department notification to the FAA and TSA.
(4) Federal, State, Federal DOD contract, local government agency aircraft operations and part 121, 129 or 135 air carrier flights with TSA-approved full aircraft operator standard security programs/procedures, if operating with DOD permission and notification to the FAA and the National Capital Regional Coordination Center (NCRCC). These flights may land and depart Andrews Air Force Base, MD, with prior permission, if required.
(5) Aircraft operations maintaining radio contact with Air Traffic Control and continuously transmitting an Air Traffic Control-assigned discrete transponder code. The pilot must monitor VHF frequency 121.5 or UHF frequency 243.0.
(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 or a DC SFRA 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.
(a) A pilot may not operate an aircraft to or from College Park Airport, MD, Potomac Airfield, MD, or Washington Executive/Hyde Field Airport, MD unless—
(1) The aircraft and its crew and passengers comply with security rules issued by the TSA in 49 CFR part 1562, subpart A;
(2) Before departing, the pilot files an IFR or DC FRZ or DC SFRA flight plan with the Washington Hub Flight Service Station (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 intermediate stop;
(3) When filing a flight plan with the Washington Hub FSS, the pilot identifies himself or herself by providing the assigned pilot identification code. The Washington Hub FSS will accept the flight plan only after verifying the code; and
(4) The pilot complies with the applicable IFR or VFR egress procedures in paragraph (b), (c) or (d) of this section.
(b) If using IFR procedures, a pilot must—
(1) Obtain an Air Traffic Control clearance from the Potomac TRACON; and
(2) Comply with Air Traffic Control departure instructions from Washington Executive/Hyde Field, Potomac Airport, or College Park Airport. The pilot must then proceed on the Air Traffic Control-assigned course and remain clear of the DC FRZ.
(c) If using VFR egress procedures, a pilot must—
(1) Depart as instructed by Air Traffic Control and expect a heading directly out of the DC FRZ until the pilot establishes two-way radio communication with Potomac Approach; and
(2) Operate as assigned by Air Traffic Control until clear of the DC FRZ, the DC SFRA, and the Class B or Class D airspace area.
(d) If using VFR ingress procedures, the aircraft must remain outside the DC SFRA until the pilot establishes communications with Air Traffic Control and receives authorization for the aircraft to enter the DC SFRA.
(e) VFR arrivals:
(1) If landing at College Park Airport a pilot may receive routing via the vicinity of Freeway Airport; or
(2) If landing at Washington Executive/Hyde Field or Potomac Airport, the pilot may receive routing via the vicinity of Maryland Airport or the Nottingham VORTAC.
(a) A pilot may depart from a fringe airport as defined in §93.335 without filing a flight plan or communicating with Air Traffic Control, unless requested, provided:
(1) The aircraft's transponder transmits code 1205;
(2) The pilot exits the DC SFRA by the most direct route before proceeding on course; and
(3) The pilot monitors VHF frequency 121.5 or UHF frequency 243.0.
(b) No pilot may operate an aircraft arriving at a fringe airport or transit the DC SFRA unless that pilot complies with the DC SFRA operating procedures in this subpart.
| File Type | application/msword |
| File Title | 14 CFR Part 93 |
| Author | Taylor CTR Dahl |
| Last Modified By | Taylor CTR Dahl |
| File Modified | 2010-10-07 |
| File Created | 2010-10-07 |