<< >> NASA ASRS Report 546846, May 2002

A319 crew had a TCASII RA when they followed the controller clearance and did not intercept the localizer.

Attributes
ACN	546846
Time
Date	200205
Day	Fri
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : phx.airport
State Reference	AZ
Altitude	msl single value : 4000
Environment
Flight Conditions	VMC
Light	Dusk
Aircraft 1
Controlling Facilities	tracon : p50.tracon tower : dtw.tower
Operator	common carrier : air carrier
Make Model Name	A319
Operating Under FAR Part	Part 121
Navigation In Use	other
Flight Phase	descent : approach
Route In Use	arrival : on vectors
Flight Plan	IFR
Aircraft 2
Controlling Facilities	tracon : p50.tracon
Make Model Name	Twin Beech 18
Operating Under FAR Part	Part 91
Flight Phase	descent : approach
Route In Use	arrival : on vectors
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp
Experience	flight time last 90 days : 200 flight time total : 6000 flight time type : 800
ASRS Report	546846
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Events
Anomaly	conflict : airborne critical non adherence : published procedure non adherence : required legal separation
Independent Detector	aircraft equipment : tcas other flight crewa other flight crewb
Resolutory Action	controller : issued advisory flight crew : took evasive action other
Miss Distance	horizontal : 1000
Supplementary
Problem Areas	Environmental Factor ATC Human Performance Flight Crew Human Performance
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Error

Narrative:

Landing in phx on runway 26. We were assigned a heading of 220 degrees. WX was VFR, but landing to the west, into the sun with hazy conditions. ATC told us to look for a twin beech at our 2 O'clock position, that was crossing the localizer. An rj was on the visual to runway 25R. As we approached the localizer, the frequency was congested. We were never cleared to intercept the localizer for runway 26, just assigned the intercept heading. We passed through the localizer. TCASII gave us a resolution command to descend. We followed the TCASII command and broke to the right to avoid the beech. ATC asked why we did not intercept the localizer. Our response was we simply were assigned a heading of 220 degrees but never cleared to intercept the localizer. Had we inquired with ATC about the heading, this could have been avoided.

Related reports:

• Air carrier flight crew annoyed ATCT ground controller when ...
• An air carrier SF340 flight crew noted that there was a new ...
• Flight crew followed clearance into position and hold. Secon...
• Air carrier flight crew states that ATC clearance for FL290 ...

	Enter your search terms Submit search form
	Web www.37000feet.com

Original NASA ASRS Text

Title: A319 CREW HAD A TCASII RA WHEN THEY FOLLOWED THE CTLR CLRNC AND DID NOT INTERCEPT THE LOC.

Narrative: LNDG IN PHX ON RWY 26. WE WERE ASSIGNED A HDG OF 220 DEGS. WX WAS VFR, BUT LNDG TO THE W, INTO THE SUN WITH HAZY CONDITIONS. ATC TOLD US TO LOOK FOR A TWIN BEECH AT OUR 2 O'CLOCK POS, THAT WAS XING THE LOC. AN RJ WAS ON THE VISUAL TO RWY 25R. AS WE APCHED THE LOC, THE FREQ WAS CONGESTED. WE WERE NEVER CLRED TO INTERCEPT THE LOC FOR RWY 26, JUST ASSIGNED THE INTERCEPT HDG. WE PASSED THROUGH THE LOC. TCASII GAVE US A RESOLUTION COMMAND TO DSND. WE FOLLOWED THE TCASII COMMAND AND BROKE TO THE R TO AVOID THE BEECH. ATC ASKED WHY WE DID NOT INTERCEPT THE LOC. OUR RESPONSE WAS WE SIMPLY WERE ASSIGNED A HDG OF 220 DEGS BUT NEVER CLRED TO INTERCEPT THE LOC. HAD WE INQUIRED WITH ATC ABOUT THE HDG, THIS COULD HAVE BEEN AVOIDED.

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.