BE20 PIC has verbal conflict with cak approach control over approach sequencing to cak airport.

Attributes
ACN	565123
Time
Date	200211
Day	Fri
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : cak.airport
State Reference	OH
Altitude	msl bound lower : 2500 msl bound upper : 7000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : cak.tracon
Operator	general aviation : personal
Make Model Name	Super King Air 200 HDC
Operating Under FAR Part	Part 91
Flight Phase	descent : intermediate altitude
Route In Use	arrival : on vectors
Flight Plan	VFR
Person 1
Affiliation	other
Function	flight crew : single pilot
Qualification	pilot : atp pilot : commercial pilot : flight engineer pilot : multi engine pilot : instrument
Experience	flight time last 90 days : 110 flight time total : 6000 flight time type : 150
ASRS Report	565123
Person 2
Affiliation	government : faa
Function	controller : approach
Events
Anomaly	non adherence : published procedure
Independent Detector	other controllera other flight crewa
Resolutory Action	controller : issued new clearance controller : separated traffic controller : issued advisory flight crew : returned to intended or assigned course flight crew : took precautionary avoidance action
Consequence	faa : assigned or threatened penalties faa : reviewed incident with flight crew
Supplementary
Problem Areas	Airspace Structure ATC Human Performance Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance

Narrative:

I was single pilot, part 91, captain of king air B200. I was on an IFR flight plan en route from kzzv to kcak at 7000 ft controled by ZID. When handed off to akron-canton approach, I was about 20 NM ssw of the airport and 10 NM from class C airspace. Approach controller told me to 'anticipate vectors to ILS approach to runway 23.' I responded that I had a visual on the airport and requested vectors to visual approach runway 23. WX was severe clear. Controller responded in a very authoritarian, annoyed voice that 'I will decide what vectors to effect airport sequencing.' I had been monitoring kcak tower on #2 VHF radio and only heard 1 light single in the pattern and 1 twin on 5-7 mi final for runway 23. Without for a handoff to the tower, I cancelled the instrument flight plan and accepted a different squawk from the annoyed approach controller. I believe I told him I was switching to kcak tower (but I don't recall). When I was at 2500 ft and 7 NM from the tower (below class C overhang), I established contact with the tower controller and asked for clearance for the visual approach. At no time did I penetrate class C airspace up to this point. His response was, 'how did you get over on this frequency?' I told him I'd cancelled instruments and just switched over without prompting. He told me to return to approach control for sequence and clearance into class 'C.' when I re-established radio contact with approach, he turned me to a 090 degree heading (as punishment for my radio breach). There was at least 5 mi separation from traffic on final and I stated that I had the visual. Still, he drove me outside of the OM before he let me have the visual. While being vectored, he badgered me about my procedures and threatened me with a comment about a 'possible deviation.' he instructed me to copy a phone number during a rather critical part of the flight. I thought he was uncooperative, spiteful and petty. I called per the instruments after landing and was told by his supervisor that he was 'going to pull the tapes and file a 'deviation report.' he accused me of not understanding class C procedures.

Original NASA ASRS Text

Title: BE20 PIC HAS VERBAL CONFLICT WITH CAK APCH CTL OVER APCH SEQUENCING TO CAK ARPT.

Narrative: I WAS SINGLE PLT, PART 91, CAPT OF KING AIR B200. I WAS ON AN IFR FLT PLAN ENRTE FROM KZZV TO KCAK AT 7000 FT CTLED BY ZID. WHEN HANDED OFF TO AKRON-CANTON APCH, I WAS ABOUT 20 NM SSW OF THE ARPT AND 10 NM FROM CLASS C AIRSPACE. APCH CTLR TOLD ME TO 'ANTICIPATE VECTORS TO ILS APCH TO RWY 23.' I RESPONDED THAT I HAD A VISUAL ON THE ARPT AND REQUESTED VECTORS TO VISUAL APCH RWY 23. WX WAS SEVERE CLR. CTLR RESPONDED IN A VERY AUTHORITARIAN, ANNOYED VOICE THAT 'I WILL DECIDE WHAT VECTORS TO EFFECT ARPT SEQUENCING.' I HAD BEEN MONITORING KCAK TWR ON #2 VHF RADIO AND ONLY HEARD 1 LIGHT SINGLE IN THE PATTERN AND 1 TWIN ON 5-7 MI FINAL FOR RWY 23. WITHOUT FOR A HDOF TO THE TWR, I CANCELLED THE INST FLT PLAN AND ACCEPTED A DIFFERENT SQUAWK FROM THE ANNOYED APCH CTLR. I BELIEVE I TOLD HIM I WAS SWITCHING TO KCAK TWR (BUT I DON'T RECALL). WHEN I WAS AT 2500 FT AND 7 NM FROM THE TWR (BELOW CLASS C OVERHANG), I ESTABLISHED CONTACT WITH THE TWR CTLR AND ASKED FOR CLRNC FOR THE VISUAL APCH. AT NO TIME DID I PENETRATE CLASS C AIRSPACE UP TO THIS POINT. HIS RESPONSE WAS, 'HOW DID YOU GET OVER ON THIS FREQ?' I TOLD HIM I'D CANCELLED INSTS AND JUST SWITCHED OVER WITHOUT PROMPTING. HE TOLD ME TO RETURN TO APCH CTL FOR SEQUENCE AND CLRNC INTO CLASS 'C.' WHEN I RE-ESTABLISHED RADIO CONTACT WITH APCH, HE TURNED ME TO A 090 DEG HDG (AS PUNISHMENT FOR MY RADIO BREACH). THERE WAS AT LEAST 5 MI SEPARATION FROM TFC ON FINAL AND I STATED THAT I HAD THE VISUAL. STILL, HE DROVE ME OUTSIDE OF THE OM BEFORE HE LET ME HAVE THE VISUAL. WHILE BEING VECTORED, HE BADGERED ME ABOUT MY PROCS AND THREATENED ME WITH A COMMENT ABOUT A 'POSSIBLE DEV.' HE INSTRUCTED ME TO COPY A PHONE NUMBER DURING A RATHER CRITICAL PART OF THE FLT. I THOUGHT HE WAS UNCOOPERATIVE, SPITEFUL AND PETTY. I CALLED PER THE INSTS AFTER LNDG AND WAS TOLD BY HIS SUPVR THAT HE WAS 'GOING TO PULL THE TAPES AND FILE A 'DEV RPT.' HE ACCUSED ME OF NOT UNDERSTANDING CLASS C PROCS.

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.