Narrative:

Left spoilers out below 1;000 feet; momentarily received stick shaker in the landing flair.fatigue; task saturation. Distractions due to ATC keeping us at higher altitude approaching the airport. Unusual airport environment; distractions from non-standard runway information needed to enter into the FMS. No glide path information available for the runway in use; I was visually focused on the final approach and glide path required adjusting for gusty wind. Spoilers were still partially deployed and omitted from our cross check by both the flying and monitoring pilot.ATC left us high inbound to crw. We queried ATC for lower altitude several times. I was flying pilot and had to use spoilers to descend and meet profile for runway 5 at crw. During the expedited descent the monitoring pilot was entering runway data into FMS to get landing data. FMS repeatedly sent back 'no landing data for the selected runway.' I was distracted; and only partially stowed the spoilers.we had earlier discussed the displaced threshold and I had suggested to check the release for a non-standard runway entry for the FMS. This was accomplished and the FMS returned correct landing data for runway 5.approaching the airport both the glide slope and VASI were inoperative for runway 5. The runway is unusual and perched atop mountainous terrain and my first time landing there. The new displaced threshold decreased available runway length and also changed the glide path perspective. We were task saturated as a crew and both omitted the spoilers from our scan. Spoilers were still partially deployed as we descended below 1;000 feet. We continued the visual approach configured and on speed. In the landing flair we momentarily received the stick shaker and the captain retracted the partial spoilers that were deployed. Event was uneventful; normal landing. Incorporating a 'spoilers stowed' into the 'before landing checklist' would prevent this type of distracted event from happening.

Related reports:

Google
 

Original NASA ASRS Text

Title: CRJ flight crew experienced a late descent clearance from ATC. As a result the spoilers were used to get back on a proper glide path and never fully retracted prior to the flare. Stick shaker is activated in the flare and the Captain quickly retracts the spoilers. Glideslope and VASI were both out of service due recent runway modifications.

Narrative: Left spoilers out below 1;000 feet; momentarily received stick shaker in the landing flair.Fatigue; task saturation. Distractions due to ATC keeping us at higher altitude approaching the airport. Unusual airport environment; distractions from non-standard runway information needed to enter into the FMS. No glide path information available for the runway in use; I was visually focused on the final approach and glide path required adjusting for gusty wind. Spoilers were still partially deployed and omitted from our cross check by both the flying and monitoring pilot.ATC left us high inbound to CRW. We queried ATC for lower altitude several times. I was flying pilot and had to use spoilers to descend and meet profile for Runway 5 at CRW. During the expedited descent the monitoring pilot was entering runway data into FMS to get landing data. FMS repeatedly sent back 'No landing data for the selected runway.' I was distracted; and only partially stowed the spoilers.We had earlier discussed the displaced threshold and I had suggested to check the release for a non-standard runway entry for the FMS. This was accomplished and the FMS returned correct landing data for Runway 5.Approaching the airport both the glide slope and VASI were inoperative for Runway 5. The runway is unusual and perched atop mountainous terrain and my first time landing there. The new displaced threshold decreased available runway length and also changed the glide path perspective. We were task saturated as a crew and both omitted the spoilers from our scan. Spoilers were still partially deployed as we descended below 1;000 feet. We continued the visual approach configured and on speed. In the landing flair we momentarily received the stick shaker and the Captain retracted the partial spoilers that were deployed. Event was uneventful; normal landing. Incorporating a 'spoilers stowed' into the 'before landing checklist' would prevent this type of distracted event from happening.

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.