Narrative:

Was cleared for quiet bridge approach to 28R at sfo. At approximately 13 DME, ATC called out traffic at our 10 O'clock. A widebody transport Y on left base for 28L. We called the widebody transport Y in sight and was told to maintain visual separation. From the position of the widebody transport Y, I could tell he was going to roll out on final side by side with us. As the widebody transport Y got closer, it became apparent that he wasn't going to turn onto final, but stay on his current heading and descending right at us. Before we could call ATC, they called widebody transport Y to confirm he was turning onto final and that he had us in sight. In broken english the response was negative. At that point we initiated a diving left turn as an evasive maneuver to avoid the widebody transport Y wake turbulence. ATC then called us and told us to move over to 28L and make a visual approach to 28L. ATC then cleared widebody transport Y for a visual to 28R. My guess is that widebody transport Y passed over us during our evasive action by about 300-400 ft and over shot both runways by over half a mi. We then made a normal approach and landing to 28L. I feel that some of the contributing factors to this incident were language communication problems between widebody transport Y and ATC, and widebody transport Y lack of understanding the unique parallel approach procedure for runways 28 at sfo. It's apparent the widebody transport Y didn't understand the visual approach clearance issued to him or he didn't realize how important it is not to overshoot your runway on final. Another problem was having a heavy aircraft line up side by side with smaller aircraft. I understand that is against the operation procedures for visuals to the 28's. I feel the problem might have been eliminated by at the least vectoring the widebody transport behind us or even better is to have him do the charted tip toe visual to 28L. I feel that all foreign carriers should be required to execute the charted visual approachs since they may not operate often enough out of sfo to be familiar with it's operation and to help insure understanding about the procedures.

Google
 

Original NASA ASRS Text

Title: FOREIGN WDB ACFT OVERSHOT TURN ONTO FINAL APCH TO RWY 28L AND HAD NMAC WITH SMT ON FINAL TO RWY 28R.

Narrative: WAS CLRED FOR QUIET BRIDGE APCH TO 28R AT SFO. AT APPROX 13 DME, ATC CALLED OUT TFC AT OUR 10 O'CLOCK. A WDB Y ON L BASE FOR 28L. WE CALLED THE WDB Y IN SIGHT AND WAS TOLD TO MAINTAIN VISUAL SEPARATION. FROM THE POS OF THE WDB Y, I COULD TELL HE WAS GOING TO ROLL OUT ON FINAL SIDE BY SIDE WITH US. AS THE WDB Y GOT CLOSER, IT BECAME APPARENT THAT HE WASN'T GOING TO TURN ONTO FINAL, BUT STAY ON HIS CURRENT HDG AND DSNDING RIGHT AT US. BEFORE WE COULD CALL ATC, THEY CALLED WDB Y TO CONFIRM HE WAS TURNING ONTO FINAL AND THAT HE HAD US IN SIGHT. IN BROKEN ENGLISH THE RESPONSE WAS NEGATIVE. AT THAT POINT WE INITIATED A DIVING L TURN AS AN EVASIVE MANEUVER TO AVOID THE WDB Y WAKE TURB. ATC THEN CALLED US AND TOLD US TO MOVE OVER TO 28L AND MAKE A VISUAL APCH TO 28L. ATC THEN CLRED WDB Y FOR A VISUAL TO 28R. MY GUESS IS THAT WDB Y PASSED OVER US DURING OUR EVASIVE ACTION BY ABOUT 300-400 FT AND OVER SHOT BOTH RWYS BY OVER HALF A MI. WE THEN MADE A NORMAL APCH AND LNDG TO 28L. I FEEL THAT SOME OF THE CONTRIBUTING FACTORS TO THIS INCIDENT WERE LANGUAGE COM PROBLEMS BTWN WDB Y AND ATC, AND WDB Y LACK OF UNDERSTANDING THE UNIQUE PARALLEL APCH PROC FOR RWYS 28 AT SFO. IT'S APPARENT THE WDB Y DIDN'T UNDERSTAND THE VISUAL APCH CLRNC ISSUED TO HIM OR HE DIDN'T REALIZE HOW IMPORTANT IT IS NOT TO OVERSHOOT YOUR RWY ON FINAL. ANOTHER PROBLEM WAS HAVING A HVY ACFT LINE UP SIDE BY SIDE WITH SMALLER ACFT. I UNDERSTAND THAT IS AGAINST THE OP PROCS FOR VISUALS TO THE 28'S. I FEEL THE PROBLEM MIGHT HAVE BEEN ELIMINATED BY AT THE LEAST VECTORING THE WDB BEHIND US OR EVEN BETTER IS TO HAVE HIM DO THE CHARTED TIP TOE VISUAL TO 28L. I FEEL THAT ALL FOREIGN CARRIERS SHOULD BE REQUIRED TO EXECUTE THE CHARTED VISUAL APCHS SINCE THEY MAY NOT OPERATE OFTEN ENOUGH OUT OF SFO TO BE FAMILIAR WITH IT'S OP AND TO HELP INSURE UNDERSTANDING ABOUT THE PROCS.

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.