MD-82
Human-Machine Interface; Situational Awareness
Deviation - Altitude Crossing Restriction Not Met; Deviation - Altitude Undershoot; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Air Traffic Control Issued New Clearance; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Returned To Clearance
Aircraft; Human Factors; Procedure
Approaching HOWDY on the WHINY 1 arrival the runway assignment was given. Upon selecting the new runway and transition the GFMS went into heading Hold. The aircraft proceeded past HOWDY maybe a mile; then we asked for a vector and told them we were unable to comply with the altitudes at VANCO. We were then given a vector and altitude; proceeded on into an approach to 36R. While loading the Arrival/transition/runway/transition this late in the game increased the workload to the point where we did not notice the aircraft went into heading hold until past HOWDY. Runway assignment on low visibility days should be given to MD80's early. The aircraft systems are not meant to fly Star arrivals with tight restrictions and FMS systems that do not easily accept changes. To change the runway is easy; to change the arrival/ transition/runway/transition then close discontinuities to fly the arrival is too much late in the arrival. Software issues should be resolved.
MD80 pilot reported a change in runway assignment approaching HOWDY on the WHINY1 arrival. The aircraft went into heading mode after the changes were initiated and not immediately detected by the crew. A track deviation occurred and the VANCO crossing restriction was missed.