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.

Google
 

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.