Narrative:

2ND leg of IFR cross country from fdk to iad. Complete briefing requested from FSS prior to departure at fdk for IFR legs from fdk direct iad and iad direct I66. NOTAMS requested and received. 2 IFR flight plans filed. (Next 2 legs) publication's carried. Taxied for departure from fdk on oct/fri/03. Advised of a 15-30 min delay in receiving clearance. Elected to take off to avoid idling new engine on ground (cooling concerns). Contacted potomac TRACON immediately on leveling at 1300 ft MSL. Advised IFR clearance still delayed. Continued to stay in contact with TRACON requesting clearance. Entered student practice area around sugarloaf mountain and loitered (approximately 2000 ft MSL) awaiting clearance. Received squawk from potomac TRACON and was then advised of a military helicopter traffic which intercepted me. After intercept, given vectors to iad and asked to call TRACON to give information for violation. Told 'we have to file violation because you were intercepted.' called eastern region. FSDO's on oct/mon/03. Advised that FSS should have briefed me about requirement for discrete squawk in the ADIZ or that I should have gotten the information from an aviation website. I think that if FSS is going to take the time to brief tfr's (which they both did), they should also brief the temporary ADIZ. Operations inspectors agreed, but stated that the failure to have a discrete code in the ADIZ is a mandatory suspension. This despite continuous 2-WAY communication with TRACON. (Albeit no radar service because they were too busy.) furthermore, this critical national security issue deserves mention in the airport facility directory since it is likely to be with us for a long time. (And on the tac which does address sfar 94, but not this). In my chart study before flight, I included sfar 94 to part 91, but this did not cover operations beneath the floor of class B at iad. Airport remarks at gai and iad also did not mention the discrete code requirement. I'm happy to comply with any requirements, particularly those deemed necessary for national security, but longstanding items like this need to be published on charts and in the airport facility directory in addition to the fdc's. A possible litmus test for what to publish in fdc's would be, 'would we care enough about this to launch an interceptor.' many fdc's are backed up in other places to ensure distribution. I think the ADIZ fdc definitely should be. These are very important security issues and they need to be very available to the public to ensure compliance.

Google
 

Original NASA ASRS Text

Title: A DEP FROM GAI WITHOUT COMPLIANCE WITH DC ADIZ PROCS IN HOPES OF GETTING A DELAYED IFR CLRNC RESULTS IN AN INTERCEPT WHILE LOITERING IN A TRAINING PRACTICE AREA. DC ADIZ PROCS WERE NOT INCLUDED IN FSS BRIEFING.

Narrative: 2ND LEG OF IFR XCOUNTRY FROM FDK TO IAD. COMPLETE BRIEFING REQUESTED FROM FSS PRIOR TO DEP AT FDK FOR IFR LEGS FROM FDK DIRECT IAD AND IAD DIRECT I66. NOTAMS REQUESTED AND RECEIVED. 2 IFR FLT PLANS FILED. (NEXT 2 LEGS) PUB'S CARRIED. TAXIED FOR DEP FROM FDK ON OCT/FRI/03. ADVISED OF A 15-30 MIN DELAY IN RECEIVING CLRNC. ELECTED TO TAKE OFF TO AVOID IDLING NEW ENG ON GND (COOLING CONCERNS). CONTACTED POTOMAC TRACON IMMEDIATELY ON LEVELING AT 1300 FT MSL. ADVISED IFR CLRNC STILL DELAYED. CONTINUED TO STAY IN CONTACT WITH TRACON REQUESTING CLRNC. ENTERED STUDENT PRACTICE AREA AROUND SUGARLOAF MOUNTAIN AND LOITERED (APPROX 2000 FT MSL) AWAITING CLRNC. RECEIVED SQUAWK FROM POTOMAC TRACON AND WAS THEN ADVISED OF A MIL HELI TFC WHICH INTERCEPTED ME. AFTER INTERCEPT, GIVEN VECTORS TO IAD AND ASKED TO CALL TRACON TO GIVE INFO FOR VIOLATION. TOLD 'WE HAVE TO FILE VIOLATION BECAUSE YOU WERE INTERCEPTED.' CALLED EASTERN REGION. FSDO'S ON OCT/MON/03. ADVISED THAT FSS SHOULD HAVE BRIEFED ME ABOUT REQUIREMENT FOR DISCRETE SQUAWK IN THE ADIZ OR THAT I SHOULD HAVE GOTTEN THE INFO FROM AN AVIATION WEBSITE. I THINK THAT IF FSS IS GOING TO TAKE THE TIME TO BRIEF TFR'S (WHICH THEY BOTH DID), THEY SHOULD ALSO BRIEF THE TEMPORARY ADIZ. OPS INSPECTORS AGREED, BUT STATED THAT THE FAILURE TO HAVE A DISCRETE CODE IN THE ADIZ IS A MANDATORY SUSPENSION. THIS DESPITE CONTINUOUS 2-WAY COM WITH TRACON. (ALBEIT NO RADAR SVC BECAUSE THEY WERE TOO BUSY.) FURTHERMORE, THIS CRITICAL NATIONAL SECURITY ISSUE DESERVES MENTION IN THE ARPT FACILITY DIRECTORY SINCE IT IS LIKELY TO BE WITH US FOR A LONG TIME. (AND ON THE TAC WHICH DOES ADDRESS SFAR 94, BUT NOT THIS). IN MY CHART STUDY BEFORE FLT, I INCLUDED SFAR 94 TO PART 91, BUT THIS DID NOT COVER OPS BENEATH THE FLOOR OF CLASS B AT IAD. ARPT REMARKS AT GAI AND IAD ALSO DID NOT MENTION THE DISCRETE CODE REQUIREMENT. I'M HAPPY TO COMPLY WITH ANY REQUIREMENTS, PARTICULARLY THOSE DEEMED NECESSARY FOR NATIONAL SECURITY, BUT LONGSTANDING ITEMS LIKE THIS NEED TO BE PUBLISHED ON CHARTS AND IN THE ARPT FACILITY DIRECTORY IN ADDITION TO THE FDC'S. A POSSIBLE LITMUS TEST FOR WHAT TO PUBLISH IN FDC'S WOULD BE, 'WOULD WE CARE ENOUGH ABOUT THIS TO LAUNCH AN INTERCEPTOR.' MANY FDC'S ARE BACKED UP IN OTHER PLACES TO ENSURE DISTRIBUTION. I THINK THE ADIZ FDC DEFINITELY SHOULD BE. THESE ARE VERY IMPORTANT SECURITY ISSUES AND THEY NEED TO BE VERY AVAILABLE TO THE PUBLIC TO ENSURE COMPLIANCE.

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.