Narrative:

During climb out on a scheduled far part 121 flight at FL220; we got an EICAS message 'slat fail.' checked status of slat position and found they failed in the zero position. The E170's limits are not to move them above FL200. We continued our climb to filed altitude of FL360 for the cruise portion of flight. During cruise; we contacted dispatch via ACARS to let them know what had happened and requested local WX so we could formulate a plan as we descended into ZZZ. As we started our descent and on with center we told them of our situation and to radio ahead to ZZZ to let them know we wanted priority handling and their longest runway. When we were handed off to approach; we again told them of our situation and they were aware. At this time we told approach we needed to slow down so we could follow the QRH and try to resolve the problem. After following the procedures in QRH we ended up with a zero slat and zero flap situation. With this we let flight attendants and passenger know of situation and that the approach speed would be much greater than normal. We did not declare an emergency. After figuring our 'unfactored' landing distances and all other considerations; I didn't feel it was necessary. (Brakes and thrust reversers were fine.) approach gave us vectors; winds were calm and visibility was greater than 10 mi. Approach speed was up to 175 KTS for our weight on this flight. Approach and landing were normal except higher speed. We landed and taxied to gate without incident to aircraft; crew or passenger. At the gate; we contacted dispatch; chief pilot and maintenance control to let everyone aware of the situation. I wrote up the discrepancy and maintenance was able to reset the slat fail problem and get the slat/flaps to more normally operations check good.

Related reports:

Google
 

Original NASA ASRS Text

Title: AN EMB170 EICAS INDICATED SLATS FAILED IN THE UP POS. CREW PERFORMED A FLAPS SLATS UP LNDG WHEN FLAPS; SLATS FAILED TO EXTEND WITH THE CHKLIST.

Narrative: DURING CLBOUT ON A SCHEDULED FAR PART 121 FLT AT FL220; WE GOT AN EICAS MESSAGE 'SLAT FAIL.' CHKED STATUS OF SLAT POS AND FOUND THEY FAILED IN THE ZERO POS. THE E170'S LIMITS ARE NOT TO MOVE THEM ABOVE FL200. WE CONTINUED OUR CLB TO FILED ALT OF FL360 FOR THE CRUISE PORTION OF FLT. DURING CRUISE; WE CONTACTED DISPATCH VIA ACARS TO LET THEM KNOW WHAT HAD HAPPENED AND REQUESTED LCL WX SO WE COULD FORMULATE A PLAN AS WE DSNDED INTO ZZZ. AS WE STARTED OUR DSCNT AND ON WITH CTR WE TOLD THEM OF OUR SIT AND TO RADIO AHEAD TO ZZZ TO LET THEM KNOW WE WANTED PRIORITY HANDLING AND THEIR LONGEST RWY. WHEN WE WERE HANDED OFF TO APCH; WE AGAIN TOLD THEM OF OUR SIT AND THEY WERE AWARE. AT THIS TIME WE TOLD APCH WE NEEDED TO SLOW DOWN SO WE COULD FOLLOW THE QRH AND TRY TO RESOLVE THE PROB. AFTER FOLLOWING THE PROCS IN QRH WE ENDED UP WITH A ZERO SLAT AND ZERO FLAP SIT. WITH THIS WE LET FLT ATTENDANTS AND PAX KNOW OF SIT AND THAT THE APCH SPD WOULD BE MUCH GREATER THAN NORMAL. WE DID NOT DECLARE AN EMER. AFTER FIGURING OUR 'UNFACTORED' LNDG DISTANCES AND ALL OTHER CONSIDERATIONS; I DIDN'T FEEL IT WAS NECESSARY. (BRAKES AND THRUST REVERSERS WERE FINE.) APCH GAVE US VECTORS; WINDS WERE CALM AND VISIBILITY WAS GREATER THAN 10 MI. APCH SPD WAS UP TO 175 KTS FOR OUR WT ON THIS FLT. APCH AND LNDG WERE NORMAL EXCEPT HIGHER SPD. WE LANDED AND TAXIED TO GATE WITHOUT INCIDENT TO ACFT; CREW OR PAX. AT THE GATE; WE CONTACTED DISPATCH; CHIEF PLT AND MAINT CTL TO LET EVERYONE AWARE OF THE SIT. I WROTE UP THE DISCREPANCY AND MAINT WAS ABLE TO RESET THE SLAT FAIL PROB AND GET THE SLAT/FLAPS TO MORE NORMALLY OPS CHK GOOD.

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