Narrative:

Air carrier X flight abc ord to phl on mar/tue/03. On ILS runway 9R approach to phl, just inside kelee OM, advised of traffic opposite direction at 11 O'clock. I acquired the traffic visually at 9 O'clock position, approximately 2 NM while I was on the GS at approximately 1500 ft AGL. Simultaneously, I received a TCASII TA. In-flight visibility, I estimate, was 3 NM and haze. I asked phl tower why the traffic was within 2 NM of the localizer when ILS approachs were in progress. I was told this was a traffic watch for a radio station on an interstate 95 overflt. Aircraft on approach to runway 9R behind me reported a TCASII RA. I believe allowing this aircraft to fly that close to a major airport approach corridor created a safety compromise which should have been obvious to everyone.

Google
 

Original NASA ASRS Text

Title: B737 ON APCH TO PHL EXPERIENCED TCASII TA WITH TFC WATCH ACFT.

Narrative: ACR X FLT ABC ORD TO PHL ON MAR/TUE/03. ON ILS RWY 9R APCH TO PHL, JUST INSIDE KELEE OM, ADVISED OF TFC OPPOSITE DIRECTION AT 11 O'CLOCK. I ACQUIRED THE TFC VISUALLY AT 9 O'CLOCK POS, APPROX 2 NM WHILE I WAS ON THE GS AT APPROX 1500 FT AGL. SIMULTANEOUSLY, I RECEIVED A TCASII TA. INFLT VISIBILITY, I ESTIMATE, WAS 3 NM AND HAZE. I ASKED PHL TWR WHY THE TFC WAS WITHIN 2 NM OF THE LOC WHEN ILS APCHS WERE IN PROGRESS. I WAS TOLD THIS WAS A TFC WATCH FOR A RADIO STATION ON AN INTERSTATE 95 OVERFLT. ACFT ON APCH TO RWY 9R BEHIND ME RPTED A TCASII RA. I BELIEVE ALLOWING THIS ACFT TO FLY THAT CLOSE TO A MAJOR ARPT APCH CORRIDOR CREATED A SAFETY COMPROMISE WHICH SHOULD HAVE BEEN OBVIOUS TO EVERYONE.

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.