37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1718288 |
Time | |
Date | 202001 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | EMB ERJ 170/175 ER/LR |
Operating Under FAR Part | Part 121 |
Flight Phase | Parked |
Flight Plan | IFR |
Component | |
Aircraft Component | Integrated Audio System |
Person 1 | |
Function | Technician |
Qualification | Maintenance Airframe Maintenance Powerplant |
Events | |
Anomaly | Aircraft Equipment Problem Critical Deviation - Procedural Published Material / Policy Deviation - Procedural MEL |
Narrative:
We had plane XXXX that had been placed on a grounded status due to the first officer (first officer) having communication errors. The captain could hear the first officer but the first officer could not hear the captain. This issue was happening across VHF 1; 2 and 3. We 1st tried to re-stow the first officer's oxygen mask which did not correct the problem. Then we swapped headsets; the digital audio panel; and the mic jacks with no luck. Maintenance control decided that we needed to try swapping comm 1 and 2. That swap did not work as well; so maintenance control decided that we needed to replace nim ii. The network interface module was looked up in the maintenance manual doing a aircraft specific search and verifying it in maintenance software under component replacement. The search came up which we did not have at our station but it had an alternate which we did have at our station. So with time constraints upon us we chose the nim and proceeded to change nim ii. The nim was installed and target load was completed without an issue. Replacing the nim ii did not fix the first officer's comm issue. I decided to leave the newly installed nim on the plane and place the nim that was taken off the plane in the save program. When we returned to the office the 1st shift had arrived; so we turned over the grounded plane to the next shift to further troubleshoot. Upon the next shift trying to return the nim they found that they could not due to the nim not being applicable to the plane even though it could be used for an alternate. We found that the nim was to be used with a pentium M processor and on plane it uses a pentium ii processor. I immediately contacted ZZZ where the plane was to land that night to be a ron and advised them that the wrong network interface module was replaced on aircraft and if they could change it once the plane arrived. They advised me that they would and the nim ii was replaced with the correct pin which was for a pentium ii.
Original NASA ASRS Text
Title: Technician reported installing the incorrect part on aircraft due to misreading the manual.
Narrative: We had plane XXXX that had been placed on a Grounded status due to the FO (First Officer) having communication errors. The Captain could hear the FO but the FO could not hear the Captain. This issue was happening across VHF 1; 2 and 3. We 1st tried to re-stow the FO's oxygen mask which did not correct the problem. Then we swapped headsets; the Digital Audio Panel; and the mic jacks with no luck. Maintenance Control decided that we needed to try swapping COMM 1 and 2. That swap did not work as well; so Maintenance Control decided that we needed to replace NIM II. The network interface module was looked up in the maintenance manual doing a aircraft specific search and verifying it in Maintenance Software under component replacement. The search came up which we did not have at our station but it had an alternate which we did have at our station. So with time constraints upon us we chose the NIM and proceeded to change NIM II. The NIM was installed and target load was completed without an issue. Replacing the NIM II did not fix the FO's comm issue. I decided to leave the newly installed NIM on the plane and place the NIM that was taken off the plane in the SAVE program. When we returned to the office the 1st shift had arrived; so we turned over the Grounded plane to the next shift to further troubleshoot. Upon the next shift trying to return the NIM they found that they could not due to the NIM not being applicable to the plane even though it could be used for an alternate. We found that the NIM was to be used with a Pentium M processor and on plane it uses a Pentium II processor. I immediately contacted ZZZ where the plane was to land that night to be a RON and advised them that the wrong network interface module was replaced on Aircraft and if they could change it once the plane arrived. They advised me that they would and the NIM II was replaced with the correct pin which was for a Pentium II.
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.