 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Air carrier first officer reported the terrain height for a mountain near mmpr is incorrect on aircraft display due to a software error.
| Attributes | |
| ACN | 1610376 |
| Time | |
| Date | 201901 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | MMPR.Airport |
| State Reference | FO |
| Environment | |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | Commercial Fixed Wing |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Climb |
| Route In Use | Vectors Direct |
| Flight Plan | IFR |
| Person 1 | |
| Function | First Officer Pilot Not Flying |
| Qualification | Flight Crew Multiengine Flight Crew Instrument Flight Crew Air Transport Pilot (ATP) |
| Experience | Flight Crew Last 90 Days 370 Flight Crew Type 10117 |
| Events | |
| Anomaly | Deviation - Procedural Published Material / Policy |
Narrative:
Known terrain at mmpr directly under an arrival and also near a departure is higher than what is in our database. Database shows 4;300 feet but the mountain is actually 4;642 feet MSL. Arrival and departure altitudes appear to be correct for terpz purposes; but a stray crew in trouble would not know they needed to be above 4;700 feet based on the data being too low in our database. They would be judging against 4;300 feet on the aircraft scope. Point in question is pvr 360/14. West of muvba by about four miles. It shows altitude on rnp runway 22; VOR runways 2 and 3 to 22. The problem is not with our jepp FD-pro charts; but with our database. The aircraft shows the peak in the correct location; just not the correct altitude. If the crew stays on jepp FD-pro it is ok; but the backup safety system not serving as designed. This is one of our chances to prove our data lines up; but in this case it fails. The error is relatively minor in this case; but it is worrisome. How many other points are incorrect this way and perhaps the magnitude is different. The database owner should rectify this [elevation] problem. Who owns the data? Who fixes the data? Who assures us the amount of data could be different from reality? What risk is the pilot assuming? What risk is the company assuming? The company needs to push more information so we can choose correctly.
Original NASA ASRS Text
Title: Air carrier First Officer reported the terrain height for a mountain near MMPR is incorrect on aircraft display due to a software error.
Narrative: Known terrain at MMPR directly under an arrival and also near a departure is higher than what is in our database. Database shows 4;300 feet but the mountain is actually 4;642 feet MSL. Arrival and departure altitudes appear to be correct for TERPZ purposes; but a stray crew in trouble would not know they needed to be above 4;700 feet based on the data being too low in our database. They would be judging against 4;300 feet on the aircraft scope. Point in question is PVR 360/14. West of MUVBA by about four miles. It shows altitude on RNP Runway 22; VOR Runways 2 and 3 to 22. The problem is not with our Jepp FD-Pro charts; but with our database. The aircraft shows the peak in the correct location; just not the correct altitude. If the crew stays on Jepp FD-Pro it is ok; but the backup safety system not serving as designed. This is one of our chances to prove our data lines up; but in this case it fails. The error is relatively minor in this case; but it is worrisome. How many other points are incorrect this way and perhaps the magnitude is different. The database owner should rectify this [elevation] problem. Who owns the data? Who fixes the data? Who assures us the amount of data could be different from reality? What risk is the pilot assuming? What risk is the company assuming? The company needs to push more information so we can choose correctly.
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.