B737 Undifferentiated or Other Model
Flight Crew Air Transport Pilot (ATP)
Flight Crew Last 90 Days 96; Flight Crew Type 11800
Workload
ATC Issue All Types
General None Reported / Taken
Human Factors; Procedure
I am making this report to highlight the potential threat to our operations induced by the frequent runway changes in Denver. Local conditions indicated that Runway 8 would be the likely departure runway; which we planned. ATIS updated to indicate Runway 17R would be used for departure. We changed the programming and re-briefed the departure. When we called ramp for pushback; we were assigned Runway 8. We reprogrammed the route; changed the runway data; re-briefed and accomplished the Departure Checklist. When we called for taxi; Ramp assigned us Runway 17R. We again reprogrammed; changed data; re-briefed and re-ran the Departure Checklist. When we contacted Ground for taxi; we were given Runway 8. We reprogrammed; re-briefed; changed data and re-ran the Departure Checklist. After we started our taxi; Ground changed our runway assignment to Runway 17R. We again reprogrammed; changed data; re-briefed and re-ran the Departure Checklist. Twice we were hustled by Ground. We resisted the time pressure and complied with our procedures. The trouble; as I see it; is that these changes run directly counter to our attempts to preplan our departures; and are a major source of errors. Furthermore; this change and uncertainty is commonplace in our Denver departures.Preventative Measures: Have Denver assign runways on the PDC. This way we can know what to expect and be pre-briefed. Also; re-emphasize with Denver the difficulties in changing runways; and let them know to expect a stop and delay prior to continuing for departure.
[Report Narrative Contained No Additional Information.]
B737 flight crew described the extra workload and opportunities for errors when they received multiple departure runway assignment changes on taxi out at DEN.