Although he had filed a flight plan, pilot of AA5 enters dc ADIZ prior to contacting pct.

Attributes
ACN	624687
Time
Date	200407
Day	Sun
Local Time Of Day	1201 To 1800
Place
Locale Reference	navaid : brv.vortac
State Reference	VA
Altitude	msl single value : 3000
Environment
Flight Conditions	Marginal
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : pct.tracon
Operator	general aviation : personal
Make Model Name	Cheetah, Tiger, Traveler
Operating Under FAR Part	Part 91
Flight Phase	cruise : level
Flight Plan	VFR
Person 1
Affiliation	other
Function	flight crew : single pilot
Qualification	pilot : cfi pilot : instrument pilot : commercial
Experience	flight time last 90 days : 35.6 flight time total : 343 flight time type : 90.9
ASRS Report	624687
Person 2
Affiliation	government : faa
Function	controller : approach
Events
Anomaly	airspace violation : entry non adherence : published procedure non adherence : far
Independent Detector	other controllera
Resolutory Action	none taken : detected after the fact
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	Flight Crew Human Performance Airspace Structure Chart Or Publication
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

The problem occurred on a leg of a cross country flight, from cambridge dorchester airport to brooke VOR. I briefly entered the washington dc metropolitan area air defense identify zone (dc) ADIZ in error, before I opened up my ADIZ flight plan. This was on file with potomac approach. The situation happened in part because I was under the impression that the ADIZ extended to only the lateral boundaries of the class B airspace. After receiving my ADIZ clearance at brooke, the ATC controller advised me to contact potomac approach. I was then informed of my violation. I have since further studied and researched the washington dc ADIZ airspace. I now feel I have a better understanding of its boundaries and procedures. A suggestion I feel would prevent other pilots from making the same mistake is, to standardize the ADIZ airspace to only the lateral boundaries of the class B airspace. This would also improve the clarity of the ADIZ on the aviation charts.

Original NASA ASRS Text

Title: ALTHOUGH HE HAD FILED A FLT PLAN, PLT OF AA5 ENTERS DC ADIZ PRIOR TO CONTACTING PCT.

Narrative: THE PROB OCCURRED ON A LEG OF A XCOUNTRY FLT, FROM CAMBRIDGE DORCHESTER ARPT TO BROOKE VOR. I BRIEFLY ENTERED THE WASHINGTON DC METRO AREA AIR DEFENSE IDENT ZONE (DC) ADIZ IN ERROR, BEFORE I OPENED UP MY ADIZ FLT PLAN. THIS WAS ON FILE WITH POTOMAC APCH. THE SIT HAPPENED IN PART BECAUSE I WAS UNDER THE IMPRESSION THAT THE ADIZ EXTENDED TO ONLY THE LATERAL BOUNDARIES OF THE CLASS B AIRSPACE. AFTER RECEIVING MY ADIZ CLRNC AT BROOKE, THE ATC CTLR ADVISED ME TO CONTACT POTOMAC APCH. I WAS THEN INFORMED OF MY VIOLATION. I HAVE SINCE FURTHER STUDIED AND RESEARCHED THE WASHINGTON DC ADIZ AIRSPACE. I NOW FEEL I HAVE A BETTER UNDERSTANDING OF ITS BOUNDARIES AND PROCS. A SUGGESTION I FEEL WOULD PREVENT OTHER PLTS FROM MAKING THE SAME MISTAKE IS, TO STANDARDIZE THE ADIZ AIRSPACE TO ONLY THE LATERAL BOUNDARIES OF THE CLASS B AIRSPACE. THIS WOULD ALSO IMPROVE THE CLARITY OF THE ADIZ ON THE AVIATION CHARTS.

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.