37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1206147 |
Time | |
Date | 201409 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | MSO.Airport |
State Reference | MT |
Environment | |
Flight Conditions | IMC |
Light | Night |
Aircraft 1 | |
Make Model Name | Regional Jet 200 ER/LR (CRJ200) |
Operating Under FAR Part | Part 121 |
Flight Phase | Initial Approach |
Flight Plan | IFR |
Person 1 | |
Function | Pilot Not Flying Captain |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Person 2 | |
Function | Pilot Flying First Officer |
Events | |
Anomaly | Deviation - Procedural Published Material / Policy Deviation - Speed All Types Inflight Event / Encounter Unstabilized Approach Inflight Event / Encounter Weather / Turbulence |
Narrative:
I was the pilot monitoring while my first officer (first officer) performed the VOR DME B approach to runway 29 in mso. We had requested and were proceeding via jepsn IAF. The controller left us high and then vectored us east of course after crossing jepsn. He then had us rejoin the course but the first officer had difficulty capturing the VOR due to distraction with altitude loss; crosswinds (45 knots direct crosswind); forgetting the spoilers were extended and going to green needles. He was unable to get centered and capture course on the final approach course prior to the FAF and I called missed approach. He did not call out the profile but seemed confused. I then called the profile calls out and helped him with the go around. I reported a missed approach with approach control and he vectored us around to try again. We discussed the course deviation and altitudes on the approach and he attempted the approach again. This time he was able to capture the course. Although the VOR was captured; the aircraft was 'swimming' on course to counteract the changing winds. In his early level-off at stevi intersection; I was cross-checking the next step down at errik (as he was getting behind the aircraft) when he got the stall stick shaker for a second as his trend vector decreased and he was slow to add power. He called maximum thrust and after gaining speed; I called go-around/missed approach. He was again slow to respond and had trouble leveling off and following ATC directions. I put the autopilot on; requested the ILS Z runway 11 approach and took control of the aircraft. Fuel was estimated to be above minimum fuel per SOP at landing after the ILS approach. I briefed and set-up the ILS approach and landed safely in mso. Factors: ATC vectoring and high altitude assignments. First officer lack of judgment due to unstable approach. First officer lack of profile knowledge and execution. Nighttime IMC in mountainous terrain. Crosswinds on complicated non-precision approach. Suggestions: performing circling approach; namely this approach in simulator training. Stressing importance of missed approach/go-around profile in approach briefings.
Original NASA ASRS Text
Title: CRJ-200 flight crew reported an unstable approach with speed and altitude deviations to MSO. Weather; ATC procedures; and First Officer inexperience were factors in this report.
Narrative: I was the pilot monitoring while my First Officer (FO) performed the VOR DME B approach to Runway 29 in MSO. We had requested and were proceeding via JEPSN IAF. The controller left us high and then vectored us east of course after crossing JEPSN. He then had us rejoin the course but the FO had difficulty capturing the VOR due to distraction with altitude loss; crosswinds (45 knots direct crosswind); forgetting the spoilers were extended and going to green needles. He was unable to get centered and capture course on the final approach course prior to the FAF and I called missed approach. He did not call out the profile but seemed confused. I then called the profile calls out and helped him with the go around. I reported a missed approach with approach control and he vectored us around to try again. We discussed the course deviation and altitudes on the approach and he attempted the approach again. This time he was able to capture the course. Although the VOR was captured; the aircraft was 'swimming' on course to counteract the changing winds. In his early level-off at STEVI intersection; I was cross-checking the next step down at ERRIK (as he was getting behind the aircraft) when he got the stall stick shaker for a second as his trend vector decreased and he was slow to add power. He called MAX THRUST and after gaining speed; I called GO-AROUND/MISSED APPROACH. He was again slow to respond and had trouble leveling off and following ATC directions. I put the autopilot on; requested the ILS Z Runway 11 approach and took control of the aircraft. Fuel was estimated to be above minimum fuel per SOP at landing after the ILS approach. I briefed and set-up the ILS approach and landed safely in MSO. Factors: ATC vectoring and high altitude assignments. First officer lack of judgment due to unstable approach. First officer lack of profile knowledge and execution. Nighttime IMC in mountainous terrain. Crosswinds on complicated non-precision approach. Suggestions: Performing circling approach; namely this approach in simulator training. Stressing importance of missed approach/go-around profile in approach briefings.
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.