Narrative:

I was in charge in the tower and traffic was building so I opened the cab coordinator position. I was pre-briefing the cc (cab coordinator) when aircraft X was cleared for takeoff. Following the pre-brief I was helping LC2 scan the runways. The situation was complex because of photo flights and volume was high because of our runway configuration. Aircraft X was a south fan destined for mlb. LC2 incorrectly fanned the aircraft north instead of south. No one noticed the mistake until north called LC2 and asked about him. After I was relieved I was questioned by the flm (front line manager) why no one noticed the incorrect fan. I told him we were very busy. The flm then told me aircraft X declared an near midair collision. I asked him how and with who but he didn't know. He said he was looking into it. Our support specialist in charge of qa/qc showed me very briefly the radar playback and saw that aircraft X was in conflict with aircraft Y. Aircraft Y appeared to turn into aircraft X but I'm not sure why because I hadn't listened to the voice recording. When runway 34 is in use the situation can be very complex. We had intersecting runway operations and photo flights conflicting with our normal departures. Also; I was the only cpc (certified professional controller) in the tower. LC2; GC1; and clearance delivery were all either devs or cpc-its certified on the positions they were working. Perhaps opening cc earlier could have helped to avoid the situation.

Related reports:

Google
 

Original NASA ASRS Text

Title: DAB CIC reports of an NMAC between two aircraft and didn't know what happened until he saw a replay later. Aircraft was supposed to turn south; but local 2 turned aircraft north; coming close to other traffic local 1 was working.

Narrative: I was in charge in the tower and traffic was building so I opened the cab coordinator position. I was pre-briefing the CC (Cab Coordinator) when Aircraft X was cleared for takeoff. Following the pre-brief I was helping LC2 scan the runways. The situation was complex because of photo flights and volume was high because of our runway configuration. Aircraft X was a south fan destined for MLB. LC2 incorrectly fanned the aircraft north instead of south. No one noticed the mistake until N called LC2 and asked about him. After I was relieved I was questioned by the FLM (Front Line Manager) why no one noticed the incorrect fan. I told him we were very busy. The FLM then told me Aircraft X declared an NMAC. I asked him how and with who but he didn't know. He said he was looking into it. Our Support Specialist in charge of QA/QC showed me very briefly the radar playback and saw that Aircraft X was in conflict with Aircraft Y. Aircraft Y appeared to turn into Aircraft X but I'm not sure why because I hadn't listened to the voice recording. When RWY 34 is in use the situation can be very complex. We had intersecting runway operations and photo flights conflicting with our normal departures. Also; I was the only CPC (Certified Professional Controller) in the tower. LC2; GC1; and CD were all either DEVs or CPC-ITs certified on the positions they were working. Perhaps opening CC earlier could have helped to avoid the situation.

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.