Narrative:

During climb out on a 'dumbarton left' (pao left standard departure to southwest) departure at about 90 KIAS, through 1500 ft west of highway 101, we (CFI student and myself, CFI) heard an old MTR report inbound for landing over stanford university while on tower frequency (118.6). The tower was busy and did not respond to the call. Since we were approaching stanford (heading about 200 degree) and were within a mi of where the aircraft reported, we immediately looked for the traffic. The MTR was over stanford campus heading straight at us (on heading 020 degree). We were climbing through 1700 ft and the other aircraft appeared to be descending through 2000 ft. Our distance was less than a mi, now, and closing rapidly. Per aim procedures, we turned right immediately and the other aircraft turned left. Contact was imminent. With less than 1/4-1/8 mi we cut power, banked sharply (45-60 degree) to the left while descending. The MTR must have finally seen us since no contact was made. When we completed a 360 degree turn we saw the other aircraft in a left circling turn over stanford. He made a second call to pao tower and was told to 'stand by'. I reported the near miss to tower, immediately, on 118.6, identing the other aircraft as the MTR. That aircraft was about 2 mi 'inside' pao air traffic area when he first called in. He continued inbound with no ATC acknowledgement. We called pao ground control while airborne outside pao air traffic area and asked, after the MTR landed and was taxiing back to the hangar, to have the pilot call us at our flying club. Ground control relayed our message to the pilot. The pilot responded sarcastically, 'yeah, right!. I reported the near miss in waiting at pao tower and it was sent to FSDO (sjc). The MTR pilot is a 'professional' medium large transport captain for an airline. Supplemental information from acn 191586: approaching pao I monitored local frequency for approximately 5 mins and noticed very busy controller trying to keep up with volume of aircraft. Sounded like she might be a trainee, called in over stanford (normal reporting point) and got no reply (too busy). Called in again entering the air traffic area and receiving a 'stand by'. Still very busy. Approaching the stanford stadium monitoring how busy the pattern was, I began a right 360 degree turn to allow the controller time to sequence me. Noticed a high wing small aircraft on either left crosswind departure or turning to left downwind. Determined it was no factor and continued 360. In turn, heard pilot of other aircraft say, 'tower...I want to report a near midair'. Tower then cleared me to enter downwind and land. Other pilot stated a 1/8 mi passing distance. Not a near miss in my opinion but a concern of a pilot who flies a collision course to the point of a near miss in his opinion. On the ground he said to controller he saw me at 2 mi and continued until his evasive maneuver at 1/8 mi. He should change flight path sooner and controller not ignore repeated transmission from inbound aircraft.

Related reports:

Google
 

Original NASA ASRS Text

Title: POTENTIAL CONFLICT LTSS IN AN OPPOSITE DIRECTION TFC SITUATION IN PROX OF ATA.

Narrative: DURING CLBOUT ON A 'DUMBARTON L' (PAO L STANDARD DEP TO SW) DEP AT ABOUT 90 KIAS, THROUGH 1500 FT W OF HIGHWAY 101, WE (CFI STUDENT AND MYSELF, CFI) HEARD AN OLD MTR RPT INBOUND FOR LNDG OVER STANFORD UNIVERSITY WHILE ON TWR FREQ (118.6). THE TWR WAS BUSY AND DID NOT RESPOND TO THE CALL. SINCE WE WERE APCHING STANFORD (HDG ABOUT 200 DEG) AND WERE WITHIN A MI OF WHERE THE ACFT RPTED, WE IMMEDIATELY LOOKED FOR THE TFC. THE MTR WAS OVER STANFORD CAMPUS HDG STRAIGHT AT US (ON HDG 020 DEG). WE WERE CLBING THROUGH 1700 FT AND THE OTHER ACFT APPEARED TO BE DSNDING THROUGH 2000 FT. OUR DISTANCE WAS LESS THAN A MI, NOW, AND CLOSING RAPIDLY. PER AIM PROCS, WE TURNED R IMMEDIATELY AND THE OTHER ACFT TURNED L. CONTACT WAS IMMINENT. WITH LESS THAN 1/4-1/8 MI WE CUT PWR, BANKED SHARPLY (45-60 DEG) TO THE L WHILE DSNDING. THE MTR MUST HAVE FINALLY SEEN US SINCE NO CONTACT WAS MADE. WHEN WE COMPLETED A 360 DEG TURN WE SAW THE OTHER ACFT IN A L CIRCLING TURN OVER STANFORD. HE MADE A SECOND CALL TO PAO TWR AND WAS TOLD TO 'STAND BY'. I RPTED THE NEAR MISS TO TWR, IMMEDIATELY, ON 118.6, IDENTING THE OTHER ACFT AS THE MTR. THAT ACFT WAS ABOUT 2 MI 'INSIDE' PAO ATA WHEN HE FIRST CALLED IN. HE CONTINUED INBOUND WITH NO ATC ACKNOWLEDGEMENT. WE CALLED PAO GND CTL WHILE AIRBORNE OUTSIDE PAO ATA AND ASKED, AFTER THE MTR LANDED AND WAS TAXIING BACK TO THE HANGAR, TO HAVE THE PLT CALL US AT OUR FLYING CLUB. GND CTL RELAYED OUR MESSAGE TO THE PLT. THE PLT RESPONDED SARCASTICALLY, 'YEAH, RIGHT!. I RPTED THE NEAR MISS IN WAITING AT PAO TWR AND IT WAS SENT TO FSDO (SJC). THE MTR PLT IS A 'PROFESSIONAL' MLG CAPT FOR AN AIRLINE. SUPPLEMENTAL INFO FROM ACN 191586: APCHING PAO I MONITORED LCL FREQ FOR APPROX 5 MINS AND NOTICED VERY BUSY CTLR TRYING TO KEEP UP WITH VOLUME OF ACFT. SOUNDED LIKE SHE MIGHT BE A TRAINEE, CALLED IN OVER STANFORD (NORMAL RPTING POINT) AND GOT NO REPLY (TOO BUSY). CALLED IN AGAIN ENTERING THE ATA AND RECEIVING A 'STAND BY'. STILL VERY BUSY. APCHING THE STANFORD STADIUM MONITORING HOW BUSY THE PATTERN WAS, I BEGAN A RIGHT 360 DEG TURN TO ALLOW THE CTLR TIME TO SEQUENCE ME. NOTICED A HIGH WING SMA ON EITHER L XWIND DEP OR TURNING TO L DOWNWIND. DETERMINED IT WAS NO FACTOR AND CONTINUED 360. IN TURN, HEARD PLT OF OTHER ACFT SAY, 'TWR...I WANT TO RPT A NEAR MIDAIR'. TWR THEN CLRED ME TO ENTER DOWNWIND AND LAND. OTHER PLT STATED A 1/8 MI PASSING DISTANCE. NOT A NEAR MISS IN MY OPINION BUT A CONCERN OF A PLT WHO FLIES A COLLISION COURSE TO THE POINT OF A NEAR MISS IN HIS OPINION. ON THE GND HE SAID TO CTLR HE SAW ME AT 2 MI AND CONTINUED UNTIL HIS EVASIVE MANEUVER AT 1/8 MI. HE SHOULD CHANGE FLT PATH SOONER AND CTLR NOT IGNORE REPEATED XMISSION FROM INBOUND ACFT.

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.