Narrative:

We had three runway changes. The first runway for departure was 10L. When we called for push they changed our runway to 9R. We loaded the data and requested new numbers. After we pushed and started engines they changed the runway for the third time to 32L at T10. They then issued taxi instructions. We told them to standby. The first officer started the runway change checklist. About halfway through the checklist they changed our taxi instructions again. I believe this is where we were distracted. The first officer entered runway 32R not 32L. He entered intersection T10. While he was requesting new numbers I was looking to see how to get to the runway with the new taxi route. Ground control wanted us to move so I told the first officer we could taxi and when the takeoff data showed up we could look at it then. There was a line of weather approaching and our radar was questionable so I wanted to leave as soon as we could. As we approached 32L at T10 a heavy airbus departed and then an rj. The numbers came over the printer so we completed the runway change checklist. As I was taking a quick look at the takeoff data they cleared us for takeoff. I did not catch that the takeoff data was for 32R; not 32L. Just a side note: there is no T10 intersection on 32R although the FMC allowed the first officer to enter it and it accepted it. I called for the takeoff checklist as I taxied onto the runway and started a rolling takeoff. Just as we lined up on the runway heading and were verifying the runway we had a navigation shift on both nds. I think this confused me a little and I responded with runway verified as I looked at the runway heading not the runway on the nd. I always look at both (except this time). I handed the aircraft over to the first officer. He pushed the throttles forward and said check thrust. Just as I took the throttles we got an EICAS message that said FMC runway disagree. I looked at the nd and knew immediately what had happened. We were picking up speed because we were so light (60;000lbs under landing wt) and I knew the runway was 9;000 feet long so I chose to continue the takeoff. The last 5 times I was in ord I took off on runway 32L at T10 so I knew it was safe. Maybe not the best idea but that's what I did. If I had been unfamiliar with the runway I would have rejected the takeoff. The numbers for all 3 runways that night were the same. Runway 9R is only 7;967 feet and 32L at T10 is almost 9;000 feet so I knew it was safe to continue the takeoff. Don't get me wrong. I am extremely upset about this. I can't believe I let this happen. Looking back I see several mistakes that were made. I also broke some of my own personal rules that I use to not let things like this happen. Never again; I hope.

Related reports:

Google
 

Original NASA ASRS Text

Title: An air carrier crew continued the takeoff at ORD with the incorrect takeoff runway in the FMC after ATC issued several taxi route changes along with three runway changes.

Narrative: We had three runway changes. The first runway for departure was 10L. When we called for push they changed our runway to 9R. We loaded the DATA and requested new numbers. After we pushed and started engines they changed the runway for the third time to 32L at T10. They then issued taxi instructions. We told them to standby. The F/O started the runway change checklist. About halfway through the checklist they changed our taxi instructions again. I believe this is where we were distracted. The First Officer entered Runway 32R not 32L. He entered intersection T10. While he was requesting new numbers I was looking to see how to get to the runway with the new taxi route. Ground Control wanted us to move so I told the First Officer we could taxi and when the takeoff data showed up we could look at it then. There was a line of weather approaching and our radar was questionable so I wanted to leave as soon as we could. As we approached 32L at T10 a heavy airbus departed and then an RJ. The numbers came over the printer so we completed the runway change checklist. As I was taking a quick look at the takeoff data they cleared us for takeoff. I did not catch that the takeoff data was for 32R; not 32L. Just a side note: There is no T10 intersection on 32R although the FMC allowed the First Officer to enter it and it accepted it. I called for the takeoff checklist as I taxied onto the runway and started a rolling takeoff. Just as we lined up on the runway heading and were verifying the runway we had a NAV SHIFT on both NDs. I think this confused me a little and I responded with runway verified as I looked at the runway heading not the runway on the ND. I always look at both (except this time). I handed the aircraft over to the First Officer. He pushed the throttles forward and said check thrust. Just as I took the throttles we got an EICAS message that said FMC runway disagree. I looked at the ND and knew immediately what had happened. We were picking up speed because we were so light (60;000lbs under landing wt) and I knew the runway was 9;000 feet long so I chose to continue the takeoff. The last 5 times I was in ORD I took off on Runway 32L at T10 so I knew it was safe. Maybe not the best idea but that's what I did. If I had been unfamiliar with the runway I would have rejected the takeoff. The numbers for all 3 runways that night were the same. Runway 9R is only 7;967 feet and 32L at T10 is almost 9;000 feet so I knew it was safe to continue the takeoff. Don't get me wrong. I am EXTREMELY upset about this. I can't believe I let this happen. Looking back I see several mistakes that were made. I also broke some of my own personal rules that I use to not let things like this happen. Never again; I hope.

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.