Narrative:

Runway was very busy with aircraft being tightly sequenced (several aircraft may have been plted by inexperienced or student pilots). WX was cavu, and apparently many pilots were out flying on this saturday afternoon. Our aircraft, a king air 200, was cleared into position and hold on runway 9, we were on an IFR flight plan. Our clearance after departure was the following: radar vectors to harris VOR, climb to 3000 ft MSL, heading 360 degrees after departure. An aircraft (piper cub or tri-pacer type) which had just landed was slow clearing the runway, and we were delayed. As we were cleared for takeoff, another aircraft on approach was instructed to go around. (It is interesting to note that we had experienced the same situation when we had previously landed -- we had to initiate a go around because traffic had not been sequenced properly.) as we climbed out and began our turn toward a 360 degree heading, we were told to contact departure. As we approached 2500 ft MSL, an aircraft (it appeared to be a C400 series aircraft) moved in front of us from right to left. We immediately stopped the turn and deviated to the right. The conflicted aircraft appeared to be at the same altitude and entering a left downwind to runway 9. When we contacted departure, we were told to watch for traffic at 2500 ft MSL at 2 O'clock position. However, by that time the aircraft was past us to the left (the west). We subsequently asked controller about the conflict. He replied that the aircraft had been handed over to ryy tower and that he was not in contact with the aircraft. This near miss apparently occurred as control for both aircraft was being passed from approach to tower and tower to departure. The busy traffic environment at ryy and our delay on the ground were contributing factors since they may have caused both aircraft to be out-of-sequence from what was planned by ATC.

Related reports:

Google
 

Original NASA ASRS Text

Title: IFR BE20 DEP FROM RYY EXPERIENCED NMAC WITH VFR TFC ENTERING PATTERN.

Narrative: RWY WAS VERY BUSY WITH ACFT BEING TIGHTLY SEQUENCED (SEVERAL ACFT MAY HAVE BEEN PLTED BY INEXPERIENCED OR STUDENT PLTS). WX WAS CAVU, AND APPARENTLY MANY PLTS WERE OUT FLYING ON THIS SATURDAY AFTERNOON. OUR ACFT, A KING AIR 200, WAS CLRED INTO POS AND HOLD ON RWY 9, WE WERE ON AN IFR FLT PLAN. OUR CLRNC AFTER DEP WAS THE FOLLOWING: RADAR VECTORS TO HARRIS VOR, CLB TO 3000 FT MSL, HDG 360 DEGS AFTER DEP. AN ACFT (PIPER CUB OR TRI-PACER TYPE) WHICH HAD JUST LANDED WAS SLOW CLRING THE RWY, AND WE WERE DELAYED. AS WE WERE CLRED FOR TKOF, ANOTHER ACFT ON APCH WAS INSTRUCTED TO GO AROUND. (IT IS INTERESTING TO NOTE THAT WE HAD EXPERIENCED THE SAME SIT WHEN WE HAD PREVIOUSLY LANDED -- WE HAD TO INITIATE A GAR BECAUSE TFC HAD NOT BEEN SEQUENCED PROPERLY.) AS WE CLBED OUT AND BEGAN OUR TURN TOWARD A 360 DEG HDG, WE WERE TOLD TO CONTACT DEP. AS WE APCHED 2500 FT MSL, AN ACFT (IT APPEARED TO BE A C400 SERIES ACFT) MOVED IN FRONT OF US FROM R TO L. WE IMMEDIATELY STOPPED THE TURN AND DEVIATED TO THE R. THE CONFLICTED ACFT APPEARED TO BE AT THE SAME ALT AND ENTERING A L DOWNWIND TO RWY 9. WHEN WE CONTACTED DEP, WE WERE TOLD TO WATCH FOR TFC AT 2500 FT MSL AT 2 O'CLOCK POS. HOWEVER, BY THAT TIME THE ACFT WAS PAST US TO THE L (THE W). WE SUBSEQUENTLY ASKED CTLR ABOUT THE CONFLICT. HE REPLIED THAT THE ACFT HAD BEEN HANDED OVER TO RYY TWR AND THAT HE WAS NOT IN CONTACT WITH THE ACFT. THIS NEAR MISS APPARENTLY OCCURRED AS CTL FOR BOTH ACFT WAS BEING PASSED FROM APCH TO TWR AND TWR TO DEP. THE BUSY TFC ENVIRONMENT AT RYY AND OUR DELAY ON THE GND WERE CONTRIBUTING FACTORS SINCE THEY MAY HAVE CAUSED BOTH ACFT TO BE OUT-OF-SEQUENCE FROM WHAT WAS PLANNED BY ATC.

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.