Narrative:

While working local control, aircraft X, an E145, checked on for landing runway 5R approximately 10 mi out. I cleared aircraft X to land on runway 5R. I had a couple of departures ready to depart runway 5R and a PA28 in the touch-and-go pattern on runway 5L. Approach was working a BE35 doing practice instrument approachs, who was on a right downwind at 2500 ft for the ILS runway 5L. After clearing my second departure on runway 5R, I looked up at the d-brite to see approachs. The BE35 had turned a 4 mi right base at 2500 ft, and aircraft X was on a 5 mi final descending through 2800 ft. I immediately climbed aircraft X to 3000 ft and told him about the traffic. Then I turned aircraft X to a heading of 320 degrees and coordination with approach. The regional office said the radar data showed closest points as 300 ft and .52 mi. They also said no loss of separation, because IFR to VFR separation for class C airspace on final is that targets don't touch. No written statement required. Good job, pat on the back, go back to work. Supplemental information from acn 573310: the BE36 was assigned a 230 degree heading for the downwind for a proactive ILS. He, instead, turned to a 330 heading, which placed him in the path of an E145 on a visual approach. I saw this happen and told the controller working the BE36 to turn him. He was turned, and the tower controller turned the E145. Callback conversation with reporter revealed the following information: reporter said traffic was very heavy at the time of the incident. The local controller said he saw the conflict on his BRITE radar and immediately climbed the E145 and issued a TA. He said the E145 pilot told him that they had received his advisory before the TCASII alerted. Asked if any of the pilots had reported a near midair collision, the reporter said no.

Google
 

Original NASA ASRS Text

Title: A BE36 VFR ON A VECTOR FOR A PRACTICE ILS TO TYS MAKES AN INCORRECT TURN AND CONFLICTS WITH A E145 ON FINAL.

Narrative: WHILE WORKING LCL CTL, ACFT X, AN E145, CHKED ON FOR LNDG RWY 5R APPROX 10 MI OUT. I CLRED ACFT X TO LAND ON RWY 5R. I HAD A COUPLE OF DEPS READY TO DEPART RWY 5R AND A PA28 IN THE TOUCH-AND-GO PATTERN ON RWY 5L. APCH WAS WORKING A BE35 DOING PRACTICE INST APCHS, WHO WAS ON A R DOWNWIND AT 2500 FT FOR THE ILS RWY 5L. AFTER CLRING MY SECOND DEP ON RWY 5R, I LOOKED UP AT THE D-BRITE TO SEE APCHS. THE BE35 HAD TURNED A 4 MI R BASE AT 2500 FT, AND ACFT X WAS ON A 5 MI FINAL DSNDING THROUGH 2800 FT. I IMMEDIATELY CLBED ACFT X TO 3000 FT AND TOLD HIM ABOUT THE TFC. THEN I TURNED ACFT X TO A HDG OF 320 DEGS AND COORD WITH APCH. THE REGIONAL OFFICE SAID THE RADAR DATA SHOWED CLOSEST POINTS AS 300 FT AND .52 MI. THEY ALSO SAID NO LOSS OF SEPARATION, BECAUSE IFR TO VFR SEPARATION FOR CLASS C AIRSPACE ON FINAL IS THAT TARGETS DON'T TOUCH. NO WRITTEN STATEMENT REQUIRED. GOOD JOB, PAT ON THE BACK, GO BACK TO WORK. SUPPLEMENTAL INFO FROM ACN 573310: THE BE36 WAS ASSIGNED A 230 DEG HDG FOR THE DOWNWIND FOR A PROACTIVE ILS. HE, INSTEAD, TURNED TO A 330 HDG, WHICH PLACED HIM IN THE PATH OF AN E145 ON A VISUAL APCH. I SAW THIS HAPPEN AND TOLD THE CTLR WORKING THE BE36 TO TURN HIM. HE WAS TURNED, AND THE TWR CTLR TURNED THE E145. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR SAID TFC WAS VERY HVY AT THE TIME OF THE INCIDENT. THE LCL CTLR SAID HE SAW THE CONFLICT ON HIS BRITE RADAR AND IMMEDIATELY CLBED THE E145 AND ISSUED A TA. HE SAID THE E145 PLT TOLD HIM THAT THEY HAD RECEIVED HIS ADVISORY BEFORE THE TCASII ALERTED. ASKED IF ANY OF THE PLTS HAD RPTED A NMAC, THE RPTR SAID NO.

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.