Potential conflict in a same runway assignment departure procedure.

Attributes
ACN	272043
Time
Date	199405
Day	Tue
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : cre
State Reference	SC
Altitude	agl bound lower : 0 agl bound upper : 400
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tower : cre
Operator	general aviation : personal
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Operating Under FAR Part	Part 91
Flight Phase	climbout : initial climbout : takeoff cruise other
Route In Use	enroute : on vectors
Flight Plan	IFR
Aircraft 2
Operator	general aviation : personal
Make Model Name	J3 Cub
Operating Under FAR Part	Part 91
Flight Phase	climbout : initial cruise other other
Flight Plan	None
Person 1
Affiliation	Other
Function	flight crew : single pilot
Qualification	pilot : atp
Experience	flight time last 90 days : 120 flight time total : 11900 flight time type : 200
ASRS Report	272043
Person 2
Affiliation	Other
Function	flight crew : single pilot
Events
Anomaly	conflict : airborne less severe non adherence : published procedure other anomaly other
Independent Detector	other controllera other flight crewa
Resolutory Action	controller : issued new clearance other
Consequence	Other
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Error

Narrative:

Crf tower had us holding for IFR release. The tower was busy, 3 aircraft were on final or base. Tower gave us a (cleared for immediate takeoff, fly heading 32 degrees). We were departing runway 5. After lift off I started my climb and started my turn to the assigned 320 degree heading. I then noticed a piper cub turning left crosswind in front of us (apparently he had been cleared for an intersection takeoff downfield of us on runway 5). The tower saw the conflict and gave him a heading to fly. I feel that the tower should have held us longer for takeoff to give better separation, or they should have given us taxiway heading until clear of the traffic. Also, a contributing factor was -- I was watching traffic on final, and was not aware that the other takeoff traffic was remaining in the pattern.

Original NASA ASRS Text

Title: POTENTIAL CONFLICT IN A SAME RWY ASSIGNMENT DEP PROC.

Narrative: CRF TWR HAD US HOLDING FOR IFR RELEASE. THE TWR WAS BUSY, 3 ACFT WERE ON FINAL OR BASE. TWR GAVE US A (CLRED FOR IMMEDIATE TKOF, FLY HDG 32 DEGS). WE WERE DEPARTING RWY 5. AFTER LIFT OFF I STARTED MY CLB AND STARTED MY TURN TO THE ASSIGNED 320 DEG HDG. I THEN NOTICED A PIPER CUB TURNING L XWIND IN FRONT OF US (APPARENTLY HE HAD BEEN CLRED FOR AN INTXN TKOF DOWNFIELD OF US ON RWY 5). THE TWR SAW THE CONFLICT AND GAVE HIM A HDG TO FLY. I FEEL THAT THE TWR SHOULD HAVE HELD US LONGER FOR TKOF TO GIVE BETTER SEPARATION, OR THEY SHOULD HAVE GIVEN US TXWY HDG UNTIL CLR OF THE TFC. ALSO, A CONTRIBUTING FACTOR WAS -- I WAS WATCHING TFC ON FINAL, AND WAS NOT AWARE THAT THE OTHER TKOF TFC WAS REMAINING IN THE PATTERN.

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.