Narrative:

This submittal is in reference to a call from pct TRACON after a one hour flight 04/sat/03, originating and ending at quantico turner airfield. The watch supervisor said that I failed to establish two-way communication with pct approach after departing the traffic pattern. I did not establish two-way communication. Despite extensive preparation including reassessment of ADIZ procedures through quantico pilot information files (pif's), watching the quantico quarterly safety meeting video on which ADIZ was highlighted, and communication with pct and jyo FSS, a series of inadequate communications and events led confusion on the subject and ultimately my error. Prior to departure, I reviewed the quantico pif's for sequential listings of ADIZ updates. I had flown a few weeks prior under pif 03-03 and exited and re-entered the ADIZ without incident. Some confusion arose in nyg pif 03-07, the latest update to 03-03, that states pattern operations are allowed whether or not the tower is operating. This pif does reiterate that pilots are required to file a security flight plan and squawk a discrete transponder code, but no mention is made of two-way communications being required. Nyg pif 03-11, regarding NOTAM 3/2762 references 1234 transponder codes at towered airports. In this pif, it states that prior to exiting the traffic pattern for operations within the ADIZ, a flight plan must be filed and discrete transponder code transmitted. It also states that two-way communications must be established prior to ADIZ penetration. The dispatcher at jyo FSS recited the ADIZ NOTAM's, but only mentioned the discrete transponder code and security flight plan requirements. I then filed a defense VFR security flight plan for local flight with jyo FSS. In the preflight check of the aircraft, I found that the radio was working differently than it had the last time I flew this specific aircraft. A push-to-talk switch had been installed through the hand-held microphone as an override to the normal yoke microphone button. I could hear incoming radio reception. I could not hear myself during transmissions. This made for difficult communications. This series of events led to so much confusion that I inadvertently forgot to call pct approach on 124.65 after I departed the traffic pattern at quantico. The latest pif suggested that I needed to establish communications only upon entry to the ADIZ from outside ('penetration'). In all the discussions and planning, never once was this requirement reiterated even when the other requirements were repeated. I was notified as soon as I landed that pct approach watch supervisor had called, so I returned the call.

Related reports:

Google
 

Original NASA ASRS Text

Title: C172 PLT ENTERED DC ADIZ WITHOUT ESTABLISHING CLRNC WITH PCT.

Narrative: THIS SUBMITTAL IS IN REFERENCE TO A CALL FROM PCT TRACON AFTER A ONE HOUR FLT 04/SAT/03, ORIGINATING AND ENDING AT QUANTICO TURNER AIRFIELD. THE WATCH SUPVR SAID THAT I FAILED TO ESTABLISH TWO-WAY COM WITH PCT APCH AFTER DEPARTING THE TFC PATTERN. I DID NOT ESTABLISH TWO-WAY COM. DESPITE EXTENSIVE PREPARATION INCLUDING REASSESSMENT OF ADIZ PROCS THROUGH QUANTICO PLT INFO FILES (PIF'S), WATCHING THE QUANTICO QUARTERLY SAFETY MEETING VIDEO ON WHICH ADIZ WAS HIGHLIGHTED, AND COM WITH PCT AND JYO FSS, A SERIES OF INADEQUATE COMS AND EVENTS LED CONFUSION ON THE SUBJECT AND ULTIMATELY MY ERROR. PRIOR TO DEP, I REVIEWED THE QUANTICO PIF'S FOR SEQUENTIAL LISTINGS OF ADIZ UPDATES. I HAD FLOWN A FEW WEEKS PRIOR UNDER PIF 03-03 AND EXITED AND RE-ENTERED THE ADIZ WITHOUT INCIDENT. SOME CONFUSION AROSE IN NYG PIF 03-07, THE LATEST UPDATE TO 03-03, THAT STATES PATTERN OPS ARE ALLOWED WHETHER OR NOT THE TWR IS OPERATING. THIS PIF DOES REITERATE THAT PLTS ARE REQUIRED TO FILE A SECURITY FLT PLAN AND SQUAWK A DISCRETE XPONDER CODE, BUT NO MENTION IS MADE OF TWO-WAY COMS BEING REQUIRED. NYG PIF 03-11, REGARDING NOTAM 3/2762 REFERENCES 1234 XPONDER CODES AT TOWERED ARPTS. IN THIS PIF, IT STATES THAT PRIOR TO EXITING THE TFC PATTERN FOR OPS WITHIN THE ADIZ, A FLT PLAN MUST BE FILED AND DISCRETE XPONDER CODE TRANSMITTED. IT ALSO STATES THAT TWO-WAY COMS MUST BE ESTABLISHED PRIOR TO ADIZ PENETRATION. THE DISPATCHER AT JYO FSS RECITED THE ADIZ NOTAM'S, BUT ONLY MENTIONED THE DISCRETE XPONDER CODE AND SECURITY FLT PLAN REQUIREMENTS. I THEN FILED A DEFENSE VFR SECURITY FLT PLAN FOR LOCAL FLT WITH JYO FSS. IN THE PREFLT CHK OF THE ACFT, I FOUND THAT THE RADIO WAS WORKING DIFFERENTLY THAN IT HAD THE LAST TIME I FLEW THIS SPECIFIC ACFT. A PUSH-TO-TALK SWITCH HAD BEEN INSTALLED THROUGH THE HAND-HELD MIKE AS AN OVERRIDE TO THE NORMAL YOKE MICROPHONE BUTTON. I COULD HEAR INCOMING RADIO RECEPTION. I COULD NOT HEAR MYSELF DURING TRANSMISSIONS. THIS MADE FOR DIFFICULT COMS. THIS SERIES OF EVENTS LED TO SO MUCH CONFUSION THAT I INADVERTENTLY FORGOT TO CALL PCT APCH ON 124.65 AFTER I DEPARTED THE TFC PATTERN AT QUANTICO. THE LATEST PIF SUGGESTED THAT I NEEDED TO ESTABLISH COMS ONLY UPON ENTRY TO THE ADIZ FROM OUTSIDE ('PENETRATION'). IN ALL THE DISCUSSIONS AND PLANNING, NEVER ONCE WAS THIS REQUIREMENT REITERATED EVEN WHEN THE OTHER REQUIREMENTS WERE REPEATED. I WAS NOTIFIED AS SOON AS I LANDED THAT PCT APCH WATCH SUPVR HAD CALLED, SO I RETURNED THE CALL.

Data retrieved from NASA's ASRS site as of July 2007 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.