Federal Aviation Administration Seal
FAA.gov Home  
Sample XML Data Packet NOTAM Number : FDC 7/0206 Download shapefiles
Issue Date : July 27, 2007 at 1640 UTC
Location : Washington Center , Washington, District of Columbia
Beginning Date and Time : August 30, 2007 at 0500 UTC
Ending Date and Time : Until further notice
Reason for NOTAM : Temporary flight restrictions for Special Security Reasons
Type : Security
Replaced NOTAM(s) : N/A
Pilots May Contact : Washington Hub (DCA) Automated Flight Service Station, 866-225-7410
Jump To:       Affected Areas
Operating Restrictions and Requirements
Other Information
Affected Area(s) Top
Area A
Airspace Definition:
Center: WASHINGTON VOR/DME(DCA) (Latitude: 38º51'34"N, Longitude: 77º02'11"W)
Radius: 30 nautical miles
Altitude: From the surface up to but not including 18000 feet MSL
Effective Date(s):
From August 30, 2007 at 0500 UTC (August 30, 2007 at 0100 EDT)
Until further notice
Area B
Airspace Definition:
Region bounded by:
Latitude: Longitude: FRD:
39º12'20"N 77º29'57"W
39º02'52"N 77º29'57"W
39º02'50"N 77º30'11"W
39º02'48"N 77º30'19"W
39º02'46"N 77º30'29"W
39º02'45"N 77º30'37"W
39º02'43"N 77º30'45"W
39º02'41"N 77º30'52"W
39º02'38"N 77º31'00"W
39º02'35"N 77º31'13"W
39º02'32"N 77º31'23"W
39º02'30"N 77º31'32"W
39º02'27"N 77º31'41"W
39º02'24"N 77º31'50"W
39º02'22"N 77º31'58"W
39º02'18"N 77º32'07"W
39º02'15"N 77º32'15"W
39º02'11"N 77º32'24"W
39º02'07"N 77º32'34"W
39º02'02"N 77º32'44"W
39º01'57"N 77º32'52"W
39º01'53"N 77º33'00"W
39º01'51"N 77º33'05"W
39º01'47"N 77º33'16"W
39º01'43"N 77º33'23"W
39º01'40"N 77º33'30"W
39º01'40"N 77º38'25"W
39º01'45"N 77º38'22"W
39º01'51"N 77º38'19"W
39º01'58"N 77º38'16"W
39º02'06"N 77º38'12"W
39º02'15"N 77º38'08"W
39º02'23"N 77º38'04"W
39º02'30"N 77º38'00"W
39º02'36"N 77º37'57"W
39º02'41"N 77º37'54"W
39º02'46"N 77º37'52"W
39º02'51"N 77º37'49"W
39º02'56"N 77º37'46"W
39º03'01"N 77º37'44"W
39º03'06"N 77º37'41"W
39º03'12"N 77º37'37"W
39º03'18"N 77º37'35"W
39º03'24"N 77º37'31"W
39º03'27"N 77º37'30"W
39º03'35"N 77º37'26"W
39º03'42"N 77º37'22"W
39º03'48"N 77º37'19"W
39º03'55"N 77º37'15"W
39º04'02"N 77º37'11"W
39º04'08"N 77º37'07"W
39º04'15"N 77º37'03"W
39º04'21"N 77º36'59"W
39º04'30"N 77º36'54"W
39º04'36"N 77º36'50"W
39º04'41"N 77º36'47"W
39º04'48"N 77º36'42"W
39º04'57"N 77º36'36"W
39º05'04"N 77º36'32"W
39º05'13"N 77º36'26"W
39º05'22"N 77º36'21"W
39º05'31"N 77º36'14"W
39º05'40"N 77º36'09"W
39º05'48"N 77º36'03"W
39º05'55"N 77º35'58"W
39º06'02"N 77º35'54"W
39º06'07"N 77º35'50"W
39º06'13"N 77º35'46"W
39º06'21"N 77º35'40"W
39º06'29"N 77º35'35"W
39º06'36"N 77º35'29"W
39º06'41"N 77º35'24"W
39º06'47"N 77º35'20"W
39º06'53"N 77º35'16"W
39º07'00"N 77º35'10"W
39º07'08"N 77º35'04"W
39º07'12"N 77º35'00"W
39º07'19"N 77º34'55"W
39º07'26"N 77º34'49"W
39º07'32"N 77º34'44"W
39º07'38"N 77º34'40"W
39º07'47"N 77º34'33"W
39º07'53"N 77º34'28"W
39º08'00"N 77º34'22"W
39º08'06"N 77º34'17"W
39º08'11"N 77º34'12"W
39º08'16"N 77º34'08"W
39º08'22"N 77º34'03"W
39º08'27"N 77º33'59"W
39º08'35"N 77º33'52"W
39º08'42"N 77º33'46"W
39º08'48"N 77º33'41"W
39º08'54"N 77º33'35"W
39º09'01"N 77º33'29"W
39º09'08"N 77º33'22"W
39º09'13"N 77º33'18"W
39º09'20"N 77º33'11"W
39º09'27"N 77º33'03"W
39º09'34"N 77º32'57"W
39º09'42"N 77º32'50"W
39º09'46"N 77º32'45"W
39º09'52"N 77º32'40"W
39º09'59"N 77º32'32"W
39º10'06"N 77º32'26"W
39º10'12"N 77º32'19"W
39º10'18"N 77º32'13"W
39º10'25"N 77º32'06"W
39º10'34"N 77º31'58"W
39º10'41"N 77º31'51"W
39º10'47"N 77º31'46"W
39º10'52"N 77º31'39"W
39º10'57"N 77º31'34"W
39º11'01"N 77º31'29"W
39º11'06"N 77º31'23"W
39º11'11"N 77º31'17"W
39º11'16"N 77º31'11"W
39º11'22"N 77º31'05"W
39º11'28"N 77º30'58"W
39º11'33"N 77º30'52"W
39º11'40"N 77º30'44"W
39º11'45"N 77º30'38"W
39º11'52"N 77º30'30"W
39º11'57"N 77º30'24"W
39º12'02"N 77º30'19"W
39º12'07"N 77º30'12"W
39º12'12"N 77º30'07"W
39º12'17"N 77º30'01"W
39º12'20"N 77º29'57"W
Altitude: From the surface up to but not including 18000 feet MSL
Effective Date(s):
From August 30, 2007 at 0500 UTC (August 30, 2007 at 0100 EDT)
Until further notice
7/0206
 
Click for Larger Map
Click for Sectional
NOTAM Text
Operating Restrictions and Requirements Top
No pilots may operate an aircraft in the areas covered by this NOTAM (except as described).
This notice and another, separate notice for the Flight Restricted Zone (DC FRZ) replaces previously issued FDC NOTAMs 6/2550 and 7/7778 for the DC ADIZ/FRZ. Effective 0708300500 UTC the NOTAMs describing temporary flight restrictions (TFRS) for the Washington, D.C. Metropolitan Area Air Defense Identification Zone (DC ADIZ) and Washington, D.C. Metropolitan Flight Restricted Zone (DC FRZ) will be replaced by a single NOTAM published in the Notice To Airman Publication (Class II) as the DC Metropolitan ADIZ/FRZ NOTAM. Pursuant to 49 USC 40103(b), the Federal Aviation Administration (FAA) classifies the DC ADIZ as "National Defense Airspace." any person who knowingly or willfully violates the rules concerning operations in this airspace is subject to certain criminal penalties under 49 USC 46307. Pilots who do not adhere to the following procedures may be intercepted, detained and interviewed by federal law enforcement/security personnel and/or DoD. It is recommended that all pilots flying under Visual Flight Rules (VFR) within 100 NM of the Washington /DCA/ VOR/DME complete special awareness training for the Washington DC Metropolitan Area. This training is available in the aviation learning center at http://www.faasafety.gov.

Pursuant to 14 CFR Sections 99.7, Special Security Instructions and 91.139, Emergency Air Traffic Rules, the following procedures are in effect for the DC ADIZ and aircraft flight operations are prohibited except as specified below and/or unless authorized by the Air Traffic Security Coordinator via the Domestic Events Network (DEN).

Part I. Standard DC ADIZ operating requirements: to operate an aircraft, including ultra-light vehicles and unmanned air systems, in the DC ADIZ, a person must meet the following operating requirements, except if conducting operations under Part II, Part III, Part IV, or Part V of this notice:

  1. The aircraft must be equipped with an operable two-way radio capable of communicating with Air Traffic Control (ATC) on appropriate radio frequencies. Aircraft must monitor VHF guard 121.5 or UHF 243.0 if able.

  2. The aircraft must be equipped with an operating transponder with automatic altitude reporting capability as specified under 14 CFR Section 91.215.

  3. Except for DoD, law enforcement aircraft and wavered lifeguard/aeromedical flights, pilots must file and activate an IFR flight plan or, for VFR, a DC ADIZ flight plan before entering the DC ADIZ.

  4. For VFR operations, the FAA will consider the DC ADIZ flight plan to enter/exit the DC ADIZ open when the pilot obtains a discrete transponder code, and will consider the DC ADIZ flight plan closed upon landing at an airport within the DC ADIZ, or when the aircraft exits the DC ADIZ.

  5. Before departing from an airport within the DC ADIZ or before entering the DC ADIZ, pilots must obtain a discrete transponder code from ATC and must continuously squawk that code until leaving the DC ADIZ or landing at an airport within the DC ADIZ. ATC may delay entry into the DC ADIZ due to operational considerations.

  6. Do not squawk 1200 at any time while in the DC ADIZ.

  7. Pilots must establish and maintain two-way radio communications with the appropriate ATC facility before entering and while operating in the DC ADIZ, except as provided in Part III, Part IV, and Part V.

  8. Except for approved DoD, law enforcement, and wavered lifeguard/aeromedical flights, all VFR aircraft operations within the DC ADIZ are restricted to an indicated airspeed of 180 knots or less, if capable. If unable the pilot must contact the appropriate ATC facility and advise them of the aircraft's operational limitations.

  9. Pilots must obtain an appropriate clearance before operating within Class B airspace and must establish two-way communications with the ATC facility providing air traffic services before entering Class D airspace.


Part II. VFR DC ADIZ traffic pattern operations at towered airports:

  1. Pilots conducting VFR traffic pattern operations (not including practice instrument approaches) at an airport with an operational airport traffic control tower within the DC ADIZ must meet the following requirements. Pilots must:


A. Request closed pattern work before departure or if airborne, before traffic pattern entry.

B. Remain in two-way radio communication with the tower.

C. Continuously squawk transponder code 1234.

D. DoD aircraft operating in the VFR traffic pattern of a military airport may be assigned a discrete code other than 1234.

E. Aircraft must monitor VHF guard 121.5 or UHF 243.0 if able.

  1. Before exiting the traffic pattern or conducting any other flight operations within the DC ADIZ, pilots must comply with the standard DC ADIZ operating requirements as described in part I of this notice.


Part III. VFR DC ADIZ traffic pattern operations at non-towered airports:

  1. Pilots conducting VFR traffic pattern operations (not including practice instrument approaches) at an airport with no operating airport traffic control tower within the DC ADIZ must meet the following requirements. Pilots must:


A. File a DC ADIZ flight plan for pattern work.

B. Obtain and squawk the ATC-assigned discrete transponder code.

C. Communicate pattern position via the published CTAF.

D. Aircraft must monitor VHF guard 121.5 or UHF 243.0 if able.

  1. Before exiting the traffic pattern or conducting any other flight operations within the DC ADIZ, pilots must comply with the standard DC ADIZ operating requirements as described in part i of this notice.


Part IV. VFR DC ADIZ procedures for Leesburg Executive Airport (JYO):

  1. VFR egress procedures for JYO: the following egress procedures apply to the JYO airport maneuvering area:


A. Pilots must file a DC ADIZ flight plan prior to departure.

B. Aircraft must squawk transponder code 1226 to indicate the pilot's intent to depart the DC ADIZ.

C. Pilots must exit the DC ADIZ via the most direct route through the JYO airport maneuvering area, defined in Part VII of this notice, before proceeding on course.

D. Pilots need not communicate with the Potomac TRACON unless otherwise directed.

E. Pilots departing JYO must activate the DC ADIZ flight plan by announcing aircraft call sign, aircraft type and intended departure runway on the published CTAF prior to departure. For JYO egress, the DC ADIZ flight plan will be considered closed when the aircraft has exited the DC ADIZ.

  1. VFR ingress procedures for JYO: the following ingress procedures apply to the JYO airport maneuvering area:


A. Pilots must file a DC ADIZ flight plan prior to entering the DC ADIZ.

B. Aircraft must squawk transponder code 1227 prior to entering the DC ADIZ to indicate the pilot's intent to enter the DC ADIZ and land at JYO.

C. Pilots must enter the DC ADIZ via the most direct route through the JYO maneuvering area, defined in Part VII of this notice.

D. Pilots need not communicate with the Potomac TRACON unless otherwise directed.

E. Before entering the DC ADIZ to land at JYO, pilots must activate the DC ADIZ flight plan by announcing aircraft call sign, aircraft type and runway of intended landing on the published CTAF. The DC ADIZ flight plan for JYO ingress will be considered closed when the aircraft has landed at JYO.

  1. Aircraft not utilizing the JYO airport maneuvering area must comply with standard DC ADIZ operating procedures as described in part I of this notice.


Part V. VFR DC ADIZ egress procedures for select airports: these procedures permit aircraft operating from select airports to exit the DC ADIZ by the shortest route without complying with the standard DC ADIZ operating requirements. These procedures apply only to aircraft exiting the DC ADIZ. These procedures do not authorize penetration of restricted areas.

  1. These procedures apply only to aircraft departing the following airports:


A. Barnes (MD47)

B. Flying M Farms (MD77)

C. Mountain Road (MD43)

D. Robinson (MD14)

E. Skyview (51VA)

F. Vint Hill Farms Station (04VA)

  1. The following egress procedures apply:


A. Pilots are not required to file a DC ADIZ flight plan, as defined in Part VII of this notice, prior to departure.

B. Aircraft must squawk code 1205 to indicate pilot's intent to depart the DC ADIZ.

C. Pilots must exit the DC ADIZ via the most direct route before proceeding on course.

D. Pilots need not communicate with the Potomac TRACON unless otherwise directed.

E. Pilots arriving at one of the above airports, or transiting the DC ADIZ, must comply with standard DC ADIZ operating procedures as described in Part I of this notice.

F. Aircraft must monitor VHF guard 121.5 or UHF 243.0 if able.

Part VI. Transponder failure: any person operating an aircraft within the DC ADIZ who becomes aware of an inability to comply with the requirement to continuously squawk the ATC assigned transponder code must immediately request control instructions and comply with all instructions from ATC. If unable to contact ATC, pilots must exit the DC ADIZ by the most direct lateral route. These procedures do not authorize penetration of restricted areas and prohibited areas.

Part VII. Definitions:

  1. For purposes of this NOTAM only, the DC ADIZ is that 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 ADIZ is that airspace, from the surface to but not including FL180, within a 30-mile radius of 385134N/0770211W or the DCA VOR/DME.

  2. The Leesburg maneuvering area within the DC ADIZ is defined as the airspace around the Leesburg Executive Airport (JYO) bounded by a line beginning at the Washington /DCA/ VOR/DME 299 degree radial at 30NM 390139.1N/0773826.7W, thence clockwise along the DCA 30 NM arc to the DCA 323 degree radial at 30 NM 391220.1N/0772957.6W, thence south via a line drawn to the AML 355 degree radial at 7 NM 390254.9N/0773000.3W, thence counterclockwise along the AML 7 NM arc to the AML 331 degree radial at 7 NM 390139.3N/0773325.5W, thence west via a line drawn to the point of beginning.

  3. The transponder requirements described in this notice are solely for security tracking purposes and do not imply ATC radar services, unless the pilot requests, and ATC agrees to provide, the additional services. The communications requirements contained herein are for maintaining the ability to immediately communicate security-based instructions, not ATC services, unless ATC services are otherwise requested and approved.

  4. For purposes of this NOTAM only, a DC ADIZ flight plan is defined as a flight plan filed for the sole purpose of complying with the security requirements for VFR operation into or out of the DC ADIZ. The DC ADIZ flight plan is separate and distinct from a standard VFR flight plan. There is no search and rescue associated with DC ADIZ flight plans.


Part VIII. Resources: direct any questions on the DC ADIZ to the FAA representative at the National Capital Region Coordination Center (NCRCC), telephone 866-598-9522. Information about waiver applications and TSA security authorization can be found at

http://www.tsa.gov/what_we_do/ga/waiver-forms.shtm (case sensitive - use lower case only), or call the National Capital Region Coordination Center (NCRCC), telephone 866-598-9522, Washington Hub Flight Service Station (FSS), telephone 866-225-7410.
Other Information: Top
ARTCC: ZDC - Washington Center
Point of Contact: National Capital Region Coordination Center
Telephone 866-598-9522
Authority: Title 14 CFR section 99.7
Depicted TFR data may not be a complete listing. Pilots should not use the information on this website for flight planning purposes. For the latest information, call your local Flight Service Station at 1-800-WX-BRIEF.
Federal Aviation Administration   |   800 Independence Avenue, SW   |   Washington DC, 20591