Washington, DC Metropolitan Area Special Flight Rules Area

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
File:070727 New Washington ADIZ-FRZ.jpg
The new Washington ADIZ (red line) compared to the old ADIZ (green line).

An Air Defense Identification Zone (ADIZ) has existed since February 10, 2003,[1] around the Baltimore-Washington Metropolitan Area to restrict air traffic near Washington, D.C.

The ADIZ was established as a precursor to the US invasion of Iraq in 2003.[2] It has been erroneously connected to the September 11 attacks as a temporary measure to prevent further attacks. It was made permanent in 2008.[3]

Despite efforts by the Federal Aviation Administration to inform pilots of the ADIZ, there are still many unauthorized incursions by unsuspecting pilots. A pilot who violates the boundaries may be intercepted by military aircraft and escorted to the nearest airport.[4][5][6]

Creation

The ADIZ (now known collectively as a Flight Restricted Zone and Special Flight Rules Area) was created by the FAA in response to demands by a working group that became formalized as the National Capital Region Coordination Center. The U.S. Congress has never legitimized these restrictions, and any consideration of opposing the Executive Branch's actions became politically unpalatable in the wake of two mishaps that led to the evacuation of the Capitol.[7][8] One involved a plane carrying Ernie Fletcher, the Governor of Kentucky. The other, almost a year later, involved a Cessna 150 flown by a student pilot accompanied by a pilot who was not familiar with the ADIZ rules, using an outdated chart.

Flight Restricted Zone

Within the ADIZ is an even more sensitive zone designated the Washington, D.C. Metropolitan Area Flight Restricted Zone (DC FRZ). The DC FRZ extends approximately 13–15 nautical miles (15–17 statute miles) around the VOR/DME located at the Ronald Reagan Washington National Airport. Flight within the FRZ is restricted to governmental, certain scheduled commercial and a limited set of waivered flights. Three general aviation airports (known as the "Maryland 3" or the "DC 3") are located inside the DC FRZ. The "Maryland 3" are College Park Airport (CGS), Washington Executive/Hyde Field (W32), and Potomac Airport (VKX).[9]


Public opposition

Pilots' groups, led by the Aircraft Owners and Pilots Association (AOPA), have argued that the ADIZ is unnecessary and has a harmful effect on the economy of small airports and aviation-related businesses in and near the ADIZ.[10] Pilots involved in law enforcement have described the ADIZ as a "major, unnecessary burden on pilots and air traffic controllers with almost no increased security benefit."[11] AOPA and other groups are hoping to persuade Congress to lift or ease the ADIZ restrictions from Washington airspace [1][dead link] – or at the very least to dramatically improve its operational aspects.

In 2006 the FAA issued a Notice of Proposed Rulemaking (NPRM) docket number 17005 concerning making the temporary rules permanent. Over 20,000 responses were received, the vast majority of them in opposition to making the temporary rules permanent.[12] There were two public hearings held by the FAA in the Washington D.C. area on the NPRM. All speakers were opposed to making the NPRM permanent.[citation needed] The FAA published transcripts of the public hearings. The transcripts were later withdrawn from the public as they were alleged to contain Sensitive Security Information, but were returned following review.[13]

Subsequent changes

On August 30, 2007, the FAA implemented new rules for air traffic controllers and issued revised NOTAMs for pilots flying in the ADIZ. Although the NOTAMs and FAA procedures state that no radar services will be provided to pilots unless requested, air traffic controllers at Potomac TRACON are providing such services. This is due to a memorandum from the Potomac TRACON Air Traffic Manager to air traffic controllers stating that a certain paragraph (2-1-2) of the Air Traffic Control handbook (7110.65) is still applicable when providing ATC Security Services.[14]

Effective February 9, 2009, any pilots flying VFR within a 60 nautical miles (110 km) radius centered on the ADIZ are required to complete training about the ADIZ. This training can be completed online through a course called "Navigating the New DC ADIZ" (now "DC Special Flight Rules Area").[15] Pilots may also complete the required training by attending a seminar offered at a Flight Standards District Office. Pilots must obtain a certificate which proves that the training has been completed. This certificate is not required to be carried with the pilot, but must be produced when requested from law enforcement or other agencies. Pilots flying IFR are not subject to this requirement.[16]

On February 17, 2009, the status of the ADIZ was scheduled to change from a temporary flight restriction to a permanent special flight rules area.[13] On February 6, 2009, White House officials declined a request to postpone the implementation.[17]

In February 2012, the FAA Modernization and Reform Act of 2012[18] required a joint plan to be submitted in 180 days by the Administrator of the Federal Aviation Administration, in consultation with the Secretaries of Homeland Security and Defense.

The plan shall outline specific changes to the D.C. Metropolitan Area Special Flight Rules Area that will decrease operational impacts and improve general aviation access to airports in the National Capital Region that are currently impacted by the zone.[18]

In June 2014, Leesburg airport traffic was granted authority to perform local traffic pattern practice without a SFRA plan filed while operating under tower control without departing the pattern.[19]

Original District of Columbia ADIZ

The old official entry and exit reference points for the ADIZ.

The original Washington ADIZ was somewhat larger and was roughly co-extensive with the Class B airspace around Washington. On August 30, 2007, the ADIZ was changed to a circle surrounding Washington, D.C., with a radius of 30 nautical miles (60 km), with a small triangular cutout for Leesburg Executive Airport. This change reduced the size of the ADIZ by 1,800 square miles (4,700 km2) and removed 33 airports from its coverage.

Laser warning system

In May 2005, NORAD started using a laser warning system to warn pilots that cross into restricted airspace. The bright laser beams, which flash red-red-green, are easily seen, even during daylight. The laser beams can be seen 15 to 20 miles away. Other pilots are unlikely to see the lasers because when activated the directional beams are pointed at the aircraft that has crossed into restricted airspace. Multiple lasers could be activated. These lasers do not harm the eyes of aircrew or passengers.[20][21][22]

File:NORAD, Laser Warning System, 1.jpg
This is a graphic to show what the NORAD Laser Warning System would look like.
File:NORAD, Laser Warning System, 2.jpg
This is what the NORAD Laser Warning System would look like in an aircraft that entered restricted airspace.

See also

References

  1. ↑ http://www.aopa.org/whatsnew/air_traffic/adiz.html
  2. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  3. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  4. ↑ http://www.gather.com/viewArticle.action?articleId=281474978717897
  5. ↑ http://www.msnbc.msn.com/id/40323858/ns/us_news-security/
  6. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  7. ↑ Brumfield, Sarah. "US Capitol Evacuated Over Unauthorized Aircraft In Airspace". http://www.huffingtonpost.com. 11 January 2011. Retrieved 5 June 2014.
  8. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  9. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  10. ↑ "ADIZ training rules too broad, won't fix problem, AOPA says": http://www.aopa.org/whatsnew/newsitems/2006/060907adiz.html
  11. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  12. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  13. ↑ 13.0 13.1 Lua error in package.lua at line 80: module 'strict' not found. Cite error: Invalid <ref> tag; name "aopanews" defined multiple times with different content
  14. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  15. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  16. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  17. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  18. ↑ 18.0 18.1 Lua error in package.lua at line 80: module 'strict' not found.
  19. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  20. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  21. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  22. ↑ Lua error in package.lua at line 80: module 'strict' not found.

External links

fi:ADIZ zh:防空識別區

Retrieved from "https://infogalactic.com/w/index.php?title=Washington,_DC_Metropolitan_Area_Special_Flight_Rules_Area&oldid=1120289"