Narrative:

We were cleared for takeoff at sjc with the san jose 4 departure. Shortly after takeoff the tower called traffic at 3 mi and said to stay with him. We looked for the traffic but the haze and sun prohibited us from seeing it, and we told the tower so. The tower asked the other traffic, an small aircraft, if he had the jet traffic in sight. This alerted us to continue to search for the other traffic. We did not see him until he was passing just off our left wing at what appeared to be 100-200'. No evasive action was required or taken. This incident was discussed by telephone with the san jose tower supervisor. Callback conversation with reporter revealed the following: the small aircraft that came close to reporter's aircraft was inbound to sjc from the northwest. Tower had told the pilot to proceed directly over the airport at 2000' for a left turn into runway 29. The small aircraft pilot became somewhat disoriented and passed approximately 4 mi west of the airport before turning towards the airport. By the time the tower noticed this error and gave reporter a traffic advisory, the small aircraft was very close to the medium large transport. At the time of the near midair collision, the small aircraft was entering downwind for runway 29. A later conversation with the small aircraft pilot revealed the following additional information: the small aircraft was actually inbound to rhv from pao over nuq. Upon calling sjc tower, the pilot was told to proceed over san jose at or above 2000' and to report passing. Pilot of small aircraft felt that was vague and did not take it to mean directly over the airport. As a consequence the small aircraft's flight path was toward rhv and would cross the departure path from runway 30 at sjc about 2 mi northwest of the airport. This is where the conflict occurred. Small aircraft pilot said that he did not feel as though this was a near miss, but did say it was too close for comfort.

Google
 

Original NASA ASRS Text

Title: CLOSE PROX BETWEEN ACR-MLG AND SMA SHORTLY AFTER MLG DEPARTED SJC.

Narrative: WE WERE CLRED FOR TKOF AT SJC WITH THE SAN JOSE 4 DEP. SHORTLY AFTER TKOF THE TWR CALLED TFC AT 3 MI AND SAID TO STAY WITH HIM. WE LOOKED FOR THE TFC BUT THE HAZE AND SUN PROHIBITED US FROM SEEING IT, AND WE TOLD THE TWR SO. THE TWR ASKED THE OTHER TFC, AN SMA, IF HE HAD THE JET TFC IN SIGHT. THIS ALERTED US TO CONTINUE TO SEARCH FOR THE OTHER TFC. WE DID NOT SEE HIM UNTIL HE WAS PASSING JUST OFF OUR LEFT WING AT WHAT APPEARED TO BE 100-200'. NO EVASIVE ACTION WAS REQUIRED OR TAKEN. THIS INCIDENT WAS DISCUSSED BY TELEPHONE WITH THE SAN JOSE TWR SUPVR. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING: THE SMA THAT CAME CLOSE TO RPTR'S ACFT WAS INBND TO SJC FROM THE NW. TWR HAD TOLD THE PLT TO PROCEED DIRECTLY OVER THE ARPT AT 2000' FOR A LEFT TURN INTO RWY 29. THE SMA PLT BECAME SOMEWHAT DISORIENTED AND PASSED APPROX 4 MI W OF THE ARPT BEFORE TURNING TOWARDS THE ARPT. BY THE TIME THE TWR NOTICED THIS ERROR AND GAVE RPTR A TFC ADVISORY, THE SMA WAS VERY CLOSE TO THE MLG. AT THE TIME OF THE NMAC, THE SMA WAS ENTERING DOWNWIND FOR RWY 29. A LATER CONVERSATION WITH THE SMA PLT REVEALED THE FOLLOWING ADDITIONAL INFO: THE SMA WAS ACTUALLY INBND TO RHV FROM PAO OVER NUQ. UPON CALLING SJC TWR, THE PLT WAS TOLD TO PROCEED OVER SAN JOSE AT OR ABOVE 2000' AND TO RPT PASSING. PLT OF SMA FELT THAT WAS VAGUE AND DID NOT TAKE IT TO MEAN DIRECTLY OVER THE ARPT. AS A CONSEQUENCE THE SMA'S FLT PATH WAS TOWARD RHV AND WOULD CROSS THE DEP PATH FROM RWY 30 AT SJC ABOUT 2 MI NW OF THE ARPT. THIS IS WHERE THE CONFLICT OCCURRED. SMA PLT SAID THAT HE DID NOT FEEL AS THOUGH THIS WAS A NEAR MISS, BUT DID SAY IT WAS TOO CLOSE FOR COMFORT.

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.