 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Technician reported that; during troubleshooting for an unrelated EICAS message; he found numerous circuit breakers pulled and collared and he reset them without documenting the corrective actions tasks in the aircraft logbook.
| Attributes | |
| ACN | 1682345 |
| Time | |
| Date | 201909 |
| Local Time Of Day | 0001-0600 |
| Place | |
| Locale Reference | ZZZ.Airport |
| State Reference | US |
| Environment | |
| Light | Night |
| Aircraft 1 | |
| Make Model Name | A320 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Parked |
| Flight Plan | IFR |
| Component | |
| Aircraft Component | Electrical Power |
| Person 1 | |
| Function | Technician |
| Qualification | Maintenance Airframe Maintenance Powerplant |
| Events | |
| Anomaly | Deviation - Procedural MEL Deviation - Procedural Maintenance Deviation - Procedural Published Material / Policy |
Narrative:
During morning gate calls. The lead received a call for maintenance at gate. I went up to the plane to find a fully boarded flight. The call was for a caution light on the fap (forward attendant panel.) I then performed a ground scan of the system and it flagged the fwd drain mast inop. I then checked the c/b for the drain mast on panel 2000vu and seen multiple c/b's pulled and collared. I then called maintenance control to tell them the problem I was having. He then checked to see if there were any open MEL's requiring those c/b's to be pulled. There were no open MEL's. So I reset the pulled c/b's. I performed the ground scan again and no faults were detected. I went back into the office and printed the ops test and bite test for those systems. And the checks were good. While writing the corrective action in the log book; I only stated the c/b that was flagged on the ground scan as being pulled (fwd drain mast). And I also did not reference all of the ops test that were performed into my write up.take your time and think everything out. Don't let the pressure of a fully boarded plane and taking a delay scare you.
Original NASA ASRS Text
Title: Technician reported that; during troubleshooting for an unrelated EICAS Message; he found numerous circuit breakers pulled and collared and he reset them without documenting the corrective actions tasks in the aircraft logbook.
Narrative: During morning gate calls. The lead received a call for maintenance at gate. I went up to the plane to find a fully boarded flight. The call was for a caution light on the FAP (Forward Attendant Panel.) I then performed a ground scan of the system and it flagged the fwd drain mast inop. I then checked the c/b for the drain mast on panel 2000vu and seen multiple c/b's pulled and collared. I then called maintenance control to tell them the problem I was having. He then checked to see if there were any open MEL'S requiring those c/b's to be pulled. There were no open MEL'S. So I reset the pulled c/b's. I performed the ground scan again and no faults were detected. I went back into the office and printed the ops test and bite test for those systems. And the checks were good. While writing the corrective action in the log book; I only stated the c/b that was flagged on the ground scan as being pulled (FWD DRAIN MAST). And I also did not reference all of the ops test that were performed into my write up.Take your time and think everything out. Don't let the pressure of a fully boarded plane and taking a delay scare you.
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.