Narrative:

On final to runway 26L at iah we were cleared the visual approach to cross JEPN1 at or below 2000 ft; which seemed a bit unusual. Approach was also calling out parallel traffic on the approach to runway 27; which we had in sight; and was being displayed on TCAS. There was other traffic being displayed on TCAS ahead; to the right; and below our altitude by about 1000 ft that approach control was not calling out. Approach tried to give us a frequency change as we were nearing the non-alerted to traffic; which I declined stating that I'd like to stay on his frequency in the event we received an RA; which we did not. We leveled at 2000 ft and once clear of the conflict I accepted the frequency change to tower and completed the remainder of the flight uneventfully. Neither the first officer nor myself ever saw the aircraft that passed directly below us with the minimum altitude being displayed as 700 ft. The cockpit was very busy this entire time watching the traffic approach control did alert us too; configuring the aircraft; turning to final; checking the unusual altitude cleared to; the potential frequency change; and watching TCAS for the aircraft we were not alerted to by approach control; and trying to locate that aircraft. After landing and thinking about the incident I'm sure approach control never saw the aircraft that was a potential hazard and at the time; with all that was going on; I was not clear to approach about the position of the aircraft we were concerned with. As stated earlier; we did not receive an RA. There was an FAA inspector on the jumpseat; who; after landing said he saw the aircraft cross below us and that he was going to talk to the approach controller about the incident. Supplemental information from acn 794439: had we continued a normal descent for JEPN1 we very likely would have impacted the small aircraft.

Google
 

Original NASA ASRS Text

Title: MD80 DELAYS SWITCH TO TOWER DUE TO POTENTIAL FOR AN RA FROM ACFT NOT APPARENT TO APCH CTL.

Narrative: ON FINAL TO RWY 26L AT IAH WE WERE CLRED THE VISUAL APCH TO CROSS JEPN1 AT OR BELOW 2000 FT; WHICH SEEMED A BIT UNUSUAL. APCH WAS ALSO CALLING OUT PARALLEL TFC ON THE APCH TO RWY 27; WHICH WE HAD IN SIGHT; AND WAS BEING DISPLAYED ON TCAS. THERE WAS OTHER TFC BEING DISPLAYED ON TCAS AHEAD; TO THE R; AND BELOW OUR ALT BY ABOUT 1000 FT THAT APCH CTL WAS NOT CALLING OUT. APCH TRIED TO GIVE US A FREQ CHANGE AS WE WERE NEARING THE NON-ALERTED TO TFC; WHICH I DECLINED STATING THAT I'D LIKE TO STAY ON HIS FREQ IN THE EVENT WE RECEIVED AN RA; WHICH WE DID NOT. WE LEVELED AT 2000 FT AND ONCE CLR OF THE CONFLICT I ACCEPTED THE FREQ CHANGE TO TWR AND COMPLETED THE REMAINDER OF THE FLT UNEVENTFULLY. NEITHER THE FO NOR MYSELF EVER SAW THE ACFT THAT PASSED DIRECTLY BELOW US WITH THE MINIMUM ALT BEING DISPLAYED AS 700 FT. THE COCKPIT WAS VERY BUSY THIS ENTIRE TIME WATCHING THE TFC APCH CTL DID ALERT US TOO; CONFIGURING THE ACFT; TURNING TO FINAL; CHKING THE UNUSUAL ALT CLRED TO; THE POTENTIAL FREQ CHANGE; AND WATCHING TCAS FOR THE ACFT WE WERE NOT ALERTED TO BY APCH CTL; AND TRYING TO LOCATE THAT ACFT. AFTER LNDG AND THINKING ABOUT THE INCIDENT I'M SURE APCH CTL NEVER SAW THE ACFT THAT WAS A POTENTIAL HAZARD AND AT THE TIME; WITH ALL THAT WAS GOING ON; I WAS NOT CLR TO APCH ABOUT THE POS OF THE ACFT WE WERE CONCERNED WITH. AS STATED EARLIER; WE DID NOT RECEIVE AN RA. THERE WAS AN FAA INSPECTOR ON THE JUMPSEAT; WHO; AFTER LNDG SAID HE SAW THE ACFT CROSS BELOW US AND THAT HE WAS GOING TO TALK TO THE APCH CTLR ABOUT THE INCIDENT. SUPPLEMENTAL INFO FROM ACN 794439: HAD WE CONTINUED A NORMAL DSCNT FOR JEPN1 WE VERY LIKELY WOULD HAVE IMPACTED THE SMALL ACFT.

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