The following revises the procedure for pilots conducting 'closed' traffic pattern work at non-towered airports located in the DC Special Flight Rules Area (SFRA). It requests that pilots communicate with air traffic to advise them when they've completed traffic pattern work. This action allows for efficient transponder coding for all users and can be done by contacting air traffic by telephone or radio the following ways:
Pilots operating at non-towered airports in the DC SFRA requesting VFR pattern work:
1-When the pilot calls on the phone or on a Remote Communications Outlet (RCO) frequency, the controller will issue discrete transponder code, instruct the aircraft to remain outside of Class "B" airspace and contact Potomac at the conclusion of pattern activity. Controller phraseology:"Squawk (beacon code), remain outside Class Bravo airspace. Report pattern work complete by calling PCT (540) 351-6129", (or if applicable), "on this frequency"
When a VFR aircraft is on frequency and requests pattern work at a non-towered SFRA airport controllers will instruct the pilot to report when their pattern work is complete:
a. If the aircraft is going to full stop at the SFRA airport where they are in the pattern, ask the pilot to call PCT on (540) 351-6129.
b. If the aircraft is going to full stop at another airport, ask the pilot to report when the pattern work is complete on the frequency.
ON September 1, 2010, the following NOTAMS will go in to effect for the Washington DC Special Flight Rules Area (DC SFRA) and DC Flight Restricted Zone (DC FRZ):
NOTAM 0/9463 replaces 7/204; (Speed Restrictions, no change from current guidance).
NOTAM 0/9477, replaces 9/4399 providing supplementary guidance to Subpart V, 14 CFR Part 93 for operations in the DC SFRA and DC FRZ.
Significant changes to the previous NOTAM and current procedures include:
1 – DC SFRA Radio Failures. DC SFRA departing aircraft experiencing a radio failure while operating in the DC SFRA must squawk 7600 and may return to the departure airport if that airport is closer than the DC SFRA boundary. Otherwise, the aircraft must exit the DC SFRA via the most direct route.
2 – DC FRZ Radio Failures. Aircraft departing airports within the DC FRZ experiencing a radio failure must squawk 7600 and may return to the departure airport if it is within 5 nm. Otherwise, the aircraft must exit the DC FRZ by the most direct route.
3 – Prohibited Operations. Float plane operations and operations from a ship or private/corporate yacht are explicitly prohibited in the DC FRZ.
4 – Medevac and Law Enforcement DC FRZ Operations. All air ambulance (medevac) and state and local law enforcement operations in the DC FRZ must be conducted in accordance with an approved FAA/TSA Waiver for DC FRZ Operations. All current letters of agreement with state and local law enforcement agencies are being revised, effective 9/1, to require DC FRZ operations in accordance with a current Waiver.
5 – DC FRZ Training Flights. With prior NCRCC coordination, law enforcement, air ambulance and approved Department of Defense (DoD)
operators may conduct limited (consistent with flight safety and pilot proficiency) training and maintenance flights inside the DC FRZ. As always, such approvals will be on a workload permitting basis.
6 – Foreign state (diplomatic or military) aircraft are not authorized to land at DCA; they must use ADW.
For more information, please contact Karen Arendt, FAA Safety Team Program Manager, Washington, DC Flight Standards District Office at email@example.com or 703-230-7664, extension 206.