Reporter aircraft probably entered arsa without ATC communication.

Attributes
ACN	110521
Time
Date	198903
Day	Wed
Local Time Of Day	1801 To 2400
Place
Locale Reference	atc facility : cak
State Reference	OH
Altitude	msl bound lower : 4500 msl bound upper : 4500
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Controlling Facilities	tracon : cak
Operator	general aviation : personal
Make Model Name	Small Transport, Low Wing, 2 Recip Eng
Flight Phase	climbout : intermediate altitude cruise other
Flight Plan	VFR
Person 1
Affiliation	Other
Function	flight crew : single pilot
Qualification	pilot : private
Experience	flight time last 90 days : 29 flight time total : 727 flight time type : 242
ASRS Report	110521
Person 2
Affiliation	government : faa
Function	controller : approach
Qualification	controller : radar
Events
Anomaly	inflight encounter other non adherence : far other anomaly other anomaly other
Independent Detector	other flight crewa
Resolutory Action	flight crew : exited penetrated airspace flight crew : regained aircraft control flight crew : returned to intended course or assigned course
Consequence	faa : reviewed incident with flight crew
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

I was permitted to continue on my present heading (180 degrees). Ultimately I was turned over to departure on that same heading and upon release from departure it was evident that I was about to or had already entered the akron/canton arsa. After being released from the departure I turned 20 degrees right and attempted to contact akron/canton approach on 118.6 and told the controller that I would probably be skirting the west side of his airspace. Controller asked whose area did I just leave and I replied cleveland hopkins. The controller indicated I was radar contact 14 mi southwest of the airport. No other substantive dialogue took place between me and the akron/canton approach control. Immediately upon landing at I40 I contacted the phone # given to me by the controller and found that the supervisor was not available. The individual I talked to stated that the supervisor wanted to informally discuss the evenings events in the interest of mutual safety. I related that the pilot characteristics exhibited upon departure are far from normal and went on to explain the reason for deviating from my original assigned heading was the turbulence. The controller related factual information re: wake turbulence and made suggestions re: a longer wait time interval after departure of heavy jets. I explained that I would have liked to have talked to the supervisor re: the incident and indicated that my deviations were the result of what I considered an immediate emergency situation. I added further that my main concern was with the safety of my passenger and other aircraft in the area and regaining full control of the aircraft. I left my home phone # with this individual and requested that the supervisor contact me if he had any further concerns or questions. At no time during the flight did any controller ask me if I had encountered a problem or the reasons for my actions. To this date no one has returned my call nor has anyone requested further explanations on my action from cleveland or akron/canton.

Original NASA ASRS Text

Title: REPORTER ACFT PROBABLY ENTERED ARSA WITHOUT ATC COM.

Narrative: I WAS PERMITTED TO CONTINUE ON MY PRESENT HDG (180 DEGS). ULTIMATELY I WAS TURNED OVER TO DEP ON THAT SAME HDG AND UPON RELEASE FROM DEP IT WAS EVIDENT THAT I WAS ABOUT TO OR HAD ALREADY ENTERED THE AKRON/CANTON ARSA. AFTER BEING RELEASED FROM THE DEP I TURNED 20 DEGS RIGHT AND ATTEMPTED TO CONTACT AKRON/CANTON APCH ON 118.6 AND TOLD THE CTLR THAT I WOULD PROBABLY BE SKIRTING THE W SIDE OF HIS AIRSPACE. CTLR ASKED WHOSE AREA DID I JUST LEAVE AND I REPLIED CLEVELAND HOPKINS. THE CTLR INDICATED I WAS RADAR CONTACT 14 MI SW OF THE ARPT. NO OTHER SUBSTANTIVE DIALOGUE TOOK PLACE BTWN ME AND THE AKRON/CANTON APCH CTL. IMMEDIATELY UPON LNDG AT I40 I CONTACTED THE PHONE # GIVEN TO ME BY THE CTLR AND FOUND THAT THE SUPVR WAS NOT AVAILABLE. THE INDIVIDUAL I TALKED TO STATED THAT THE SUPVR WANTED TO INFORMALLY DISCUSS THE EVENINGS EVENTS IN THE INTEREST OF MUTUAL SAFETY. I RELATED THAT THE PLT CHARACTERISTICS EXHIBITED UPON DEP ARE FAR FROM NORMAL AND WENT ON TO EXPLAIN THE REASON FOR DEVIATING FROM MY ORIGINAL ASSIGNED HDG WAS THE TURB. THE CTLR RELATED FACTUAL INFO RE: WAKE TURB AND MADE SUGGESTIONS RE: A LONGER WAIT TIME INTERVAL AFTER DEP OF HEAVY JETS. I EXPLAINED THAT I WOULD HAVE LIKED TO HAVE TALKED TO THE SUPVR RE: THE INCIDENT AND INDICATED THAT MY DEVIATIONS WERE THE RESULT OF WHAT I CONSIDERED AN IMMEDIATE EMER SITUATION. I ADDED FURTHER THAT MY MAIN CONCERN WAS WITH THE SAFETY OF MY PAX AND OTHER ACFT IN THE AREA AND REGAINING FULL CTL OF THE ACFT. I LEFT MY HOME PHONE # WITH THIS INDIVIDUAL AND REQUESTED THAT THE SUPVR CONTACT ME IF HE HAD ANY FURTHER CONCERNS OR QUESTIONS. AT NO TIME DURING THE FLT DID ANY CTLR ASK ME IF I HAD ENCOUNTERED A PROB OR THE REASONS FOR MY ACTIONS. TO THIS DATE NO ONE HAS RETURNED MY CALL NOR HAS ANYONE REQUESTED FURTHER EXPLANATIONS ON MY ACTION FROM CLEVELAND OR AKRON/CANTON.

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.