A B737-300 was dispatched and operated in non compliance with a service check overdue caused by a maintenance router computer entry error.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	557562
Time
Date	200208
Day	Wed
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : zzz.airport
State Reference	US
Altitude	agl single value : 0
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	B737-300
Operating Under FAR Part	Part 121
Flight Phase	ground : parked
Person 1
Affiliation	company : air carrier
Function	maintenance : technician
Qualification	technician : airframe technician : powerplant
ASRS Report	557562
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 200 flight time total : 15000 flight time type : 13000
ASRS Report	557563
Events
Anomaly	aircraft equipment problem : less severe maintenance problem : improper documentation maintenance problem : improper maintenance non adherence : published procedure
Independent Detector	aircraft equipment other aircraft equipment : log book entries other flight crewa other flight crewb other other : person 1
Resolutory Action	none taken : detected after the fact
Consequence	other other
Factors
Maintenance	contributing factor : schedule pressure performance deficiency : scheduled maintenance performance deficiency : non compliance with legal requirements performance deficiency : logbook entry
Supplementary
Problem Areas	Aircraft Chart Or Publication Company Maintenance Human Performance
Primary Problem	Maintenance Human Performance

Narrative:

On aug/wed/02, OTS desk controller notified maintenance router that the pilot of aircraft called saying there was a discrepancy with the logbook. The last airworthiness release was dated aug/tue/02. The router researched maintenance system and found that the aircraft had come out of half D [partial heavy 'D' phase check] on aug/mon/02 and was released for flight aug/tue/02, meaning that the aircraft should have had a service check the night before and was now overdue. Further fact finding found that the night shift router had erroneously updated the 'a' check in maintenance system as of aug/wed/02 which updated the service check from that date also giving a false due date of aug/wed/02. Additionally, we found that the original planning record was canceled in maintenance system and not completed. The aircraft was pulled from service where it was headed when the pilot made the initial notification and the service check was performed.

Original NASA ASRS Text

Title: A B737-300 WAS DISPATCHED AND OPERATED IN NON COMPLIANCE WITH A SVC CHK OVERDUE CAUSED BY A MAINT ROUTER COMPUTER ENTRY ERROR.

Narrative: ON AUG/WED/02, OTS DESK CTLR NOTIFIED MAINT ROUTER THAT THE PLT OF ACFT CALLED SAYING THERE WAS A DISCREPANCY WITH THE LOGBOOK. THE LAST AIRWORTHINESS RELEASE WAS DATED AUG/TUE/02. THE ROUTER RESEARCHED MAINT SYS AND FOUND THAT THE ACFT HAD COME OUT OF HALF D [PARTIAL HVY 'D' PHASE CHK] ON AUG/MON/02 AND WAS RELEASED FOR FLT AUG/TUE/02, MEANING THAT THE ACFT SHOULD HAVE HAD A SVC CHK THE NIGHT BEFORE AND WAS NOW OVERDUE. FURTHER FACT FINDING FOUND THAT THE NIGHT SHIFT ROUTER HAD ERRONEOUSLY UPDATED THE 'A' CHK IN MAINT SYS AS OF AUG/WED/02 WHICH UPDATED THE SVC CHK FROM THAT DATE ALSO GIVING A FALSE DUE DATE OF AUG/WED/02. ADDITIONALLY, WE FOUND THAT THE ORIGINAL PLANNING RECORD WAS CANCELED IN MAINT SYS AND NOT COMPLETED. THE ACFT WAS PULLED FROM SVC WHERE IT WAS HEADED WHEN THE PLT MADE THE INITIAL NOTIFICATION AND THE SVC CHK WAS PERFORMED.

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.