37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1013411 |
Time | |
Date | 201205 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Environment | |
Light | Daylight |
Aircraft 1 | |
Make Model Name | A300 |
Operating Under FAR Part | Part 121 |
Flight Phase | Parked |
Component | |
Aircraft Component | Navigation Database |
Person 1 | |
Function | Technician |
Qualification | Maintenance Avionics |
Events | |
Anomaly | Aircraft Equipment Problem Critical Deviation - Procedural Published Material / Policy |
Narrative:
Went out [during] pre departure to load a navigation (navigation) database update and loaded XX5-0006 and should have loaded XX3-0006. [Approximately] four hours later; flight crew noticed there was a problem loading the ZZZ1 identifier into the flight plan. I was dispatched to the aircraft and placed the navigation database on MEL. After completing the database load; checked the control display unit (CDU) for the current software load. I was looking for the -0006 in the software code as documented in the maintenance item and it was there for both flight management computers (fmcs).recommend: 1) they need to state the whole number of the navigation database software: example XX3-0006 on the maintenance item. 2) the software disks XX3-0006 and the XX5-0006 were in the same drawer and were the same color. Note* since this mistake happened; a divider has been incorporated to separate XX3-0006 and XX5-0006 disks from each other. Also; on the divider it is clearly labeled 'FMS ferry'. This label helps identify what is in the divider drawer. The lead and I decided to take these corrective actions to prevent future mistakes.
Original NASA ASRS Text
Title: An Avionics Technician reports that he mistakenly loaded incorrect Navigation (NAV) Database software into the FMCs on an A300 aircraft.
Narrative: Went out [during] pre departure to load a Navigation (NAV) Database update and loaded XX5-0006 and should have loaded XX3-0006. [Approximately] four hours later; flight crew noticed there was a problem loading the ZZZ1 identifier into the flight plan. I was dispatched to the aircraft and placed the NAV Database on MEL. After completing the database load; checked the Control Display Unit (CDU) for the current software load. I was looking for the -0006 in the software code as documented in the Maintenance item and it was there for both Flight Management Computers (FMCs).Recommend: 1) They need to state the whole number of the NAV Database software: example XX3-0006 on the Maintenance item. 2) The software disks XX3-0006 and the XX5-0006 were in the same drawer and were the same color. NOTE* since this mistake happened; a divider has been incorporated to separate XX3-0006 and XX5-0006 disks from each other. Also; on the divider it is clearly labeled 'FMS FERRY'. This label helps identify what is in the divider drawer. The Lead and I decided to take these corrective actions to prevent future mistakes.
Data retrieved from NASA's ASRS site as of July 2013 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.