Less than standard separation in the phx departure corridor.

Attributes
ACN	278690
Time
Date	199408
Day	Tue
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : phx
State Reference	AZ
Altitude	msl bound lower : 2000 msl bound upper : 2000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tower : phx
Operator	common carrier : air carrier
Make Model Name	B727 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	climbout : initial climbout : takeoff
Route In Use	departure other
Flight Plan	IFR
Aircraft 2
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Operating Under FAR Part	Part 91
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 150 flight time total : 15000 flight time type : 1500
ASRS Report	278690
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : instrument pilot : commercial
Events
Anomaly	conflict : airborne less severe non adherence : far
Independent Detector	aircraft equipment other aircraft equipment : unspecified other controllera other flight crewa
Resolutory Action	flight crew : took evasive action
Consequence	faa : reviewed incident with flight crew
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Error

Narrative:

Phx tower cleared us for takeoff from runway 26R and did not issue any TA to us. At approximately 2000 ft MSL, TCASII called 'traffic, traffic' and a target appeared at plus 100 ft. We were still in the noise abatement profile at 15-16 degrees nose up and retracting flaps. TCASII then called 'monitor vertical speed' and a red arc appeared on the vsi. I pushed the power up and pulled for the top of the red arc when TCASII called 'climb, climb' and a green fly-to arc appeared. I pulled up into the green arc. A second or two later TCASII called 'clear of conflict.' at this point tower told us to change to departure control. Departure asked if tower had advised us of the light airplane traffic. Tower did not advise us and was very slow in switching us to departure control. The departure controller was aware of the light airplane and was quite concerned by what he was seeing on his radar. ATC apparently had an internal communications breakdown about the light airplane's position and did not relay its position to us. What was a light airplane doing at 1000-1500 ft AGL on the centerline of a departure runway used by air carrier turbojets anyway?

Original NASA ASRS Text

Title: LTSS IN THE PHX DEP CORRIDOR.

Narrative: PHX TWR CLRED US FOR TKOF FROM RWY 26R AND DID NOT ISSUE ANY TA TO US. AT APPROX 2000 FT MSL, TCASII CALLED 'TFC, TFC' AND A TARGET APPEARED AT PLUS 100 FT. WE WERE STILL IN THE NOISE ABATEMENT PROFILE AT 15-16 DEGS NOSE UP AND RETRACTING FLAPS. TCASII THEN CALLED 'MONITOR VERT SPD' AND A RED ARC APPEARED ON THE VSI. I PUSHED THE PWR UP AND PULLED FOR THE TOP OF THE RED ARC WHEN TCASII CALLED 'CLB, CLB' AND A GREEN FLY-TO ARC APPEARED. I PULLED UP INTO THE GREEN ARC. A SECOND OR TWO LATER TCASII CALLED 'CLR OF CONFLICT.' AT THIS POINT TWR TOLD US TO CHANGE TO DEP CTL. DEP ASKED IF TWR HAD ADVISED US OF THE LIGHT AIRPLANE TFC. TWR DID NOT ADVISE US AND WAS VERY SLOW IN SWITCHING US TO DEP CTL. THE DEP CTLR WAS AWARE OF THE LIGHT AIRPLANE AND WAS QUITE CONCERNED BY WHAT HE WAS SEEING ON HIS RADAR. ATC APPARENTLY HAD AN INTERNAL COMS BREAKDOWN ABOUT THE LIGHT AIRPLANE'S POS AND DID NOT RELAY ITS POS TO US. WHAT WAS A LIGHT AIRPLANE DOING AT 1000-1500 FT AGL ON THE CTRLINE OF A DEP RWY USED BY ACR TURBOJETS ANYWAY?

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.