Narrative:

I unintentionaly penetrated the phx TCA southeast of mesa, az. Falcon field while executing the missed approach procedure from the NDB-C approach at that airport. We had completed the phx sky harbor il, the sdl VOR-a, the dvt NDB and the ffz NDB-C. All had gone quite smoothly, with approach control allowing the same squawk on the transponder and return to approach frequency 120.7 following the sdl and dvt approachs. Following the dvt NDB approach, I requested from approach control the NDB-C to ffz (falcon) to be a 'missed approach' followed by radar vectors to the P10 (chandler) VOR runway 4 approach for a 'full stop' landing. The controller on 120.7 told me I was 'cleared' practice NDB-C approach to falcon field, squawk 1200, contact falcon tower 124.6 and use 124.1 on the missed approach. The new controller would have a squawk for us. Well, we made the approach and commenced the missed approach procedure as published at the map. Falcon tower told us to contact approach leaving 2900'. We were light in weight and climb out was probably over 1000 FPM. When we changed to 124.1 and attempted to contact approach control the controller said he could 'only hear our call sign' and that there was static squeal backgnd noise in our transmission. We heard the controller quite clearly. I took over rt from my student and changed radios to communication #2 which the controller understood. However, before we received our clearance we had climbed through the floor of the TCA which was 4000' in that area. The controller asked our altitude and informed us we were in the TCA already. I took control and began a descent and asked the controller what he wanted us to do. He went ahead and cleared us with a radar vector toward the (IAF) for the chandler VOR approach. What followed then was an informative description of far 91.131 regarding TCA entry west/O a clearance. The controller then indicated that they would pursue the matter no further. We were vectored for chandler and completed the flight west/O further problem. The controller was professional and courteous and no telephone number was issued. This is my first and only TCA encroachment after more than 1 1/2 yrs in the san diego area, flying almost daily, to include regular flts in the los angeles area. As PIC there are 3 things on my part which could have prevented this situation: unfamiliarity with the orientation of the FF2 missed approach to the phx TCA. Frankly, this was the first time I had done this approach and I should have oriented myself better before doing it. Division of attention between instructing, watching the rate of climb, and the radio problem which caused me to switch to communication 2 and do the rt. Being lulled into the smoothness of contacting approach control in previous approachs and therefore expecting the controller to be aware of what we had requested from the previous controller. That assumption was in error. I might add that the controller on 124.1 was the only one whoheard a loud static backgnd squeal in our transmission. We had no prior or subsequent problems with initial rt in the phoenix area or the tucson area. Had the first rt been more clear to the controller the event would not have happened. However the far is quite clear in this matter, poor communications being no defense.

Google
 

Original NASA ASRS Text

Title: IFR TRAINING FLT ON A MISSED APCH, PENETRATED TCA ON CLIMBOUT.

