Narrative:

My flight was on a r-hand pattern entry to runway 29 at bed. At the same time, a C310 was approaching from the north on a 90 degree pattern intercept angle. Tower called my flight as traffic to the C310. The C310 pilot reported my flight in sight and was told to follow my flight. When it became apparent that the C310 wasn't modifying his pattern (approximately 1/2 mi separation) I called tower to confirm the sequence. This call was mainly to wake up the C310 pilot. As the separation continued to decrease I pitched up and called tower again. The horizontal separation was 0 ft, vertical -200 ft. At no time did the C310 alter his course. The following are important considerations: 1) the C310 pilot never had me in sight until the separation was compromised. Even then he elected to do nothing. 2) 3 of the C310 passenger watched the whole event unfold. 3) both aircraft were under control of the tower, which had a bright scope. 4) controller training was in progress. 5) tower never said anything during the unfolding of this event. 6) my PNF co-captain was occupied with the before landing checklist. Thus I was making the traffic calls. 7) then to top it off, the C310 compromised separation again on landing by keeping his pattern in too close behind my flight. Tower gave him a go around, which the C310 pilot denied. Tower finally cleared him for landing as I was clearing the runway. From my angle, it looked like the C310 was rolling out already. 8) I discussed these events with the C310 pilot and the tower supervisor. The tower supervisor is reviewing the tapes to determine appropriate safety action. 9) the C310 pattern entry was at the turbojet pattern altitude.

Related reports:

Google
 

Original NASA ASRS Text

Title: FLC OF LEAR 35G IN TFC PATTERN HAS NMAC WITH A C310 WHO HAS BEEN CLRED TO FOLLOW HIM ON APCH.

Narrative: MY FLT WAS ON A R-HAND PATTERN ENTRY TO RWY 29 AT BED. AT THE SAME TIME, A C310 WAS APCHING FROM THE N ON A 90 DEG PATTERN INTERCEPT ANGLE. TWR CALLED MY FLT AS TFC TO THE C310. THE C310 PLT RPTED MY FLT IN SIGHT AND WAS TOLD TO FOLLOW MY FLT. WHEN IT BECAME APPARENT THAT THE C310 WASN'T MODIFYING HIS PATTERN (APPROX 1/2 MI SEPARATION) I CALLED TWR TO CONFIRM THE SEQUENCE. THIS CALL WAS MAINLY TO WAKE UP THE C310 PLT. AS THE SEPARATION CONTINUED TO DECREASE I PITCHED UP AND CALLED TWR AGAIN. THE HORIZ SEPARATION WAS 0 FT, VERT -200 FT. AT NO TIME DID THE C310 ALTER HIS COURSE. THE FOLLOWING ARE IMPORTANT CONSIDERATIONS: 1) THE C310 PLT NEVER HAD ME IN SIGHT UNTIL THE SEPARATION WAS COMPROMISED. EVEN THEN HE ELECTED TO DO NOTHING. 2) 3 OF THE C310 PAX WATCHED THE WHOLE EVENT UNFOLD. 3) BOTH ACFT WERE UNDER CTL OF THE TWR, WHICH HAD A BRIGHT SCOPE. 4) CTLR TRAINING WAS IN PROGRESS. 5) TWR NEVER SAID ANYTHING DURING THE UNFOLDING OF THIS EVENT. 6) MY PNF CO-CAPT WAS OCCUPIED WITH THE BEFORE LNDG CHKLIST. THUS I WAS MAKING THE TFC CALLS. 7) THEN TO TOP IT OFF, THE C310 COMPROMISED SEPARATION AGAIN ON LNDG BY KEEPING HIS PATTERN IN TOO CLOSE BEHIND MY FLT. TWR GAVE HIM A GAR, WHICH THE C310 PLT DENIED. TWR FINALLY CLRED HIM FOR LNDG AS I WAS CLRING THE RWY. FROM MY ANGLE, IT LOOKED LIKE THE C310 WAS ROLLING OUT ALREADY. 8) I DISCUSSED THESE EVENTS WITH THE C310 PLT AND THE TWR SUPVR. THE TWR SUPVR IS REVIEWING THE TAPES TO DETERMINE APPROPRIATE SAFETY ACTION. 9) THE C310 PATTERN ENTRY WAS AT THE TURBOJET PATTERN ALT.

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.