 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
B737-800 captain reported catching an error in the FMC data link that called for flaps 1 when the correct setting was flaps 5.
| Attributes | |
| ACN | 1411111 |
| Time | |
| Date | 201612 |
| Local Time Of Day | 0601-1200 |
| Place | |
| Locale Reference | ZZZ.Airport |
| State Reference | US |
| Aircraft 1 | |
| Make Model Name | B737-800 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Taxi |
| Flight Plan | IFR |
| Person 1 | |
| Function | Captain Pilot Not Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Events | |
| Anomaly | Deviation - Procedural Published Material / Policy Deviation - Procedural Weight And Balance |
Narrative:
Upon receiving the close-out we noticed the data uplinked to the FMC showed an incorrect flap setting of flaps 1. The planned flap setting was flaps 5. The FMC data uplink to the jet showed flaps 1; but the speeds were for flaps 5. We both cross-checked the data with the takeoff performance system (tps). The numbers were within 1 knot of the flap 5 speeds the weights matched closely. We over-rode the flap 1 indication in the FMC and inserted flaps 5 to match the tps. We made the take-off with flaps 5 as per the tps and over-rode the incorrectly uplinked flaps 1 indication to show flaps 5 in the FMC.uplink error or input error from loads I suspect.I have seen erroneous flap settings in the uplinked FMC data before. This could present a problem if crews are not alert to catch the error.this is always a potential problem with the long flight schedules for 2-pilot crews flying multi-leg days with the advent of far 117. In fact; on this day; we were scheduled to fly 8 hours and 33 minutes. Illegal for years until far 117 replaced far 121; ostensibly to give crews more rest. We had just begun our day; so we were alert and caught the error. Performing a take-off with flaps 1; but with flaps 5 speeds (as uplinked); could be very dangerous.
Original NASA ASRS Text
Title: B737-800 Captain reported catching an error in the FMC data link that called for Flaps 1 when the correct setting was Flaps 5.
Narrative: Upon receiving the close-out we noticed the data uplinked to the FMC showed an incorrect flap setting of flaps 1. The planned flap setting was flaps 5. The FMC data uplink to the jet showed flaps 1; but the speeds were for flaps 5. We both cross-checked the data with the Takeoff Performance System (TPS). The numbers were within 1 knot of the flap 5 speeds the weights matched closely. We over-rode the flap 1 indication in the FMC and inserted flaps 5 to match the TPS. We made the take-off with flaps 5 as per the TPS and over-rode the incorrectly uplinked flaps 1 indication to show flaps 5 in the FMC.Uplink error or input error from loads I suspect.I have seen erroneous flap settings in the uplinked FMC data before. This could present a problem if crews are not alert to catch the error.This is always a potential problem with the long flight schedules for 2-pilot crews flying multi-leg days with the advent of FAR 117. In fact; on this day; we were scheduled to fly 8 hours and 33 minutes. Illegal for years until FAR 117 replaced FAR 121; ostensibly to give crews more rest. We had just begun our day; so we were alert and caught the error. Performing a take-off with flaps 1; but with flaps 5 speeds (as uplinked); could be very dangerous.
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.