Narrative:

Cdw ATIS X in effect landing runway 4; departing runway 4 and 28. Closed traffic training touch and go activity on runway 4 was taking place. We were cleared to take off on runway 28; runway heading for at least 1 mile and then right downwind departure to the east. We were aware of the closed traffic touch and go training on rw 4 (left traffic pattern) as we departed runway 28. After we reached 1 mile upwind on runway 28 and at about 1200 feet MSL; we reconfirmed with tower and that we were turning crosswind for a right downwind departure and climbing to 2000. Tower acknowledged. No traffic observed that would have been cause for alarm during take off. The only traffic we observed was the touch and go traffic; which was about to turn base for runway 4 at that time. About 10 seconds later; we hear a conversation of a pilot; presumed to be in closed traffic runway 4 touch and go; complain to the tower that another aircraft; and we do not know if that was us; 'almost hit' them. Tower appeared surprised by that call and cleared that aircraft to land on runway 4. No other conversation took place between that aircraft and tower at that time. No other conversation took place between tower and ourselves as we departed to the east.we presumed that the runway 4 touch and go traffic was unaware of us taking off on runway 28 and was surprised to find us depart runway 28; and climb out below them; while they were on left downwind for runway 4. Multiple runway departures obviously can be problematic; especially if everyone involved is not acutely aware of what is happening. The only recommendation; if one is needed; would be for tower to point out traffic departing; or in the pattern; to make everyone aware and avoid surprises.

Google
 

Original NASA ASRS Text

Title: C172 pilot overhears a conversation on CDW Tower frequency that leads him to believe that he may have been involved in a near miss during departure.

Narrative: CDW ATIS X in effect landing Runway 4; departing Runway 4 and 28. Closed traffic training touch and go activity on Runway 4 was taking place. We were cleared to take off on Runway 28; Runway heading for at least 1 mile and then right downwind departure to the East. We were aware of the closed traffic touch and go training on RW 4 (left traffic pattern) as we departed Runway 28. After we reached 1 mile upwind on Runway 28 and at about 1200 feet MSL; we reconfirmed with Tower and that we were turning crosswind for a right downwind departure and climbing to 2000. Tower acknowledged. No traffic observed that would have been cause for alarm during take off. The only traffic we observed was the touch and go traffic; which was about to turn base for Runway 4 at that time. About 10 seconds later; we hear a conversation of a pilot; presumed to be in closed traffic Runway 4 touch and go; complain to the Tower that another aircraft; and we do not know if that was us; 'almost hit' them. Tower appeared surprised by that call and cleared that aircraft to land on Runway 4. No other conversation took place between that aircraft and Tower at that time. No other conversation took place between Tower and ourselves as we departed to the East.We presumed that the Runway 4 touch and go traffic was unaware of us taking off on Runway 28 and was surprised to find us depart Runway 28; and climb out below them; while they were on left downwind for Runway 4. Multiple Runway departures obviously can be problematic; especially if everyone involved is not acutely aware of what is happening. The only recommendation; if one is needed; would be for Tower to point out traffic departing; or in the pattern; to make everyone aware and avoid surprises.

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