A tower supervisor reports that a local controller placed two aircraft head to head to each other at...

Narrative:

I was just made aware of the event through emailed contacted from the aircraft involved. I have reviewed the tapes and created a falcon (radar and audio replay) of the event. I was in a training class at the time of the event and the event was not shared with me until today. Local 1 controller cleared aircraft X for touch and go runway 21L (established in left closed traffic). Aircraft X was on the go for upwind (assumed and unable to verify; approved separation). Local 1 then cleared aircraft Y for takeoff runway 21L with 'left closed traffic approved'; no reference to the traffic ahead (on upwind or on the go from their touch and go). Aircraft Y (the trail aircraft) turned crosswind before aircraft X and created a conflict. The local 1 controller recognized the conflict and told aircraft Y (the trail aircraft) to make a right 360 degree turn; which now put the two head on. The targets merged and would estimate they were less than 100 feet vertical. No traffic was exchanged. Both pilots sounded distraught. [The company traffic] is hesitant to state near midair collision on frequency. Standard procedures are to issue a straight out departure for aircraft requesting closed traffic when there is 'traffic'. Once the aircraft is in stable flight common practice is to call traffic and instruct the aircraft to follow.local 1 controller then confused aircraft Y with aircraft Z who was holding short of runway 21L ready for departure. It was reported that the local 1 controller was not following local procedures in using flight progress strips which were written by ground control and passed onto them. This controller has recent events appearing to be blatant disregard for operational procedures introducing risk. I wish to provide a falcon replay with audio of this event for review. Further recommend set (skill enhancement training) for this individual.

Original NASA ASRS Text

Title: A Tower Supervisor reports that a Local Controller placed two aircraft head to head to each other at the same altitude and failed to take appropriate action to separate successive departures.

Narrative: I was just made aware of the event through emailed contacted from the aircraft involved. I have reviewed the tapes and created a FALCON (radar and audio replay) of the event. I was in a training class at the time of the event and the event was not shared with me until today. Local 1 controller cleared Aircraft X for touch and go runway 21L (established in left closed traffic). Aircraft X was on the go for upwind (assumed and unable to verify; approved separation). Local 1 then cleared Aircraft Y for takeoff runway 21L with 'left closed traffic approved'; no reference to the traffic ahead (on upwind or on the go from their touch and go). Aircraft Y (the trail aircraft) turned crosswind before Aircraft X and created a conflict. The Local 1 controller recognized the conflict and told Aircraft Y (the trail aircraft) to make a right 360 degree turn; which now put the two head on. The targets merged and would estimate they were less than 100 feet vertical. No traffic was exchanged. Both pilots sounded distraught. [The company traffic] is hesitant to state NMAC on frequency. Standard procedures are to issue a straight out departure for aircraft requesting closed traffic when there is 'traffic'. Once the aircraft is in stable flight common practice is to call traffic and instruct the aircraft to follow.Local 1 controller then confused Aircraft Y with Aircraft Z who was holding short of runway 21L ready for departure. It was reported that the Local 1 controller was not following local procedures in using Flight Progress strips which were written by Ground Control and passed onto them. This controller has recent events appearing to be blatant disregard for operational procedures introducing risk. I wish to provide a FALCON replay with audio of this event for review. Further recommend SET (Skill Enhancement Training) for this individual.

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.

Attributes
ACN	1356618
Time
Date	201604
Local Time Of Day	0001-0600
Place
Locale Reference	PRC.Airport
State Reference	AZ
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	Small Aircraft
Operating Under FAR Part	Part 91
Flight Phase	Takeoff
Route In Use	VFR Route
Flight Plan	VFR
Aircraft 2
Make Model Name	Small Aircraft
Operating Under FAR Part	Part 91
Flight Phase	Takeoff
Route In Use	None
Flight Plan	VFR
Person 1
Function	Supervisor / CIC
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Time Certified In Pos 1 (yrs) 2
Events
Anomaly	ATC Issue All Types Conflict NMAC Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types

A tower supervisor reports that a local controller placed two aircraft head to head to each other at the same altitude and failed to take appropriate action to separate successive departures.