Narrative:

I was returning from a business meeting to my home airport, IFR in clear, but occasionally cloudy VMC. I entered the traffic pattern on the downwind for runway 16 while still under radar control but with the airport clearly visible and was cleared #1 for a visual to runway 16. I extended my downwind slightly as I slowed down the plane (T206H) and as I turned on base, approach called me and told to make my turn and go to the numbers, that I was #1 to land on runway 16. I was then asked if I had another plane (I believe it was a beech bonanza) that would have been to my north and would be #2 behind me. I advised I did not have a visual on him but I did have him on my traffic avoidance system and continued my turn from base to final. As I completed my turn to final, I heard approach tell the bonanza it was #1 to land. Simultaneously my TAS began to wail like a banshee 'traffic, traffic, traffic.' I looked at it and the little white DOT representing the plane behind me was about 300 ft above me and behind me, but so close I could not see any spacing on its image on the TAS. I then began a shallow descent and a 360 degree turn to the east without notifying approach (I assumed the controller knew what was going on and I really believed I had no time to talk, only time to fly the plane, this happened so quickly). The controller came on the line and, without asking me any questions, asked me if I was turning out of the approach path. I said yes, and then was berated over making the turn without calling him first and the problems that could cause by doing it without notification. I was surprised and taken aback by what he said to me and said nothing in response but continued the 360 degree turn, was then cleared to land and landed. Upon landing and while still on the runway the approach controller called me up and apologized saying that he did not know that radar had approved another plane to land number one while I was on the approach, and that he had 'put me between a rock and a hard place.' I thanked him. Contributing factors: I should have had my plane fully slowed to approach or nearly approach speed when I entered the downwind for landing. I should not have extended my downwind without notifying approach first. I could have tried harder to get a visual on the bonanza, or whatever the second plane was, but there were some clouds in the area and just assumed when I could not find him, he was probably obscured by the clouds. My TAS showed him not to be a problem. I should have monitored the TAS a little more closely on approach. Because the other plane was close enough to set off its warning, I was taken by surprise when it alerted me and did not believe I had time to call approach to advise them of the conflict I had encountered or to tell them two planes have been approved number one to land on the same runway at the same time. I responded first planning to call after I got out of the flight path.

Google
 

Original NASA ASRS Text

Title: A C206 PLT CLRED FOR A VISUAL APCH TO RWY 16 AT AVL TOOK EVASIVE ACTION TO AVOID A BEECH BONANZA THAT WAS ALSO TURNED IN FOR AN APCH.

Narrative: I WAS RETURNING FROM A BUSINESS MEETING TO MY HOME ARPT, IFR IN CLR, BUT OCCASIONALLY CLOUDY VMC. I ENTERED THE TFC PATTERN ON THE DOWNWIND FOR RWY 16 WHILE STILL UNDER RADAR CTL BUT WITH THE ARPT CLRLY VISIBLE AND WAS CLRED #1 FOR A VISUAL TO RWY 16. I EXTENDED MY DOWNWIND SLIGHTLY AS I SLOWED DOWN THE PLANE (T206H) AND AS I TURNED ON BASE, APCH CALLED ME AND TOLD TO MAKE MY TURN AND GO TO THE NUMBERS, THAT I WAS #1 TO LAND ON RWY 16. I WAS THEN ASKED IF I HAD ANOTHER PLANE (I BELIEVE IT WAS A BEECH BONANZA) THAT WOULD HAVE BEEN TO MY N AND WOULD BE #2 BEHIND ME. I ADVISED I DID NOT HAVE A VISUAL ON HIM BUT I DID HAVE HIM ON MY TFC AVOIDANCE SYS AND CONTINUED MY TURN FROM BASE TO FINAL. AS I COMPLETED MY TURN TO FINAL, I HEARD APCH TELL THE BONANZA IT WAS #1 TO LAND. SIMULTANEOUSLY MY TAS BEGAN TO WAIL LIKE A BANSHEE 'TFC, TFC, TFC.' I LOOKED AT IT AND THE LITTLE WHITE DOT REPRESENTING THE PLANE BEHIND ME WAS ABOUT 300 FT ABOVE ME AND BEHIND ME, BUT SO CLOSE I COULD NOT SEE ANY SPACING ON ITS IMAGE ON THE TAS. I THEN BEGAN A SHALLOW DSCNT AND A 360 DEG TURN TO THE E WITHOUT NOTIFYING APCH (I ASSUMED THE CTLR KNEW WHAT WAS GOING ON AND I REALLY BELIEVED I HAD NO TIME TO TALK, ONLY TIME TO FLY THE PLANE, THIS HAPPENED SO QUICKLY). THE CTLR CAME ON THE LINE AND, WITHOUT ASKING ME ANY QUESTIONS, ASKED ME IF I WAS TURNING OUT OF THE APCH PATH. I SAID YES, AND THEN WAS BERATED OVER MAKING THE TURN WITHOUT CALLING HIM FIRST AND THE PROBS THAT COULD CAUSE BY DOING IT WITHOUT NOTIFICATION. I WAS SURPRISED AND TAKEN ABACK BY WHAT HE SAID TO ME AND SAID NOTHING IN RESPONSE BUT CONTINUED THE 360 DEG TURN, WAS THEN CLRED TO LAND AND LANDED. UPON LNDG AND WHILE STILL ON THE RWY THE APCH CTLR CALLED ME UP AND APOLOGIZED SAYING THAT HE DID NOT KNOW THAT RADAR HAD APPROVED ANOTHER PLANE TO LAND NUMBER ONE WHILE I WAS ON THE APCH, AND THAT HE HAD 'PUT ME BETWEEN A ROCK AND A HARD PLACE.' I THANKED HIM. CONTRIBUTING FACTORS: I SHOULD HAVE HAD MY PLANE FULLY SLOWED TO APCH OR NEARLY APCH SPEED WHEN I ENTERED THE DOWNWIND FOR LNDG. I SHOULD NOT HAVE EXTENDED MY DOWNWIND WITHOUT NOTIFYING APCH FIRST. I COULD HAVE TRIED HARDER TO GET A VISUAL ON THE BONANZA, OR WHATEVER THE SECOND PLANE WAS, BUT THERE WERE SOME CLOUDS IN THE AREA AND JUST ASSUMED WHEN I COULD NOT FIND HIM, HE WAS PROBABLY OBSCURED BY THE CLOUDS. MY TAS SHOWED HIM NOT TO BE A PROB. I SHOULD HAVE MONITORED THE TAS A LITTLE MORE CLOSELY ON APCH. BECAUSE THE OTHER PLANE WAS CLOSE ENOUGH TO SET OFF ITS WARNING, I WAS TAKEN BY SURPRISE WHEN IT ALERTED ME AND DID NOT BELIEVE I HAD TIME TO CALL APCH TO ADVISE THEM OF THE CONFLICT I HAD ENCOUNTERED OR TO TELL THEM TWO PLANES HAVE BEEN APPROVED NUMBER ONE TO LAND ON THE SAME RWY AT THE SAME TIME. I RESPONDED FIRST PLANNING TO CALL AFTER I GOT OUT OF THE FLT PATH.

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.