Narrative:

I was on an IFR flight plan in VMC conditions speaking with point mugu approach. My clearance was to fly from fim VOR direct to cooga intersection; descend and maintain 4000 ft. The ATIS specified that the VOR runway 26 approach was in use. At 0.4 DME from cooga; the point mugu approach controller cleared me for the VOR runway 26 approach and requested that I contact the tower. According to the camarillo VOR runway 26 approach chart; cooga is the IAF. Cooga requires a procedure turn. There is no mention on the chart of no procedure turn from fim to cooga! As requested; I tuned the tower frequency as I turned left to an outbound course of 067 degrees to start my procedure turn for the VOR runway 26 approach. Within 5 - 10 seconds the tower requested that I re-contact point mugu approach. I did as requested and was promptly rebuked for doing a procedure turn. The controller stated that I had not been given permission to fly the procedure turn and gave me a heading to intercept the final approach course back on the VOR runway 26 approach. Shocked; I turned to the heading; intercepted the final inbound course and was told to contact the tower. I landed without further incident. It is important to understand that I was not initially given radar vectors to intercept the final approach course inbound. Nor; was I asked not to do the procedure turn by the controller. My clearance upon reaching cooga was; 'cleared VOR runway 26 approach; contact tower 128.2.' there is no mention of nopt! I feel that this incident was directly related to a controller who wanted one thing but instead cleared me to do another. I recently spoke with another pilot on my field who had this same exact scenario years ago while flying a gulfstream ii. As far as I know there was no conflict with traffic in my case. However; something needs to be changed with how clrnces are issued to prevent this from happening in the future.

Google
 

Original NASA ASRS Text

Title: WHILE FLYING FIM DIRECT COOGA IN VMC CONDITIONS ON AN IFR FLT CLRNC; PLT OF TBM850 IS CLRED FOR A VOR RWY 26 APCH TO CMA. WHEN INITIATING THE PROC TURN; RPTR IS ADVISED BY APCH CTLR THAT A PROC TURN WAS NEITHER REQUIRED NOR AUTHORIZED.

Narrative: I WAS ON AN IFR FLT PLAN IN VMC CONDITIONS SPEAKING WITH POINT MUGU APCH. MY CLRNC WAS TO FLY FROM FIM VOR DIRECT TO COOGA INTXN; DSND AND MAINTAIN 4000 FT. THE ATIS SPECIFIED THAT THE VOR RWY 26 APCH WAS IN USE. AT 0.4 DME FROM COOGA; THE POINT MUGU APCH CTLR CLRED ME FOR THE VOR RWY 26 APCH AND REQUESTED THAT I CONTACT THE TWR. ACCORDING TO THE CAMARILLO VOR RWY 26 APCH CHART; COOGA IS THE IAF. COOGA REQUIRES A PROC TURN. THERE IS NO MENTION ON THE CHART OF NO PROC TURN FROM FIM TO COOGA! AS REQUESTED; I TUNED THE TWR FREQ AS I TURNED L TO AN OUTBOUND COURSE OF 067 DEGS TO START MY PROC TURN FOR THE VOR RWY 26 APCH. WITHIN 5 - 10 SECONDS THE TWR REQUESTED THAT I RE-CONTACT POINT MUGU APCH. I DID AS REQUESTED AND WAS PROMPTLY REBUKED FOR DOING A PROC TURN. THE CTLR STATED THAT I HAD NOT BEEN GIVEN PERMISSION TO FLY THE PROC TURN AND GAVE ME A HDG TO INTERCEPT THE FINAL APCH COURSE BACK ON THE VOR RWY 26 APCH. SHOCKED; I TURNED TO THE HDG; INTERCEPTED THE FINAL INBOUND COURSE AND WAS TOLD TO CONTACT THE TWR. I LANDED WITHOUT FURTHER INCIDENT. IT IS IMPORTANT TO UNDERSTAND THAT I WAS NOT INITIALLY GIVEN RADAR VECTORS TO INTERCEPT THE FINAL APCH COURSE INBOUND. NOR; WAS I ASKED NOT TO DO THE PROC TURN BY THE CTLR. MY CLRNC UPON REACHING COOGA WAS; 'CLRED VOR RWY 26 APCH; CONTACT TWR 128.2.' THERE IS NO MENTION OF NOPT! I FEEL THAT THIS INCIDENT WAS DIRECTLY RELATED TO A CTLR WHO WANTED ONE THING BUT INSTEAD CLRED ME TO DO ANOTHER. I RECENTLY SPOKE WITH ANOTHER PLT ON MY FIELD WHO HAD THIS SAME EXACT SCENARIO YEARS AGO WHILE FLYING A GULFSTREAM II. AS FAR AS I KNOW THERE WAS NO CONFLICT WITH TFC IN MY CASE. HOWEVER; SOMETHING NEEDS TO BE CHANGED WITH HOW CLRNCES ARE ISSUED TO PREVENT THIS FROM HAPPENING IN THE FUTURE.

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