A B757-200 was possibly dispatched in non compliance with an alleged incorrect rudder ratio check ac...

Attributes
ACN	530017
Time
Date	200111
Day	Mon
Place
Locale Reference	airport : zzz.airport
State Reference	US
Altitude	agl single value : 0
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	B757-200
Operating Under FAR Part	Part 121
Flight Phase	cruise : level ground : maintenance
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
ASRS Report	530017
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer maintenance : technician
Events
Anomaly	aircraft equipment problem : critical maintenance problem : improper documentation maintenance problem : improper maintenance non adherence : published procedure non adherence : far
Independent Detector	other flight crewa other flight crewb
Resolutory Action	none taken : detected after the fact
Consequence	other other
Factors
Maintenance	contributing factor : schedule pressure performance deficiency : testing performance deficiency : non compliance with legal requirements performance deficiency : logbook entry performance deficiency : fault isolation
Supplementary
Problem Areas	Flight Crew Human Performance Maintenance Human Performance Aircraft Company
Primary Problem	Maintenance Human Performance

Narrative:

The aircraft overnighted at ZZZ1 and there was some maintenance performed. I checked the logbook and checked the signoff for the rudder ratio EICAS message against the MEL. There was a required check of the system before the aircraft could depart. Maintenance was notified, and did the required check and made the entry in the logbook. We departed the gate, and flew to ZZZ2. During the flight, I looked at the procedure that maintenance performed, and I think that they did a rudder ratio light procedure, and not the EICAS message procedure. I alerted ZZZ2 maintenance concerning this, and was assured that the proper signoff would be done. When I returned to ZZZ3, I pulled up the data and I do not believe that the proper signoff was ever done. I called ZZZ4 technician and alerted them that they might have an aircraft flying around that had an improper signoff and they told me that they would take care of it.

Original NASA ASRS Text

Title: A B757-200 WAS POSSIBLY DISPATCHED IN NON COMPLIANCE WITH AN ALLEGED INCORRECT RUDDER RATIO CHK ACCOMPLISHED.

Narrative: THE ACFT OVERNIGHTED AT ZZZ1 AND THERE WAS SOME MAINT PERFORMED. I CHKED THE LOGBOOK AND CHKED THE SIGNOFF FOR THE RUDDER RATIO EICAS MESSAGE AGAINST THE MEL. THERE WAS A REQUIRED CHK OF THE SYS BEFORE THE ACFT COULD DEPART. MAINT WAS NOTIFIED, AND DID THE REQUIRED CHK AND MADE THE ENTRY IN THE LOGBOOK. WE DEPARTED THE GATE, AND FLEW TO ZZZ2. DURING THE FLT, I LOOKED AT THE PROC THAT MAINT PERFORMED, AND I THINK THAT THEY DID A RUDDER RATIO LIGHT PROC, AND NOT THE EICAS MESSAGE PROC. I ALERTED ZZZ2 MAINT CONCERNING THIS, AND WAS ASSURED THAT THE PROPER SIGNOFF WOULD BE DONE. WHEN I RETURNED TO ZZZ3, I PULLED UP THE DATA AND I DO NOT BELIEVE THAT THE PROPER SIGNOFF WAS EVER DONE. I CALLED ZZZ4 TECHNICIAN AND ALERTED THEM THAT THEY MIGHT HAVE AN ACFT FLYING AROUND THAT HAD AN IMPROPER SIGNOFF AND THEY TOLD ME THAT THEY WOULD TAKE CARE OF IT.

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 B757-200 was possibly dispatched in non compliance with an alleged incorrect rudder ratio check accomplished.