Narrative:

On visual approach to runway 30L at sjc, we initiated pull-up and right bank after seeing a light, single engine airplane on converging course from left. The other aircraft was 300-500 ft to our left, in a shallow left bank. We were probably outside his field of vision. My first reaction was that other aircraft was attempting to land on our runway, but in retrospect, probably overshot final to closely spaced runway 29. We were in contact with sjc tower and at no time were we advised of traffic in pattern for runway 29. We continued to go around and flew an uneventful right pattern to landing. Although we had been cleared for visual approach, it would have been my expectation that approach control or tower would advise us of potential traffic conflict on such a closely spaced runway. The go around was initiated with a pull-up and right turn to avoid collision. I did not immediately correct back to runway 30L centerline as I was preoccupied with aircraft confign in the initial stages of go around. Our resulting flight path took us over runway 30R and could have caused a potential conflict with traffic landing/departing on that runway. No apparent conflict occurred as we were assigned a 300 degree heading and 3000 ft altitude shortly after the go around. Supplemental information from acn 401050: B757 on final ahead of us. We never received a TCASII traffic alert on this traffic. The PNF on the left side of aircraft took control of the airplane since he believed the other plane was on a collision course with us. Recommend review of approach control to tower handoff procedures and tower traffic control procedures for practice approachs to sjc. Recommend review of other aircraft data to include transponder codes used and if squawk was active so TCASII should have advised. Request follow-up and disposition of this incident be forwarded to all parties involved.

Related reports:

Google
 

Original NASA ASRS Text

Title: WHILE ON SHORT APCH TO SJC RWY 30L, THE CREW ON LGT ACR X OBSERVED SMALL FIXED WING ACFT Y ON L SIDE AT THE SAME ALT ON A CONVERGING COURSE. ACR X MADE AN EVASIVE MANEUVER TO THE R THEN A GAR TO RETURN LAND. ACR X CREW ESTIMATED SEPARATION OF ZERO FT VERT AND 300 FT HORIZ. TFC WAS NOT ISSUED TO ACR X AND TCASII DID NOT ALARM.

Narrative: ON VISUAL APCH TO RWY 30L AT SJC, WE INITIATED PULL-UP AND R BANK AFTER SEEING A LIGHT, SINGLE ENG AIRPLANE ON CONVERGING COURSE FROM L. THE OTHER ACFT WAS 300-500 FT TO OUR L, IN A SHALLOW L BANK. WE WERE PROBABLY OUTSIDE HIS FIELD OF VISION. MY FIRST REACTION WAS THAT OTHER ACFT WAS ATTEMPTING TO LAND ON OUR RWY, BUT IN RETROSPECT, PROBABLY OVERSHOT FINAL TO CLOSELY SPACED RWY 29. WE WERE IN CONTACT WITH SJC TWR AND AT NO TIME WERE WE ADVISED OF TFC IN PATTERN FOR RWY 29. WE CONTINUED TO GO AROUND AND FLEW AN UNEVENTFUL R PATTERN TO LNDG. ALTHOUGH WE HAD BEEN CLRED FOR VISUAL APCH, IT WOULD HAVE BEEN MY EXPECTATION THAT APCH CTL OR TWR WOULD ADVISE US OF POTENTIAL TFC CONFLICT ON SUCH A CLOSELY SPACED RWY. THE GAR WAS INITIATED WITH A PULL-UP AND R TURN TO AVOID COLLISION. I DID NOT IMMEDIATELY CORRECT BACK TO RWY 30L CTRLINE AS I WAS PREOCCUPIED WITH ACFT CONFIGN IN THE INITIAL STAGES OF GAR. OUR RESULTING FLT PATH TOOK US OVER RWY 30R AND COULD HAVE CAUSED A POTENTIAL CONFLICT WITH TFC LNDG/DEPARTING ON THAT RWY. NO APPARENT CONFLICT OCCURRED AS WE WERE ASSIGNED A 300 DEG HDG AND 3000 FT ALT SHORTLY AFTER THE GAR. SUPPLEMENTAL INFO FROM ACN 401050: B757 ON FINAL AHEAD OF US. WE NEVER RECEIVED A TCASII TFC ALERT ON THIS TFC. THE PNF ON THE L SIDE OF ACFT TOOK CTL OF THE AIRPLANE SINCE HE BELIEVED THE OTHER PLANE WAS ON A COLLISION COURSE WITH US. RECOMMEND REVIEW OF APCH CTL TO TWR HDOF PROCS AND TWR TFC CTL PROCS FOR PRACTICE APCHS TO SJC. RECOMMEND REVIEW OF OTHER ACFT DATA TO INCLUDE XPONDER CODES USED AND IF SQUAWK WAS ACTIVE SO TCASII SHOULD HAVE ADVISED. REQUEST FOLLOW-UP AND DISPOSITION OF THIS INCIDENT BE FORWARDED TO ALL PARTIES INVOLVED.

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.