B767 flight crew has a track heading deviations departure dfw.

Attributes
ACN	704457
Time
Date	200607
Local Time Of Day	0601 To 1200
Place
Locale Reference	intersection : firmn
State Reference	TX
Altitude	msl single value : 11000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : d10.tracon tower : dfw.tower tower : dfw.tower
Operator	common carrier : air carrier
Make Model Name	B767-300 and 300 ER
Operating Under FAR Part	Part 121
Navigation In Use	other
Flight Phase	climbout : intermediate altitude
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
ASRS Report	704457
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
ASRS Report	704605
Events
Anomaly	non adherence : clearance non adherence : published procedure other spatial deviation
Independent Detector	other controllera
Resolutory Action	controller : issued advisory flight crew : returned to intended or assigned course
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance

Narrative:

Originally scheduled from dfw to mci. After loading the FMS and preparing the cockpit for our flight; we were informed that we were being reassigned to fly to sfo with the same flight number. A new flight plan and tps were pulled up and the new route was loaded into the FMS. A new clearance was requested via ACARS. While we continued to set up for the new destination we discovered the paper was jammed in the ACARS printer. We rectified that problem then continued with a checklist but never requested another clearance. Startup; taxi-out and takeoff were uneventful. Our original clearance was to fly the bleco 2 departure while the new routing was to fly the slott 2 departure. The track on both departures are the same until you reach firmn. After that point; departure control asked us if we were on a vector. It was then that we realized our error and requested routing in the appropriate direction. It is the flight crew's responsibility to check the routing with the clearance and we failed at this.

Original NASA ASRS Text

Title: B767 FLT CREW HAS A TRACK HDG DEVS DEP DFW.

Narrative: ORIGINALLY SCHEDULED FROM DFW TO MCI. AFTER LOADING THE FMS AND PREPARING THE COCKPIT FOR OUR FLT; WE WERE INFORMED THAT WE WERE BEING REASSIGNED TO FLY TO SFO WITH THE SAME FLT NUMBER. A NEW FLT PLAN AND TPS WERE PULLED UP AND THE NEW RTE WAS LOADED INTO THE FMS. A NEW CLRNC WAS REQUESTED VIA ACARS. WHILE WE CONTINUED TO SET UP FOR THE NEW DEST WE DISCOVERED THE PAPER WAS JAMMED IN THE ACARS PRINTER. WE RECTIFIED THAT PROB THEN CONTINUED WITH A CHKLIST BUT NEVER REQUESTED ANOTHER CLRNC. STARTUP; TAXI-OUT AND TKOF WERE UNEVENTFUL. OUR ORIGINAL CLRNC WAS TO FLY THE BLECO 2 DEP WHILE THE NEW ROUTING WAS TO FLY THE SLOTT 2 DEP. THE TRACK ON BOTH DEPS ARE THE SAME UNTIL YOU REACH FIRMN. AFTER THAT POINT; DEP CTL ASKED US IF WE WERE ON A VECTOR. IT WAS THEN THAT WE REALIZED OUR ERROR AND REQUESTED ROUTING IN THE APPROPRIATE DIRECTION. IT IS THE FLT CREW'S RESPONSIBILITY TO CHK THE ROUTING WITH THE CLRNC AND WE FAILED AT THIS.

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