Narrative:

We were coming in from mry on a visibility to runway 28L. We were given a vector (about 350 degree) which took us across runway 28L localizer and also took us across the 095 degree right of the sfo VOR (final approach course for runway 28R). We were told to follow an aircraft not behind us and slowed and maneuvered to avoid a widebody transport. We were cleared for visibility and then revectored back across runway 28R final to get back to runway 28L. As the aircraft behind us was descending, we descended quickly (and informed ATC) to avoid him (he was an medium large transport and not landing either). We ended up going through the san carlos air traffic area at about 1500'. We spoke to ATC who said there was a problem and they would look into it. I believe it may have been a new controller who got behind. What a mess!

Google
 

Original NASA ASRS Text

Title: ACFT BEING VECTORED TO SFO RWY 28L FINAL APCH COURSE ENTERED THE ATA OF SQL WITHOUT COORD.

Narrative: WE WERE COMING IN FROM MRY ON A VIS TO RWY 28L. WE WERE GIVEN A VECTOR (ABOUT 350 DEG) WHICH TOOK US ACROSS RWY 28L LOC AND ALSO TOOK US ACROSS THE 095 DEG R OF THE SFO VOR (FINAL APCH COURSE FOR RWY 28R). WE WERE TOLD TO FOLLOW AN ACFT NOT BEHIND US AND SLOWED AND MANEUVERED TO AVOID A WDB. WE WERE CLRED FOR VIS AND THEN REVECTORED BACK ACROSS RWY 28R FINAL TO GET BACK TO RWY 28L. AS THE ACFT BEHIND US WAS DSNDING, WE DSNDED QUICKLY (AND INFORMED ATC) TO AVOID HIM (HE WAS AN MLG AND NOT LNDG EITHER). WE ENDED UP GOING THROUGH THE SAN CARLOS ATA AT ABOUT 1500'. WE SPOKE TO ATC WHO SAID THERE WAS A PROB AND THEY WOULD LOOK INTO IT. I BELIEVE IT MAY HAVE BEEN A NEW CTLR WHO GOT BEHIND. WHAT A MESS!

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.