Narrative:

I took off from airmen's acres airport on runway at about XX12. Destination harvey young airport. Soon as I was airborne I called tulsa approach 119.1 for a transponder code and recognition and got no response. Then I called, I believe, 3 more times before getting a response. I was at 900 ft AGL. Meanwhile, I must have picked up on a tailwind at 900 ft as I was moving faster than usual. I was west, or right of runway 35-17 flight path (east commercial runway) and had looked for traffic and crossed over it to the east and then south. 119.5 was not very active and I expected a response to my call any second and probably was slightly in arsa when controller responded, which had happened fairly regular in past. It seemed to be routine for it to be that way and just got out of hand. When the controller got around to contacting me, he gave me a code and after 30-40 seconds, acknowledged radar contact and said 3 mi. Then he asked me to call tower and later called and said to call (telephone number), which turned out to be a private residence. I tried to call on arrival but the airport phone was busy, it was busy after I tied down, so I went home and tried to call all afternoon, but they wouldn't answer it. I was in my small aircraft. They wouldn't answer the tower phone on the next day either. I think it would be beneficial if, when pilots stack up on controllers, for controllers to issue a general warning for all planes wanting code to hold short of air traffic area until answered. But, what could be more dangerous than a bunch of planes doing 180's and 360's.

Related reports:

Google
 

Original NASA ASRS Text

Title: ERRONEOUS PENETRATION OF AIRSPACE. PROX OF ATA APCH RTE.

Narrative: I TOOK OFF FROM AIRMEN'S ACRES ARPT ON RWY AT ABOUT XX12. DEST HARVEY YOUNG ARPT. SOON AS I WAS AIRBORNE I CALLED TULSA APCH 119.1 FOR A TRANSPONDER CODE AND RECOGNITION AND GOT NO RESPONSE. THEN I CALLED, I BELIEVE, 3 MORE TIMES BEFORE GETTING A RESPONSE. I WAS AT 900 FT AGL. MEANWHILE, I MUST HAVE PICKED UP ON A TAILWIND AT 900 FT AS I WAS MOVING FASTER THAN USUAL. I WAS W, OR R OF RWY 35-17 FLT PATH (E COMMERCIAL RWY) AND HAD LOOKED FOR TFC AND CROSSED OVER IT TO THE E AND THEN S. 119.5 WAS NOT VERY ACTIVE AND I EXPECTED A RESPONSE TO MY CALL ANY SECOND AND PROBABLY WAS SLIGHTLY IN ARSA WHEN CTLR RESPONDED, WHICH HAD HAPPENED FAIRLY REGULAR IN PAST. IT SEEMED TO BE ROUTINE FOR IT TO BE THAT WAY AND JUST GOT OUT OF HAND. WHEN THE CTLR GOT AROUND TO CONTACTING ME, HE GAVE ME A CODE AND AFTER 30-40 SECONDS, ACKNOWLEDGED RADAR CONTACT AND SAID 3 MI. THEN HE ASKED ME TO CALL TWR AND LATER CALLED AND SAID TO CALL (TELEPHONE NUMBER), WHICH TURNED OUT TO BE A PRIVATE RESIDENCE. I TRIED TO CALL ON ARR BUT THE ARPT PHONE WAS BUSY, IT WAS BUSY AFTER I TIED DOWN, SO I WENT HOME AND TRIED TO CALL ALL AFTERNOON, BUT THEY WOULDN'T ANSWER IT. I WAS IN MY SMA. THEY WOULDN'T ANSWER THE TWR PHONE ON THE NEXT DAY EITHER. I THINK IT WOULD BE BENEFICIAL IF, WHEN PLTS STACK UP ON CTLRS, FOR CTLRS TO ISSUE A GENERAL WARNING FOR ALL PLANES WANTING CODE TO HOLD SHORT OF ATA UNTIL ANSWERED. BUT, WHAT COULD BE MORE DANGEROUS THAN A BUNCH OF PLANES DOING 180'S AND 360'S.

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.