Narrative:

I was on an IFR flight plan from prescott, az, to deer valley, az. The flight was instructional in nature. I had requested the full NDB approach into deer valley airport. Approximately 5 mins from the IAF, phx approach control began issuing radar vectors for direct deer valley airport. When I queried approach control about the possibility of the full NDB approach, they advised me they were unable at this time IFR, however, I could conduct the practice approach VFR. I canceled IFR and approach control advised me to remain on their frequency with my current squawk for continued TA's and radar vectors. Phx approach control handed me off to deer valley tower. Deer valley tower asked me to advise them on how the approach would terminate. I advised them I would like to execute the missed approach as published to the hold and pick up my IFR back to prescott. Deer valley tower instructed me to execute the missed approach as published, advised when missed approach and that I would have to contact phx approach control after I went missed for my IFR back to prescott. At the missed approach point, I advised deer valley tower that I was going missed approach. Deer valley tower instructed me to contact the alternate deer valley tower frequency. I reported on frequency and continued to execute the missed approach as published. I then contacted phx approach control and reported holding as published at avent intersection 7000 ft and requested to pick up my IFR to prescott. Phx approach control told me to remain VMC, depart avent intersection northwest and contact ZAB for my IFR to prescott. I contacted ZAB and requested my IFR back to prescott. ZAB asked me if I was squawking VFR. ZAB then issued me a new squawk code and cleared me IFR to prescott. While en route to prescott, ZAB advised me to contact phx approach control after landing. While still in-flight, I began to reflect on why phx approach would want to talk to me. I then realized that published missed approach procedure at deer valley airport depicts the hold at 7000 ft MSL while the floor of the class B airspace at that location is 6000 ft MSL. I should have realized earlier that executing the missed approach as published would have placed me inside class B airspace. Since I was VFR at the time, when told to execute the missed approach as published, I should have requested a lower altitude for the hold to remain clear of the class B airspace. To prevent this from happening in the future, I should not be locked into executing a missed approach as published if VFR and not on an IFR flight plan at the time, regardless of my squawk code. Secondly, if given an instruction that could allow me to infringe upon a regulation, I should query the controller for further clarification or request another action. Thirdly, I should review controled airspace dimensions prior to operating in or near controled airspace.

Related reports:

Google
 

Original NASA ASRS Text

Title: BE76 PLT EXECUTES A VFR MISSED APCH AND CLBS INTO CLASS B AIRSPACE WITHOUT CLRNC.

Narrative: I WAS ON AN IFR FLT PLAN FROM PRESCOTT, AZ, TO DEER VALLEY, AZ. THE FLT WAS INSTRUCTIONAL IN NATURE. I HAD REQUESTED THE FULL NDB APCH INTO DEER VALLEY ARPT. APPROX 5 MINS FROM THE IAF, PHX APCH CTL BEGAN ISSUING RADAR VECTORS FOR DIRECT DEER VALLEY ARPT. WHEN I QUERIED APCH CTL ABOUT THE POSSIBILITY OF THE FULL NDB APCH, THEY ADVISED ME THEY WERE UNABLE AT THIS TIME IFR, HOWEVER, I COULD CONDUCT THE PRACTICE APCH VFR. I CANCELED IFR AND APCH CTL ADVISED ME TO REMAIN ON THEIR FREQ WITH MY CURRENT SQUAWK FOR CONTINUED TA'S AND RADAR VECTORS. PHX APCH CTL HANDED ME OFF TO DEER VALLEY TWR. DEER VALLEY TWR ASKED ME TO ADVISE THEM ON HOW THE APCH WOULD TERMINATE. I ADVISED THEM I WOULD LIKE TO EXECUTE THE MISSED APCH AS PUBLISHED TO THE HOLD AND PICK UP MY IFR BACK TO PRESCOTT. DEER VALLEY TWR INSTRUCTED ME TO EXECUTE THE MISSED APCH AS PUBLISHED, ADVISED WHEN MISSED APCH AND THAT I WOULD HAVE TO CONTACT PHX APCH CTL AFTER I WENT MISSED FOR MY IFR BACK TO PRESCOTT. AT THE MISSED APCH POINT, I ADVISED DEER VALLEY TWR THAT I WAS GOING MISSED APCH. DEER VALLEY TWR INSTRUCTED ME TO CONTACT THE ALTERNATE DEER VALLEY TWR FREQ. I RPTED ON FREQ AND CONTINUED TO EXECUTE THE MISSED APCH AS PUBLISHED. I THEN CONTACTED PHX APCH CTL AND RPTED HOLDING AS PUBLISHED AT AVENT INTXN 7000 FT AND REQUESTED TO PICK UP MY IFR TO PRESCOTT. PHX APCH CTL TOLD ME TO REMAIN VMC, DEPART AVENT INTXN NW AND CONTACT ZAB FOR MY IFR TO PRESCOTT. I CONTACTED ZAB AND REQUESTED MY IFR BACK TO PRESCOTT. ZAB ASKED ME IF I WAS SQUAWKING VFR. ZAB THEN ISSUED ME A NEW SQUAWK CODE AND CLRED ME IFR TO PRESCOTT. WHILE ENRTE TO PRESCOTT, ZAB ADVISED ME TO CONTACT PHX APCH CTL AFTER LNDG. WHILE STILL INFLT, I BEGAN TO REFLECT ON WHY PHX APCH WOULD WANT TO TALK TO ME. I THEN REALIZED THAT PUBLISHED MISSED APCH PROC AT DEER VALLEY ARPT DEPICTS THE HOLD AT 7000 FT MSL WHILE THE FLOOR OF THE CLASS B AIRSPACE AT THAT LOCATION IS 6000 FT MSL. I SHOULD HAVE REALIZED EARLIER THAT EXECUTING THE MISSED APCH AS PUBLISHED WOULD HAVE PLACED ME INSIDE CLASS B AIRSPACE. SINCE I WAS VFR AT THE TIME, WHEN TOLD TO EXECUTE THE MISSED APCH AS PUBLISHED, I SHOULD HAVE REQUESTED A LOWER ALT FOR THE HOLD TO REMAIN CLR OF THE CLASS B AIRSPACE. TO PREVENT THIS FROM HAPPENING IN THE FUTURE, I SHOULD NOT BE LOCKED INTO EXECUTING A MISSED APCH AS PUBLISHED IF VFR AND NOT ON AN IFR FLT PLAN AT THE TIME, REGARDLESS OF MY SQUAWK CODE. SECONDLY, IF GIVEN AN INSTRUCTION THAT COULD ALLOW ME TO INFRINGE UPON A REG, I SHOULD QUERY THE CTLR FOR FURTHER CLARIFICATION OR REQUEST ANOTHER ACTION. THIRDLY, I SHOULD REVIEW CTLED AIRSPACE DIMENSIONS PRIOR TO OPERATING IN OR NEAR CTLED 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.