CL65 crew had improper aircraft maintenance on chronic system problems at tri.

Attributes
ACN	491177
Time
Date	200010
Day	Sat
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : tri.airport
State Reference	TN
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tower : cre.tower
Operator	common carrier : air carrier
Make Model Name	Regional Jet CL65, Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	ground : parked
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp pilot : multi engine pilot : instrument
Experience	flight time last 90 days : 250 flight time total : 8000 flight time type : 2000
ASRS Report	491177
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : instrument pilot : multi engine pilot : commercial
Events
Anomaly	aircraft equipment problem : less severe maintenance problem : improper maintenance maintenance problem : non compliance with mel non adherence : far non adherence : published procedure other anomaly other
Independent Detector	other flight crewa other flight crewb
Resolutory Action	none taken : anomaly accepted
Consequence	other
Factors
Maintenance	contributing factor : schedule pressure performance deficiency : non compliance with legal requirements performance deficiency : fault isolation performance deficiency : repair
Supplementary
Problem Areas	Company Maintenance Human Performance
Primary Problem	Company

Narrative:

After landing, several faults were annunciated including: failure of flight director, and a yaw damper system. I had flown the same aircraft 2 days earlier and had encountered exactly the same problem. It had been cleared and signed off by resetting circuit breakers. This time I checked past history in the logbook and found 8 identical write-ups within the pervious 40 days. Almost all had been signed off the same way, with a circuit breaker reset. This time I noted the reference to the other prior write-ups in my log entry. To my surprise, the write-up signed off the same way again, with a circuit breaker reset. I was told the aircraft would be back through for maintenance in a couple of days and the problem would be looked at more thoroughly. This looks to me like a 40 day deferral with no MEL authority/authorized or deferral record.

Original NASA ASRS Text

Title: CL65 CREW HAD IMPROPER ACFT MAINT ON CHRONIC SYS PROBS AT TRI.

Narrative: AFTER LNDG, SEVERAL FAULTS WERE ANNUNCIATED INCLUDING: FAILURE OF FLT DIRECTOR, AND A YAW DAMPER SYS. I HAD FLOWN THE SAME ACFT 2 DAYS EARLIER AND HAD ENCOUNTERED EXACTLY THE SAME PROB. IT HAD BEEN CLRED AND SIGNED OFF BY RESETTING CIRCUIT BREAKERS. THIS TIME I CHKED PAST HISTORY IN THE LOGBOOK AND FOUND 8 IDENTICAL WRITE-UPS WITHIN THE PERVIOUS 40 DAYS. ALMOST ALL HAD BEEN SIGNED OFF THE SAME WAY, WITH A CIRCUIT BREAKER RESET. THIS TIME I NOTED THE REF TO THE OTHER PRIOR WRITE-UPS IN MY LOG ENTRY. TO MY SURPRISE, THE WRITE-UP SIGNED OFF THE SAME WAY AGAIN, WITH A CIRCUIT BREAKER RESET. I WAS TOLD THE ACFT WOULD BE BACK THROUGH FOR MAINT IN A COUPLE OF DAYS AND THE PROB WOULD BE LOOKED AT MORE THOROUGHLY. THIS LOOKS TO ME LIKE A 40 DAY DEFERRAL WITH NO MEL AUTH OR DEFERRAL RECORD.

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.