Narrative:

We were being vectored for approach to runway xxc at ZZZ. We were level at 7000 ft with a clean wing indicating 190 KTS. Green dot was 180. Approach asked us to slow to 170 KTS and then descend to 5000 ft. The first officer was flying and called for flaps 1. Shortly after I selected flaps 1 we received an aural caution and the following four EICAS messages; stickshaker anticipated; aoa fail; spoiler fault; and slat fail. The EICAS indicated slats 0 and amber dashes. The flaps were in transit to one. I informed approach that we had a flap problem and needed to maintain 190 KTS while we ran the checklist. In accordance with the QRH; I selected flaps to their previous position (0) and waited 10 seconds. During the 10 seconds the slat fail message never extinguished. The QRH then directed me to extend the flaps again. The other 3 messages returned and the slat fail message remained. We asked for vectors to keep us in the area while we ran the checklist. Approach was pressing us for how much time this was going to require and I told them 10 minutes. I continued to run the checklist and asked the first officer to handle any radio calls from ATC regarding altitude and heading changes. The QRH under considerations suggested burning off fuel to reduce landing weight so we extended the landing gear and maintained 190 KIAS. We elected at this point to go ahead and configure for landing in order to increase our fuel burn. So we continued to be vectored west of the field with gear down and flaps 2. I then contacted the flight attendants and told them that we had a flap problem but to plan on a normal landing in about 10 minutes. I advised them that the safety equipment would be standing by on our landing but the landing should be normal. I then contacted operations and asked them to advise our dispatcher. Then I called approach control and declared an emergency and requested that the equipment be standing by. I completed the flap and/or slat fail checklist and then accomplished the flap/slat fail descent - approach checklist followed by the flap/slat fail landing checklist since we were configured for landing. I then advised approach that we were ready to proceed to the airport. While we were being vectored back to the field I sent the following ACARS message to dispatch; 'emerg slats 0 flaps 2'. I then ran the spoiler fault checklist and advised the first officer that we might not get ground all or any ground spoilers. I then asked the first officer if he was comfortable continuing to fly the aircraft to landing and he responded that he was. Vref was 150 KTS with a vapch speed of 156. We landed uneventfully; released the emergency equipment and proceeded to our gate. After arriving at the gate and talking to maintenance I found that the aircraft had a history of slat problems. I do not at this time know why the event occurred but I suspect a computer problem.

Related reports:

Google
 

Original NASA ASRS Text

Title: An ERJ-190 EICAS alerted SLATS FAIL on final as the aircraft was slowed. An uneventful emergency landing was completed with Flaps 2; Slats O. This was a repeat anomaly with the computer suspected as the failure point.

Narrative: We were being vectored for approach to Runway XXC at ZZZ. We were level at 7000 FT with a clean wing indicating 190 KTS. Green dot was 180. Approach asked us to slow to 170 KTS and then descend to 5000 FT. The First Officer was flying and called for Flaps 1. Shortly after I selected Flaps 1 we received an aural caution and the following four EICAS messages; STICKSHAKER ANTICIPATED; AOA FAIL; SPOILER FAULT; and SLAT FAIL. The EICAS indicated SLATS 0 and amber dashes. The flaps were in transit to one. I informed approach that we had a flap problem and needed to maintain 190 KTS while we ran the checklist. In accordance with the QRH; I selected flaps to their previous position (0) and waited 10 seconds. During the 10 seconds the SLAT FAIL message never extinguished. The QRH then directed me to extend the flaps again. The other 3 messages returned and the SLAT FAIL message remained. We asked for vectors to keep us in the area while we ran the checklist. Approach was pressing us for how much time this was going to require and I told them 10 minutes. I continued to run the checklist and asked the First Officer to handle any radio calls from ATC regarding altitude and heading changes. The QRH under considerations suggested burning off fuel to reduce landing weight so we extended the landing gear and maintained 190 KIAS. We elected at this point to go ahead and configure for landing in order to increase our fuel burn. So we continued to be vectored west of the field with gear down and Flaps 2. I then contacted the flight attendants and told them that we had a flap problem but to plan on a normal landing in about 10 minutes. I advised them that the safety equipment would be standing by on our landing but the landing should be normal. I then contacted operations and asked them to advise our Dispatcher. Then I called Approach Control and declared an emergency and requested that the equipment be standing by. I completed the Flap and/or Slat Fail checklist and then accomplished the Flap/Slat Fail Descent - Approach Checklist followed by the Flap/Slat Fail Landing Checklist since we were configured for landing. I then advised approach that we were ready to proceed to the airport. While we were being vectored back to the field I sent the following ACARS message to dispatch; 'EMERG SLATS 0 FLAPS 2'. I then ran the SPOILER FAULT checklist and advised the First Officer that we might not get ground all or any ground spoilers. I then asked the First Officer if he was comfortable continuing to fly the aircraft to landing and he responded that he was. Vref was 150 KTS with a Vapch speed of 156. We landed uneventfully; released the emergency equipment and proceeded to our gate. After arriving at the gate and talking to Maintenance I found that the aircraft had a history of SLAT problems. I do not at this time know why the event occurred but I suspect a computer problem.

Data retrieved from NASA's ASRS site as of April 2012 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.