Narrative:

Filed IFR to W29 bay bridge. 10 mi from W29 at 2800 ft, ATC cleared us to go to advisories, but stay on code. Everything ok to this point. Ready to leave, I filed IFR to depart W29. Taxied to the end of runway. Multiple tries to contact clearance delivery failed on 2 different phones. (We travel to bay bridge multiple times a yr.) from time to time, we have departed VFR to pick up clearance in air (heading 120 degrees) away from W29. At 800 ft, contacted baltimore departure for clearance at which time I was told that VFR departure was not authority/authorized from bay bridge. When I filed the IFR, flight service did not mention that any procedures had changed at bay bridge or that any special actions were required. We stayed at 1400 ft, heading 120 degrees until clearance was received, then proceeded IFR to our destination. Inside the airport, there were no special notices stating that no VFR departures are authority/authorized. Nobody had knowledge for these procedures (as per AOPA airport directory 2003, no special procedures are noted). The ATIS for bay bridge airport had no special instruction for their airspace, except for pattern procedures, which we use every time. All flts with our airplane are IFR. As a long time pilot, I feel that the system let me down. The airplane is always flown with 2 pilots, as we did this day. Callback conversation with reporter revealed the following information: reporter stated that since he could not obtain clearance verification on the ground, that it would be easier to get going, because of the aircraft's owner on board, and obtain an airborne, air filing IFR flight plan. The pilot stated that he did not see any local notifications or reminders at the airport 'desk' alerting a pilot of the area far requirements.

Google
 

Original NASA ASRS Text

Title: CORPORATE PA42 FLC VIOLATE WASHINGTON ADIZ WHEN DEPARTING W29 VFR WITHOUT COMPLYING WITH FAR REQUIREMENTS.

Narrative: FILED IFR TO W29 BAY BRIDGE. 10 MI FROM W29 AT 2800 FT, ATC CLRED US TO GO TO ADVISORIES, BUT STAY ON CODE. EVERYTHING OK TO THIS POINT. READY TO LEAVE, I FILED IFR TO DEPART W29. TAXIED TO THE END OF RWY. MULTIPLE TRIES TO CONTACT CLRNC DELIVERY FAILED ON 2 DIFFERENT PHONES. (WE TRAVEL TO BAY BRIDGE MULTIPLE TIMES A YR.) FROM TIME TO TIME, WE HAVE DEPARTED VFR TO PICK UP CLRNC IN AIR (HDG 120 DEGS) AWAY FROM W29. AT 800 FT, CONTACTED BALTIMORE DEP FOR CLRNC AT WHICH TIME I WAS TOLD THAT VFR DEP WAS NOT AUTH FROM BAY BRIDGE. WHEN I FILED THE IFR, FLT SVC DID NOT MENTION THAT ANY PROCS HAD CHANGED AT BAY BRIDGE OR THAT ANY SPECIAL ACTIONS WERE REQUIRED. WE STAYED AT 1400 FT, HDG 120 DEGS UNTIL CLRNC WAS RECEIVED, THEN PROCEEDED IFR TO OUR DEST. INSIDE THE ARPT, THERE WERE NO SPECIAL NOTICES STATING THAT NO VFR DEPS ARE AUTH. NOBODY HAD KNOWLEDGE FOR THESE PROCS (AS PER AOPA ARPT DIRECTORY 2003, NO SPECIAL PROCS ARE NOTED). THE ATIS FOR BAY BRIDGE ARPT HAD NO SPECIAL INSTRUCTION FOR THEIR AIRSPACE, EXCEPT FOR PATTERN PROCS, WHICH WE USE EVERY TIME. ALL FLTS WITH OUR AIRPLANE ARE IFR. AS A LONG TIME PLT, I FEEL THAT THE SYS LET ME DOWN. THE AIRPLANE IS ALWAYS FLOWN WITH 2 PLTS, AS WE DID THIS DAY. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR STATED THAT SINCE HE COULD NOT OBTAIN CLRNC VERIFICATION ON THE GND, THAT IT WOULD BE EASIER TO GET GOING, BECAUSE OF THE ACFT'S OWNER ON BOARD, AND OBTAIN AN AIRBORNE, AIR FILING IFR FLT PLAN. THE PLT STATED THAT HE DID NOT SEE ANY LCL NOTIFICATIONS OR REMINDERS AT THE ARPT 'DESK' ALERTING A PLT OF THE AREA FAR REQUIREMENTS.

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.