3 ZID controllers involved in operational error involving DC8 and DC9.

Attributes
ACN	495397
Time
Date	200012
Day	Tue
Local Time Of Day	0601 To 1200
Place
Locale Reference	navaid : ape.vortac
State Reference	OH
Altitude	msl single value : 230
Environment
Flight Conditions	VMC
Weather Elements	Turbulence
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zid.artcc tower : gmu.tower
Operator	common carrier : air carrier
Make Model Name	DC-8 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	cruise : enroute altitude change
Route In Use	enroute : on vectors
Flight Plan	IFR
Aircraft 2
Controlling Facilities	artcc : zid.artcc
Operator	common carrier : air carrier
Make Model Name	DC-9 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	cruise : level
Route In Use	enroute airway : j86.airway
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : radar
Qualification	controller : radar
Experience	controller radar : 15 controller time certified in position1 : 2
ASRS Report	495397
Person 2
Affiliation	government : faa
Function	controller : radar
Qualification	controller : radar
Experience	controller radar : 16 controller time certified in position1 : 9
ASRS Report	495396
Events
Anomaly	conflict : airborne less severe inflight encounter : turbulence non adherence : required legal separation non adherence : published procedure
Independent Detector	atc equipment : conflict alert other controllera other controllerb
Resolutory Action	none taken : detected after the fact
Consequence	faa : investigated
Miss Distance	horizontal : 27000 vertical : 0
Supplementary
Problem Areas	Weather ATC Human Performance
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Error

Narrative:

Aircraft #1 was in a turn to the right to proceed eastbound to ape VORTAC at FL230. Aircraft #2 was sbound at FL230. When aircraft #1 completed the turn it came 4.5 mi behind aircraft #2. Aedp and conflict alert activated nearly simultaneously. A strong southwest wind reduced aircraft #2 ground speed to 310 KTS while pushing aircraft #1 to 470 KT ground speed. Controller failed to notice the significant difference in ground speed. Supplemental information from acn 495396: I handed off air carrier X to sector 30. They immediately handed the aircraft off to the high altitude sector. I called the sector to see if they wanted to talk to the aircraft or have me put it on the high altitude sector. They aid to put it on the high altitude sector. I put him on the high sector for them. The high sector did not climb him right away and he backsided air carrier Y. I did nothing wrong (according to my first line supervisor) but upper management removed me from duties as a performance issue. What I did was standard protocol for ZID.

Original NASA ASRS Text

Title: 3 ZID CTLRS INVOLVED IN OPERROR INVOLVING DC8 AND DC9.

Narrative: ACFT #1 WAS IN A TURN TO THE R TO PROCEED EBOUND TO APE VORTAC AT FL230. ACFT #2 WAS SBOUND AT FL230. WHEN ACFT #1 COMPLETED THE TURN IT CAME 4.5 MI BEHIND ACFT #2. AEDP AND CONFLICT ALERT ACTIVATED NEARLY SIMULTANEOUSLY. A STRONG SW WIND REDUCED ACFT #2 GND SPD TO 310 KTS WHILE PUSHING ACFT #1 TO 470 KT GND SPD. CTLR FAILED TO NOTICE THE SIGNIFICANT DIFFERENCE IN GND SPD. SUPPLEMENTAL INFO FROM ACN 495396: I HANDED OFF ACR X TO SECTOR 30. THEY IMMEDIATELY HANDED THE ACFT OFF TO THE HIGH ALT SECTOR. I CALLED THE SECTOR TO SEE IF THEY WANTED TO TALK TO THE ACFT OR HAVE ME PUT IT ON THE HIGH ALT SECTOR. THEY AID TO PUT IT ON THE HIGH ALT SECTOR. I PUT HIM ON THE HIGH SECTOR FOR THEM. THE HIGH SECTOR DID NOT CLB HIM RIGHT AWAY AND HE BACKSIDED ACR Y. I DID NOTHING WRONG (ACCORDING TO MY FIRST LINE SUPVR) BUT UPPER MGMNT REMOVED ME FROM DUTIES AS A PERFORMANCE ISSUE. WHAT I DID WAS STANDARD PROTOCOL FOR ZID.

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.