<< >> NASA ASRS Report 578949, April 2003

Chs departure controller idents an MO21 without an operable transponder and later forgets to make a handoff to the next sector.

Attributes
ACN	578949
Time
Date	200304
Day	Sun
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : chs.tracon
State Reference	SC
Altitude	msl single value : 6000
Environment
Flight Conditions	IMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : chs.tracon tower : oak.tower
Operator	general aviation : personal
Make Model Name	M-20 E Super 21
Operating Under FAR Part	Part 91
Flight Phase	cruise : level
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : departure
Qualification	controller : radar pilot : instrument
Experience	controller non radar : 14 controller radar : 6 controller time certified in position1 : 5 flight time total : 3000
ASRS Report	578949
Person 2
Affiliation	government : faa
Function	other personnel other
Events
Anomaly	non adherence : required legal separation non adherence : published procedure
Independent Detector	other controllera other controllerb other flight crewa
Resolutory Action	other
Supplementary
Problem Areas	ATC Human Performance
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Deviation

Narrative:

Aircraft Y, an MO21, called off chs airport (IFR departure). I radar idented a primary target, climbed the aircraft to 6000 ft and on course V53 nwbound. At this time, traffic was heavy. There was a pilot xchanneled, blocking the frequency continuously and in the meantime, the watch supervisor was splitting the radar sectors off. I simply forgot the departing traffic. The pilot later, southeast of cae VOR, asked if he should not have been frequency changed. After some confusion (the strip had been put away by the radar associate who had assumed the aircraft had been handed off). The pilot stated that the transponder circuit breaker had popped, and that he wished to cancel IFR. No excuses from me. However, there were many, many, distractions and very heavy traffic and complexities involved. We have asked for a procedure where local control would advise radar of a non-tagged departure.

Related reports:

• Crw local controller fails to coordination with departure co...
• Combined tower controller for both ground and local, inadver...
• A departure small aircraft private pilot is advised by depar...
• Flight crew of DC9 uses wrong transponder code on departure....
• Departure controller mistakenly told an light transport depa...
• Departure controller forgot about a non transponder mlt on a...

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

Original NASA ASRS Text

Title: CHS DEP CTLR IDENTS AN MO21 WITHOUT AN OPERABLE XPONDER AND LATER FORGETS TO MAKE A HDOF TO THE NEXT SECTOR.

Narrative: ACFT Y, AN MO21, CALLED OFF CHS ARPT (IFR DEP). I RADAR IDENTED A PRIMARY TARGET, CLBED THE ACFT TO 6000 FT AND ON COURSE V53 NWBOUND. AT THIS TIME, TFC WAS HVY. THERE WAS A PLT XCHANNELED, BLOCKING THE FREQ CONTINUOUSLY AND IN THE MEANTIME, THE WATCH SUPVR WAS SPLITTING THE RADAR SECTORS OFF. I SIMPLY FORGOT THE DEPARTING TFC. THE PLT LATER, SE OF CAE VOR, ASKED IF HE SHOULD NOT HAVE BEEN FREQ CHANGED. AFTER SOME CONFUSION (THE STRIP HAD BEEN PUT AWAY BY THE RADAR ASSOCIATE WHO HAD ASSUMED THE ACFT HAD BEEN HANDED OFF). THE PLT STATED THAT THE XPONDER CIRCUIT BREAKER HAD POPPED, AND THAT HE WISHED TO CANCEL IFR. NO EXCUSES FROM ME. HOWEVER, THERE WERE MANY, MANY, DISTRACTIONS AND VERY HVY TFC AND COMPLEXITIES INVOLVED. WE HAVE ASKED FOR A PROC WHERE LCL CTL WOULD ADVISE RADAR OF A NON-TAGGED DEP.

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