Narrative: I UNINTENTIONALY PENETRATED THE PHX TCA SE OF MESA, AZ. FALCON FIELD WHILE EXECUTING THE MISSED APCH PROC FROM THE NDB-C APCH AT THAT ARPT. WE HAD COMPLETED THE PHX SKY HARBOR IL, THE SDL VOR-A, THE DVT NDB AND THE FFZ NDB-C. ALL HAD GONE QUITE SMOOTHLY, WITH APCH CTL ALLOWING THE SAME SQUAWK ON THE XPONDER AND RETURN TO APCH FREQ 120.7 FOLLOWING THE SDL AND DVT APCHS. FOLLOWING THE DVT NDB APCH, I REQUESTED FROM APCH CTL THE NDB-C TO FFZ (FALCON) TO BE A 'MISSED APCH' FOLLOWED BY RADAR VECTORS TO THE P10 (CHANDLER) VOR RWY 4 APCH FOR A 'FULL STOP' LNDG. THE CTLR ON 120.7 TOLD ME I WAS 'CLRED' PRACTICE NDB-C APCH TO FALCON FIELD, SQUAWK 1200, CONTACT FALCON TWR 124.6 AND USE 124.1 ON THE MISSED APCH. THE NEW CTLR WOULD HAVE A SQUAWK FOR US. WELL, WE MADE THE APCH AND COMMENCED THE MISSED APCH PROC AS PUBLISHED AT THE MAP. FALCON TWR TOLD US TO CONTACT APCH LEAVING 2900'. WE WERE LIGHT IN WEIGHT AND CLBOUT WAS PROBABLY OVER 1000 FPM. WHEN WE CHANGED TO 124.1 AND ATTEMPTED TO CONTACT APCH CTL THE CTLR SAID HE COULD 'ONLY HEAR OUR CALL SIGN' AND THAT THERE WAS STATIC SQUEAL BACKGND NOISE IN OUR XMISSION. WE HEARD THE CTLR QUITE CLRLY. I TOOK OVER RT FROM MY STUDENT AND CHANGED RADIOS TO COM #2 WHICH THE CTLR UNDERSTOOD. HOWEVER, BEFORE WE RECEIVED OUR CLRNC WE HAD CLBED THROUGH THE FLOOR OF THE TCA WHICH WAS 4000' IN THAT AREA. THE CTLR ASKED OUR ALT AND INFORMED US WE WERE IN THE TCA ALREADY. I TOOK CTL AND BEGAN A DSNT AND ASKED THE CTLR WHAT HE WANTED US TO DO. HE WENT AHEAD AND CLRED US WITH A RADAR VECTOR TOWARD THE (IAF) FOR THE CHANDLER VOR APCH. WHAT FOLLOWED THEN WAS AN INFORMATIVE DESCRIPTION OF FAR 91.131 REGARDING TCA ENTRY W/O A CLRNC. THE CTLR THEN INDICATED THAT THEY WOULD PURSUE THE MATTER NO FURTHER. WE WERE VECTORED FOR CHANDLER AND COMPLETED THE FLT W/O FURTHER PROB. THE CTLR WAS PROFESSIONAL AND COURTEOUS AND NO TELEPHONE NUMBER WAS ISSUED. THIS IS MY FIRST AND ONLY TCA ENCROACHMENT AFTER MORE THAN 1 1/2 YRS IN THE SAN DIEGO AREA, FLYING ALMOST DAILY, TO INCLUDE REGULAR FLTS IN THE LOS ANGELES AREA. AS PIC THERE ARE 3 THINGS ON MY PART WHICH COULD HAVE PREVENTED THIS SITUATION: UNFAMILIARITY WITH THE ORIENTATION OF THE FF2 MISSED APCH TO THE PHX TCA. FRANKLY, THIS WAS THE FIRST TIME I HAD DONE THIS APCH AND I SHOULD HAVE ORIENTED MYSELF BETTER BEFORE DOING IT. DIVISION OF ATTN BTWN INSTRUCTING, WATCHING THE RATE OF CLB, AND THE RADIO PROB WHICH CAUSED ME TO SWITCH TO COM 2 AND DO THE RT. BEING LULLED INTO THE SMOOTHNESS OF CONTACTING APCH CTL IN PREVIOUS APCHS AND THEREFORE EXPECTING THE CTLR TO BE AWARE OF WHAT WE HAD REQUESTED FROM THE PREVIOUS CTLR. THAT ASSUMPTION WAS IN ERROR. I MIGHT ADD THAT THE CTLR ON 124.1 WAS THE ONLY ONE WHOHEARD A LOUD STATIC BACKGND SQUEAL IN OUR XMISSION. WE HAD NO PRIOR OR SUBSEQUENT PROBS WITH INITIAL RT IN THE PHOENIX AREA OR THE TUCSON AREA. HAD THE FIRST RT BEEN MORE CLR TO THE CTLR THE EVENT WOULD NOT HAVE HAPPENED. HOWEVER THE FAR IS QUITE CLR IN THIS MATTER, POOR COMS BEING NO DEFENSE.

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.