Date: 201308
Local time of day: 0001-0600
Location: ORD.Airport, IL
Flight conditions: Mixed
Light: Daylight
Aircraft: Medium Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight phase: Initial Approach
Airspace: Class B ORD
ATC / advisory: TRACON C90
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Distraction; Fatigue; Situational Awareness; Workload
Second reporter function: First Officer; Pilot Not Flying
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Weather / Turbulence; Inflight Event / Encounter CFTT / CFIT; Inflight Event / Encounter Unstabilized Approach
Detector: Automation Aircraft Terrain Warning; Person Air Traffic Control; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Flight Crew Executed Go Around / Missed Approach; Flight Crew Took Evasive Action
Contributing factors: Human Factors; Procedure; Weather; Environment - Non Weather Related
Primary problem: Ambiguous

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.


Second narrative: I asked the Captain 'Are you sure you want to do this?' We continued and had a low altitude alert warning from the Tower and a 'glideslope' warning from the airplane. At that point the Captain elected to go-around and we executed a missed approach. The Captain later stated that he misidentified the field. [There was a] lack of assertion on the (First Officer and pilot not flying). The aircraft was properly configured but clearly we had a total lack of situational awareness in terms of where we were with respect to the runway. I was uncomfortable with the approach. I did not see the airport and we were going to have to descend/maneuver below/around a scattered layer of clouds to get in a position to see the runway. I needed to speak up much earlier and rather than 'suggesting to go around'. I should have stated runway not insight we need to 'Go-around now.' Once the airport was not in sight we should have executed a go-around immediately.


Synopsis: 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.'