Pilot of small aircraft aircraft inadvertently penetrated an arsa due miscoms with ATC.

Attributes
ACN	223023
Time
Date	199210
Day	Thu
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : fay
State Reference	NC
Altitude	msl bound lower : 3200 msl bound upper : 3200
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : fay tower : msp
Operator	general aviation : personal
Make Model Name	Small Aircraft, High Wing, 1 Eng, Fixed Gear
Flight Phase	cruise other
Flight Plan	None
Person 1
Affiliation	Other
Function	flight crew : single pilot
Qualification	pilot : commercial pilot : instrument
ASRS Report	223023
Person 2
Affiliation	government : faa
Function	controller : approach
Qualification	controller : radar
Events
Anomaly	non adherence : far other anomaly other
Independent Detector	atc equipment other atc equipment : unspecified other controllera
Resolutory Action	none taken : detected after the fact
Consequence	faa : reviewed incident with flight crew
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

On a VFR flight from anp to dlc, I was cruising at 4500 MSL with the intention of crossing pob and fay arsa above. I was squawking 1200 with mode C operating. At 20 NM more or less north of pob, I encountered a cloud layer with a base of 3700 MSL. In order to remain VFR I descended to 3500 MSL. I soon realized that I was in or near the fby-pob arsa. I called fby tower, gave my approximately position and tail number and requested the frequency of the ATC. The tower gave me the ATC frequency and confirmed an erroneous call sign. I called ATC, giving my tail number. He confirmed using the same incorrect call sign. The controller confirmed my altitude, then 3200 MSL and gave me a squawk code. I continued to respond to incorrect call sign because I did not wish to further bother the harried controller. I followed the controller's directions through the arsa without further incident. The flight continued to dlc. I was asked to call the tower upon landing. This I did. A supervisor and I discussed the event at length and I relayed the events as described above. The controller asked my name and address which I declined to give. The supervisor told me that a flight from pob had been diverted because of my presence. They had seen my transponder signal and the flight had collision avoidance equipment on board.

Original NASA ASRS Text

Title: PLT OF SMA ACFT INADVERTENTLY PENETRATED AN ARSA DUE MISCOMS WITH ATC.

Narrative: ON A VFR FLT FROM ANP TO DLC, I WAS CRUISING AT 4500 MSL WITH THE INTENTION OF XING POB AND FAY ARSA ABOVE. I WAS SQUAWKING 1200 WITH MODE C OPERATING. AT 20 NM MORE OR LESS N OF POB, I ENCOUNTERED A CLOUD LAYER WITH A BASE OF 3700 MSL. IN ORDER TO REMAIN VFR I DSNDED TO 3500 MSL. I SOON REALIZED THAT I WAS IN OR NEAR THE FBY-POB ARSA. I CALLED FBY TWR, GAVE MY APPROX POS AND TAIL NUMBER AND REQUESTED THE FREQ OF THE ATC. THE TWR GAVE ME THE ATC FREQ AND CONFIRMED AN ERRONEOUS CALL SIGN. I CALLED ATC, GIVING MY TAIL NUMBER. HE CONFIRMED USING THE SAME INCORRECT CALL SIGN. THE CTLR CONFIRMED MY ALT, THEN 3200 MSL AND GAVE ME A SQUAWK CODE. I CONTINUED TO RESPOND TO INCORRECT CALL SIGN BECAUSE I DID NOT WISH TO FURTHER BOTHER THE HARRIED CTLR. I FOLLOWED THE CTLR'S DIRECTIONS THROUGH THE ARSA WITHOUT FURTHER INCIDENT. THE FLT CONTINUED TO DLC. I WAS ASKED TO CALL THE TWR UPON LNDG. THIS I DID. A SUPVR AND I DISCUSSED THE EVENT AT LENGTH AND I RELAYED THE EVENTS AS DESCRIBED ABOVE. THE CTLR ASKED MY NAME AND ADDRESS WHICH I DECLINED TO GIVE. THE SUPVR TOLD ME THAT A FLT FROM POB HAD BEEN DIVERTED BECAUSE OF MY PRESENCE. THEY HAD SEEN MY TRANSPONDER SIGNAL AND THE FLT HAD COLLISION AVOIDANCE EQUIP ON BOARD.

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.