Narrative:

We were cleared for takeoff on runway 36 and told to maintain runway heading. As we were lining up for takeoff; I saw a GA aircraft approximately 3.5 miles to the south of the airport. I also observed a C152 midfield; just to the east of the centerline of runway 36 on a northeast heading approximately 100 feet AGL. This aircraft was on a practice miss approach or go around. It appeared that the C152 was turning right.takeoff roll and rotation were normal. No unusual events noted.at positive rate; first officer (first officer) flying pilot called for gear up. Right after selecting gear up; we got a TCAS popup and we observed a C152 at our same altitude (approximately 300 feet AGL) and approximately 250 feet on the left side of our aircraft. At no time during takeoff roll and/or rotation did the first officer or myself see the C152 anywhere near our flight path. Nor did we see the C152 turn left into our flight path.below remarks are from a conversation that I had with the msn tower supervisor:the supervisor told me that the C152 was a local based trainer with a CFI and student on board. The tower supervisor also told me that the controller had told the C152 to turn right twice and maintain a pattern altitude of 1000 feet (which I did hear). The controller didn't get any readback from the C152. Right after the second attempt trying to communicate with the C152; the controller got distracted by another aircraft. When the controller looked down field; he observed that the C152 had actually turned left. He thought that the C152 was well west of the extended centerline of RWY36. In my opinion the C152 was not well west of the extended centerline of runway 36.human error was caused by tower controller getting distracted and the CFI not having situational awareness (missed ATC call).[suggest] delay takeoff until you are sure that all aircrafts are clear of the departure path at a ATC controlled airport.

Related reports:

Google
 

Original NASA ASRS Text

Title: EMB-145 Captain reported NMAC with a C152 shortly after takeoff from MSN.

Narrative: We were cleared for takeoff on Runway 36 and told to maintain Runway heading. As we were lining up for takeoff; I saw a GA aircraft approximately 3.5 miles to the South of the airport. I also observed a C152 midfield; just to the east of the centerline of Runway 36 on a northeast heading approximately 100 feet AGL. This aircraft was on a practice miss approach or go around. It appeared that the C152 was turning right.Takeoff roll and rotation were normal. No unusual events noted.At positive rate; First Officer (FO) Flying Pilot called for gear up. Right after selecting gear up; we got a TCAS popup and we observed a C152 at our same altitude (approximately 300 feet AGL) and approximately 250 Feet on the left side of our aircraft. At no time during takeoff roll and/or rotation did the FO or myself see the C152 anywhere near our flight path. Nor did we see the C152 turn left into our flight path.Below remarks are from a conversation that I had with the MSN Tower Supervisor:The Supervisor told me that the C152 was a local based trainer with a CFI and student on board. The Tower Supervisor also told me that the Controller had told the C152 to turn right twice and maintain a pattern altitude of 1000 Feet (which I did hear). The Controller didn't get any readback from the C152. Right after the second attempt trying to communicate with the C152; the Controller got distracted by another aircraft. When the Controller looked down field; he observed that the C152 had actually turned left. He thought that the C152 was well west of the extended centerline of RWY36. In my opinion the C152 was not well west of the extended centerline of Runway 36.Human Error was caused by Tower Controller getting distracted and the CFI not having situational awareness (missed ATC call).[Suggest] Delay takeoff until you are sure that all aircrafts are clear of the departure path at a ATC controlled airport.

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.