<< >> NASA ASRS Report 431953, March 1999

A B757-200 was dispatched in non compliance with a logbook maintenance item not properly entered in the logbook with the corrective action taken.

Attributes
ACN	431953
Time
Date	199903
Day	Sun
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : zzz.airport
State Reference	US
Altitude	agl single value : 0
Aircraft 1
Controlling Facilities	tower : ewr.tower
Person 1
Affiliation	company : air carrier
Function	maintenance : technician
Qualification	technician : powerplant technician : airframe
ASRS Report	431953
Person 2
Affiliation	other
Function	maintenance : technician
Qualification	technician : powerplant technician : airframe
Events
Anomaly	aircraft equipment problem : less severe maintenance problem : improper documentation non adherence : company policies non adherence : far non adherence : published procedure other anomaly other
Independent Detector	other other : mech 1
Resolutory Action	none taken : detected after the fact
Consequence	other
Factors
Maintenance	contributing factor : manuals performance deficiency : unqualified personnel performance deficiency : logbook entry
Supplementary
Problem Areas	Maintenance Human Performance
Primary Problem	Maintenance Human Performance

Narrative:

On mar/xa/99, aircraft xyz was in ZZZ (air carrier flight xzx). 3 PIREPS were written into the logbook (items xx, yy and zz). All 3 items were corrected by contract maintenance. However, item yy has an invalid action taken plus no signature or employee number. The aircraft departed ZZZ to xyx on flight abc with this invalid corrective action taken entry. I voided the action taken entry, rewrote a correct action taken item. I made a maintenance entry and corrective action taken entry to reinspect the item and released the logbook. Callback conversation with reporter revealed the following information: the reporter stated the logbook entry was made by a contract mechanic and the improper logbook entry was a deferred maintenance item. The reporter said he cannot remember the exact details of what system was involved. The reporter said the item was entered in the logbook as a deferred item with no reference and no special procedures accomplished. The reporter stated that when the aircraft arrived in xyx the logbook was corrected.

Related reports:

• A CRJ700 was dispatched with a maintenance requested air con...

	Enter your search terms Submit search form
	Web www.37000feet.com

Original NASA ASRS Text

Title: A B757-200 WAS DISPATCHED IN NON COMPLIANCE WITH A LOGBOOK MAINT ITEM NOT PROPERLY ENTERED IN THE LOGBOOK WITH THE CORRECTIVE ACTION TAKEN.

Narrative: ON MAR/XA/99, ACFT XYZ WAS IN ZZZ (ACR FLT XZX). 3 PIREPS WERE WRITTEN INTO THE LOGBOOK (ITEMS XX, YY AND ZZ). ALL 3 ITEMS WERE CORRECTED BY CONTRACT MAINT. HOWEVER, ITEM YY HAS AN INVALID ACTION TAKEN PLUS NO SIGNATURE OR EMPLOYEE NUMBER. THE ACFT DEPARTED ZZZ TO XYX ON FLT ABC WITH THIS INVALID CORRECTIVE ACTION TAKEN ENTRY. I VOIDED THE ACTION TAKEN ENTRY, REWROTE A CORRECT ACTION TAKEN ITEM. I MADE A MAINT ENTRY AND CORRECTIVE ACTION TAKEN ENTRY TO REINSPECT THE ITEM AND RELEASED THE LOGBOOK. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: THE RPTR STATED THE LOGBOOK ENTRY WAS MADE BY A CONTRACT MECH AND THE IMPROPER LOGBOOK ENTRY WAS A DEFERRED MAINT ITEM. THE RPTR SAID HE CANNOT REMEMBER THE EXACT DETAILS OF WHAT SYS WAS INVOLVED. THE RPTR SAID THE ITEM WAS ENTERED IN THE LOGBOOK AS A DEFERRED ITEM WITH NO REF AND NO SPECIAL PROCS ACCOMPLISHED. THE RPTR STATED THAT WHEN THE ACFT ARRIVED IN XYX THE LOGBOOK WAS CORRECTED.

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.