C182 pilot at 9;500 ft; using flight following with luke approach; is issued a 030 degree heading to...

Narrative:

[I was on a] VFR part 91 flight to abq. At about 30 NM west of phx at an altitude of 9;500 MSL; contacted phx approach as a courtesy for radar advisories while transitioning the phx area above class bravo airspace. Received transponder code and was identified. Phx approach indicated to notify prior to any altitude change. I was then told to contact luke approach; which I did. Luke controller directed me to change heading to 030. No other information was given; not a traffic advisory; not a conflict; nothing; no reason given. This heading would turn me directly into alert area A231. I informed luke that I was VFR; in class echo airspace and my flight plan was direct to peaks intersection then to sjn VOR. Controller again; with no reason given; directed me to turn to a heading of 030. I again informed him I was VFR in class echo airspace and 'unable.' luke controller indicated that I was violating a 'high altitude' traffic pattern and need to turn away from it. I was monitoring an IFR certified G430 moving map; had a ipad moving map utilizing 'foreflight;' also current; a current phx sectional paper map; a phx tac chart all in front of me with no (I mean none) indication of restricted; MOA; alert; prohibited or any other special use airspace that I might be encroaching upon. I asked multiple times what airspace I was violating. I requested a time check and asked if a supervisor could plug in and explain why a VFR flight was attempting to be vectored. I requested a phone number as so I could speak with them upon my arrival to abq. I spoke with a sergeant who indicated that he was in charge and he indicated a potential deviation would be filed and he used a chapter 5 aim paragraph as the regulation that he could vector anyone anywhere he decided. I tried to explain that he could suggest a heading or vector; but it was not proper; from my 30 years of flying; to be vectoring VFR flights; because of uncharted airspace that they claim they own and control. I ceased any further discussion with him.

Original NASA ASRS Text

Title: C182 pilot at 9;500 FT; using flight following with Luke Approach; is issued a 030 degree heading to avoid a 'high altitude traffic pattern.' Since there is no indication of military airspace on available charts or GPS the reporter declines the request.

Narrative: [I was on a] VFR Part 91 flight to ABQ. At about 30 NM west of PHX at an altitude of 9;500 MSL; contacted PHX Approach as a courtesy for radar advisories while transitioning the PHX area above Class Bravo airspace. Received transponder code and was identified. PHX Approach indicated to notify prior to any altitude change. I was then told to contact Luke Approach; which I did. Luke Controller directed me to change heading to 030. No other information was given; not a traffic advisory; not a conflict; nothing; no reason given. This heading would turn me directly into Alert Area A231. I informed Luke that I was VFR; in Class Echo airspace and my flight plan was direct to PEAKS Intersection then to SJN VOR. Controller again; with no reason given; directed me to turn to a heading of 030. I again informed him I was VFR in Class Echo airspace and 'unable.' Luke Controller indicated that I was violating a 'high altitude' traffic pattern and need to turn away from it. I was monitoring an IFR certified G430 moving map; had a iPad moving map utilizing 'Foreflight;' also current; a current PHX sectional paper map; a PHX TAC chart all in front of me with no (I mean none) indication of restricted; MOA; Alert; Prohibited or any other special use airspace that I might be encroaching upon. I asked multiple times what airspace I was violating. I requested a time check and asked if a supervisor could plug in and explain why a VFR flight was attempting to be vectored. I requested a phone number as so I could speak with them upon my arrival to ABQ. I spoke with a Sergeant who indicated that he was in charge and he indicated a potential deviation would be filed and he used a Chapter 5 AIM paragraph as the regulation that he could vector anyone anywhere he decided. I tried to explain that he could suggest a heading or vector; but it was not proper; from my 30 years of flying; to be vectoring VFR flights; because of uncharted airspace that they claim they own and control. I ceased any further discussion with him.

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

Attributes
ACN	1010658
Time
Date	201205
Local Time Of Day	1201-1800
Place
Locale Reference	PHX.Airport
State Reference	AZ
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	Skylane 182/RG Turbo Skylane/RG
Operating Under FAR Part	Part 91
Flight Phase	Cruise
Route In Use	Direct
Flight Plan	VFR
Person 1
Function	Pilot Flying Single Pilot
Qualification	Flight Crew Instrument Flight Crew Multiengine Flight Crew Flight Instructor Flight Crew Air Transport Pilot (ATP)
Experience	Flight Crew Last 90 Days 35 Flight Crew Total 3100 Flight Crew Type 2900
Events
Anomaly	ATC Issue All Types Deviation - Procedural Published Material / Policy

C182 pilot at 9;500 ft; using flight following with luke approach; is issued a 030 degree heading to avoid a 'high altitude traffic pattern.' since there is no indication of military airspace on available charts or GPS the reporter declines the request.