A B737-400 flight crew flies the wrong STAR into anc after a rushed departure from odk, ak.

Attributes
ACN	487340
Time
Date	200010
Day	Mon
Local Time Of Day	1201 To 1800
Place
Locale Reference	navaid : odk.vortac
State Reference	AK
Altitude	msl single value : 35000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zan.artcc
Operator	common carrier : air carrier
Make Model Name	B737-400
Operating Under FAR Part	Part 121
Navigation In Use	other other vortac
Flight Phase	cruise : level
Route In Use	arrival star : ammot
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp
Experience	flight time last 90 days : 180 flight time total : 3800 flight time type : 1500
ASRS Report	487340
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 180 flight time total : 12000 flight time type : 1500
ASRS Report	487133
Events
Anomaly	aircraft equipment problem : less severe non adherence : clearance non adherence : published procedure other anomaly other other spatial deviation
Independent Detector	other controllera
Resolutory Action	controller : issued advisory controller : issued new clearance flight crew : returned to original clearance
Supplementary
Problem Areas	Aircraft Environmental Factor Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

Captain loaded FMC for flight from kodiak to anchorage, ak. He did so, pulling up a stored routing. I double-checked the routing with the flight plan and failed to notice the arrival (AMOTT5) was not loaded. Upon receiving our clearance, we were given a SID leaving kodiak. I noticed this was not loaded either, and corrected the FMC, but still did not notice the lack of a 'STAR.' en route, center queried our route of flight, and gave us a 30 degree correction. Contributing factors: 1) I had been slow to catch a right FMC 'soft' failure on the previous leg. Because we didn't have time to fix it on the ground, it was MEL'ed. This took away the 'rnp to J6,' the ideal approach getting into kodiak. As a result, the captain flew the ILS runway 25, with a tailwind, to minimums. I was still preoccupied with that during my preflight. 2) 'lip service.' I looked at the route, had the flight plan in my hand, but didn't see the discrepancy. Just because it is usually right, doesn't mean it is. Supplemental information from acn 487133: neither crew caught the FMC route differed from filed route. Recent change in anc airspace changed filed route from FMC route which crew was used to. Rushed inbound high workload contributed to rushed environment on ground odk. Familiarity with route from previous flts and rushed environment resulted in both crew missing flight plan discrepancy.

Original NASA ASRS Text

Title: A B737-400 FLC FLIES THE WRONG STAR INTO ANC AFTER A RUSHED DEP FROM ODK, AK.

Narrative: CAPT LOADED FMC FOR FLT FROM KODIAK TO ANCHORAGE, AK. HE DID SO, PULLING UP A STORED ROUTING. I DOUBLE-CHKED THE ROUTING WITH THE FLT PLAN AND FAILED TO NOTICE THE ARR (AMOTT5) WAS NOT LOADED. UPON RECEIVING OUR CLRNC, WE WERE GIVEN A SID LEAVING KODIAK. I NOTICED THIS WAS NOT LOADED EITHER, AND CORRECTED THE FMC, BUT STILL DID NOT NOTICE THE LACK OF A 'STAR.' ENRTE, CTR QUERIED OUR RTE OF FLT, AND GAVE US A 30 DEG CORRECTION. CONTRIBUTING FACTORS: 1) I HAD BEEN SLOW TO CATCH A RIGHT FMC 'SOFT' FAILURE ON THE PREVIOUS LEG. BECAUSE WE DIDN'T HAVE TIME TO FIX IT ON THE GND, IT WAS MEL'ED. THIS TOOK AWAY THE 'RNP TO J6,' THE IDEAL APCH GETTING INTO KODIAK. AS A RESULT, THE CAPT FLEW THE ILS RWY 25, WITH A TAILWIND, TO MINIMUMS. I WAS STILL PREOCCUPIED WITH THAT DURING MY PREFLT. 2) 'LIP SVC.' I LOOKED AT THE RTE, HAD THE FLT PLAN IN MY HAND, BUT DIDN'T SEE THE DISCREPANCY. JUST BECAUSE IT IS USUALLY RIGHT, DOESN'T MEAN IT IS. SUPPLEMENTAL INFO FROM ACN 487133: NEITHER CREW CAUGHT THE FMC RTE DIFFERED FROM FILED RTE. RECENT CHANGE IN ANC AIRSPACE CHANGED FILED RTE FROM FMC RTE WHICH CREW WAS USED TO. RUSHED INBOUND HIGH WORKLOAD CONTRIBUTED TO RUSHED ENVIRONMENT ON GND ODK. FAMILIARITY WITH RTE FROM PREVIOUS FLTS AND RUSHED ENVIRONMENT RESULTED IN BOTH CREW MISSING FLT PLAN DISCREPANCY.

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.