37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1002763 |
Time | |
Date | 201204 |
Local Time Of Day | 0001-0600 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Make Model Name | B757-200 |
Operating Under FAR Part | Part 121 |
Flight Phase | Initial Approach |
Route In Use | Vectors |
Flight Plan | IFR |
Component | |
Aircraft Component | Leading Edge Slat |
Person 1 | |
Function | Pilot Flying Captain |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 60 Flight Crew Total 12000 Flight Crew Type 6100 |
Person 2 | |
Function | Pilot Not Flying First Officer |
Events | |
Anomaly | Aircraft Equipment Problem Critical |
Narrative:
We were being vectored from downwind to base for runway yy. We were slowing preparing for a visual approach and I called for flaps 1. The pilot monitoring; first officer; selected flaps 1. The le slat disagree EICAS message and light illuminated. We told the tower and they gave us vectors around the airport so we could work the problem. I was the flying pilot. I called for the le slat disagree checklist and the first officer worked the problem. We also verified the non normal landing distance for flaps less than full. We declared an emergency and asked for runway xx because it was the longest. The company was contacted via ACARS in the short time available about our emergency. We completed the non normal checklists and landed on runway xx without incident. We were able to taxi on our own to the ramp without further assistance. We talked to the crash first rescue commander on a discrete frequency and told him we no longer needed assistance. The non normal was written up in the logbook and maintenance was notified. The first officer did a fantastic job of managing the checklist and situational awareness during a very busy phase of flight.
Original NASA ASRS Text
Title: A B757-200 LE SLAT DISAGREE EICAS alerted during landing preparations so an emergency was declared. During a vector delay the LE Slat Disagree Checklist was completed; followed by a normal landing.
Narrative: We were being vectored from downwind to base for Runway YY. We were slowing preparing for a visual approach and I called for flaps 1. The pilot monitoring; First Officer; selected flaps 1. The LE SLAT DISAGREE EICAS message and light illuminated. We told the Tower and they gave us vectors around the airport so we could work the problem. I was the flying pilot. I called for the LE Slat Disagree Checklist and the First Officer worked the problem. We also verified the non normal landing distance for flaps less than full. We declared an emergency and asked for Runway XX because it was the longest. The Company was contacted via ACARS in the short time available about our emergency. We completed the non normal checklists and landed on Runway XX without incident. We were able to taxi on our own to the ramp without further assistance. We talked to the Crash First Rescue Commander on a discrete frequency and told him we no longer needed assistance. The non normal was written up in the logbook and maintenance was notified. The First Officer did a fantastic job of managing the checklist and situational awareness during a very busy phase of flight.
Data retrieved from NASA's ASRS site as of July 2013 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.