Narrative:

On short approach for [runway] 28R into ord a cat walked onto the runway as we were visual with the runway. Tower told us to go-around. After the go-around; we were vectored onto a downwind at 4;000; 250 KTS assigned. ATC asked if we could see the runway. I said yes. We were cleared for the visual to [runway] 28R inside wilt. I began configuration and descent as I turned toward the field. We were told of traffic for both northern parallels. We were on glideslope and approaching the localizer when we descended below glideslope and still south of the localizer. Tower gave us a low altitude warning. I realized I had misidentified the airport and we went around at about 1;000 ft AGL. We entered downwind for [runway] 27R and landed without event. Hindsight I should have gone out further on downwind and gotten stabilized but I thought I saw the field so I continued the approach. The first officer should have spoken up more as an experienced pilot not flying; and I should have never let the approach go as far as it did. Day 4; early morning wake up; 6 hours sleep for the third night in a row; low clouds/weather; multiple go-arounds; on-time performance pressure; trying to 'get it done'; misidentification of runway; out of position to begin the approach (high and fast); pilot not flying not speaking up; traffic on north parallels kept me from making a more direct path toward the localizer. I learned to not try to make an approach work and just take the extra time to get setup and configured.

Google
 

Original NASA ASRS Text

Title: An Air Carrier on approach to ORD 28L was issued a go-around because of an animal on the runway and on the second approach the Captain misidentified the airport; got low; and executed another go-around after a 'glideslope warning.'

Narrative: On short approach for [Runway] 28R into ORD a cat walked onto the runway as we were visual with the runway. Tower told us to go-around. After the go-around; we were vectored onto a downwind at 4;000; 250 KTS assigned. ATC asked if we could see the runway. I said yes. We were cleared for the visual to [Runway] 28R inside Wilt. I began configuration and descent as I turned toward the field. We were told of traffic for both northern parallels. We were on glideslope and approaching the localizer when we descended below glideslope and still south of the localizer. Tower gave us a low altitude warning. I realized I had misidentified the airport and we went around at about 1;000 FT AGL. We entered downwind for [Runway] 27R and landed without event. Hindsight I should have gone out further on downwind and gotten stabilized but I thought I saw the field so I continued the approach. The First Officer should have spoken up more as an experienced pilot not flying; and I should have never let the approach go as far as it did. Day 4; early morning wake up; 6 hours sleep for the third night in a row; low clouds/weather; multiple go-arounds; on-time performance pressure; trying to 'get it done'; misidentification of runway; out of position to begin the approach (high and fast); pilot not flying not speaking up; traffic on north parallels kept me from making a more direct path toward the localizer. I learned to not try to make an approach work and just take the extra time to get setup and configured.

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.