Narrative:

B737-700 aircraft had a proximity sensor electronics unit (pseu) light illuminated after landing in ZZZ1. I contacted contract maintenance and the mechanic performed a pseu bite check to see what was causing the light. The fault codes reported were 32-62014 (landing flap a and B disagree) and a 32-64004 (do not dispatch). Because of the do not dispatch message; I advised the mechanic we had to look at the root cause which was the flap landing warning switch. I sent him the required fault isolation manual (fim) task and he performed the task and inspected the switch. I advised him to clean and actuate the switch and do the fim task again. The fault cleared and it was signed-off. Approximately 10 minutes after the logbook was signed; the pseu light re-illuminated so I advised the mechanic to perform another bite check on the pseu. The same fault codes as before came back. Because of the do not dispatch fault; I determined that the aircraft was now aircraft on ground (aog). I asked the mechanic if he could standby; while I began to search for a replacement part. He agreed to stay to help me. After determining that a part was not available locally and having two in our air carrier's stock in ZZZ; I began preparing for the aircraft to overnight in ZZZ1 until the part would arrive. Soon after; I found our air carrier's maintenance manual supplement that allowed for the spare contacts in the switch to be used. I called the mechanic and asked if he would be able to perform the task and he again agreed to help me. I sent him the maintenance manual supplement and the associated boeing wiring diagram manual (wdm) and he performed the task flawlessly and retested the flap landing warning switch system to confirm the repair. There were no faults; so I advised him that we could now sign-off the second write-up in the logbook. The last step of the maintenance manual supplement states that company maintenance control will create a deferred maintenance item (dmi) to track the use of the spare contacts in the switch. I knew that the [acronym] 'dmi' needed to be revised to maintenance tracking item (mti); since our air carrier implemented a new maintenance tracking and compliance system and placed the spare contacts on mti for tracking purposes with the mechanic. The aircraft departed three hours and 33 minutes late without incident. I discovered after the fact; the next night; that there is indeed an MEL for using the spare contacts for the S138 switch; but I was unaware that MEL 32-21 existed. Because of the do not dispatch message [that] the pseu was faulting; I never checked the MEL to see if there was any relief because I considered the do not dispatch message an aog situation. After finding the maintenance manual supplement to correct the problem (air carrier supplemental aircraft maintenance manual (samm) 27-51-00); I generated the tracking item that it called out for. I never considered that a repair to the [flap landing warning switch] system; with a satisfactory operational check would have required an MEL for a now perfectly operating system; so I never looked at the MEL. After reviewing the MEL the next night; the repair outcome of the MEL dispatch deviation guide (ddg) maintenance procedure (MEL 32-21 and amm 32-00-00-040) is the same as the maintenance manual supplement (air carrier samm 27-51-00). A company maintenance request has been submitted to change the statement at the end of the samm to indicate to place the S138 switch on MEL 32-21 rather than a dmi and change the dmi to mti for the other two switches in the samm. I would also like it noted that the mechanics involved in this; performed everything under my advisement and should not be held accountable for my mistake. In order to prevent an event like this from happening again; I will remember to reference the MEL first to see if there is MEL relief available. I also would like to note that MEL 32-17 for the pseu light does reference you to the 32-21 MEL in regards to; if you have a do not dispatch message. Perhaps there could be a better way to make this more noticeable because do not dispatch generally means an aog situation and the MEL may not be looked at (i.e. My mistake). When you type in the fault code for the fim reference; there is no mention of the MEL relief available for the S138 switch. In my opinion; the manuals related to a S138 switch failure do not guide you to this MEL; so if not consulting the MEL first; the MEL relief for this switch can easily be missed. MEL 32-17-C. 'Do not dispatch' message #32-64004 - dispatch is not allowed. If messages #32-62009; 32-62109; 32-62010; 32-62110; or 32-62014 are also displayed; refer to MEL item 32-21; flap landing warning switch. The bottom line is; if all of the referenced manual steps matched each other; or even referenced that MEL 32-21 should be consulted; if using the spare switch contact option; I think that it would not have been missed.

Related reports:

Google
 

Original NASA ASRS Text

Title: A Maintenance Controller was informed he should have applied MEL 32-17 to a B737-700 aircraft for a Flap Landing Warning Switch S-138 repair he had directed; instead of using their Maintenance Tracking Item procedures. The Proximity Sensor Electronics Unit (PSEU) light and Master Caution light had previously illuminated after landing.

