SA227 crew and an air carrier B737 had less than legal separation on approach in phx class B.

Attributes
ACN	575671
Time
Date	200303
Day	Thu
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : phx.airport
State Reference	AZ
Altitude	msl single value : 4100
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Controlling Facilities	tower : phx.tower
Operator	common carrier : air carrier
Make Model Name	SA-227 AC Metro III
Operating Under FAR Part	Part 135
Flight Phase	descent : approach
Route In Use	approach : visual
Flight Plan	IFR
Aircraft 2
Controlling Facilities	tower : phx.tower
Operator	common carrier : air carrier
Make Model Name	B737 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	descent : approach
Route In Use	approach : visual
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : single pilot
Qualification	pilot : atp
Experience	flight time last 90 days : 250 flight time total : 7000 flight time type : 1600
ASRS Report	575671
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Events
Anomaly	conflict : airborne critical non adherence : clearance non adherence : far non adherence : required legal separation other anomaly other
Independent Detector	aircraft equipment : tcas other flight crewa other flight crewb
Resolutory Action	controller : issued advisory flight crew : took evasive action
Consequence	faa : reviewed incident with flight crew
Miss Distance	horizontal : 1300 vertical : 0
Supplementary
Problem Areas	ATC Human Performance FAA Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation Inter Facility Coordination Failure

Narrative:

On a visual approach to runway 25L at phx, at approximately 7 mi DME, I was alerted by tower of traffic at my 9 O'clock position, same altitude -- controller was unsure of the other aircraft's intentions as B737 was talking to north tower on a different frequency. B737 was advised of my location and reported me in sight. They were advised to maintain visual separation, and were cleared for a visual approach to runway 26. The flight headed on a collision course for me until receiving a TCASII alert. After I was advised of their location, I felt we were too close and I started to climb. Then the 737 started to turn and climb, I then descended and landed. The 737 went overhead and was re-sequenced for runway 26. After talking with TRACON, they said they expected the B737 to cross above and behind me, then turn for runway 26 -- he instead went directly toward runway 26.

Original NASA ASRS Text

Title: SA227 CREW AND AN ACR B737 HAD LESS THAN LEGAL SEPARATION ON APCH IN PHX CLASS B.

Narrative: ON A VISUAL APCH TO RWY 25L AT PHX, AT APPROX 7 MI DME, I WAS ALERTED BY TWR OF TFC AT MY 9 O'CLOCK POS, SAME ALT -- CTLR WAS UNSURE OF THE OTHER ACFT'S INTENTIONS AS B737 WAS TALKING TO N TWR ON A DIFFERENT FREQ. B737 WAS ADVISED OF MY LOCATION AND RPTED ME IN SIGHT. THEY WERE ADVISED TO MAINTAIN VISUAL SEPARATION, AND WERE CLRED FOR A VISUAL APCH TO RWY 26. THE FLT HEADED ON A COLLISION COURSE FOR ME UNTIL RECEIVING A TCASII ALERT. AFTER I WAS ADVISED OF THEIR LOCATION, I FELT WE WERE TOO CLOSE AND I STARTED TO CLB. THEN THE 737 STARTED TO TURN AND CLB, I THEN DSNDED AND LANDED. THE 737 WENT OVERHEAD AND WAS RE-SEQUENCED FOR RWY 26. AFTER TALKING WITH TRACON, THEY SAID THEY EXPECTED THE B737 TO CROSS ABOVE AND BEHIND ME, THEN TURN FOR RWY 26 -- HE INSTEAD WENT DIRECTLY TOWARD RWY 26.

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.