MD-11 Technician reported communications issues caused an extended aircraft delay due to an MEL not having been processed correctly during maintenance.

Date: 2022-06 · Aircraft: MD-11

Anomalies: aircraft-equipment-problem-critical|deviation-discrepancy-procedural-far|deviation-discrepancy-procedural-mel-cdl|deviation-discrepancy-procedural-maintenance|deviation-discrepancy-procedural-published-material-policy

Synopsis

MD-11 Technician reported communications issues caused an extended aircraft delay due to an MEL not having been processed correctly during maintenance.

Narrative

Aircraft X arrived in ZZZ with a pilot write up for #2 Full authority Digital Electronic Control (FADEC) ALTN followed Quick Reference Handbook (QRH) procedures and no help. Upon troubleshooting found multiple flight legs showing faults in both EEC2A and EEC2B which would be cause for an OOS (Out of Service) event due to being unable to defer the FADEC. I relayed this information to my Supervisor and was asked to stay late and assist the other mechanics as I was the only qualified; eligible mechanic on the MD-11 that evening. I informed my Supervisor that I had a TDY in the morning and that I had to drive to my TDY location and would not be able to stay. I found that 2 mechanics Person A and Person B were forced to stay and replace a Relay that Maintenance Control believed to be the cause of the issue. I decided that I would stay and assist them with the engine runs as they were unfortunate enough to be forced incorrectly based on the rules which state the least senior mechanics on shift were supposed to be forced.Person A and Person B changed the relay and I performed the Engine Runs on #2; during the runs no faults were noted and after 5 mins I shut down the engine and checked for faults in EEC2A and EEC2B; only EEC2B showed a fault for 2.95 BLD which I informed my Supervisor of and upon him speaking with Maintenance Control we found this was a deferrable issue. During the process of signing the logbook; my Supervisor handed me the MEL required and said he was speaking with Maintenance Control about the deferral. Person A signed off the Replacement of the relay and began documenting the fault and MEL on the following step leaving blank the SOT for the Control Number once the MEL was called in. It was at this moment that my Supervisor informed us that the airplane was being placed OOS for a Possible HYD leak in the tail; this caused myself; Person A and Person B to speak up as to why then be forced to fix an issue that would cause the airplane to go OOS if he was going to put it OOS regardless. After this discussion with my Supervisor we all called fatigue and decided to leave and work the aircraft in the morning since it would be OOS and I would travel on TDY in the morning. During this time and lack of communication I failed to call Maintenance Control to document the MEL procedure and receive a control number for the MEL. After 2 days I received a phone call today; from the ZZZ NDA supervisor advising me that they were trying to impact the paperwork for Aircraft X and were unable to impact the MEL as there was no Control Number for it. I contacted Maintenance Control and explained to them what had happened and that I had dropped the ball by documenting the fault and corrective action but failed to contact them for the deferral; it was at this time that I was informed by Maintenance Control that due to me being on TDY at another gateway; I could not legally document the Deferral for an Aircraft in ZZZ; and it would have to be redone in ZZZ.

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.