Date: 201507
Local time of day: 0001-0600
Location: DEN.Airport, CO
Flight conditions: IMC
Weather elements / visibility: Thunderstorm
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class A ZDV
ATC / advisory: Center ZDV
Aircraft component: FMS/FMC
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Human factors: Human-Machine Interface; Training / Qualification
Anomaly: Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Air Traffic Control Issued New Clearance; Flight Crew Became Reoriented; Flight Crew Returned To Clearance
Contributing factors: Aircraft; Human Factors; Procedure
Primary problem: Human Factors

Narrative: Flight was delayed due to thunderstorms in the area. The aircraft we were to fly arrived late; our required fourth Flight Attendant was delayed arriving from another flight and due to lightning in the area; fueling was delayed. Already late; at call up to ramp control for pushback we were informed that East departures were closed and to contact Clearance delivery for new routing. The FMS was originally built with runway 08 but clearance was saying to expect runway 25. The route was entered via the company route function on the RTE page; the routing was verified off the RTE pages. The initial point was YOKES4.DEHLI.  I contacted ramp control and cleared to push and expect runway 08. I entered the new departure runway; with DEHLI; cleared up discontinuities and verified the route again.  Again the first point was YOKES4.DEHLI. Taxi from that point was uneventful.Takeoff we were given a heading of 065 and the remainder of takeoff was uneventful. Five minutes after takeoff we were cleared direct to YOKES; That was inputted in the FMS by the Pilot monitoring (PM) and verified by Pilot Flying.  Direct YOKES the autopilot was engaged and we were given a climb to FL230. The climb was uneventful until arriving at YOKES we were given a change to a different Center frequency and once contacted they started to ask where we were heading.  PM stated direct ONL (ONEIL). Center stated that was not the proper routing for what we were given; he cleared us direct ONL and started to ask if we were given a runway change during taxi.  Per the SID the DEHLI transition has you flying to two other north easterly points before heading for ONL. Center stated that we were not the only aircraft to have this problem that night and that this has been a problem for over a year.  The Center control started to ask how we entered information into our system to try to determine the cause of the problem. The discussion lasted a few minutes and we stated exactly what and how we entered our information (see above). The controller handed us to another Denver Center controller who on initial call up stated to give them a call and that they we going to violate us for the course deviation. The remainder of the flight was uneventful.




Synopsis: A B737 First Officer departing DEN receives a route change with a new SID after calling for taxi and is entered in the FMC with the expected runway. A new runway is assigned during taxi and entered in the FMC. After passing YOKES in the climb ATC questions the route and it is discovered that the DEHLI transition of the YOKES4 departure has been omitted.