A B737-300 flight crew encountered a leading edge flap problem after takeoff and decided to return to departure airport.
Synopsis
A B737-300 flight crew encountered a leading edge flap problem after takeoff and decided to return to departure airport.
Narrative
After selecting flaps up on departure; we noticed the amber LE Transit light was illuminated and the #1 Kruger flap indicated that it was fully extended. I ran the QRH and was somewhat confused as to what to do since it only referred to 'amber LE flap in transit' and either one or two slat portions partially extended. It doesn't refer to Kruger flaps being fully extended. After conversing with the Captain; I asked him to look at the QRH and he did so. I then took control of the aircraft and he ran the QRH. He too was somewhat confused as to the direction to take. He then called Dispatch to get clarification. It took an extremely long time to get someone with Dispatch and Maintenance. I am thinking about 10 minutes. By that time we had notified ATC we had leveled off at FL230 and were cruising at 230 KIAS. Finally; after speaking with Dispatch and Maintenance; it was agreed that we should return to departure airport. We turned around and landed without incident. After landing and re-reading the QRH in a non-time pressured type environment; we interpreted it to mean that even though there was no yaw and we felt it was an indication only; it still stated that we should consider the Kruger flap actually extended. In that case; we should have leveled off at FL200 instead of climbing to FL230. Compounding the problem was Dispatch not responding to our numerous requests for help and clarification of the direction to take.
Second reporter narrative
QRH note describes that a flap indication problem that cannot be visually confirmed must be considered as flaps extended. We were working this problem at FL230. If the flaps must be considered extended; then we have exceeded the aircraft flap limitation of FL200. This QRH is long and confusing with a long list on notes.
More incidents for this aircraft family →
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.