Narrative:

Approach control pointed out the traffic we were to follow for a visual to 26L. We had this traffic in sight. Approach control pointed out additional traffic at our 2 O'clock who was to land on 26R. This traffic was in sight and was the cause of our first TCASII warning. As both aircraft turned final on 26L and 26R our TCASII warning became an RA. I was on localizer and GS for 26L. The RA's became intermittent until the OM, where they became continuous. The medium large transport Y was at our 3 O'clock position constantly and slightly lower (approximately 100 ft). Once inside the OM, with the 'before landing checklist' completed, we could not safely fly the approach and keep the medium large transport in sight. The medium large transport Y was too close (approximately 100 ft vertical and 700 ft horizontal). I declared a missed approach. Tower gave us 7000 ft and a heading of 010 degrees. Another air carrier large transport Z had just departed 35L and was climbing to 10000 ft. We had this traffic in sight. There was aural concern with the controllers. We were given 8000 ft and a 010 heading. The large transport Z was held to 7000 ft. Our next heading of 080 degrees ended all conflict. Normal visual approach to 26R. After landing, I called the tower from our operations office. Initially, I spoke with a gentleman who stated that this situation was an everyday occurrence. 'No one else complained.' I also spoke with one of the supervisors, mr a. Mr a expressed great concern and apologized for the necessity of our missed approach. He promised he would investigate further. He did state that there was a lot of training being carried out to get everyone ready for the new airport, and that their normal procedure is to stagger the aircraft on parallel approachs. The main problem ctrs on both aircraft side-by-side with just a small amount of lateral separation. With the medium large transport Y's descending through our altitude to his proper GS intercept altitude, our TCASII gave an RA to 'descend now.'

Google
 

Original NASA ASRS Text

Title: ACR LGT PERFORMS GAR AFTER EXPERIENCING DIFFICULTY IN KEEPING VISUAL CONTACT WITH ACFT ON PARALLEL RWY APCH CURING A VISUAL APCH INTO DEN 26L. FLC DISTR AUDIBLE INTERFERENCE WITH TCASII RA.

Narrative: APCH CTL POINTED OUT THE TFC WE WERE TO FOLLOW FOR A VISUAL TO 26L. WE HAD THIS TFC IN SIGHT. APCH CTL POINTED OUT ADDITIONAL TFC AT OUR 2 O'CLOCK WHO WAS TO LAND ON 26R. THIS TFC WAS IN SIGHT AND WAS THE CAUSE OF OUR FIRST TCASII WARNING. AS BOTH ACFT TURNED FINAL ON 26L AND 26R OUR TCASII WARNING BECAME AN RA. I WAS ON LOC AND GS FOR 26L. THE RA'S BECAME INTERMITTENT UNTIL THE OM, WHERE THEY BECAME CONTINUOUS. THE MLG Y WAS AT OUR 3 O'CLOCK POS CONSTANTLY AND SLIGHTLY LOWER (APPROX 100 FT). ONCE INSIDE THE OM, WITH THE 'BEFORE LNDG CHKLIST' COMPLETED, WE COULD NOT SAFELY FLY THE APCH AND KEEP THE MLG IN SIGHT. THE MLG Y WAS TOO CLOSE (APPROX 100 FT VERT AND 700 FT HORIZ). I DECLARED A MISSED APCH. TWR GAVE US 7000 FT AND A HDG OF 010 DEGS. ANOTHER ACR LGT Z HAD JUST DEPARTED 35L AND WAS CLBING TO 10000 FT. WE HAD THIS TFC IN SIGHT. THERE WAS AURAL CONCERN WITH THE CTLRS. WE WERE GIVEN 8000 FT AND A 010 HDG. THE LGT Z WAS HELD TO 7000 FT. OUR NEXT HDG OF 080 DEGS ENDED ALL CONFLICT. NORMAL VISUAL APCH TO 26R. AFTER LNDG, I CALLED THE TWR FROM OUR OPS OFFICE. INITIALLY, I SPOKE WITH A GENTLEMAN WHO STATED THAT THIS SITUATION WAS AN EVERYDAY OCCURRENCE. 'NO ONE ELSE COMPLAINED.' I ALSO SPOKE WITH ONE OF THE SUPVRS, MR A. MR A EXPRESSED GREAT CONCERN AND APOLOGIZED FOR THE NECESSITY OF OUR MISSED APCH. HE PROMISED HE WOULD INVESTIGATE FURTHER. HE DID STATE THAT THERE WAS A LOT OF TRAINING BEING CARRIED OUT TO GET EVERYONE READY FOR THE NEW ARPT, AND THAT THEIR NORMAL PROC IS TO STAGGER THE ACFT ON PARALLEL APCHS. THE MAIN PROBLEM CTRS ON BOTH ACFT SIDE-BY-SIDE WITH JUST A SMALL AMOUNT OF LATERAL SEPARATION. WITH THE MLG Y'S DSNDING THROUGH OUR ALT TO HIS PROPER GS INTERCEPT ALT, OUR TCASII GAVE AN RA TO 'DSND NOW.'

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.