Narrative:

Conducting cdogg two arrival with ILS 11 approach transition. At kaycc intersection crew was cleared ILS 11 approach. Crew cleared discontinuity and at that time the snow flake no longer showed aircraft on 3.0 glide and was now well above snow flake glide path. This was due to the fact that the ILS transition selected was the limer transition so once everything was cleaned up on the legs page it showed the aircraft well above a 3.0 glide. The crew continued on the approach and configured on speed. Aircraft was configured outside the FAF but slightly above the ILS glide path. However; the altitude captured and the aircraft began to drift above the glide path. Pilot monitoring (pm) stated above glide path and the pilot flying (PF) tried to correct but did not reset altitude. Pm then selected a different altitude and engaged vs 1;500 fpm. At this time the localizer went full scale deflection and pm called for go around. PF advanced power and hit go-around bugs but did not pitch into command bars. Pm selected flaps 8 and selected gear up. PF still had not pitched to command bars and pm (captain) took controls and recovered aircraft just as speed touch 230 kias. Captain called and asked tower for a heading and altitude and complied with ATC instructions. Aircraft was vectored for another ILS 11 and landed without incident.pwm was known as an unstable airport as provided by ACARS. Crew discussed this and planned to descend early and maintain a 3.0 degree glide. The error was we did not account for the distance change once we cleaned up the approach which took away approximately 16 miles of ground distance from our original descent computation. Undesired aircraft state was attained because the approach became rushed. As soon as I felt the approach was being rushed I should have requested vectors for the approach.

Related reports:

Google
 

Original NASA ASRS Text

Title: A CRJ-700 Captain and a trainee First Officer describe an unstabilized approach and go around during which the First Officer does not pitch up and the Captain assumes control of the aircraft. Selecting an inappropriate ILS transition led the crew to believe they were on a proper descent path when they were not.

Narrative: Conducting CDOGG TWO arrival with ILS 11 approach transition. At KAYCC intersection crew was cleared ILS 11 approach. Crew cleared discontinuity and at that time the snow flake no longer showed aircraft on 3.0 glide and was now well above snow flake glide path. This was due to the fact that the ILS transition selected was the LIMER transition so once everything was cleaned up on the legs page it showed the aircraft well above a 3.0 glide. The crew continued on the approach and configured on speed. Aircraft was configured outside the FAF but slightly above the ILS glide path. However; the altitude captured and the aircraft began to drift above the glide path. Pilot Monitoring (PM) stated above glide path and the Pilot Flying (PF) tried to correct but did not reset altitude. PM then selected a different altitude and engaged VS 1;500 fpm. At this time the localizer went full scale deflection and PM called for go around. PF advanced power and hit go-around bugs but did not pitch into command bars. PM selected flaps 8 and selected gear up. PF still had not pitched to command bars and PM (Captain) took controls and recovered aircraft just as speed touch 230 kias. Captain called and asked tower for a heading and altitude and complied with ATC instructions. Aircraft was vectored for another ILS 11 and landed without incident.PWM was known as an unstable airport as provided by ACARS. Crew discussed this and planned to descend early and maintain a 3.0 degree glide. The error was we did not account for the distance change once we cleaned up the approach which took away approximately 16 miles of ground distance from our original descent computation. Undesired aircraft state was attained because the approach became rushed. As soon as I felt the approach was being rushed I should have requested vectors for the approach.

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.