Narrative:

On [arrival] on a VFR day at 9000 feet I called for flaps 1 at 210 knots. We got a leading edge disagree. I said 'my aircraft 'and directed first officer (first officer) to do the QRH. I handed first officer my ipad with QRH ready while the first officer's [troubleshooting app] was loading. Training department does not teach our pilots to have [the troubleshooting app] up and running for every flight. I always do; but many of my copilots don't. This is a fundamental training failure/issue as many of us go to the ipad for emergencies. First officer did a great job of working through a somewhat elaborate flight control checklist with a re-direct to asymmetry checklist. We reviewed QRH steps twice because I was overly cautious. All steps were accomplished properly. We coordinated everything with ATC; including a request to notify company. However; ATC did not call [central operations]; but instead called the local operations who failed to pass the info to [central ops]/dispatch. As pilots we were both concerned about the min maneuvering hook being so close to our airspeed. A note in the QRH would've been helpful. Also; despite the fact that flap override was selected and all checklist steps were followed; we got numerous egpws terrain warnings below 200 feet while landing. The checklist should have you turn off [the egpws] also; very distracting! Smooth landing and arff (airport rescue fire fighting) was great! ATC other than calling ops versus [central operations] was excellent. We taxied to the gate. Repeat mx (maintenance) write up. They didn't find the cause of the first failure of slats to extend or trouble shoot enough to confirm proper operation. Maintenance should have done a more thorough job after the first occurrence. Also; deselecting epgws should be part of the leading edge flap asymmetry checklist.

Related reports:

Google
 

Original NASA ASRS Text

Title: B757 Captain reported landing safely after experiencing a leading edge flap disagree alert.

Narrative: On [arrival] on a VFR day at 9000 feet I called for Flaps 1 at 210 knots. We got a leading edge disagree. I said 'my aircraft 'and directed FO (First Officer) to do the QRH. I handed FO my iPad with QRH ready while the FO's [troubleshooting app] was loading. Training department does not teach our pilots to have [the troubleshooting app] up and running for every flight. I always do; but many of my copilots don't. This is a fundamental training failure/issue as many of us go to the iPad for emergencies. FO did a great job of working through a somewhat elaborate flight control checklist with a re-direct to asymmetry checklist. We reviewed QRH steps twice because I was overly cautious. All steps were accomplished properly. We coordinated everything with ATC; including a request to notify company. However; ATC did not call [central operations]; but instead called the Local Operations who failed to pass the info to [central ops]/Dispatch. As pilots we were both concerned about the min maneuvering hook being so close to our airspeed. A note in the QRH would've been helpful. Also; despite the fact that flap override was selected and all checklist steps were followed; we got numerous EGPWS terrain warnings below 200 feet while landing. The checklist should have you turn off [the EGPWS] also; very distracting! Smooth landing and ARFF (Airport Rescue Fire Fighting) was great! ATC other than calling Ops versus [central operations] was excellent. We taxied to the gate. Repeat Mx (maintenance) write up. They didn't find the cause of the first failure of slats to extend or trouble shoot enough to confirm proper operation. Maintenance should have done a more thorough job after the first occurrence. Also; deselecting EPGWS should be part of the leading edge flap asymmetry checklist.

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.