A B737-400 logbook was inspected by an FAA aci and found no signoff in the airworthiness block. A re...

Narrative:

On aug/xa/97 at approximately XA30, I signed off a 'transit check' on air carrier aircraft YYY. The airworthiness block was signed off then also. I entered the information into the computer, marked the yellow (original) logsheet for such entries, pulled the yellow sheet from the logbook, and advanced to the next yellow logsheet. The logbook was returned to the aircraft for an XB50 departure from ZZZ to xyz. The log page I pulled out of the logbook was placed with my completed transit check paperwork where the lead mechanic doublechks paperwork, then the yellow logsheet is faxed to air carrier records in xyz. Then the problem arose when aircraft arrived in xyz and the FAA met it for a ramp inspection. Upon inspecting the logbook, the white copy page did not reflect the airworthiness block being signed off. Air carrier uses a 'carbonless copy' type logbook. The copy page (white) did not pick up the signoff. The original log page had the airworthiness signed off. More confusion came about when the FAA wanted to see the faxed copy. Aircraft records 'couldn't find' their copy of the log page. ZZZ was called and the original logsheet was taken out of company mail and refaxed to xyz to review. It is my knowledge that at this time the FAA is not satisfied with the chain of events and has this matter under review. Callback conversation with reporter revealed the following information: reporter states this logbook white sheet is a problem because any work or checks accomplished on the airplane is entered on the white logbook sheet and then when all the entries are complete, the white sheet is torn from the logbook. The reporter said any entry on the white sheet is supposed to be copied onto the yellow sheet underneath and remain in the logbook -- this does not always happen. The reporter stated the logbook is called a carbonless copy type logbook. Reporter advised it was later proved the airworthiness block was signed.

Original NASA ASRS Text

Title: A B737-400 LOGBOOK WAS INSPECTED BY AN FAA ACI AND FOUND NO SIGNOFF IN THE AIRWORTHINESS BLOCK. A RECHK OF THE PAPERWORK AT THE DOWNLINE STATION VERIFIED SIGNOFF BUT WHITE LOG PAGE DID NOT COPY ONTO SHEET REMAINING IN LOG. AN ONGOING PROB.

Narrative: ON AUG/XA/97 AT APPROX XA30, I SIGNED OFF A 'TRANSIT CHK' ON ACR ACFT YYY. THE AIRWORTHINESS BLOCK WAS SIGNED OFF THEN ALSO. I ENTERED THE INFO INTO THE COMPUTER, MARKED THE YELLOW (ORIGINAL) LOGSHEET FOR SUCH ENTRIES, PULLED THE YELLOW SHEET FROM THE LOGBOOK, AND ADVANCED TO THE NEXT YELLOW LOGSHEET. THE LOGBOOK WAS RETURNED TO THE ACFT FOR AN XB50 DEP FROM ZZZ TO XYZ. THE LOG PAGE I PULLED OUT OF THE LOGBOOK WAS PLACED WITH MY COMPLETED TRANSIT CHK PAPERWORK WHERE THE LEAD MECH DOUBLECHKS PAPERWORK, THEN THE YELLOW LOGSHEET IS FAXED TO ACR RECORDS IN XYZ. THEN THE PROB AROSE WHEN ACFT ARRIVED IN XYZ AND THE FAA MET IT FOR A RAMP INSPECTION. UPON INSPECTING THE LOGBOOK, THE WHITE COPY PAGE DID NOT REFLECT THE AIRWORTHINESS BLOCK BEING SIGNED OFF. ACR USES A 'CARBONLESS COPY' TYPE LOGBOOK. THE COPY PAGE (WHITE) DID NOT PICK UP THE SIGNOFF. THE ORIGINAL LOG PAGE HAD THE AIRWORTHINESS SIGNED OFF. MORE CONFUSION CAME ABOUT WHEN THE FAA WANTED TO SEE THE FAXED COPY. ACFT RECORDS 'COULDN'T FIND' THEIR COPY OF THE LOG PAGE. ZZZ WAS CALLED AND THE ORIGINAL LOGSHEET WAS TAKEN OUT OF COMPANY MAIL AND REFAXED TO XYZ TO REVIEW. IT IS MY KNOWLEDGE THAT AT THIS TIME THE FAA IS NOT SATISFIED WITH THE CHAIN OF EVENTS AND HAS THIS MATTER UNDER REVIEW. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR STATES THIS LOGBOOK WHITE SHEET IS A PROB BECAUSE ANY WORK OR CHKS ACCOMPLISHED ON THE AIRPLANE IS ENTERED ON THE WHITE LOGBOOK SHEET AND THEN WHEN ALL THE ENTRIES ARE COMPLETE, THE WHITE SHEET IS TORN FROM THE LOGBOOK. THE RPTR SAID ANY ENTRY ON THE WHITE SHEET IS SUPPOSED TO BE COPIED ONTO THE YELLOW SHEET UNDERNEATH AND REMAIN IN THE LOGBOOK -- THIS DOES NOT ALWAYS HAPPEN. THE RPTR STATED THE LOGBOOK IS CALLED A CARBONLESS COPY TYPE LOGBOOK. RPTR ADVISED IT WAS LATER PROVED THE AIRWORTHINESS BLOCK WAS SIGNED.

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.

Attributes
ACN	376688
Time
Date	199708
Day	Fri
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : zzz
State Reference	US
Altitude	agl bound lower : 0 agl bound upper : 0
Environment
Light	Daylight
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	B737-400
Operating Under FAR Part	Part 121
Navigation In Use	Other Other
Flight Phase	other
Flight Plan	None
Person 1
Affiliation	company : air carrier
Function	other personnel other oversight : supervisor
Qualification	other other : other
ASRS Report	376688
Person 2
Affiliation	company : air carrier
Function	other personnel other
Qualification	other other : other
Events
Anomaly	aircraft equipment problem : less severe other anomaly other
Independent Detector	other other : unspecified
Resolutory Action	other
Consequence	faa : investigated
Supplementary
Air Traffic Incident	other

A B737-400 logbook was inspected by an FAA aci and found no signoff in the airworthiness block. A rechk of the paperwork at the downline station verified signoff but white log page did not copy onto sheet remaining in log. An ongoing problem.