Pilot of PC12 enters dc ADIZ when he squawks VFR code after canceling IFR flight plan to anp.

Attributes
ACN	624615
Time
Date	200407
Day	Tue
Place
Locale Reference	airport : anp.airport
State Reference	MD
Altitude	msl single value : 2000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : pct.tracon artcc : abq.artcc
Operator	general aviation : corporate
Make Model Name	PC-12
Operating Under FAR Part	Part 91
Navigation In Use	other
Flight Phase	descent : approach
Route In Use	approach : traffic pattern
Flight Plan	IFR
Person 1
Affiliation	company : corporate
Function	flight crew : single pilot
Qualification	pilot : private pilot : instrument
Experience	flight time last 90 days : 67 flight time total : 6000 flight time type : 1900
ASRS Report	624615
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 : assigned or threatened penalties faa : reviewed incident with flight crew
Supplementary
Problem Areas	FAA Flight Crew Human Performance Airspace Structure ATC Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

I was on an IFR flight plan from shd to anp. Due to WX, the route was changed shortly after takeoff. The amended route was direct mrb, ruane, EMI then direct. After several WX deviations, we were cleared from near the balance VOR direct to anp and asked to report the field in sight. At or near 2000 ft MSL and about 4 mi, I called the airport in sight. I was cleared to go to the advisory frequency and asked to advise of cancellation of my IFR flight plan. I canceled at that time and switched codes from IFR to VFR. On jul/thu/04, I received a phone call from FSDO stating that by changing to VFR code prior to landing I had committed a violation that required a 30 day suspension of my license. I now understand that there is a NOTAM that requires the code stay in place until after landing. It would seem to me that when the IFR plan is canceled, a simple 'retain your squawk code until landing' would eliminate this problem and save a lot of work for a lot of people.

Original NASA ASRS Text

Title: PLT OF PC12 ENTERS DC ADIZ WHEN HE SQUAWKS VFR CODE AFTER CANCELING IFR FLT PLAN TO ANP.

Narrative: I WAS ON AN IFR FLT PLAN FROM SHD TO ANP. DUE TO WX, THE RTE WAS CHANGED SHORTLY AFTER TKOF. THE AMENDED RTE WAS DIRECT MRB, RUANE, EMI THEN DIRECT. AFTER SEVERAL WX DEVS, WE WERE CLRED FROM NEAR THE BAL VOR DIRECT TO ANP AND ASKED TO RPT THE FIELD IN SIGHT. AT OR NEAR 2000 FT MSL AND ABOUT 4 MI, I CALLED THE ARPT IN SIGHT. I WAS CLRED TO GO TO THE ADVISORY FREQ AND ASKED TO ADVISE OF CANCELLATION OF MY IFR FLT PLAN. I CANCELED AT THAT TIME AND SWITCHED CODES FROM IFR TO VFR. ON JUL/THU/04, I RECEIVED A PHONE CALL FROM FSDO STATING THAT BY CHANGING TO VFR CODE PRIOR TO LNDG I HAD COMMITTED A VIOLATION THAT REQUIRED A 30 DAY SUSPENSION OF MY LICENSE. I NOW UNDERSTAND THAT THERE IS A NOTAM THAT REQUIRES THE CODE STAY IN PLACE UNTIL AFTER LNDG. IT WOULD SEEM TO ME THAT WHEN THE IFR PLAN IS CANCELED, A SIMPLE 'RETAIN YOUR SQUAWK CODE UNTIL LNDG' WOULD ELIMINATE THIS PROB AND SAVE A LOT OF WORK FOR A LOT OF PEOPLE.

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.