Narrative:

Upon calling the airport (stl) and MD80 at 2 O'clock (on base to parallel runway) 'in sight,' approach cleared us for visual approach to runway 12L. As we descended through 4000 ft, ATC informed us the MD80 next to us was overshooting his final and, did we still see him? We said 'no' as he'd gone under us. ATC then canceled our approach clearance and told us to maintain 3500 ft. We read it back and looked for the MD80. When we rescanned back in to the altimeter it read 3000 ft. Just as we initiated a climb back to 3500 ft, we saw the MD80, called it, and were reclred for the visual. Occurrences like this are a dime a dozen in the stl terminal area. Ground control has aircraft continuously crossing runways to and from the gate. Tower has 3 parallel runways taking off and landing while performing hold short operations on a runway that intersects all 3. Aircraft are being cleared for takeoff before the last one has even rotated to prevent gars, etc. The fact we got 500 ft low isn't itself to be blamed on the st louis situation totally, but it goes to show that the saturated st louis terminal area leaves little to no room for error to prevent a scary situation. Other contributing factors could have been: 1) the MD80 fault or his controller's late turn to cause him to cross to our side. 2) I had a new and inexperienced first officer that I felt I had to help assist in looking for the traffic (as he'd lost it) and missed giving me the standard altitude calls to alert me of my altitude. 3) the typical case of 'one guy fix the problem (find the traffic), one guy fly the airplane' broke down!

Google
 

Original NASA ASRS Text

Title: BA31 DSNDS THROUGH CLRED ALT ON APCH TO STL.

Narrative: UPON CALLING THE ARPT (STL) AND MD80 AT 2 O'CLOCK (ON BASE TO PARALLEL RWY) 'IN SIGHT,' APCH CLRED US FOR VISUAL APCH TO RWY 12L. AS WE DSNDED THROUGH 4000 FT, ATC INFORMED US THE MD80 NEXT TO US WAS OVERSHOOTING HIS FINAL AND, DID WE STILL SEE HIM? WE SAID 'NO' AS HE'D GONE UNDER US. ATC THEN CANCELED OUR APCH CLRNC AND TOLD US TO MAINTAIN 3500 FT. WE READ IT BACK AND LOOKED FOR THE MD80. WHEN WE RESCANNED BACK IN TO THE ALTIMETER IT READ 3000 FT. JUST AS WE INITIATED A CLB BACK TO 3500 FT, WE SAW THE MD80, CALLED IT, AND WERE RECLRED FOR THE VISUAL. OCCURRENCES LIKE THIS ARE A DIME A DOZEN IN THE STL TERMINAL AREA. GND CTL HAS ACFT CONTINUOUSLY XING RWYS TO AND FROM THE GATE. TWR HAS 3 PARALLEL RWYS TAKING OFF AND LNDG WHILE PERFORMING HOLD SHORT OPS ON A RWY THAT INTERSECTS ALL 3. ACFT ARE BEING CLRED FOR TKOF BEFORE THE LAST ONE HAS EVEN ROTATED TO PREVENT GARS, ETC. THE FACT WE GOT 500 FT LOW ISN'T ITSELF TO BE BLAMED ON THE ST LOUIS SIT TOTALLY, BUT IT GOES TO SHOW THAT THE SATURATED ST LOUIS TERMINAL AREA LEAVES LITTLE TO NO ROOM FOR ERROR TO PREVENT A SCARY SIT. OTHER CONTRIBUTING FACTORS COULD HAVE BEEN: 1) THE MD80 FAULT OR HIS CTLR'S LATE TURN TO CAUSE HIM TO CROSS TO OUR SIDE. 2) I HAD A NEW AND INEXPERIENCED FO THAT I FELT I HAD TO HELP ASSIST IN LOOKING FOR THE TFC (AS HE'D LOST IT) AND MISSED GIVING ME THE STANDARD ALT CALLS TO ALERT ME OF MY ALT. 3) THE TYPICAL CASE OF 'ONE GUY FIX THE PROB (FIND THE TFC), ONE GUY FLY THE AIRPLANE' BROKE DOWN!

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.