Narrative:

I called flight service to check NOTAMS and WX for VFR trip from N47 (base airport) to ezf to check on an engine. Departing N47, visibility was less than expected. I flew on the east side of washington airspace, staying over the shore to avoid airspace. Problem was, I did not realize ADIZ zone was active. I do not fly that way often and thought that was active only when the threat level was higher. I avoided the regular washington airspace, but not the extended perimeter. When I landed at frederick, va, I was told to contact united states customs and supplied them with all information required. On the return trip, I gave a wide berth all the way back. I am based right outside philadelphia and their ADIZ has not been active. It was completely my fault for not realizing it. I was confused as to why it had been active at this time.

Related reports:

Google
 

Original NASA ASRS Text

Title: A CHEROKEE 6 PLT VIOLATED THE DC ADIZ.

Narrative: I CALLED FLT SVC TO CHK NOTAMS AND WX FOR VFR TRIP FROM N47 (BASE ARPT) TO EZF TO CHK ON AN ENG. DEPARTING N47, VISIBILITY WAS LESS THAN EXPECTED. I FLEW ON THE E SIDE OF WASHINGTON AIRSPACE, STAYING OVER THE SHORE TO AVOID AIRSPACE. PROB WAS, I DID NOT REALIZE ADIZ ZONE WAS ACTIVE. I DO NOT FLY THAT WAY OFTEN AND THOUGHT THAT WAS ACTIVE ONLY WHEN THE THREAT LEVEL WAS HIGHER. I AVOIDED THE REGULAR WASHINGTON AIRSPACE, BUT NOT THE EXTENDED PERIMETER. WHEN I LANDED AT FREDERICK, VA, I WAS TOLD TO CONTACT UNITED STATES CUSTOMS AND SUPPLIED THEM WITH ALL INFO REQUIRED. ON THE RETURN TRIP, I GAVE A WIDE BERTH ALL THE WAY BACK. I AM BASED RIGHT OUTSIDE PHILADELPHIA AND THEIR ADIZ HAS NOT BEEN ACTIVE. IT WAS COMPLETELY MY FAULT FOR NOT REALIZING IT. I WAS CONFUSED AS TO WHY IT HAD BEEN ACTIVE AT THIS TIME.

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.