A flight crew cleared for the eca.ECA2 arrival to oak; but entered the eca.madns in FMC before recei...

Attributes
ACN	981435
Time
Date	201111
Local Time Of Day	0601-1200
Place
Locale Reference	SFO.Airport
State Reference	CA
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	Large Transport Low Wing 2 Turbojet Eng
Operating Under FAR Part	Part 121
Flight Phase	Descent
Route In Use	STAR ECA.ECA2
Flight Plan	IFR
Component
Aircraft Component	FMS/FMC
Person 1
Function	First Officer Pilot Not Flying
Experience	Flight Crew Last 90 Days 164 Flight Crew Type 5300
Person 2
Function	Pilot Flying Captain
Qualification	Flight Crew Air Transport Pilot (ATP)
Events
Anomaly	Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types

Narrative:

Captain entered route in the FMC prior to receiving the release and the clearance. He entered the standard route for this flight; but the flight was cleared via a non-standard route; which was as the release showed. Entry error was eca.MADN5 instead of eca.ECA2. First officer confirmed that clearance matched the release; but failed to catch FMC STAR entry error. This resulted in a wrong turn at common fix along the route; which was noticed and corrected by ATC. Additionally; captain briefed the STAR as it was entered in the FMC; so no discrepancy was noticed during the arrival briefing. Basically; just do what I thought that I always did (at least prior to this event); which is to verify route 2 matches the release and that they both match the clearance; and to resolve any discrepancies regardless of who entered what; when; and how into the FMC. Personally; I feel that any 'additional help' by the captain with regard to preflight duties tends to disrupt my normal flow and often creates more workload rather than less.

Original NASA ASRS Text

Title: A flight crew cleared for the ECA.ECA2 arrival to OAK; but entered the ECA.MADNS in FMC before receiving the PDC clearance. Neither pilot checked the routing; so a track error occurred after the common leg.

Narrative: Captain entered route in the FMC prior to receiving the release and the clearance. He entered the standard route for this flight; but the flight was cleared via a non-standard route; which was as the release showed. Entry error was ECA.MADN5 instead of ECA.ECA2. First Officer confirmed that clearance matched the release; but failed to catch FMC STAR entry error. This resulted in a wrong turn at common fix along the route; which was noticed and corrected by ATC. Additionally; Captain briefed the STAR as it was entered in the FMC; so no discrepancy was noticed during the arrival briefing. Basically; just do what I thought that I always did (at least prior to this event); which is to verify RTE 2 matches the release and that they both match the clearance; and to resolve any discrepancies regardless of who entered what; when; and how into the FMC. Personally; I feel that any 'additional help' by the Captain with regard to preflight duties tends to disrupt my normal flow and often creates more workload rather than less.

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

A flight crew cleared for the eca.ECA2 arrival to oak; but entered the eca.madns in FMC before receiving the pre departure clearance clearance. Neither pilot checked the routing; so a track error occurred after the common leg.