Narrative: B737-700 aircraft had a Proximity Sensor Electronics Unit (PSEU) light illuminated after landing in ZZZ1. I contacted Contract Maintenance and the Mechanic performed a PSEU BITE Check to see what was causing the light. The Fault Codes reported were 32-62014 (Landing Flap A and B disagree) and a 32-64004 (DO NOT DISPATCH). Because of the DO NOT DISPATCH message; I advised the Mechanic we had to look at the root cause which was the Flap Landing Warning Switch. I sent him the required Fault Isolation Manual (FIM) Task and he performed the task and inspected the switch. I advised him to clean and actuate the switch and do the FIM Task again. The Fault cleared and it was signed-off. Approximately 10 minutes after the logbook was signed; the PSEU light re-illuminated so I advised the Mechanic to perform another BITE Check on the PSEU. The same fault codes as before came back. Because of the DO NOT DISPATCH fault; I determined that the aircraft was now Aircraft On Ground (AOG). I asked the Mechanic if he could standby; while I began to search for a replacement part. He agreed to stay to help me. After determining that a part was not available locally and having two in our Air Carrier's stock in ZZZ; I began preparing for the aircraft to overnight in ZZZ1 until the part would arrive. Soon after; I found our Air Carrier's Maintenance Manual Supplement that allowed for the spare contacts in the switch to be used. I called the Mechanic and asked if he would be able to perform the Task and he again agreed to help me. I sent him the Maintenance Manual Supplement and the associated Boeing wiring Diagram Manual (WDM) and he performed the Task flawlessly and retested the Flap Landing Warning Switch System to confirm the repair. There were no faults; so I advised him that we could now sign-off the second write-up in the logbook. The last step of the Maintenance Manual Supplement states that company Maintenance Control will create a Deferred Maintenance Item (DMI) to track the use of the spare contacts in the switch. I knew that the [acronym] 'DMI' needed to be revised to Maintenance Tracking Item (MTI); since our Air Carrier implemented a new Maintenance Tracking and Compliance System and placed the spare contacts on MTI for tracking purposes with the mechanic. The aircraft departed three hours and 33 minutes late without incident. I discovered after the fact; the next night; that there is indeed an MEL for using the spare contacts for the S138 Switch; but I was unaware that MEL 32-21 existed. Because of the DO NOT DISPATCH message [that] the PSEU was faulting; I never checked the MEL to see if there was any relief because I considered the DO NOT DISPATCH message an AOG situation. After finding the Maintenance Manual Supplement to correct the problem (Air Carrier Supplemental Aircraft Maintenance Manual (SAMM) 27-51-00); I generated the tracking item that it called out for. I never considered that a repair to the [Flap Landing Warning Switch] System; with a satisfactory Operational Check would have required an MEL for a now perfectly operating system; so I never looked at the MEL. After reviewing the MEL the next night; the repair outcome of the MEL Dispatch Deviation Guide (DDG) Maintenance Procedure (MEL 32-21 and AMM 32-00-00-040) is the same as the Maintenance Manual Supplement (Air Carrier SAMM 27-51-00). A Company Maintenance request has been submitted to change the statement at the end of the SAMM to indicate to place the S138 Switch on MEL 32-21 rather than a DMI and change the DMI to MTI for the other two switches in the SAMM. I would also like it noted that the mechanics involved in this; performed everything under my advisement and should not be held accountable for my mistake. In order to prevent an event like this from happening again; I will remember to reference the MEL first to see if there is MEL relief available. I also would like to note that MEL 32-17 for the PSEU light does reference you to the 32-21 MEL in regards to; if you have a DO NOT DISPATCH message. Perhaps there could be a better way to make this more noticeable because DO NOT DISPATCH generally means an AOG situation and the MEL may not be looked at (i.e. my mistake). When you type in the fault code for the FIM reference; there is no mention of the MEL relief available for the S138 Switch. In my opinion; the manuals related to a S138 Switch failure do not guide you to this MEL; so if not consulting the MEL first; the MEL relief for this switch can easily be missed. MEL 32-17-C. 'DO NOT DISPATCH' message #32-64004 - dispatch is not allowed. If messages #32-62009; 32-62109; 32-62010; 32-62110; or 32-62014 are also displayed; refer to MEL Item 32-21; Flap Landing Warning Switch. The bottom line is; if all of the referenced Manual steps matched each other; or even referenced that MEL 32-21 should be consulted; if using the spare switch contact option; I think that it would not have been missed.

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.