GA small aircraft unauthorized penetration of airspace.

Attributes
ACN	120945
Time
Date	198908
Day	Thu
Local Time Of Day	1801 To 2400
Place
Locale Reference	atc facility : bos
State Reference	MA
Altitude	msl bound lower : 2500 msl bound upper : 2500
Environment
Flight Conditions	VMC
Light	Dusk
Aircraft 1
Controlling Facilities	tracon : bos tower : fmh
Operator	general aviation : instructional
Make Model Name	Small Aircraft, High Wing, 1 Eng, Fixed Gear
Flight Phase	cruise other
Route In Use	enroute : direct
Flight Plan	None
Person 1
Affiliation	Other
Function	flight crew : single pilot
Qualification	pilot : private
Experience	flight time last 90 days : 25 flight time total : 160 flight time type : 100
ASRS Report	120945
Person 2
Affiliation	government : faa
Function	controller : approach
Qualification	controller : radar
Events
Anomaly	non adherence : far other anomaly other
Independent Detector	other controllera other flight crewa
Resolutory Action	controller : provided flight assist flight crew : exited penetrated airspace flight crew : became reoriented other
Consequence	faa : reviewed incident with flight crew
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

I am very unfamiliar with the boston TCA. I was navigating by pilotage only when I decided to land at plymouth, ma. I contacted unicom and was advised that runway 33 was in use. As I began looking for the airport, I saw a clearing that I thought was plymouth. (I was using only the boston TCA chart.) as I approached the airport I noticed first a control tower. Then I noticed that I was on a downwind for runway 32 (not 33). I aborted my landing and began back north toward boston. As I headed for my point of origin (bed) I called boston approach and asked for radar vectors. It was obvious that I was lost. After regaining my bearings, boston released me and told me to squawk VFR and call hanscom tower. On approach to land at hanscom the tower told me 'boston called and asked that you be more familiar with the TCA next time'. This led me to believe that I violated the TCA. After a landed I consulted a new york sectional. I realized that I went straight through R4101 and otis AFB airspace without so much as calling the tower. So in short, I violated R4101, otis AFB airspace and I may have violated the boston TCA.

Original NASA ASRS Text

Title: GA SMA UNAUTH PENETRATION OF AIRSPACE.

Narrative: I AM VERY UNFAMILIAR WITH THE BOSTON TCA. I WAS NAVIGATING BY PILOTAGE ONLY WHEN I DECIDED TO LAND AT PLYMOUTH, MA. I CONTACTED UNICOM AND WAS ADVISED THAT RWY 33 WAS IN USE. AS I BEGAN LOOKING FOR THE ARPT, I SAW A CLEARING THAT I THOUGHT WAS PLYMOUTH. (I WAS USING ONLY THE BOSTON TCA CHART.) AS I APCHED THE ARPT I NOTICED FIRST A CTL TWR. THEN I NOTICED THAT I WAS ON A DOWNWIND FOR RWY 32 (NOT 33). I ABORTED MY LNDG AND BEGAN BACK N TOWARD BOSTON. AS I HEADED FOR MY POINT OF ORIGIN (BED) I CALLED BOSTON APCH AND ASKED FOR RADAR VECTORS. IT WAS OBVIOUS THAT I WAS LOST. AFTER REGAINING MY BEARINGS, BOSTON RELEASED ME AND TOLD ME TO SQUAWK VFR AND CALL HANSCOM TWR. ON APCH TO LAND AT HANSCOM THE TWR TOLD ME 'BOSTON CALLED AND ASKED THAT YOU BE MORE FAMILIAR WITH THE TCA NEXT TIME'. THIS LED ME TO BELIEVE THAT I VIOLATED THE TCA. AFTER A LANDED I CONSULTED A NEW YORK SECTIONAL. I REALIZED THAT I WENT STRAIGHT THROUGH R4101 AND OTIS AFB AIRSPACE WITHOUT SO MUCH AS CALLING THE TWR. SO IN SHORT, I VIOLATED R4101, OTIS AFB AIRSPACE AND I MAY HAVE VIOLATED THE BOSTON TCA.

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