Air carrier X had less than standard separation from military aircraft Y. System error.

Attributes
ACN	168810
Time
Date	199101
Day	Wed
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : ilm
State Reference	NC
Altitude	msl bound lower : 23000 msl bound upper : 23000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zdc
Operator	common carrier : air carrier
Make Model Name	Medium Large Transport
Navigation In Use	Other Other
Flight Phase	climbout : intermediate altitude cruise other
Route In Use	enroute : direct
Flight Plan	IFR
Aircraft 2
Operator	other
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Flight Phase	cruise other
Route In Use	enroute : direct
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : radar
Qualification	controller : radar
Experience	controller non radar : 4 controller radar : 3
ASRS Report	168810
Person 2
Affiliation	government : faa
Function	controller : radar
Qualification	controller : radar
Events
Anomaly	conflict : airborne less severe non adherence : published procedure non adherence : required legal separation
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance other
Consequence	faa : investigated
Miss Distance	horizontal : 12000 vertical : 0
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	Intra Facility Coordination Failure Operational Error

Narrative:

Air carrier X departure from rdu climbing to FL230 given to next sector (high sector) out of FL180, observed climbing to FL260 in data block. Military aircraft Y cruising at FL230 nebnd crossing air carrier X track. Should have been no factor and below air carrier X if air carrier X not descended and turned. Became aware of air carrier X seeming to level at FL230 and then descending and turning in my airspace, so turned military aircraft Y to north heading, then west heading and descended to FL220. Military aircraft Y had air carrier X in sight. Wasn't aware that high sector controller was turning air carrier X southwest and descending, putting it into path of military aircraft Y. Lack of coordination between low sector controller (myself) and high sector controller seemed to be problem, since both took corrective action but aircraft turned same direction because of lack of coordination.

Original NASA ASRS Text

Title: ACR X HAD LESS THAN STANDARD SEPARATION FROM MIL ACFT Y. SYSTEM ERROR.

Narrative: ACR X DEP FROM RDU CLBING TO FL230 GIVEN TO NEXT SECTOR (HIGH SECTOR) OUT OF FL180, OBSERVED CLBING TO FL260 IN DATA BLOCK. MIL ACFT Y CRUISING AT FL230 NEBND XING ACR X TRACK. SHOULD HAVE BEEN NO FACTOR AND BELOW ACR X IF ACR X NOT DSNDED AND TURNED. BECAME AWARE OF ACR X SEEMING TO LEVEL AT FL230 AND THEN DSNDING AND TURNING IN MY AIRSPACE, SO TURNED MIL ACFT Y TO N HDG, THEN W HDG AND DSNDED TO FL220. MIL ACFT Y HAD ACR X IN SIGHT. WASN'T AWARE THAT HIGH SECTOR CTLR WAS TURNING ACR X SW AND DSNDING, PUTTING IT INTO PATH OF MIL ACFT Y. LACK OF COORD BTWN LOW SECTOR CTLR (MYSELF) AND HIGH SECTOR CTLR SEEMED TO BE PROB, SINCE BOTH TOOK CORRECTIVE ACTION BUT ACFT TURNED SAME DIRECTION BECAUSE OF LACK OF COORD.

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.