Special flight rules area

In United States aviation, a special flight rules area (SFRA) is a region in which the normal regulations of flight do not apply in whole or in part, especially regulations concerning airspace classification, altitude, course, and speed restrictions, and the like.

Washington, DC Special Flight Rules Area
Main article: Washington, DC Metropolitan Area Special Flight Rules Area

Following the terrorist attacks of September 11, 2001, the airspace around Washington DC underwent a number of changes designed to restrict flying around the city. In 2003, a temporary flight rules area was created and was named the Washington DC Air Defense Identification Zone. In 2008 the temporary status of the ADIZ was removed and the rule was made permanent.[1]

In order to fly within the DC SFRA, pilots of general aviation aircraft are required to file a special flight rules flight plan, obtain a discrete transponder code, and remain in contact with air traffic control at all times.[2] Special training is required in order to fly within 60nm of the Washington DC (KDCA) VOR.[3]

Los Angeles Special Flight Rules Area

Long established in the Los Angeles basin is the Los Angeles SFRA. Los Angeles International Airport is surrounded by extensive Class B airspace, which is difficult for VFR traffic to navigate. In particular, the airport has four large runways running east/west that have airspace protection from 10,000 feet down to the surface that is 25 statute miles wide. This large swath of Class B airspace bisects Los Angeles and makes flights between the airports north of LAX and south of LAX require air traffic control to route these flights. To alleviate this load on ATC, the SFRA over LAX defines two exceptions to the Class B airspace to allow VFR aircraft to transit without control from ATC.

There are two routes, one for southeast-bound traffic and one for northwest-bound traffic. Both follow the 132° radial of the Santa Monica VOR between the Santa Monica Airport and the intersection of Interstate 405 and Imperial Highway. Southeast-bound traffic flies at 3,500 feet. Northwest-bound traffic flies at 4,500 feet. Despite being in the Class B airspace, aircraft following the rules of this corridor need not communicate with ATC.

The rules are fairly simple: Turn on all practical lights, day or night. Squawk 1201. Do not exceed 140 knots IAS. Monitor and self-report on 128.55 MHz. Have a copy of the Los Angeles TAC in the aircraft. No jets.[4][5]

Hudson River Special Flight Rules Area

On November 19, 2009, the FAA effected an SFRA in the New York City Class B airspace, motivated largely by the mid-air collision of a private general aviation aircraft and a sightseeing helicopter ride along the Hudson River VFR corridor in the summer of 2009.[6][7]

The Hudson River Class B exclusion area is formed from the airspace above the Hudson River between the Alpine Tower and the Verrazano-Narrows Bridge. It is bounded by the banks of the Hudson river and runs from the surface of the river up to 1,300 feet. Aircraft fly along the right-hand bank to separate northbound and southbound traffic. Aircraft transiting the entire corridor fly between 1,000' and 1,300'. Aircraft performing local operations (mostly landing and taking off) inside the area fly under 1,000'. Aircraft need not communicate with ATC, but they must make certain mandatory self-reports at certain charted points.

In addition, there is a further Class B exclusion area over the East River between the Hudson river and just past the Queensboro Bridge. This length cannot be transited, as the Queensboro end of the corridor ends inside the Class B airspace. Additionally, aircraft not landing or taking off inside the East river exclusion must be in contact with ATC.

Other Examples

Other examples of SFRAs include:

An SFRA is currently proposed for Luke AFB in Arizona but it has not been finalized yet.[12]

gollark: TJ09 is clearly viewbombing them.
gollark: DUN DUN DUNNNN
gollark: I have a perpetually-experimental 4-refreshes-per-second ARer, but it never seems to help.
gollark: I see them loads.
gollark: ^^^

References
  1. http://www.aopa.org/flightplanning/articles/2008/081215adiz.html
  2. http://www.aopa.org/adiz/adiz.html
  3. http://www.aopa.org/whatsnew/air_traffic/adiz-training.html
  4. http://www.gpo.gov/fdsys/granule/CFR-1998-title14-vol2/CFR-1998-title14-vol2-part91-subjectgroup-id377
  5. https://www.federalregister.gov/articles/2003/07/10/03-17460/special-air-traffic-rules-in-the-vicinity-of-los-angeles-international-airport
  6. https://www.faasafety.gov/gslac/ALC/course_content.aspx?cID=79
  7. http://www.eaa27.org/resources/hudson_SFRA_VFR.pdf
  8. "Archived copy". Archived from the original on 2012-12-09. Retrieved 2012-10-12.CS1 maint: archived copy as title (link)
  9. https://www.faa.gov/about/office_org/headquarters_offices/ato/service_units/systemops/fs/alaskan/juneau_ketchikan/ketchikan/
  10. http://www.gpo.gov/fdsys/pkg/CFR-2012-title14-vol2/pdf/CFR-2012-title14-vol2-part93-subpartF.pdf
  11. http://www.ecfr.gov/cgi-bin/text-idx?c=ecfr&tpl=/ecfrbrowse/Title14/14cfr93_main_02.tpl
  12. http://www.sunlakesaeroclub.org/updates_web_data/060219/Luke_Airforce_Traffic.htm
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.