Date: 201307
Local time of day: 1201-1800
Location: ORD.Airport, IL
Flight conditions: VMC
Aircraft: B737-800
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Descent
Airspace: Class B ORD
ATC / advisory: TRACON C90
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Human factors: Confusion
Second reporter function: First Officer; Pilot Flying
Anomaly: ATC Issue All Types; Deviation - Speed All Types; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Became Reoriented; Flight Crew Returned To Clearance
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: [We were] on BULLZ Five Arrival given speed 300 KTS and 10;000 at KRENA. Prepped for Runway 27R; thus had programmed the arrival from SOOLU to HIMGO. Just prior to SOOLU; ORD Approach Control gave us a descent to 7;000 FT and expect [Runway] 28R. I went heads down to reprogram [Runway] 28R and the First Officer started a descent to 7;000 FT in [LVL] CHG; still at 300 KTS. When the [Runway] 28R approach was selected; the arrival changed from the north to HIMGO to the south to TONIE; VERY disorienting. Several seconds discussion was initiated between pilots as to where to go. As we referenced the chart and looked at the display; we noticed we were at 7;000 FT still at 300 KTS. Started slowing to 250 KTS and using heading select to get back towards JORJO; ORD Approach called and asked if we were on the approach. We stated we were heading to JORJO; and then they gave us direct to MONKZ. Rest of approach and landing was normal. EXCEPT: on landing roll; ORD Tower was giving us taxiing instructions: 'exit M1; M; cross Runway 32L; and stay with me.' Dangerous and dangerous as we are still at 80 KTS and slowing.Changing runways is a fact of life; BUT to assign a runway close to the airport JUST prior to a significant change in the direction of the arrival is unsafe and unsound. They were telling us that they would give us a short approach; and in their haste to get the aircraft on the ground; they almost created an unsafe condition. DO NOT assign runways or change unless significant time is given to comply. Another way to help would be to assign the new runway and give a heading or direct to a point of the new part of the arrival. Keeping us at 300 KTS was inviting problems as they want you to slow and descend and turn early for an approach. UNSAFE. Do not assign a high rate of speed and a lower altitude without calling: 'Slow to 250 KTS; then descend to 7;000 FT.'


Second narrative: On BULLZ arrival assigned 300 KTS going to Runway 27R. Just prior SOOLU we were given a decent 7;000 FT and runway change to Runway 28R. The pilot not flying went heads down to make the change to the FMC; as the change was inserted the airplane made a significant turn to the right. Causing a bit of distraction and confusion for me; I took the airplane out of LNAV and went to HDG select as the magenta line seemed to disappear. I ended up on a heading pointed somewhere between JORJO and MONKZ. With the confusion of the course changes I did not notice our speed was still 300 KTS and we were below 10;000 FT. As soon as I noticed we were still at 300 KTS I immediately slowed the plane back to 250. And when we were about to contact Approach they called us and gave us direct to MONKZ. At that point we were back on an ATC approved aircraft path and speed. The rest of the approach and landing were normal except while still at a relatively high speed we were exit M1 M cross 32L and stay with me. The fact that we changed runways at the last minute and were left on the arrival contributed to this. A better solution from Approach would have been a heading along with the new runway assignment. I did not have any experience with runway changes at ORD at the last minute while still on arrival. This contributed significantly to my confusion; if the same thing were to happen again I think I would be able to handle it better. Still I think runway changes that affect the arrival should come with a heading change rather than an assumption of continuing the arrival. The runway exit instruction should have probably been abbreviated to exit at M1 one stay with me.


Synopsis: B737-800 flight crew reports a track deviation and an overspeed during the BULLZ 5 arrival to ORD Runway 27R when ATC switches to Runway 28R just as the flight is approaching SOOLU. SOOLU is the point at which the arrival diverges for Runway 28R and the crew is not prepared for the changes that occur when the FMC is reprogrammed.