Amended route was not entered in FMC causing the aircraft to fly the wrong route.

Attributes
ACN	218760
Time
Date	199208
Day	Thu
Local Time Of Day	0601 To 1200
Place
Locale Reference	atc facility : ewc
State Reference	PA
Altitude	msl bound lower : 18000 msl bound upper : 28000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zob
Operator	common carrier : air carrier
Make Model Name	Medium Large Transport, Low Wing, 2 Turbojet Eng
Navigation In Use	Other
Flight Phase	climbout : intermediate altitude cruise other
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : cfi pilot : atp
Experience	flight time last 90 days : 120 flight time total : 11000 flight time type : 300
ASRS Report	218760
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : flight engineer pilot : atp
Experience	flight time last 90 days : 150 flight time total : 13500 flight time type : 750
ASRS Report	220373
Events
Anomaly	non adherence : clearance non adherence other other spatial deviation
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance other
Consequence	faa : reviewed incident with flight crew
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

Flight, pit direct hpn, departed pit and soon received several vectors and altitude assignments. Requested direct to ewc; additional vectors were received and executed. Soon after crossing ewc VOR controller questions our routing. After verifying route from dispatch release, pre departure clearance ACARS message and actual flight path, a small correction was taken to fly appropriate routing. A short discussion with controller ensued explaining that this aircraft has a possibility of having several flight routing available; release, ACARS, fmcs. The controller also pointed out the departure routing out of pit was on a test basis and slightly differed from the previous standard departure to the north and east. We were soon cleared direct to dny VOR and the flight completed without incident. Obviously there exists a weak area in the fmcs and ACARS pdu data banks. Cross-talk should be able to prevent erroneous flight plans from being activated when discrepancies exist and an appropriate warning present to pilot and/or pre departure clearance monitors. Also fmcs data bank changes should be much more timely.

Original NASA ASRS Text

Title: AMENDED RTE WAS NOT ENTERED IN FMC CAUSING THE ACFT TO FLY THE WRONG RTE.

Narrative: FLT, PIT DIRECT HPN, DEPARTED PIT AND SOON RECEIVED SEVERAL VECTORS AND ALT ASSIGNMENTS. REQUESTED DIRECT TO EWC; ADDITIONAL VECTORS WERE RECEIVED AND EXECUTED. SOON AFTER XING EWC VOR CTLR QUESTIONS OUR ROUTING. AFTER VERIFYING RTE FROM DISPATCH RELEASE, PDC ACARS MESSAGE AND ACTUAL FLT PATH, A SMALL CORRECTION WAS TAKEN TO FLY APPROPRIATE ROUTING. A SHORT DISCUSSION WITH CTLR ENSUED EXPLAINING THAT THIS ACFT HAS A POSSIBILITY OF HAVING SEVERAL FLT ROUTING AVAILABLE; RELEASE, ACARS, FMCS. THE CTLR ALSO POINTED OUT THE DEP ROUTING OUT OF PIT WAS ON A TEST BASIS AND SLIGHTLY DIFFERED FROM THE PREVIOUS STANDARD DEP TO THE N AND E. WE WERE SOON CLRED DIRECT TO DNY VOR AND THE FLT COMPLETED WITHOUT INCIDENT. OBVIOUSLY THERE EXISTS A WEAK AREA IN THE FMCS AND ACARS PDU DATA BANKS. CROSS-TALK SHOULD BE ABLE TO PREVENT ERRONEOUS FLT PLANS FROM BEING ACTIVATED WHEN DISCREPANCIES EXIST AND AN APPROPRIATE WARNING PRESENT TO PLT AND/OR PDC MONITORS. ALSO FMCS DATA BANK CHANGES SHOULD BE MUCH MORE TIMELY.

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.