<< >> NASA ASRS Report 713635, October 2006

Mem local controller described incident when supervisor controller released opposite direction traffic without completing appropriate coordination.

Attributes
ACN	713635
Time
Date	200610
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : mem.tower
State Reference	TN
Environment
Light	Daylight
Aircraft 1
Controlling Facilities	tower : mem.tower
Person 1
Affiliation	government : faa
Function	controller : local
Experience	controller military : 4 controller radar : 18 controller time certified in position1 : 1 controller time certified in position2 : 2
ASRS Report	713635
Events
Anomaly	other anomaly other
Independent Detector	other controllera
Resolutory Action	none taken : anomaly accepted
Supplementary
Problem Areas	FAA
Primary Problem	FAA
Situations
ATC Facility	procedure or policy : mem.tower

Narrative:

I was working local control 1 (local control-1) during the afternoon departure push. Local control 2 was open; cabin attendant coordinator was open; and there was a supervisor monitoring the operation. There were 4 or 5 J-35 and 'cuba gate' departures at runway 18R in sequence. Suddenly the cabin attendant coordinator rushed to my position to ask where my departures were going. When I told the cabin attendant coordinator J-35 and cuba gate; I was advised to stop all north departures. The cabin attendant coordinator informed me later that the supervisor had released an opposite direction departure off of runway 36C; and this departure would enter my airspace; and ultimately affect my departures that were assigned J-35 and cuba gate. The supervisor failed to coordination with the local control 1 position; and neglected to coordination with the cabin attendant coordinator. This happens on a daily basis here. Supervisors routinely approve releases and fail to inform other position that will be affected. We usually catch the error and stop our departures.

Related reports:

• Air carrier medium large transport was allowed to penetrate ...
• Cha local controller released departure without appropriate ...
• Local controller described a loss of separation event when c...
• ARTCC radar controller violated W122 while the warning area ...
• ZID controller described a confused four digit; same company...

	Enter your search terms Submit search form
	Web www.37000feet.com

Original NASA ASRS Text

Title: MEM LCL CTLR DESCRIBED INCIDENT WHEN SUPVR CTLR RELEASED OPPOSITE DIRECTION TFC WITHOUT COMPLETING APPROPRIATE COORD.

Narrative: I WAS WORKING LCL CTL 1 (LC-1) DURING THE AFTERNOON DEP PUSH. LCL CTL 2 WAS OPEN; CAB COORDINATOR WAS OPEN; AND THERE WAS A SUPVR MONITORING THE OP. THERE WERE 4 OR 5 J-35 AND 'CUBA GATE' DEPS AT RWY 18R IN SEQUENCE. SUDDENLY THE CAB COORDINATOR RUSHED TO MY POS TO ASK WHERE MY DEPS WERE GOING. WHEN I TOLD THE CAB COORDINATOR J-35 AND CUBA GATE; I WAS ADVISED TO STOP ALL N DEPS. THE CAB COORDINATOR INFORMED ME LATER THAT THE SUPVR HAD RELEASED AN OPPOSITE DIRECTION DEP OFF OF RWY 36C; AND THIS DEP WOULD ENTER MY AIRSPACE; AND ULTIMATELY AFFECT MY DEPS THAT WERE ASSIGNED J-35 AND CUBA GATE. THE SUPVR FAILED TO COORD WITH THE LCL CTL 1 POS; AND NEGLECTED TO COORD WITH THE CAB COORDINATOR. THIS HAPPENS ON A DAILY BASIS HERE. SUPVRS ROUTINELY APPROVE RELEASES AND FAIL TO INFORM OTHER POS THAT WILL BE AFFECTED. WE USUALLY CATCH THE ERROR AND STOP OUR DEPS.

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