Beech T34 pilot has a ramp security area incursion while taxiing at gon.

Attributes
ACN	696217
Time
Date	200605
Place
Locale Reference	airport : gon.airport
State Reference	CT
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	general aviation : personal
Make Model Name	Mentor (T-34)
Operating Under FAR Part	Part 91
Flight Phase	ground : taxi
Flight Plan	None
Person 1
Affiliation	other
Function	flight crew : single pilot
Qualification	pilot : private pilot : instrument
Experience	flight time last 90 days : 25 flight time total : 3400 flight time type : 900
ASRS Report	696217
Person 2
Affiliation	government : faa
Function	controller : ground
Events
Anomaly	non adherence : published procedure
Independent Detector	other controllera
Resolutory Action	controller : issued advisory
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	Flight Crew Human Performance Airport Chart Or Publication
Primary Problem	Flight Crew Human Performance

Narrative:

I was on a VFR flight to gon. I was cleared by the gon tower to land on runway 23. I proceeded to land on runway 23 and exited the runway to the northwest on taxiway D. The tower inquired as to my 'intentions' and I advised that I was going to a shop. I was issued a clearance to shop and instructed to monitor the ground control frequency. Immediately to the northwest of taxiway D is a poorly marked security area; which I inadvertently taxied into on my taxi to shop. On my arrival at the shop; the gon controller advised me of the error and noted the proper route for future reference. The security area is not indicated on the gon charts. I also feel it is poorly marked (very faded). The problem could have been avoided if I asked the ground controller for progressive taxi instructions to the shop. Callback conversation with reporter revealed the following information: reporter stated that markings for the 'security area' were faded and hard to visualize. Additionally; he felt the tower operator did not provide much help with regard to the taxi route/instructions. He stated that he was not familiar with the airport and that may have been one of the problems. He confessed that he should have asked for progressive taxi instructions.

Original NASA ASRS Text

Title: BEECH T34 PLT HAS A RAMP SECURITY AREA INCURSION WHILE TAXIING AT GON.

Narrative: I WAS ON A VFR FLT TO GON. I WAS CLRED BY THE GON TWR TO LAND ON RWY 23. I PROCEEDED TO LAND ON RWY 23 AND EXITED THE RWY TO THE NW ON TXWY D. THE TWR INQUIRED AS TO MY 'INTENTIONS' AND I ADVISED THAT I WAS GOING TO A SHOP. I WAS ISSUED A CLRNC TO SHOP AND INSTRUCTED TO MONITOR THE GND CTL FREQ. IMMEDIATELY TO THE NW OF TXWY D IS A POORLY MARKED SECURITY AREA; WHICH I INADVERTENTLY TAXIED INTO ON MY TAXI TO SHOP. ON MY ARR AT THE SHOP; THE GON CTLR ADVISED ME OF THE ERROR AND NOTED THE PROPER RTE FOR FUTURE REF. THE SECURITY AREA IS NOT INDICATED ON THE GON CHARTS. I ALSO FEEL IT IS POORLY MARKED (VERY FADED). THE PROB COULD HAVE BEEN AVOIDED IF I ASKED THE GND CTLR FOR PROGRESSIVE TAXI INSTRUCTIONS TO THE SHOP. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR STATED THAT MARKINGS FOR THE 'SECURITY AREA' WERE FADED AND HARD TO VISUALIZE. ADDITIONALLY; HE FELT THE TWR OPERATOR DID NOT PROVIDE MUCH HELP WITH REGARD TO THE TAXI RTE/INSTRUCTIONS. HE STATED THAT HE WAS NOT FAMILIAR WITH THE ARPT AND THAT MAY HAVE BEEN ONE OF THE PROBS. HE CONFESSED THAT HE SHOULD HAVE ASKED FOR PROGRESSIVE TAXI INSTRUCTIONS.

Data retrieved from NASA's ASRS site as of January 2009 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.