A dornier 328 was dispatched in non compliance with the propeller synchronization system deferred wi...

Attributes
ACN	538006
Time
Date	200202
Day	Wed
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : zzz.airport
State Reference	US
Altitude	agl single value : 0
Environment
Light	Daylight
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	Do 328 TP (Turboprop)
Operating Under FAR Part	Part 121
Flight Phase	ground : parked
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp pilot : cfi pilot : instrument pilot : multi engine
Experience	flight time last 90 days : 200 flight time total : 3100 flight time type : 2100
ASRS Report	538006
Person 2
Affiliation	company : air carrier
Function	other personnel other
Events
Anomaly	aircraft equipment problem : critical maintenance problem : non compliance with mel non adherence : far non adherence : published procedure
Independent Detector	aircraft equipment other aircraft equipment : prop sync circuit breaker other flight crewa
Resolutory Action	none taken : detected after the fact
Consequence	other
Factors
Maintenance	contributing factor : schedule pressure performance deficiency : non compliance with legal requirements performance deficiency : logbook entry performance deficiency : unqualified personnel
Supplementary
Problem Areas	Maintenance Human Performance Flight Crew Human Performance Chart Or Publication Aircraft
Primary Problem	Maintenance Human Performance

Narrative:

Got into company aircraft X for a roundtrip. Release showed propeller synch MEL'ed. At our company, MEL's can be found in 1 of 2 places in the logbook, where the actual discrepancy occurs or in the back on a card stock 'hard card' attached to logbook. I found the propeller sync entered on hard card. As I scanned the logbook for open discrepancies, I came across the original propeller sync entry. The corrective action said it had been MEL'ed and the 'M' function (maintenance) complied with. Since this was in the corrective action block, it signifies the item is on the hard card. I found the 'M function' entry odd because there was no 'M' function listed for propeller sync in the MEL. I didn't even think too much about it because the hard card was correct. I figured the 'M function' entry was force of habit. Flew the roundtrip. 10 mins from landing on second leg, I noticed out of the corner of my eye a circuit breaker collar over propeller sync. The MEL does not call for this. My heart sank as I remembered the 'M function' entry and realized that must've referenced the circuit breaker. Upon engine shutdown, I immediately phoned maintenance control. I think he had dealt with this earlier. He had an answer saying they did have the authority/authorized to pull breakers to deactivate system. He said it is granted in MEL. I was skeptical. Later I read the MEL policies. I phoned maintenance controller later. He also seemed well versed in the situation I was referencing and sad they do have that authority/authorized. He said if the previous maintenance controller misspoke when referencing the preamble for authority/authorized and also the 'M function' signoff probably was not the most appropriate verbiage, and led to the confusion most likely. I am still a bit skeptical. It makes sense, but neither maintenance controller offered me any evidence to support it in a challenge from, say an inspector.

Original NASA ASRS Text

Title: A DORNIER 328 WAS DISPATCHED IN NON COMPLIANCE WITH THE PROP SYNCHRONIZATION SYS DEFERRED WITH THE CIRCUIT BREAKER PULLED AND CAPPED IN CONFLICT WITH THE MEL.

Narrative: GOT INTO COMPANY ACFT X FOR A ROUNDTRIP. RELEASE SHOWED PROP SYNCH MEL'ED. AT OUR COMPANY, MEL'S CAN BE FOUND IN 1 OF 2 PLACES IN THE LOGBOOK, WHERE THE ACTUAL DISCREPANCY OCCURS OR IN THE BACK ON A CARD STOCK 'HARD CARD' ATTACHED TO LOGBOOK. I FOUND THE PROP SYNC ENTERED ON HARD CARD. AS I SCANNED THE LOGBOOK FOR OPEN DISCREPANCIES, I CAME ACROSS THE ORIGINAL PROP SYNC ENTRY. THE CORRECTIVE ACTION SAID IT HAD BEEN MEL'ED AND THE 'M' FUNCTION (MAINT) COMPLIED WITH. SINCE THIS WAS IN THE CORRECTIVE ACTION BLOCK, IT SIGNIFIES THE ITEM IS ON THE HARD CARD. I FOUND THE 'M FUNCTION' ENTRY ODD BECAUSE THERE WAS NO 'M' FUNCTION LISTED FOR PROP SYNC IN THE MEL. I DIDN'T EVEN THINK TOO MUCH ABOUT IT BECAUSE THE HARD CARD WAS CORRECT. I FIGURED THE 'M FUNCTION' ENTRY WAS FORCE OF HABIT. FLEW THE ROUNDTRIP. 10 MINS FROM LNDG ON SECOND LEG, I NOTICED OUT OF THE CORNER OF MY EYE A CIRCUIT BREAKER COLLAR OVER PROP SYNC. THE MEL DOES NOT CALL FOR THIS. MY HEART SANK AS I REMEMBERED THE 'M FUNCTION' ENTRY AND REALIZED THAT MUST'VE REFED THE CIRCUIT BREAKER. UPON ENG SHUTDOWN, I IMMEDIATELY PHONED MAINT CTL. I THINK HE HAD DEALT WITH THIS EARLIER. HE HAD AN ANSWER SAYING THEY DID HAVE THE AUTH TO PULL BREAKERS TO DEACTIVATE SYS. HE SAID IT IS GRANTED IN MEL. I WAS SKEPTICAL. LATER I READ THE MEL POLICIES. I PHONED MAINT CTLR LATER. HE ALSO SEEMED WELL VERSED IN THE SIT I WAS REFING AND SAD THEY DO HAVE THAT AUTH. HE SAID IF THE PREVIOUS MAINT CTLR MISSPOKE WHEN REFING THE PREAMBLE FOR AUTH AND ALSO THE 'M FUNCTION' SIGNOFF PROBABLY WAS NOT THE MOST APPROPRIATE VERBIAGE, AND LED TO THE CONFUSION MOST LIKELY. I AM STILL A BIT SKEPTICAL. IT MAKES SENSE, BUT NEITHER MAINT CTLR OFFERED ME ANY EVIDENCE TO SUPPORT IT IN A CHALLENGE FROM, SAY AN INSPECTOR.

Data retrieved from NASA's ASRS site as of July 2007 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.

A dornier 328 was dispatched in non compliance with the propeller synchronization system deferred with the circuit breaker pulled and capped in conflict with the MEL.