Air carrier arrival into sdf voiced concern regarding the multiple runway changes issued during the ...

Narrative:

Flight was on arrival at sdf. After an incident from last week we were hyper vigilant on changes to landing runway. Starting approximately 30 minutes prior to landing the runway for landing was changed five times. This involves extensive FMC changes to insert and verify that the now new arrival has been properly loaded. We had hardly completed one change when the runway was reversed and we had to go through the process once again. After the last change when we were given to approach control we asked are we still cleared on the MAUDD1 arrival. There was some hesitation and at that time we were given a heading to intercept 35R localizer and eventually cleared visual for uneventful landing. After parking the runway was reversed once again. On a previous flight after a last minute runway change which resulted in a deviation our crew was extremely vigilant on proper FMC loading and verification. This was all happening on descent and during the time in all flights when history shows the highest chance of an accident or incident occurs. There needs to be an understanding of the work load incurred every time there are changes made to the landing runway.

Original NASA ASRS Text

Title: Air Carrier arrival into SDF voiced concern regarding the multiple runway changes issued during the descent into the airport listing the increased FMS workload needed to accommodate the changes.

Narrative: Flight was on arrival at SDF. After an incident from last week we were hyper vigilant on changes to landing runway. Starting approximately 30 minutes prior to landing the runway for landing was changed five times. This involves extensive FMC changes to insert and verify that the now new arrival has been properly loaded. We had hardly completed one change when the runway was reversed and we had to go through the process once again. After the last change when we were given to Approach Control we asked are we still cleared on the MAUDD1 arrival. There was some hesitation and at that time we were given a heading to intercept 35R LOC and eventually cleared visual for uneventful landing. After parking the runway was reversed once again. On a previous flight after a last minute runway change which resulted in a deviation our crew was extremely vigilant on proper FMC loading and verification. This was all happening on descent and during the time in all flights when history shows the highest chance of an accident or incident occurs. There needs to be an understanding of the work load incurred every time there are changes made to the landing runway.

Data retrieved from NASA's ASRS site as of July 2013 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.

Attributes
ACN	1039473
Time
Date	201209
Local Time Of Day	0601-1200
Place
Locale Reference	ZID.ARTCC
State Reference	IN
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	Commercial Fixed Wing
Operating Under FAR Part	Part 121
Flight Phase	Descent
Route In Use	STAR MAUDD ONE
Flight Plan	IFR
Person 1
Function	Captain Pilot Flying
Experience	Flight Crew Last 90 Days 15 Flight Crew Total 30000 Flight Crew Type 2500
Events
Anomaly	ATC Issue All Types

Air carrier arrival into sdf voiced concern regarding the multiple runway changes issued during the descent into the airport listing the increased FMS workload needed to accommodate the changes.