Narrative:

Small aircraft X was on an ILS approach to runway 7L and small aircraft Y was vectored to the base leg. It appeared that Y was being vectored to follow X. On the final now, 3 mi out, I punched in (keyed up) the override to ask the status of Y, but the radar controller was busy and I came off the override. Now, about 2 mi from the airport, Y appeared to turn to get in front of X on final. I then overrode the radar controller and asked if Y was turning in, and the reply was yes. I said, 'send him to me now.' just as soon as Y was on my frequency I advised him to fly straight to the runway and keep his speed up, that traffic was on the ILS ot follow him. Then I issued traffic to X that Y was turning final in front of him and did he have him in sight. The pilot of X said he had him in sight and it looked close to him and requested runway 7R. I coordinated with local control #2 and got a #1 sequence to land. I then sidestepped X to runway 7R and cleared him to land. 3 hours later the pilot called to file a near miss. At no time was target resolution lost. At no time did aircraft X have to make an evasive turn. The sidestep was a normal operation and visibility sep was maintained. It did appear that the pilot of the small aircraft X was going real fast. The pilot stated 120 KTS. If X was at normal speed (80/90 KTS) there would not have been any problem and X could have landed behind Y with no problem. Supplemental information from acn 101990: I, being the approach controller, was vectoring Y to sequence him in front of X. One fact I was not aware of was X was traveling at approximately 120 KTS on final approach. Small aircraft Y was traveling at approximately 60 KTS.

Google
 

Original NASA ASRS Text

Title: LESS THAN STANDARD SEPARATION BETWEEN IFR SMA AND VFR SMA IN ARSA ON SHORT FINAL APCH FOR SAME RWY. OPERATIONAL ERROR.

Narrative: SMA X WAS ON AN ILS APCH TO RWY 7L AND SMA Y WAS VECTORED TO THE BASE LEG. IT APPEARED THAT Y WAS BEING VECTORED TO FOLLOW X. ON THE FINAL NOW, 3 MI OUT, I PUNCHED IN (KEYED UP) THE OVERRIDE TO ASK THE STATUS OF Y, BUT THE RADAR CTLR WAS BUSY AND I CAME OFF THE OVERRIDE. NOW, ABOUT 2 MI FROM THE ARPT, Y APPEARED TO TURN TO GET IN FRONT OF X ON FINAL. I THEN OVERRODE THE RADAR CTLR AND ASKED IF Y WAS TURNING IN, AND THE REPLY WAS YES. I SAID, 'SEND HIM TO ME NOW.' JUST AS SOON AS Y WAS ON MY FREQ I ADVISED HIM TO FLY STRAIGHT TO THE RWY AND KEEP HIS SPD UP, THAT TFC WAS ON THE ILS OT FOLLOW HIM. THEN I ISSUED TFC TO X THAT Y WAS TURNING FINAL IN FRONT OF HIM AND DID HE HAVE HIM IN SIGHT. THE PLT OF X SAID HE HAD HIM IN SIGHT AND IT LOOKED CLOSE TO HIM AND REQUESTED RWY 7R. I COORDINATED WITH LCL CTL #2 AND GOT A #1 SEQUENCE TO LAND. I THEN SIDESTEPPED X TO RWY 7R AND CLRED HIM TO LAND. 3 HRS LATER THE PLT CALLED TO FILE A NEAR MISS. AT NO TIME WAS TARGET RESOLUTION LOST. AT NO TIME DID ACFT X HAVE TO MAKE AN EVASIVE TURN. THE SIDESTEP WAS A NORMAL OPERATION AND VIS SEP WAS MAINTAINED. IT DID APPEAR THAT THE PLT OF THE SMA X WAS GOING REAL FAST. THE PLT STATED 120 KTS. IF X WAS AT NORMAL SPD (80/90 KTS) THERE WOULD NOT HAVE BEEN ANY PROB AND X COULD HAVE LANDED BEHIND Y WITH NO PROB. SUPPLEMENTAL INFO FROM ACN 101990: I, BEING THE APCH CTLR, WAS VECTORING Y TO SEQUENCE HIM IN FRONT OF X. ONE FACT I WAS NOT AWARE OF WAS X WAS TRAVELING AT APPROX 120 KTS ON FINAL APCH. SMA Y WAS TRAVELING AT APPROX 60 KTS.

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.