B737 landing lax during opposite direction operations experienced TCAS RA and executes go around.

Attributes
ACN	631252
Time
Date	200409
Day	Sat
Local Time Of Day	0001 To 0600
Place
Locale Reference	airport : lax.airport
State Reference	CA
Altitude	msl single value : 2000
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Controlling Facilities	tower : lax.tower
Operator	common carrier : air carrier
Make Model Name	B737-800
Operating Under FAR Part	Part 121
Navigation In Use	ils localizer & glide slope : 6r
Flight Phase	descent : approach descent : intermediate altitude
Route In Use	approach : instrument precision
Flight Plan	IFR
Aircraft 2
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Flight Phase	climbout : takeoff
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
ASRS Report	631252
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Events
Anomaly	conflict : airborne less severe
Independent Detector	aircraft equipment : tcas other flight crewa
Resolutory Action	flight crew : took evasive action flight crew : executed go around
Supplementary
Problem Areas	ATC Human Performance Airport
Primary Problem	ATC Human Performance

Narrative:

While conducting an ILS approach to runway 6R lax, our aircraft was level at 2000 ft, heading 090 degrees to intercept final course, cleared approach with approximately 10 mi final, scattered to broken cloud layer at 1300 ft and runway not in sight. We lost our flight director inputs (cause unknown) with heading selected and VOR/localizer armed. While the first officer attempted to correct the problem we received a TCAS TA. Both pilots heads up looking for traffic which appeared from below cloud deck at approximately the 1-2 O'clock position. Tower then issued TA concurrently with TCAS RA alert. Tower then advised traffic had us in sight and would maintain visual separation. We complied with RA alert. Due to conflicting flight director and VOR/localizer information, while complying with RA alert, aircraft was never established on a stable approach, therefore, I elected to go around. It is important to note with utmost concern that we were never advised of traffic departing in the opposite direction at the field. It is my opinion, with the existing WX conditions, this procedure should not be used. It is an accident waiting to happen.

Original NASA ASRS Text

Title: B737 LNDG LAX DURING OPPOSITE DIRECTION OPS EXPERIENCED TCAS RA AND EXECUTES GAR.

Narrative: WHILE CONDUCTING AN ILS APCH TO RWY 6R LAX, OUR ACFT WAS LEVEL AT 2000 FT, HDG 090 DEGS TO INTERCEPT FINAL COURSE, CLRED APCH WITH APPROX 10 MI FINAL, SCATTERED TO BROKEN CLOUD LAYER AT 1300 FT AND RWY NOT IN SIGHT. WE LOST OUR FLT DIRECTOR INPUTS (CAUSE UNKNOWN) WITH HDG SELECTED AND VOR/LOC ARMED. WHILE THE FO ATTEMPTED TO CORRECT THE PROB WE RECEIVED A TCAS TA. BOTH PLTS HEADS UP LOOKING FOR TFC WHICH APPEARED FROM BELOW CLOUD DECK AT APPROX THE 1-2 O'CLOCK POS. TWR THEN ISSUED TA CONCURRENTLY WITH TCAS RA ALERT. TWR THEN ADVISED TFC HAD US IN SIGHT AND WOULD MAINTAIN VISUAL SEPARATION. WE COMPLIED WITH RA ALERT. DUE TO CONFLICTING FLT DIRECTOR AND VOR/LOC INFO, WHILE COMPLYING WITH RA ALERT, ACFT WAS NEVER ESTABLISHED ON A STABLE APCH, THEREFORE, I ELECTED TO GO AROUND. IT IS IMPORTANT TO NOTE WITH UTMOST CONCERN THAT WE WERE NEVER ADVISED OF TFC DEPARTING IN THE OPPOSITE DIRECTION AT THE FIELD. IT IS MY OPINION, WITH THE EXISTING WX CONDITIONS, THIS PROC SHOULD NOT BE USED. IT IS AN ACCIDENT WAITING TO HAPPEN.

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.