A BE33 pilot violated the dc ADIZ.

Attributes
ACN	584225
Time
Date	200306
Day	Tue
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : w29.airport
State Reference	MD
Altitude	msl single value : 2500
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : pct.tracon tracon : phl.tracon
Operator	general aviation : personal
Make Model Name	Bonanza 33
Operating Under FAR Part	Part 91
Flight Phase	descent : approach
Flight Plan	None
Person 1
Affiliation	other
Function	flight crew : single pilot
Qualification	pilot : private
Experience	flight time last 90 days : 30 flight time total : 4200 flight time type : 3000
ASRS Report	584225
Person 2
Affiliation	government : faa
Function	controller : approach
Events
Anomaly	airspace violation : entry non adherence : far non adherence : published procedure
Independent Detector	other controllera
Resolutory Action	none taken : detected after the fact
Consequence	faa : reviewed incident with flight crew faa : assigned or threatened penalties
Supplementary
Problem Areas	Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

Finally got a good day, WX wise, in the philadelphia area and decided to take a pleasure flight to have some lunch at the bay bridge airport in maryland (W29). Worked phl approach for VFR TA's. As I left the philadelphia area, I was told to squawk 1200 and try potomac approach. I just thought the handoff was for continued VFR flight following and attempted 1 call. I heard nothing, so I continued since I was only about 15 mi to the north of bay bridge, our destination. I was explaining to my passenger how to stay below washington baltimore class B airspace on my garmin 530. Thought I did a good job, until I landed, and was told I violated the tfr airspace around the washington area. I was met by the custom's people, showed them the paperwork they requested, told what I had done, was told to call TRACON, which I did. Then, I proceeded to file a VFR flight plan, got a discrete code, and departed for wing's field (LOM) my home field.

Original NASA ASRS Text

Title: A BE33 PLT VIOLATED THE DC ADIZ.

Narrative: FINALLY GOT A GOOD DAY, WX WISE, IN THE PHILADELPHIA AREA AND DECIDED TO TAKE A PLEASURE FLT TO HAVE SOME LUNCH AT THE BAY BRIDGE ARPT IN MARYLAND (W29). WORKED PHL APCH FOR VFR TA'S. AS I LEFT THE PHILADELPHIA AREA, I WAS TOLD TO SQUAWK 1200 AND TRY POTOMAC APCH. I JUST THOUGHT THE HDOF WAS FOR CONTINUED VFR FLT FOLLOWING AND ATTEMPTED 1 CALL. I HEARD NOTHING, SO I CONTINUED SINCE I WAS ONLY ABOUT 15 MI TO THE N OF BAY BRIDGE, OUR DEST. I WAS EXPLAINING TO MY PAX HOW TO STAY BELOW WASHINGTON BALTIMORE CLASS B AIRSPACE ON MY GARMIN 530. THOUGHT I DID A GOOD JOB, UNTIL I LANDED, AND WAS TOLD I VIOLATED THE TFR AIRSPACE AROUND THE WASHINGTON AREA. I WAS MET BY THE CUSTOM'S PEOPLE, SHOWED THEM THE PAPERWORK THEY REQUESTED, TOLD WHAT I HAD DONE, WAS TOLD TO CALL TRACON, WHICH I DID. THEN, I PROCEEDED TO FILE A VFR FLT PLAN, GOT A DISCRETE CODE, AND DEPARTED FOR WING'S FIELD (LOM) MY HOME FIELD.

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.