Narrative:

I was working local; training was in progress on ground. A supervisor transferred months ago; and still not qualified on any control position; was also in the cab. Runway 14 was active. Ground was taxing aircraft to runway 14 full length via taxiway alpha and to runway 14 at the charlie intersection. The sun was setting; and the lighting conditions were sunset conditions. The BE58 called ready for take off. I had a PA28 on a two mile final. The strip for the BE58 was marked by ground as a charlie intersection departure. At charlie; I observed two aircraft; and I cleared the BE58 for take off. I then realized that the first aircraft was a SR22; and well back; still in the run-up pad was a light twin that I thought was the BE58. I saw no movement; and I canceled take off clearance. I told the BE58 to move out of the run-up area and call when number one. The BE58 said I was confused. While I was trying to sort things out; the un-qualified supervisor started to shout; 'he's on the runway; he's on the runway' over and over. I could not hear myself think; let alone the frequency; so I asked everybody to 'shut up!' I did not trust what the supervisor was saying given his/her track record. I then saw the BE58 on the runway at the full length. The aircraft that I thought was the BE58 at the charlie intersection was actually a C310. The PA28 initiated a go around. I then cleared the BE58 with standard separation behind the PA28 that went around. Given that training was in progress; I should have been extra cautious. I took it for granted that the trainer on ground control would catch all errors made by his trainee. If I had been extra vigilant and scanned the full runway; instead of focusing where I was expecting the aircraft would be; the error would not have happened. An added factor was the supervisor; who seems to have no idea how to handle the situation. Normally; when a controller; controller in charge; or osic spots a potential problem by calling it out; i.e. 'Traffic on the runway'; or 'send the cherokee [around]'. Any seasoned controller will understand that the local controller is busy; but also has the 'tower ear' and will hear the call out; and not shout over and over in the cab. By the local controllers actions; it would be apparent to any qualified member of the team; that the local controller heard the call out.

Google
 

Original NASA ASRS Text

Title: A go around around caused by confusion due to multiple aircraft awaiting departure and uncertainty regarding their position was complicated by supervisory distraction/s adding to the confusion.

Narrative: I was working Local; training was in progress on Ground. A supervisor transferred months ago; and still not qualified on any control position; was also in the cab. Runway 14 was active. Ground was taxing aircraft to Runway 14 full length via Taxiway Alpha and to Runway 14 at the Charlie Intersection. The sun was setting; and the lighting conditions were sunset conditions. The BE58 called ready for take off. I had a PA28 on a two mile final. The strip for the BE58 was marked by Ground as a Charlie Intersection departure. At Charlie; I observed two aircraft; and I cleared the BE58 for take off. I then realized that the first aircraft was a SR22; and well back; still in the run-up pad was a light twin that I thought was the BE58. I saw no movement; and I canceled take off clearance. I told the BE58 to move out of the run-up area and call when number one. The BE58 said I was confused. While I was trying to sort things out; the un-qualified supervisor started to shout; 'he's on the runway; he's on the runway' over and over. I could not hear myself think; let alone the frequency; so I asked everybody to 'shut up!' I did not trust what the supervisor was saying given his/her track record. I then saw the BE58 on the runway at the full length. The aircraft that I thought was the BE58 at the Charlie Intersection was actually a C310. The PA28 initiated a go around. I then cleared the BE58 with standard separation behind the PA28 that went around. Given that training was in progress; I should have been extra cautious. I took it for granted that the trainer on Ground Control would catch all errors made by his trainee. If I had been extra vigilant and scanned the full runway; instead of focusing where I was expecting the aircraft would be; the error would not have happened. An added factor was the supervisor; who seems to have no idea how to handle the situation. Normally; when a controller; CIC; or OSIC spots a potential problem by calling it out; i.e. 'Traffic on the runway'; or 'send the Cherokee [around]'. Any seasoned controller will understand that the Local Controller is busy; but also has the 'tower ear' and will hear the call out; and not shout over and over in the cab. By the Local Controllers actions; it would be apparent to any qualified member of the team; that the Local Controller heard the call out.

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.