PF has erroneous ILS information displayed. Flew through the localizer until noticed by both controller and PNF who called for correction to be made.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	476192
Time
Date	200006
Day	Fri
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : lax.airport
State Reference	CA
Altitude	msl single value : 2200
Environment
Flight Conditions	IMC
Light	Night
Aircraft 1
Controlling Facilities	tracon : sct.tracon
Operator	common carrier : air carrier
Make Model Name	B737-300
Operating Under FAR Part	Part 121
Navigation In Use	ils localizer & glide slope : 24r other
Flight Phase	descent : approach
Route In Use	arrival : on vectors
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp pilot : commercial pilot : multi engine
Experience	flight time last 90 days : 220 flight time total : 22000 flight time type : 4700
ASRS Report	476192
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Events
Anomaly	aircraft equipment problem : less severe non adherence : clearance other anomaly other other spatial deviation
Independent Detector	other controllerb other flight crewa
Resolutory Action	controller : issued new clearance flight crew : returned to intended or assigned course other
Supplementary
Problem Areas	Flight Crew Human Performance Navigational Facility Aircraft
Primary Problem	Aircraft
Air Traffic Incident	Pilot Deviation

Narrative:

Radar vector for ILS runway 24R off sadde 6 arrival, 210 degree heading intercept ILS runway 24R. Captain said 'I'll never intercept on this heading.' I showed it as a good intercept. My localizer started to come alive and I said so. Approach controller then gave us traffic on the south complex 1000 ft above us (we were IMC) and then noticed the captain hadn't started to turn and we flew through the localizer. Approach told us to turn right and reintercept the localizer. Captain started a slow turn. I looked at his CDI and it had not moved. (I don't know why, he had the correct frequency in and I had idented it on approach.) I then took the aircraft because I was receiving the correct information. We got back on the localizer and the captain took the aircraft back (he then had correct guidance and we were VMC). One good thing out of this was our airline's CRM training. He let me 'have the aircraft' without question knowing that I must have had the correct information displayed to me.

Original NASA ASRS Text

Title: PF HAS ERRONEOUS ILS INFO DISPLAYED. FLEW THROUGH THE LOC UNTIL NOTICED BY BOTH CTLR AND PNF WHO CALLED FOR CORRECTION TO BE MADE.

Narrative: RADAR VECTOR FOR ILS RWY 24R OFF SADDE 6 ARR, 210 DEG HDG INTERCEPT ILS RWY 24R. CAPT SAID 'I'LL NEVER INTERCEPT ON THIS HDG.' I SHOWED IT AS A GOOD INTERCEPT. MY LOC STARTED TO COME ALIVE AND I SAID SO. APCH CTLR THEN GAVE US TFC ON THE S COMPLEX 1000 FT ABOVE US (WE WERE IMC) AND THEN NOTICED THE CAPT HADN'T STARTED TO TURN AND WE FLEW THROUGH THE LOC. APCH TOLD US TO TURN R AND REINTERCEPT THE LOC. CAPT STARTED A SLOW TURN. I LOOKED AT HIS CDI AND IT HAD NOT MOVED. (I DON'T KNOW WHY, HE HAD THE CORRECT FREQ IN AND I HAD IDENTED IT ON APCH.) I THEN TOOK THE ACFT BECAUSE I WAS RECEIVING THE CORRECT INFO. WE GOT BACK ON THE LOC AND THE CAPT TOOK THE ACFT BACK (HE THEN HAD CORRECT GUIDANCE AND WE WERE VMC). ONE GOOD THING OUT OF THIS WAS OUR AIRLINE'S CRM TRAINING. HE LET ME 'HAVE THE ACFT' WITHOUT QUESTION KNOWING THAT I MUST HAVE HAD THE CORRECT INFO DISPLAYED TO ME.

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.