 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Air carrier first officer reported database update issues while transiting through brazilian airspace. Crew were cleared to waypoints not in the updated database.
| Attributes | |
| ACN | 1478423 |
| Time | |
| Date | 201708 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | SBGR.Airport |
| State Reference | FO |
| Aircraft 1 | |
| Make Model Name | Widebody Low Wing 2 Turbojet Eng |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Taxi |
| Flight Plan | IFR |
| Component | |
| Aircraft Component | Navigation Database |
| Person 1 | |
| Function | First Officer Pilot Not Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy |
Narrative:
Scheduled to depart ZZZ. A new nav database was valid. As we were not sure which database to use we consulted the flight manual which stated that the database changed; and if that was during the flight we could elect either database; but we would have to verify everything for the time the database was outdated. As we were arriving right after this time we elected to use the old database. We only received a partial route uplink. We consulted with dispatch and they stated that the new database was effective and there were new airways through brazil. So we switched to the new database. We then were able to load the full clearance. We were cleared as filed. Enroute [ATC] asked our route and informed us that the airways and waypoints we were filed on didn't exist. Further; they attempted to clear us to waypoints that we no longer had in our database. We were finally able to get a clearance to a waypoint that was at the end of brazilian airspace; and we had no problems after that. I submitted a [report] asking if the fom the brazilian controllers [were using] were correct; or if dispatch was correct concerning the time the new database was effective.
Original NASA ASRS Text
Title: Air carrier First Officer reported database update issues while transiting through Brazilian airspace. Crew were cleared to waypoints not in the updated database.
Narrative: Scheduled to depart ZZZ. A new Nav database was valid. As we were not sure which database to use we consulted the Flight Manual which stated that the database changed; and if that was during the flight we could elect either database; but we would have to verify everything for the time the database was outdated. As we were arriving right after this time we elected to use the old database. We only received a partial route uplink. We consulted with dispatch and they stated that the new database was effective and there were new airways through Brazil. So we switched to the new database. We then were able to load the full clearance. We were cleared as filed. Enroute [ATC] asked our route and informed us that the airways and waypoints we were filed on didn't exist. Further; they attempted to clear us to waypoints that we no longer had in our database. We were finally able to get a clearance to a waypoint that was at the end of Brazilian airspace; and we had no problems after that. I submitted a [report] asking if the FOM the Brazilian controllers [were using] were correct; or if dispatch was correct concerning the time the new database was effective.
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.