Less than standard separation between corp jet and air carrier. Operational error.

Attributes
ACN	91924
Time
Date	198808
Day	Wed
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : elx
State Reference	MI
Altitude	msl bound lower : 21700 msl bound upper : 22000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zau
Operator	general aviation : corporate
Make Model Name	Light Transport, Low Wing, 2 Turbojet Eng
Flight Phase	cruise other
Route In Use	enroute airway : zau
Flight Plan	IFR
Aircraft 2
Operator	common carrier : air carrier
Make Model Name	Large Transport, Low Wing, 3 Turbojet Eng
Flight Phase	climbout : intermediate altitude
Route In Use	enroute : direct
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : radar
Qualification	controller : radar
Experience	controller non radar : 7 controller radar : 5
ASRS Report	91924
Person 2
Affiliation	government : faa
Function	controller : radar
Qualification	controller : radar
Experience	controller military : 4 controller radar : 6
ASRS Report	93130
Events
Anomaly	conflict : airborne less severe non adherence : required legal separation
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance none taken : unable other
Consequence	faa : investigated
Miss Distance	horizontal : 18000 vertical : 300
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	Intra Facility Coordination Failure Operational Error

Narrative:

Corp jet X was level at FL220, filed pmm pwk and was deviating south of course for WX. Corp X had been pointed out to the east department sector controller. I observed a limited data block climbing eastbound and assumed that the east departure controller had cleared that aircraft Y to FL210 only. When I observed the mode C go above FL210, I simultaneously forced up the data block, the yelled out, 'who's climbing the air carrier Y.' then I told corp X to turn immediately to heading 220 degrees. The pilot complied, then reported a few seconds later that the air carrier was in sight. Supplemental information from acn 93130: corp X not observed by me, had started his turn back to his original course. This put the 2 aircraft in conflict. Air carrier Y and corp X were both turned when the conflict alert activated. One of the major factors involved in this incident was numerous deviations occurring due to WX.

Original NASA ASRS Text

Title: LESS THAN STANDARD SEPARATION BETWEEN CORP JET AND ACR. OPERATIONAL ERROR.

Narrative: CORP JET X WAS LEVEL AT FL220, FILED PMM PWK AND WAS DEVIATING S OF COURSE FOR WX. CORP X HAD BEEN POINTED OUT TO THE E DEPT SECTOR CTLR. I OBSERVED A LIMITED DATA BLOCK CLBING EBND AND ASSUMED THAT THE E DEP CTLR HAD CLRED THAT ACFT Y TO FL210 ONLY. WHEN I OBSERVED THE MODE C GO ABOVE FL210, I SIMULTANEOUSLY FORCED UP THE DATA BLOCK, THE YELLED OUT, 'WHO'S CLBING THE ACR Y.' THEN I TOLD CORP X TO TURN IMMEDIATELY TO HDG 220 DEGS. THE PLT COMPLIED, THEN RPTED A FEW SECS LATER THAT THE ACR WAS IN SIGHT. SUPPLEMENTAL INFO FROM ACN 93130: CORP X NOT OBSERVED BY ME, HAD STARTED HIS TURN BACK TO HIS ORIGINAL COURSE. THIS PUT THE 2 ACFT IN CONFLICT. ACR Y AND CORP X WERE BOTH TURNED WHEN THE CONFLICT ALERT ACTIVATED. ONE OF THE MAJOR FACTORS INVOLVED IN THIS INCIDENT WAS NUMEROUS DEVIATIONS OCCURRING DUE TO WX.

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