Less than standard separation between commuter and large transport-air carrier. Operational error.

Attributes
ACN	101052
Time
Date	198812
Day	Fri
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : iah
State Reference	TX
Altitude	msl bound lower : 6000 msl bound upper : 6000
Environment
Flight Conditions	IMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : iah
Operator	common carrier : air carrier
Make Model Name	Medium Transport, High Wing, 2 Turboprop Eng
Flight Phase	climbout : intermediate altitude
Route In Use	enroute : on vectors
Flight Plan	IFR
Aircraft 2
Operator	common carrier : air carrier
Make Model Name	Large Transport, Low Wing, 3 Turbojet Eng
Flight Phase	cruise other descent : approach other
Route In Use	enroute : on vectors
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : approach controller : departure
Qualification	controller : radar
ASRS Report	101052
Person 2
Affiliation	government : faa
Function	controller : approach
Qualification	controller : radar
Events
Anomaly	conflict : airborne less severe non adherence : required legal separation
Independent Detector	other other : unspecified atc
Resolutory Action	none taken : unable
Consequence	faa : investigated
Miss Distance	horizontal : 9000 vertical : 0
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Error Intra Facility Coordination Failure

Narrative:

Iah in the process of changing from runway 8 and 9 to runway 26 and 27. Commuter X departed iah northbound. I was working arrival east and departure east. I did not see any downwind traffic and climbed X to 15000'. Tower coordinated a missed approach off runway 9. I alerted final of the missed approach. Supervisor yelled at me to watch out for aircraft X. X had traffic, air carrier Y at 6000' heading 080 degrees on north downwind for runway 26. I turned X to heading 080 degrees to parallel the traffic. Leaving 8000' I turned aircraft X back on course. The situation occurred during a runway change. I was finding out what exactly was going to be the new flow would it be runway 26/27 only or would it be runway 14/26 & 27? The missed approach happened during this time with traffic inbound to runway 27. Then commuter X checked on frequency level at 4000' crossing the final of runway 27 northbound. I think the runway change should have been coordinated more in advance. Not just a broadcast to vector for runway 26/27. All possible questions should be eliminated before (not in the process of the change). We have too many different runway airspace configns having you question yourself what airspace you own.

Original NASA ASRS Text

Title: LESS THAN STANDARD SEPARATION BETWEEN COMMUTER AND LGT-ACR. OPERATIONAL ERROR.

Narrative: IAH IN THE PROCESS OF CHANGING FROM RWY 8 AND 9 TO RWY 26 AND 27. COMMUTER X DEPARTED IAH NBND. I WAS WORKING ARR E AND DEP E. I DID NOT SEE ANY DOWNWIND TFC AND CLBED X TO 15000'. TWR COORDINATED A MISSED APCH OFF RWY 9. I ALERTED FINAL OF THE MISSED APCH. SUPVR YELLED AT ME TO WATCH OUT FOR ACFT X. X HAD TFC, ACR Y AT 6000' HDG 080 DEGS ON N DOWNWIND FOR RWY 26. I TURNED X TO HDG 080 DEGS TO PARALLEL THE TFC. LEAVING 8000' I TURNED ACFT X BACK ON COURSE. THE SITUATION OCCURRED DURING A RWY CHANGE. I WAS FINDING OUT WHAT EXACTLY WAS GOING TO BE THE NEW FLOW WOULD IT BE RWY 26/27 ONLY OR WOULD IT BE RWY 14/26 & 27? THE MISSED APCH HAPPENED DURING THIS TIME WITH TFC INBOUND TO RWY 27. THEN COMMUTER X CHKED ON FREQ LEVEL AT 4000' XING THE FINAL OF RWY 27 NBND. I THINK THE RWY CHANGE SHOULD HAVE BEEN COORDINATED MORE IN ADVANCE. NOT JUST A BROADCAST TO VECTOR FOR RWY 26/27. ALL POSSIBLE QUESTIONS SHOULD BE ELIMINATED BEFORE (NOT IN THE PROCESS OF THE CHANGE). WE HAVE TOO MANY DIFFERENT RWY AIRSPACE CONFIGNS HAVING YOU QUESTION YOURSELF WHAT AIRSPACE YOU OWN.

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.