Narrative:

On ILS approach to runway 8 at lns, I was switched to tower outside the marker, and tower asked that I report on a 3 mi final. I broke out at about 2200 ft MSL, and was alerted to traffic by traffic information service (ground-based traffic information service). I located an aerostar in cruise flight at my 2:30 O'clock position, less than 1 mi, slightly lower altitude, closing rapidly from right to left. I maneuvered clear and advised. The aerostar did not change course or altitude. Tower queried the aerostar, and he reported seeing me, but only after I had maneuvered clear. Corrective actions: in MVFR conditions, the tower should not clear VFR aircraft across the localizer at altitudes that conflict with IFR arrs. The aerostar could have been cleared through class D by going over the airport or via the outer marker. Aerostar should have been lower. The aerostar was at an altitude that did not meet the minimum cloud clearance for VFR flight. Tower should have advised me of the potential conflict, either by questioning the aerostar pilot or by use of the har remote radar display. Tower cleared the aerostar through the class D airspace at an altitude that they should have known would not meet VFR cloud clearance standards. Human performance considerations -- while on the tower frequency, I heard several aircraft being cleared through the class D en route to or from another airport (smoketown). The tower was moderately busy working a mix of IFR arrivals to lns and VFR aircraft to or from smoketown. It was difficult to obtain a clear picture of the traffic situation while in clouds shooting the ILS. I believe that it was also difficult for the aerostar to estimate my position on the localizer. Because of the altitude of the aerostar, I was only in visual conditions for about 30 seconds before seeing the conflicting traffic. (Likewise, the aerostar had only 30 seconds to find and avoid my aircraft.) traffic information service functioned well to alert me to the traffic conflict. I do not think I would have seen the aerostar without the traffic information service alert.

Related reports:

Google
 

Original NASA ASRS Text

Title: C182 PLT AND A PIPER AEROSTAR HAD LESS THAN LEGAL SEPARATION IN LNS CLASS D.

Narrative: ON ILS APCH TO RWY 8 AT LNS, I WAS SWITCHED TO TWR OUTSIDE THE MARKER, AND TWR ASKED THAT I RPT ON A 3 MI FINAL. I BROKE OUT AT ABOUT 2200 FT MSL, AND WAS ALERTED TO TFC BY TFC INFO SVC (GND-BASED TFC INFO SVC). I LOCATED AN AEROSTAR IN CRUISE FLT AT MY 2:30 O'CLOCK POS, LESS THAN 1 MI, SLIGHTLY LOWER ALT, CLOSING RAPIDLY FROM R TO L. I MANEUVERED CLR AND ADVISED. THE AEROSTAR DID NOT CHANGE COURSE OR ALT. TWR QUERIED THE AEROSTAR, AND HE RPTED SEEING ME, BUT ONLY AFTER I HAD MANEUVERED CLR. CORRECTIVE ACTIONS: IN MVFR CONDITIONS, THE TWR SHOULD NOT CLR VFR ACFT ACROSS THE LOC AT ALTS THAT CONFLICT WITH IFR ARRS. THE AEROSTAR COULD HAVE BEEN CLRED THROUGH CLASS D BY GOING OVER THE ARPT OR VIA THE OUTER MARKER. AEROSTAR SHOULD HAVE BEEN LOWER. THE AEROSTAR WAS AT AN ALT THAT DID NOT MEET THE MINIMUM CLOUD CLRNC FOR VFR FLT. TWR SHOULD HAVE ADVISED ME OF THE POTENTIAL CONFLICT, EITHER BY QUESTIONING THE AEROSTAR PLT OR BY USE OF THE HAR REMOTE RADAR DISPLAY. TWR CLRED THE AEROSTAR THROUGH THE CLASS D AIRSPACE AT AN ALT THAT THEY SHOULD HAVE KNOWN WOULD NOT MEET VFR CLOUD CLRNC STANDARDS. HUMAN PERFORMANCE CONSIDERATIONS -- WHILE ON THE TWR FREQ, I HEARD SEVERAL ACFT BEING CLRED THROUGH THE CLASS D ENRTE TO OR FROM ANOTHER ARPT (SMOKETOWN). THE TWR WAS MODERATELY BUSY WORKING A MIX OF IFR ARRIVALS TO LNS AND VFR ACFT TO OR FROM SMOKETOWN. IT WAS DIFFICULT TO OBTAIN A CLR PICTURE OF THE TFC SIT WHILE IN CLOUDS SHOOTING THE ILS. I BELIEVE THAT IT WAS ALSO DIFFICULT FOR THE AEROSTAR TO ESTIMATE MY POS ON THE LOC. BECAUSE OF THE ALT OF THE AEROSTAR, I WAS ONLY IN VISUAL CONDITIONS FOR ABOUT 30 SECONDS BEFORE SEEING THE CONFLICTING TFC. (LIKEWISE, THE AEROSTAR HAD ONLY 30 SECONDS TO FIND AND AVOID MY ACFT.) TFC INFO SVC FUNCTIONED WELL TO ALERT ME TO THE TFC CONFLICT. I DO NOT THINK I WOULD HAVE SEEN THE AEROSTAR WITHOUT THE TFC INFO SVC ALERT.

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.