37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1150226 |
Time | |
Date | 201402 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | MSP.Airport |
State Reference | MN |
Environment | |
Flight Conditions | Marginal |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Regional Jet 200 ER/LR (CRJ200) |
Operating Under FAR Part | Part 121 |
Flight Phase | Initial Approach |
Route In Use | STAR TWOLF2 |
Flight Plan | IFR |
Component | |
Aircraft Component | FMS/FMC |
Person 1 | |
Function | Captain Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types |
Narrative:
We were on the TWOLF2 arrival into msp and had been told to expect the ILS to runway 12R. The arrival; which ends at slikk; contains instructions to fly a 300 heading departing slikk. Upon reaching this fix; the first officer (first officer) [and] pilot flying remained in white needles and FMS mode. This technique initially kept the aircraft on the required heading as prescribed by the STAR. I asked the first officer if he was ready for final nav setup. I then set up the FMS accordingly by bringing up the first fix on the ILS 12R (paetn) into L1 and setting the inbound course. I asked the first officer to confirm the change; and he reviewed it and said 'execute'. I executed the FMS and did not immediately notice that he had not yet reverted to heading mode and green needles. Additionally; ATC issued another instruction at this time (lower altitude and speed assignment) that diverted our attention. Because FMS mode was still active; the aircraft began a turn to the right toward the 12R final approach course. I soon noticed this and instructed the first officer to immediately go to heading mode and turn back to the assigned heading. He then disengaged the autopilot; at which time ATC gave us an immediate left turn to heading 270. He started the turn to 270; at which time ATC also issued a lower altitude and speed. I could tell that he was starting to get somewhat overwhelmed as he did not respond to the new lower altitude initially and was focused only on getting back to the assigned heading. I suggested he turn the autopilot back on to reduce his workload and suggested vs mode down to get to the new assigned altitude. ATC then reiterated the 270 heading and new altitude. After re- engaging the autopilot and selecting the correct modes; we were back on the assigned heading and descending to the new altitude.I should have been more attentive to the fact that the first officer was still in FMS mode prior to prompting him for final nav setup. When I began the final nav setup; I incorrectly assumed that he would revert to heading mode prior to confirming and executing the FMS. I should have verified that he selected heading first as part of the procedure. When the mistake was made; the first officer's relatively low experience in the airplane made it harder for him to correct in a prompt manner.
Original NASA ASRS Text
Title: CRJ-200 turned prematurely toward the final approach course when the First Officer (pilot flying) remained in 'white needles' FMS mode as the Captain set the ILS approach course and; with the First Officer's concurrence; activated the FMS. Captain thought the First Officer was in heading mode ('green needles').
Narrative: We were on the TWOLF2 arrival into MSP and had been told to expect the ILS to Runway 12R. The arrival; which ends at SLIKK; contains instructions to fly a 300 heading departing SLIKK. Upon reaching this fix; the First Officer (FO) [and] pilot flying remained in white needles and FMS mode. This technique initially kept the aircraft on the required heading as prescribed by the STAR. I asked the FO if he was ready for final Nav setup. I then set up the FMS accordingly by bringing up the first fix on the ILS 12R (PAETN) into L1 and setting the inbound course. I asked the FO to confirm the change; and he reviewed it and said 'execute'. I executed the FMS and did not immediately notice that he had not yet reverted to HDG mode and green needles. Additionally; ATC issued another instruction at this time (lower altitude and speed assignment) that diverted our attention. Because FMS mode was still active; the aircraft began a turn to the right toward the 12R final approach course. I soon noticed this and instructed the FO to immediately go to HDG mode and turn back to the assigned heading. He then disengaged the autopilot; at which time ATC gave us an immediate left turn to heading 270. He started the turn to 270; at which time ATC also issued a lower altitude and speed. I could tell that he was starting to get somewhat overwhelmed as he did not respond to the new lower altitude initially and was focused only on getting back to the assigned heading. I suggested he turn the autopilot back on to reduce his workload and suggested VS mode down to get to the new assigned altitude. ATC then reiterated the 270 heading and new altitude. After re- engaging the autopilot and selecting the correct modes; we were back on the assigned heading and descending to the new altitude.I should have been more attentive to the fact that the FO was still in FMS mode prior to prompting him for final Nav setup. When I began the final Nav setup; I incorrectly assumed that he would revert to HDG mode prior to confirming and executing the FMS. I should have verified that he selected HDG first as part of the procedure. When the mistake was made; the FO's relatively low experience in the airplane made it harder for him to correct in a prompt manner.
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.