B757 fails to follow programmed FMS route on canuk RNAV STAR to atl.

Attributes
ACN	801183
Time
Date	200808
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : atl.airport
State Reference	GA
Altitude	msl single value : 11000
Environment
Flight Conditions	Mixed
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : a80.tracon
Operator	common carrier : air carrier
Make Model Name	B757 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	descent : approach ground : parked
Route In Use	arrival star : canuk
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : multi engine pilot : atp pilot : commercial pilot : flight engineer pilot : instrument
Experience	flight time last 90 days : 100 flight time total : 6400 flight time type : 1500
ASRS Report	801183
Person 2
Affiliation	government : faa
Function	controller : approach
Events
Anomaly	non adherence : published procedure non adherence : clearance other spatial deviation
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance controller : issued advisory
Supplementary
Problem Areas	Aircraft Flight Crew Human Performance
Primary Problem	Aircraft
Air Traffic Incident	Pilot Deviation

Narrative:

On the canuk arrival to atl. LNAV linked to the autoplt. Approach changed our runway. I entered the new runway into the FMS and noted that we were still on the arrival and the ADI indicator we were flying toward the active waypoint (rippi). At rippi; the aircraft continued to fly straight ahead instead of turn and the FMC displayed 'flight plan discontinuity.' I switched to heading select and as I was deviating from the arrival; ATC called and gave me vectors. The database is new in our aircraft and is supposed to correct problems associated with runway changes. I have not received any training with this new database. Either the database does not make the correction; or I do not know how to use the equipment properly. Callback conversation with reporter revealed the following information: reporter advised the waypoint at which the anomaly occurred was bojaa vice rippi as stated in the narrative. Reporter emphasized that after the new runway was executed the magenta active route line had no discontinuity displayed; the autoflt system was in LNAV and bojaa was magenta; identifying it as the active waypoint. The SOP at this air carrier allows the PF (the reporter) to program the FMS when the aircraft is on autoplt and the PNF is responsible for verifying programming changes prior to execution. Reporter could not specifically vouch the verification was actually done since both pilots were busy during the terminal operation. Reporter was unaware of other instances of this anomaly.

Original NASA ASRS Text

Title: B757 FAILS TO FOLLOW PROGRAMMED FMS ROUTE ON CANUK RNAV STAR TO ATL.

Narrative: ON THE CANUK ARR TO ATL. LNAV LINKED TO THE AUTOPLT. APCH CHANGED OUR RWY. I ENTERED THE NEW RWY INTO THE FMS AND NOTED THAT WE WERE STILL ON THE ARR AND THE ADI INDICATOR WE WERE FLYING TOWARD THE ACTIVE WAYPOINT (RIPPI). AT RIPPI; THE ACFT CONTINUED TO FLY STRAIGHT AHEAD INSTEAD OF TURN AND THE FMC DISPLAYED 'FLT PLAN DISCONTINUITY.' I SWITCHED TO HDG SELECT AND AS I WAS DEVIATING FROM THE ARR; ATC CALLED AND GAVE ME VECTORS. THE DATABASE IS NEW IN OUR ACFT AND IS SUPPOSED TO CORRECT PROBS ASSOCIATED WITH RWY CHANGES. I HAVE NOT RECEIVED ANY TRAINING WITH THIS NEW DATABASE. EITHER THE DATABASE DOES NOT MAKE THE CORRECTION; OR I DO NOT KNOW HOW TO USE THE EQUIP PROPERLY. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: REPORTER ADVISED THE WAYPOINT AT WHICH THE ANOMALY OCCURRED WAS BOJAA VICE RIPPI AS STATED IN THE NARRATIVE. REPORTER EMPHASIZED THAT AFTER THE NEW RWY WAS EXECUTED THE MAGENTA ACTIVE ROUTE LINE HAD NO DISCONTINUITY DISPLAYED; THE AUTOFLT SYSTEM WAS IN LNAV AND BOJAA WAS MAGENTA; IDENTIFYING IT AS THE ACTIVE WAYPOINT. THE SOP AT THIS ACR ALLOWS THE PF (THE REPORTER) TO PROGRAM THE FMS WHEN THE ACFT IS ON AUTOPLT AND THE PNF IS RESPONSIBLE FOR VERIFYING PROGRAMMING CHANGES PRIOR TO EXECUTION. REPORTER COULD NOT SPECIFICALLY VOUCH THE VERIFICATION WAS ACTUALLY DONE SINCE BOTH PILOTS WERE BUSY DURING THE TERMINAL OPERATION. REPORTER WAS UNAWARE OF OTHER INSTANCES OF THIS ANOMALY.

Data retrieved from NASA's ASRS site as of May 2009 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.