A300 departing dfw fails to program txk transition on triss RNAV SID.

Attributes
ACN	749816
Time
Date	200708
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : dfw.airport
State Reference	TX
Altitude	msl single value : 23000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zfw.artcc
Operator	common carrier : air carrier
Make Model Name	A300
Operating Under FAR Part	Part 121
Navigation In Use	other
Flight Phase	climbout : intermediate altitude
Route In Use	departure sid : triss
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Experience	flight time last 90 days : 65 flight time total : 5600 flight time type : 4000
ASRS Report	749816
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Experience	flight time last 90 days : 86 flight time total : 4500 flight time type : 700
ASRS Report	749815
Events
Anomaly	aircraft equipment problem : less severe non adherence : published procedure non adherence : clearance other spatial deviation
Independent Detector	other controllera
Resolutory Action	controller : issued advisory controller : issued new clearance
Supplementary
Problem Areas	Flight Crew Human Performance Aircraft Chart Or Publication
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

Departing runway 17C dfw; TRISS2 SID/txk transition. After passing the triss intersection and approximately FL230; headed for txk; ZFW called asking if we were direct shero intersection. We said 'no; we are going to txk.' ZFW said we should be going to shero; which we did right away. We then noticed shero between triss and txk. When loading the flight plan from the flight release; shero was not automatic-loaded into the box and the first officer missed the intersection in his check. When I went to check the flight plan from the flight release; what I remember seeing was the TRISS2 SID followed by txk/J42 flight plan. In my mind for some reason that was ok because that was on the top part of the flight release. After the correction on course my first officer and myself talked about what happened; how it happened and what we would do in the future to prevent this from happening again; ie; reading the flight plan to each other after it has been loaded.

Original NASA ASRS Text

Title: A300 DEPARTING DFW FAILS TO PROGRAM TXK TRANSITION ON TRISS RNAV SID.

Narrative: DEPARTING RWY 17C DFW; TRISS2 SID/TXK TRANSITION. AFTER PASSING THE TRISS INTXN AND APPROX FL230; HEADED FOR TXK; ZFW CALLED ASKING IF WE WERE DIRECT SHERO INTXN. WE SAID 'NO; WE ARE GOING TO TXK.' ZFW SAID WE SHOULD BE GOING TO SHERO; WHICH WE DID RIGHT AWAY. WE THEN NOTICED SHERO BTWN TRISS AND TXK. WHEN LOADING THE FLT PLAN FROM THE FLT RELEASE; SHERO WAS NOT AUTO-LOADED INTO THE BOX AND THE FO MISSED THE INTXN IN HIS CHK. WHEN I WENT TO CHK THE FLT PLAN FROM THE FLT RELEASE; WHAT I REMEMBER SEEING WAS THE TRISS2 SID FOLLOWED BY TXK/J42 FLT PLAN. IN MY MIND FOR SOME REASON THAT WAS OK BECAUSE THAT WAS ON THE TOP PART OF THE FLT RELEASE. AFTER THE CORRECTION ON COURSE MY FO AND MYSELF TALKED ABOUT WHAT HAPPENED; HOW IT HAPPENED AND WHAT WE WOULD DO IN THE FUTURE TO PREVENT THIS FROM HAPPENING AGAIN; IE; READING THE FLT PLAN TO EACH OTHER AFTER IT HAS BEEN LOADED.

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.