![]() |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
| Attributes | |
| ACN | 1367496 |
| Time | |
| Date | 201606 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | ZZZ.Airport |
| State Reference | US |
| Environment | |
| Light | Dusk |
| Aircraft 1 | |
| Make Model Name | B737-700 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Parked |
| Flight Plan | IFR |
| Component | |
| Aircraft Component | FMS/FMC |
| Person 1 | |
| Function | Captain |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Experience | Flight Crew Last 90 Days 156 |
| Person 2 | |
| Function | First Officer |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Experience | Flight Crew Last 90 Days 194 |
| Events | |
| Anomaly | Aircraft Equipment Problem Less Severe Deviation - Procedural Published Material / Policy |
Narrative:
We obviously missed it on the first leg; however; during the before pushback checklist in ZZZ; I noticed the thrust reduction altitude for the autothrottles on takeoff 2/2 was 1500 AGL. I asked the first officer to correct the issue. Flight continued uneventfully. Same thing happened again in ZZZ1. We again corrected the issue.after discussion with the first officer during the flight; I felt a call to maintenance to discuss the issue was appropriate when we arrived in ZZZ1. I contacted dispatch; who patched in maintenance control. They had station maintenance come out to resolve the issue. I have written an incident report on the debacle that ensued getting the FMC software installed; but of note; it was also discovered that the wrong VNAV logic (full geo versus app geo) was also installed/selected.
Original NASA ASRS Text
Title: B737 flight crew reported an FMS anomaly in its database resulting in non-standard power reductions after takeoff.
Narrative: We obviously missed it on the first leg; however; during the Before Pushback Checklist in ZZZ; I noticed the thrust reduction altitude for the autothrottles on takeoff 2/2 was 1500 AGL. I asked the First Officer to correct the issue. Flight continued uneventfully. Same thing happened again in ZZZ1. We again corrected the issue.After discussion with the First Officer during the flight; I felt a call to Maintenance to discuss the issue was appropriate when we arrived in ZZZ1. I contacted Dispatch; who patched in Maintenance Control. They had Station Maintenance come out to resolve the issue. I have written an incident report on the debacle that ensued getting the FMC software installed; but of note; it was also discovered that the wrong VNAV logic (FULL GEO versus APP GEO) was also installed/selected.
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.