A11 TRACON flm reports of opposite direction departure request by anc local control. Local is told t...

Attributes
ACN	1190320
Time
Date	201407
Local Time Of Day	1801-2400
Place
Locale Reference	ANC.Airport
State Reference	AK
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Make Model Name	B747 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	Taxi
Route In Use	None
Flight Plan	IFR
Aircraft 2
Make Model Name	B747 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	Taxi
Flight Plan	IFR
Person 1
Function	Supervisor / CIC
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Time Certified In Pos 1 (yrs) 3
Events
Anomaly	ATC Issue All Types Airspace Violation All Types Conflict Airborne Conflict Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy

Narrative:

Anchorage was in a runway 7/33 configuration with runway 7L/25R closed; training on final west; moderate inbound traffic; VMC. Anc tower controller in charge coordinated with the A11 os/controller in charge for an opposite direction departure for aircraft X. Anc tower was advised that there would be a 25 minute delay for the opposite direction operation and to expect release reference several inbounds. The local controller circumvented the controller in charge coordination by contacting the training team on final west and getting a release for the opposite direction departure. This resulted in five aircraft having to be delay vectored to avoid conflict. The north radar controller was advised by the south radar controller to red light the tower to protect the operation. Immediately after the red light was instigated; the local controller [requested] a release for aircraft Y that if the red light had not been activated; would have departed into conflict with aircraft X. Opposite direction operations are inherently risky and must be well managed. The local controller must not by pass controller in charge coordination or unnecessary risk will be introduced to the system.

Original NASA ASRS Text

Title: A11 TRACON FLM reports of opposite direction departure request by ANC Local Control. Local is told to expect release in 25 minutes due to arrival traffic. Local then coordinates a release with another sector and obtains the release. Aircraft are vectored away from the departure. Local then requests a release on another jet for departure; which would be in conflict with the previous departure.

Narrative: Anchorage was in a Runway 7/33 configuration with Runway 7L/25R closed; training on Final West; moderate inbound traffic; VMC. ANC Tower CIC coordinated with the A11 OS/CIC for an opposite direction departure for Aircraft X. ANC Tower was advised that there would be a 25 minute delay for the opposite direction operation and to expect release reference several inbounds. The Local Controller circumvented the CIC coordination by contacting the training team on Final West and getting a release for the opposite direction departure. This resulted in five aircraft having to be delay vectored to avoid conflict. The North Radar Controller was advised by the South Radar Controller to RED LIGHT the Tower to protect the operation. Immediately after the red light was instigated; the Local Controller [requested] a release for Aircraft Y that if the red light had not been activated; would have departed into conflict with Aircraft X. Opposite Direction Operations are inherently risky and must be well managed. The Local Controller must not by pass CIC coordination or unnecessary risk will be introduced to the system.

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.