Narrative:

I was en route from mxe VOR to mrb VOR. I wanted to clear P-40 by a wide margin, because I know that the restr airspace around P-40 fluctuates, and the largest boundary is not marked on the sectional charts. I decided to fly south of frederick airport (fdk). Unfortunately, I think I flew a little too far south, and inadvertently entered the washington dc ADIZ/class B airspace. I was monitoring 121.5 and heard a voice stating, in effect, that an airplane had entered restr airspace, was approximately 13 mi north of leesburg, squawking 1200, and the shortest exit from the airspace was 1 mi north. I immediately turned north until well clear of the ADIZ. I believe this mistake was caused by my failure to ensure flight free from restr airspace. I believe contributing factors include: 1) the largest boundary of P-40 is not depicted on sectional charts. If it was, I would not have changed my original course to travel so far south. 2) failure by myself to speak directly with an FSS briefer about the status of P-40, and rely instead on my duats briefing. The voluminous amount of NOTAM data from duats makes it time consuming, and often difficult, to ensure a pilot successfully recognizes and understands all tfr's and other relevant 'pop-up' restrs. I should have followed up my duats briefing with a call to the FSS for active NOTAM information. In order to help positively identify an aircraft in question, the person who idented the airspace violation on 121.5 should have also included the transponder reported altitude, and possibly observed direction of flight. As soon as the person stated the event, I heard another pilot, east of bay bridge airport, ask if he was the offender.

Related reports:

Google
 

Original NASA ASRS Text

Title: SR20 PLT INADVERTENTLY ENTERS THE DC ADIZ WHILE ATTEMPTING TO AVOID THE P-40 AIRSPACE.

Narrative: I WAS ENRTE FROM MXE VOR TO MRB VOR. I WANTED TO CLR P-40 BY A WIDE MARGIN, BECAUSE I KNOW THAT THE RESTR AIRSPACE AROUND P-40 FLUCTUATES, AND THE LARGEST BOUNDARY IS NOT MARKED ON THE SECTIONAL CHARTS. I DECIDED TO FLY S OF FREDERICK ARPT (FDK). UNFORTUNATELY, I THINK I FLEW A LITTLE TOO FAR S, AND INADVERTENTLY ENTERED THE WASHINGTON DC ADIZ/CLASS B AIRSPACE. I WAS MONITORING 121.5 AND HEARD A VOICE STATING, IN EFFECT, THAT AN AIRPLANE HAD ENTERED RESTR AIRSPACE, WAS APPROX 13 MI N OF LEESBURG, SQUAWKING 1200, AND THE SHORTEST EXIT FROM THE AIRSPACE WAS 1 MI N. I IMMEDIATELY TURNED N UNTIL WELL CLR OF THE ADIZ. I BELIEVE THIS MISTAKE WAS CAUSED BY MY FAILURE TO ENSURE FLT FREE FROM RESTR AIRSPACE. I BELIEVE CONTRIBUTING FACTORS INCLUDE: 1) THE LARGEST BOUNDARY OF P-40 IS NOT DEPICTED ON SECTIONAL CHARTS. IF IT WAS, I WOULD NOT HAVE CHANGED MY ORIGINAL COURSE TO TRAVEL SO FAR S. 2) FAILURE BY MYSELF TO SPEAK DIRECTLY WITH AN FSS BRIEFER ABOUT THE STATUS OF P-40, AND RELY INSTEAD ON MY DUATS BRIEFING. THE VOLUMINOUS AMOUNT OF NOTAM DATA FROM DUATS MAKES IT TIME CONSUMING, AND OFTEN DIFFICULT, TO ENSURE A PLT SUCCESSFULLY RECOGNIZES AND UNDERSTANDS ALL TFR'S AND OTHER RELEVANT 'POP-UP' RESTRS. I SHOULD HAVE FOLLOWED UP MY DUATS BRIEFING WITH A CALL TO THE FSS FOR ACTIVE NOTAM INFO. IN ORDER TO HELP POSITIVELY IDENT AN ACFT IN QUESTION, THE PERSON WHO IDENTED THE AIRSPACE VIOLATION ON 121.5 SHOULD HAVE ALSO INCLUDED THE XPONDER RPTED ALT, AND POSSIBLY OBSERVED DIRECTION OF FLT. AS SOON AS THE PERSON STATED THE EVENT, I HEARD ANOTHER PLT, E OF BAY BRIDGE ARPT, ASK IF HE WAS THE OFFENDER.

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.