An air carrier frtr flew the wrong SID after programming the right SID.

Attributes
ACN	267309
Time
Date	199403
Day	Fri
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : pom airport : ont
State Reference	CA
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	B757 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Navigation In Use	Other Other
Flight Phase	climbout : intermediate altitude ground : preflight
Route In Use	departure other departure sid : sid enroute airway : zny
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp pilot : flight engineer
Experience	flight time total : 7000
ASRS Report	267309
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : commercial pilot : instrument
Events
Anomaly	non adherence : clearance non adherence : published procedure other anomaly other other spatial deviation
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance flight crew : overcame equipment problem other
Consequence	faa : reviewed incident with flight crew
Supplementary
Primary Problem	Aircraft
Air Traffic Incident	other

Narrative:

In preparation for departing ont, FMC's loaded with assigned route, using the pom 6 departure. Routing verified on route page, waypoints verified with crossing restrs on legs page, and confirmed on HSI plan view. First officer double checked route, activated and executed. Prior to departure, takeoff runway changed in FMC from 26R to 26L. Takeoff completed and turned northwest over pom VOR meeting crossing restr on pom 6 departure. A short time later, we noticed the waypoints displayed on the HSI map and legs page did not match the pom 6 departure and at approximately the same time ZLA asked which departure we were using. The route page or the FMC still showed the pom 6 departure. However the legs page had defaulted to the waypoints of the ont 2 departure. ATC vectored us the west to rejoin the pom 6. Raw data was used to complete the departure procedure. En route the flight plan routing was entered into route Z in an attempt to troubleshoot the problem. Several times the same anomaly showed up, pom 6 showing on the route page, but the waypoints of the ont 2 SID showing on the legs page.

Original NASA ASRS Text

Title: AN ACR FRTR FLEW THE WRONG SID AFTER PROGRAMMING THE RIGHT SID.

Narrative: IN PREPARATION FOR DEPARTING ONT, FMC'S LOADED WITH ASSIGNED RTE, USING THE POM 6 DEP. ROUTING VERIFIED ON RTE PAGE, WAYPOINTS VERIFIED WITH XING RESTRS ON LEGS PAGE, AND CONFIRMED ON HSI PLAN VIEW. FO DOUBLE CHKED RTE, ACTIVATED AND EXECUTED. PRIOR TO DEP, TKOF RWY CHANGED IN FMC FROM 26R TO 26L. TKOF COMPLETED AND TURNED NW OVER POM VOR MEETING XING RESTR ON POM 6 DEP. A SHORT TIME LATER, WE NOTICED THE WAYPOINTS DISPLAYED ON THE HSI MAP AND LEGS PAGE DID NOT MATCH THE POM 6 DEP AND AT APPROX THE SAME TIME ZLA ASKED WHICH DEP WE WERE USING. THE RTE PAGE OR THE FMC STILL SHOWED THE POM 6 DEP. HOWEVER THE LEGS PAGE HAD DEFAULTED TO THE WAYPOINTS OF THE ONT 2 DEP. ATC VECTORED US THE W TO REJOIN THE POM 6. RAW DATA WAS USED TO COMPLETE THE DEP PROC. ENRTE THE FLT PLAN ROUTING WAS ENTERED INTO RTE Z IN AN ATTEMPT TO TROUBLESHOOT THE PROB. SEVERAL TIMES THE SAME ANOMALY SHOWED UP, POM 6 SHOWING ON THE RTE PAGE, BUT THE WAYPOINTS OF THE ONT 2 SID SHOWING ON THE LEGS PAGE.

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.