37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1302002 |
Time | |
Date | 201510 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | ZOA.ARTCC |
State Reference | CA |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Large Transport |
Operating Under FAR Part | Part 121 |
Flight Phase | Cruise |
Flight Plan | IFR |
Component | |
Aircraft Component | Navigation Database |
Person 1 | |
Function | Pilot Not Flying Captain |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 135 Flight Crew Type 135 |
Person 2 | |
Function | First Officer Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 151 |
Events | |
Anomaly | Aircraft Equipment Problem Less Severe Deviation - Procedural Published Material / Policy |
Narrative:
During briefing and preparation for arrival; we discovered the altitudes on the arrival did not match the FMC. Upon checking the database we found the [future] database to be active. We verified the fixes and altitudes on the arrival and approach and proceeded without incident. At the gate; maintenance verified that they had done a navigation update the night before. It seems the new database was put in the current use line prematurely by maintenance during the update. We missed the error during our preflight.
Original NASA ASRS Text
Title: The crew noticed an altitude discrepancy between the Electric Flight Bag (EFB) and the FMC on the arrival procedure. It was determined that maintenance had updated the database the night before and had prematurely activated that new revision.
Narrative: During briefing and preparation for arrival; we discovered the altitudes on the arrival did not match the FMC. Upon checking the database we found the [future] database to be active. We verified the fixes and altitudes on the arrival and approach and proceeded without incident. At the gate; Maintenance verified that they had done a NAV update the night before. It seems the new database was put in the current use line prematurely by Maintenance during the update. We missed the error during our preflight.
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.