Narrative:

I believe oversaturation of radio communications with both ZAB, phx approach, and scottsdale tower were contributing factors to this near midair collision. Our flight from prc-sdl was VFR. We were unable to obtain radar services from ZAB or phx approach, which could have led to a smoother transition to sdl tower. We contacted sdl tower 10 NM out. The tower was too busy to respond to us. At 8 NM out, we called the tower again. He simply stated something like he was not able to get us on his radar. He did not issue sequencing instructions. At 6 NM out, we called again, requesting landing. Using our call sign he advised us to call him back in 3 mins. He did not tell us to remain clear of class D airspace. I asked for clarification. He did not respond. At this time, we felt it prudent to remain clear of the sdl airspace and circle to the nnw. After about 2 360 degree circles, we contacted tower again. He told us to make a 4 mi 45 degree right entry for runway 21. (We now were to the north of the airport.) upon positioning for the 45 degree entry heading wbound, an aircraft to the north was observed. We maneuvered in a steep turn to the right to avoid this aircraft. The aircraft made no maneuvers to avoid us, and shortly after contacted sdl tower (approximately 3-4 mi out). I believe the sdl tower in addition to the other aircraft caused this situation to occur by not giving us entry instructions when originally requested, thereby only increasing frequency congestion and positioning us in a dangerous location where other arriving aircraft would be transitioning.

Related reports:

Google
 

Original NASA ASRS Text

Title: C172 INSTRUCTOR PLT CONCERNED WITH DIFFICULTY IN PATTERN ENTRY INTO SDF AND MANEUVERING AWAY FROM A DEPARTING C172 THAT APPARENTLY DID NOT HAVE THEM IN SIGHT.

Narrative: I BELIEVE OVERSATURATION OF RADIO COMS WITH BOTH ZAB, PHX APCH, AND SCOTTSDALE TWR WERE CONTRIBUTING FACTORS TO THIS NMAC. OUR FLT FROM PRC-SDL WAS VFR. WE WERE UNABLE TO OBTAIN RADAR SVCS FROM ZAB OR PHX APCH, WHICH COULD HAVE LED TO A SMOOTHER TRANSITION TO SDL TWR. WE CONTACTED SDL TWR 10 NM OUT. THE TWR WAS TOO BUSY TO RESPOND TO US. AT 8 NM OUT, WE CALLED THE TWR AGAIN. HE SIMPLY STATED SOMETHING LIKE HE WAS NOT ABLE TO GET US ON HIS RADAR. HE DID NOT ISSUE SEQUENCING INSTRUCTIONS. AT 6 NM OUT, WE CALLED AGAIN, REQUESTING LNDG. USING OUR CALL SIGN HE ADVISED US TO CALL HIM BACK IN 3 MINS. HE DID NOT TELL US TO REMAIN CLR OF CLASS D AIRSPACE. I ASKED FOR CLARIFICATION. HE DID NOT RESPOND. AT THIS TIME, WE FELT IT PRUDENT TO REMAIN CLR OF THE SDL AIRSPACE AND CIRCLE TO THE NNW. AFTER ABOUT 2 360 DEG CIRCLES, WE CONTACTED TWR AGAIN. HE TOLD US TO MAKE A 4 MI 45 DEG R ENTRY FOR RWY 21. (WE NOW WERE TO THE N OF THE ARPT.) UPON POSITIONING FOR THE 45 DEG ENTRY HDG WBOUND, AN ACFT TO THE N WAS OBSERVED. WE MANEUVERED IN A STEEP TURN TO THE R TO AVOID THIS ACFT. THE ACFT MADE NO MANEUVERS TO AVOID US, AND SHORTLY AFTER CONTACTED SDL TWR (APPROX 3-4 MI OUT). I BELIEVE THE SDL TWR IN ADDITION TO THE OTHER ACFT CAUSED THIS SIT TO OCCUR BY NOT GIVING US ENTRY INSTRUCTIONS WHEN ORIGINALLY REQUESTED, THEREBY ONLY INCREASING FREQ CONGESTION AND POSITIONING US IN A DANGEROUS LOCATION WHERE OTHER ARRIVING ACFT WOULD BE TRANSITIONING.

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.