CRJ-200 Flight Crew reported letting the aircraft's speed get to Vref-5 on final approach producing a momentary stick shaker. The unstable approached was caused by inattention to detail during the approach; possible fatigue; and a drive to complete the mission after 2 failed attempts that day and poor CRM.

Date: 2022-05 · Aircraft: Regional Jet 200 ER/LR (CRJ200)

Anomalies: deviation-speed-all-types|deviation-discrepancy-procedural-published-material-policy|inflight-event-encounter-unstabilized-approach|inflight-event-encounter-weather-turbulence

Synopsis

CRJ-200 Flight Crew reported letting the aircraft's speed get to Vref-5 on final approach producing a momentary stick shaker. The unstable approached was caused by inattention to detail during the approach; possible fatigue; and a drive to complete the mission after 2 failed attempts that day and poor CRM.

Narrative

While enroute to ZZZ; we received weather at ZZZ of few clouds 1;000 ft. and overcast clouds 1;500 ft. We expected a low ceiling; but we're still expecting VFR conditions. We set up for and we're cleared for the localizer Runway XX approach. The glide slope was OTS so the localizer was the next best. Passing through 1;000 ft. we were stable. A few hundred feet above minimums we still didn't have the runway in sight. As we were searching for the runway; speed decayed to approximately Vref -5. The PM (Pilot Monitoring) called 'Speed' and PF (Pilot Flying) began correcting; however the stick shaker momentarily activated and the autopilot disconnected. The PF assumed manual control and corrected the deviation. We got the runway was in sight 100 ft. above minimums and the approach continued to landing.Both the PF and PM were expecting significantly better weather than what was forecasted and were anticipating a successful approach. As the approach progressed with no runway in sight; the PF transitioned focus outside to help in the search. While doing so; speed decayed. When the speed callout was made; it was too late to prevent the stick shaker. Expectation bias and distraction both played a role. We also had tried to get in to ZZZ earlier that afternoon and had gone missed twice before diverting to ZZZ1. I think there was pressure felt to 'make it work.'Bottom line is a decision to execute a missed approach should have been made when speed was noticed to be below Vref. The approach was unstable at that point. We were outside the stabilized approach criteria and fell in to the trap of 'making it work'.

Second reporter narrative

Coming in from ZZZ1 to ZZZ; we were on LOC Runway XX approach. At 1;000 ft. we were stabilized. Weather was reporting to be OVC 1;500 ft. but as we descended down to around 300 ft. above the minimum we still didn't have the runway insight and I was looking out for the runway. I got distracted looking out and let the speed got low; as the FO (First Officer) called out 'watch your speed' I realized we were slow. Before I corrected for it the stick shaker went on and autopilot was disconnected. Instead of going miss which we should've done I continued hand fly the aircraft and landed.The shake went on for only a brief sec; the FO (Pilot Monitoring) mentioned that the lowest airspeed he saw was about 5 it's below Vref; and I (Pilot Flying) saw airspeed was around 6 knots below Vref. The speed was corrected immediately; and we had the runway insight shortly after. We were both a little surprised the shaker was activated; nevertheless the proper action was to execute a miss approach since we were unstable below 1000' AFE. Earlier in the day we tried to get into ZZZ twice and went miss both times. On the third time going in I kind of felt the pressure to get in. Weather was worse than what's reporting so I got distracted looking out for the runway.Always be prepared to go miss. Do not get distracted and focus on flying the aircraft at all times.

More incidents for this aircraft family →

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.