Cle approach controller experienced operational error at approximately 5000 when second aircraft bei...

Attributes
ACN	731072
Time
Date	200703
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : cle.airport
State Reference	OH
Altitude	msl bound lower : 4200 msl bound upper : 5000
Environment
Flight Conditions	Marginal
Light	Night
Aircraft 1
Controlling Facilities	tracon : cle.tracon
Operator	common carrier : air carrier
Make Model Name	EMB ERJ 145 ER&LR
Operating Under FAR Part	Part 121
Flight Phase	descent : intermediate altitude
Route In Use	arrival : on vectors
Flight Plan	IFR
Aircraft 2
Controlling Facilities	tracon : cle.tracon
Operator	common carrier : air carrier
Make Model Name	EMB ERJ 145 ER&LR
Operating Under FAR Part	Part 121
Flight Phase	descent : intermediate altitude
Route In Use	arrival : on vectors
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : approach
Qualification	controller : radar
Experience	controller military : 3 controller radar : 23
ASRS Report	731072
Events
Anomaly	conflict : airborne less severe non adherence : required legal separation
Independent Detector	atc equipment : conflict alert other controllera
Resolutory Action	controller : issued alert controller : issued new clearance
Consequence	faa : investigated
Miss Distance	horizontal : 16500 vertical : 800
Supplementary
Problem Areas	ATC Human Performance
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Error

Narrative:

I was working the final on the inner low position. Runway 24R in use. Air carrier X was handed off to me from the arrival over controller at 7000 ft; 210 KTS. Air carrier Y was handed off to me leaving the chardon VOR (cxr) on a 290 degree heading leaving 9000 ft for 7000 ft at 210 KTS. Both aircraft were 25 mi apart on initial contact. The final would soon reach 25 mi with air carrier Z trailing air carrier Y and additional traffic on the downwinds. When both aircraft checked in; I descended air carrier X to 4000 ft and air carrier Y to 5000 ft. 20 mi northeast of cleveland hopkins; I turned air carrier X to a 140 degree heading and noticed that his speed was faster than the traffic I ran on an earlier session. That is when I noticed air carrier X was still at 210 KTS; so I reduced him to 170 KTS. I turned air carrier Y to a 320 degree heading and observed air carrier X leaving 5000 ft and air carrier Y leaving 6500 ft. I observed air carrier X was now doing 230 KTS on a right base and I told him to expect vectors across the localizer for spacing; and that I needed the speed (170 KTS) now. Air carrier X stated 'I'm at it.' I observed that he leveled off first at 4400 ft and then once again at 4200 ft. I told air carrier X to turn right heading 270 degrees and join the localizer. Then; I issued a speed restr to an air carrier a jet. Someone over the frequency said my transmission was blocked. I started to reissue the restr to air carrier a when I noticed air carrier X was still on a base leg and still at 4200 ft. I again issued air carrier X to turn to a 270 degree heading and join the localizer. That is when I observed air carrier X starting his turn; and it corresponded with the data read off. However; separation was lost; 2.75 NM/800 ft. I believe this was pilot error/deviation. 1) I don't believe air carrier X was at 170 KTS when he stated he was at it. 2) data shows air carrier X still on a base heading 10 seconds after I told him the first time to turn and join the localizer. 3) it took air carrier X 2 mins 50 seconds to descend from 5000 ft to 4000 ft.

Original NASA ASRS Text

Title: CLE APCH CTLR EXPERIENCED OPERROR AT APPROX 5000 WHEN SECOND ACFT BEING VECTORED TO FINAL OVERTOOK FIRST ACFT; CITING PLT ERROR AS CAUSE.

Narrative: I WAS WORKING THE FINAL ON THE INNER LOW POS. RWY 24R IN USE. ACR X WAS HANDED OFF TO ME FROM THE ARR OVER CTLR AT 7000 FT; 210 KTS. ACR Y WAS HANDED OFF TO ME LEAVING THE CHARDON VOR (CXR) ON A 290 DEG HDG LEAVING 9000 FT FOR 7000 FT AT 210 KTS. BOTH ACFT WERE 25 MI APART ON INITIAL CONTACT. THE FINAL WOULD SOON REACH 25 MI WITH ACR Z TRAILING ACR Y AND ADDITIONAL TFC ON THE DOWNWINDS. WHEN BOTH ACFT CHKED IN; I DSNDED ACR X TO 4000 FT AND ACR Y TO 5000 FT. 20 MI NE OF CLEVELAND HOPKINS; I TURNED ACR X TO A 140 DEG HDG AND NOTICED THAT HIS SPD WAS FASTER THAN THE TFC I RAN ON AN EARLIER SESSION. THAT IS WHEN I NOTICED ACR X WAS STILL AT 210 KTS; SO I REDUCED HIM TO 170 KTS. I TURNED ACR Y TO A 320 DEG HDG AND OBSERVED ACR X LEAVING 5000 FT AND ACR Y LEAVING 6500 FT. I OBSERVED ACR X WAS NOW DOING 230 KTS ON A R BASE AND I TOLD HIM TO EXPECT VECTORS ACROSS THE LOC FOR SPACING; AND THAT I NEEDED THE SPD (170 KTS) NOW. ACR X STATED 'I'M AT IT.' I OBSERVED THAT HE LEVELED OFF FIRST AT 4400 FT AND THEN ONCE AGAIN AT 4200 FT. I TOLD ACR X TO TURN R HDG 270 DEGS AND JOIN THE LOC. THEN; I ISSUED A SPD RESTR TO AN ACR A JET. SOMEONE OVER THE FREQ SAID MY XMISSION WAS BLOCKED. I STARTED TO REISSUE THE RESTR TO ACR A WHEN I NOTICED ACR X WAS STILL ON A BASE LEG AND STILL AT 4200 FT. I AGAIN ISSUED ACR X TO TURN TO A 270 DEG HDG AND JOIN THE LOC. THAT IS WHEN I OBSERVED ACR X STARTING HIS TURN; AND IT CORRESPONDED WITH THE DATA READ OFF. HOWEVER; SEPARATION WAS LOST; 2.75 NM/800 FT. I BELIEVE THIS WAS PLT ERROR/DEV. 1) I DON'T BELIEVE ACR X WAS AT 170 KTS WHEN HE STATED HE WAS AT IT. 2) DATA SHOWS ACR X STILL ON A BASE HDG 10 SECONDS AFTER I TOLD HIM THE FIRST TIME TO TURN AND JOIN THE LOC. 3) IT TOOK ACR X 2 MINS 50 SECONDS TO DSND FROM 5000 FT TO 4000 FT.

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

Cle approach controller experienced operational error at approximately 5000 when second aircraft being vectored to final overtook first aircraft; citing pilot error as cause.