BE36 pilot had the approach controller become upset when he established communication at cak.

Attributes
ACN	537856
Time
Date	200202
Day	Fri
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : akr.airport
State Reference	OH
Altitude	msl single value : 3100
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : cak.tracon
Operator	general aviation : corporate
Make Model Name	Bonanza 36
Operating Under FAR Part	Part 91
Flight Phase	climbout : initial
Route In Use	departure : vfr
Flight Plan	None
Person 1
Affiliation	company : corporate
Function	flight crew : single pilot
Qualification	pilot : commercial pilot : multi engine pilot : instrument
Experience	flight time last 90 days : 15 flight time total : 1650 flight time type : 600
ASRS Report	537856
Person 2
Affiliation	government : faa
Function	controller : approach
Events
Anomaly	other anomaly other
Independent Detector	other controllera
Resolutory Action	none taken : anomaly accepted
Supplementary
Problem Areas	ATC Human Performance Flight Crew Human Performance
Primary Problem	ATC Human Performance
Air Traffic Incident	other

Narrative:

Upon departing from akr which is an uncontrolled airport within the cak class C airspace, in clear VMC, I called cak approach stating that I had just departed runway 7 at akr, on an easterly heading, that I had the current cak ATIS information, and was inbound to cak. I received no immediate response. Watching for traffic and continuing to climb, I called a second time. Cak approach answered and assigned a transponder code to me. Shortly thereafter, approach called again stating that I was in radar contact 7 mi east of akr. Moments later he called again asking for my altitude. I responded that I was level at 3100 ft MSL. The controller then became quite angered and strong in his criticism of my having reached that altitude without being in contact with him. He assigned a heading for 'traffic separation' of 090 degrees, which took me well outside of the class C airspace. Later, while he assigned a reciprocal heading of 270 degrees to me, he continued his criticism of my having entered his airspace explaining that he was working other traffic. His tone was less harsh at this time, almost instructive. At the completion of his critique he told me to contact cak tower. I simply thanked him and changed to the tower frequency. In the future, I will be more attentive to the altitude restrs of the various classes of airspace.

Original NASA ASRS Text

Title: BE36 PLT HAD THE APCH CTLR BECOME UPSET WHEN HE ESTABLISHED COM AT CAK.

Narrative: UPON DEPARTING FROM AKR WHICH IS AN UNCTLED ARPT WITHIN THE CAK CLASS C AIRSPACE, IN CLR VMC, I CALLED CAK APCH STATING THAT I HAD JUST DEPARTED RWY 7 AT AKR, ON AN EASTERLY HDG, THAT I HAD THE CURRENT CAK ATIS INFO, AND WAS INBOUND TO CAK. I RECEIVED NO IMMEDIATE RESPONSE. WATCHING FOR TFC AND CONTINUING TO CLB, I CALLED A SECOND TIME. CAK APCH ANSWERED AND ASSIGNED A XPONDER CODE TO ME. SHORTLY THEREAFTER, APCH CALLED AGAIN STATING THAT I WAS IN RADAR CONTACT 7 MI E OF AKR. MOMENTS LATER HE CALLED AGAIN ASKING FOR MY ALT. I RESPONDED THAT I WAS LEVEL AT 3100 FT MSL. THE CTLR THEN BECAME QUITE ANGERED AND STRONG IN HIS CRITICISM OF MY HAVING REACHED THAT ALT WITHOUT BEING IN CONTACT WITH HIM. HE ASSIGNED A HDG FOR 'TFC SEPARATION' OF 090 DEGS, WHICH TOOK ME WELL OUTSIDE OF THE CLASS C AIRSPACE. LATER, WHILE HE ASSIGNED A RECIPROCAL HDG OF 270 DEGS TO ME, HE CONTINUED HIS CRITICISM OF MY HAVING ENTERED HIS AIRSPACE EXPLAINING THAT HE WAS WORKING OTHER TFC. HIS TONE WAS LESS HARSH AT THIS TIME, ALMOST INSTRUCTIVE. AT THE COMPLETION OF HIS CRITIQUE HE TOLD ME TO CONTACT CAK TWR. I SIMPLY THANKED HIM AND CHANGED TO THE TWR FREQ. IN THE FUTURE, I WILL BE MORE ATTENTIVE TO THE ALT RESTRS OF THE VARIOUS CLASSES OF AIRSPACE.

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.