Narrative:

After a normal engine start; taxi; and run up; I called springs tower that I was ready for departure on 17R. There was significant traffic at the airport and the tower frequency was very busy. It was my impression that the controller was a trainee. After waiting approximately 15 minutes at the hold short line; I was cleared for takeoff on runway 17R. After a normal takeoff; springs tower instructed me to turn right to a heading of 260. This is a normal procedure for westbound departures from this runway. I made turn and continued my climb out. There was significant radio traffic on the tower frequency. I heard another aircraft report entering on a 45; making this transmission several times without an acknowledgement from ATC. During my scan; I then saw another aircraft at my 11:00 position above me heading toward me. I made an immediate right hand diving evasive turn. After the maneuver; tower called me to report traffic at 11:00 less than one mile. I thought of responding to tower that I just avoided that traffic; but elected not to make the transmission due to the channel congestion. I then proceeded with my climb out and was directed to contact departure control. The flight was completed without further incident. I believe the root cause of the problem was with the local controller at kcos. Both the tower frequency and the airspace around the airport was extremely busy. The controller appeared to be a trainee and was very busy; with takeoffs; landings; and pattern work occurring on 3 different runways (17L;right; 13). This is evidenced by the very long delay I encountered waiting for a VFR take off clearance and the delayed traffic call out of my near miss traffic. I didn't receive the traffic notification until after I had taken evasive action.

Google
 

Original NASA ASRS Text

Title: An aircraft departing COS 17R was given a westbound turnout with another aircraft inbound on the 45; which resulted in the departing aircraft taking evasive action.

Narrative: After a normal engine start; taxi; and run up; I called Springs Tower that I was ready for departure on 17R. There was significant traffic at the airport and the Tower frequency was very busy. It was my impression that the controller was a trainee. After waiting approximately 15 minutes at the hold short line; I was cleared for takeoff on Runway 17R. After a normal takeoff; Springs Tower instructed me to turn right to a heading of 260. This is a normal procedure for westbound departures from this runway. I made turn and continued my climb out. There was significant radio traffic on the Tower frequency. I heard another aircraft report entering on a 45; making this transmission several times without an acknowledgement from ATC. During my scan; I then saw another aircraft at my 11:00 position above me heading toward me. I made an immediate right hand diving evasive turn. After the maneuver; Tower called me to report traffic at 11:00 less than one mile. I thought of responding to Tower that I just avoided that traffic; but elected not to make the transmission due to the channel congestion. I then proceeded with my climb out and was directed to contact Departure Control. The flight was completed without further incident. I believe the root cause of the problem was with the Local Controller at KCOS. Both the Tower frequency and the airspace around the airport was extremely busy. The controller appeared to be a trainee and was very busy; with takeoffs; landings; and pattern work occurring on 3 different runways (17L;R; 13). This is evidenced by the very long delay I encountered waiting for a VFR take off clearance and the delayed traffic call out of my near miss traffic. I didn't receive the traffic notification until after I had taken evasive action.

Data retrieved from NASA's ASRS site 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.