Narrative:

Upon entering rdu airspace, flying an light transport on a scheduled passenger flight. We were assigned runway 23R by the initial controller. Final controller changed runway assignment to 23L, which meant we would have to cross runway 23R traffic to land on 23L. Controller then called traffic at 12 O'clock to follow for a visual approach to 23L (passenger large transport). At the same time traffic at 10 O'clock position on different controller and for runway 23R (an air carrier Y passenger jet) was converging on collision course. We asked about that traffic and obtained no response until after we made rapid descent to avoid traffic. Continued to uneventful landing. Upon speaking to approach supervisor he stated that the heavy traffic load and the fact that the controller changed runways were the contributing factors to this incident.

Google
 

Original NASA ASRS Text

Title: CLOSE PROX COMMUTER-LTT ACR-MLG.

Narrative: UPON ENTERING RDU AIRSPACE, FLYING AN LTT ON A SCHEDULED PAX FLT. WE WERE ASSIGNED RWY 23R BY THE INITIAL CTLR. FINAL CTLR CHANGED RWY ASSIGNMENT TO 23L, WHICH MEANT WE WOULD HAVE TO CROSS RWY 23R TFC TO LAND ON 23L. CTLR THEN CALLED TFC AT 12 O'CLOCK TO FOLLOW FOR A VISUAL APCH TO 23L (PAX LGT). AT THE SAME TIME TFC AT 10 O'CLOCK POS ON DIFFERENT CTLR AND FOR RWY 23R (AN ACR Y PAX JET) WAS CONVERGING ON COLLISION COURSE. WE ASKED ABOUT THAT TFC AND OBTAINED NO RESPONSE UNTIL AFTER WE MADE RAPID DSCNT TO AVOID TFC. CONTINUED TO UNEVENTFUL LNDG. UPON SPEAKING TO APCH SUPVR HE STATED THAT THE HEAVY TFC LOAD AND THE FACT THAT THE CTLR CHANGED RWYS WERE THE CONTRIBUTING FACTORS TO THIS INCIDENT.

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