37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1276240 |
Time | |
Date | 201507 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | DEN.Airport |
State Reference | CO |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | B737 Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | Parked Taxi |
Flight Plan | IFR |
Person 1 | |
Function | Captain |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 96 Flight Crew Type 11800 |
Person 2 | |
Function | First Officer |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 141 Flight Crew Type 6000 |
Events | |
Anomaly | ATC Issue All Types |
Narrative:
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 pre departure clearance. 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.
Original NASA ASRS Text
Title: B737 flight crew described the extra workload and opportunities for errors when they received multiple departure runway assignment changes on taxi out at DEN.
Narrative: 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.
Data retrieved from NASA's ASRS site 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.