A B737-300, due to lack of maintenance planning, missed the required service check by 3 days.

Attributes
ACN	565158
Time
Date	200211
Day	Sat
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : zzz.airport
State Reference	US
Altitude	agl single value : 0
Environment
Light	Daylight
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	B737-300
Operating Under FAR Part	Part 121
Flight Phase	ground : maintenance
Person 1
Affiliation	company : air carrier
Function	other personnel other oversight : supervisor
Qualification	technician : powerplant technician : airframe
ASRS Report	565158
Person 2
Affiliation	company : air carrier
Function	maintenance : technician
Events
Anomaly	aircraft equipment problem : critical maintenance problem : improper maintenance maintenance problem : improper documentation non adherence : far non adherence : published procedure
Independent Detector	other other : person 1
Resolutory Action	none taken : detected after the fact
Consequence	other other
Factors
Maintenance	performance deficiency : logbook entry performance deficiency : non compliance with legal requirements
Supplementary
Problem Areas	Company Maintenance Human Performance Aircraft
Primary Problem	Maintenance Human Performance

Narrative:

At XA30 hours on nov/sat/02, I was informed that the records technician in station called to inform planning that the service check paperwork for aircraft which was planned for nov/wed/02, was not in the package for nov/wed/02. This service check was due as a 7 day must on nov/wed/02. Aircraft went OTS on this day. When the planning router found out that this aircraft would not leave that night, he informed the maintenance control team lead who in turn informed mechanics that they would have to comply with this service check that night. The router then faxed the service check paperwork and entered it. The turn over required that mechanics must comply with the service check on nov/wed/02. This aircraft stayed OTS until nov/xx/02. The work package was then sent to records who received it and audited it on nov/sat/02. As soon as I discovered that the service check was 3 days overdue, I informed the maintenance control team lead. He arranged to have ZZZ1 mechanics go and comply with the service check on this aircraft before it made its first flight that morning of nov/sat/02.

Original NASA ASRS Text

Title: A B737-300, DUE TO LACK OF MAINT PLANNING, MISSED THE REQUIRED SVC CHK BY 3 DAYS.

Narrative: AT XA30 HRS ON NOV/SAT/02, I WAS INFORMED THAT THE RECORDS TECHNICIAN IN STATION CALLED TO INFORM PLANNING THAT THE SVC CHK PAPERWORK FOR ACFT WHICH WAS PLANNED FOR NOV/WED/02, WAS NOT IN THE PACKAGE FOR NOV/WED/02. THIS SVC CHK WAS DUE AS A 7 DAY MUST ON NOV/WED/02. ACFT WENT OTS ON THIS DAY. WHEN THE PLANNING ROUTER FOUND OUT THAT THIS ACFT WOULD NOT LEAVE THAT NIGHT, HE INFORMED THE MAINT CTL TEAM LEAD WHO IN TURN INFORMED MECHS THAT THEY WOULD HAVE TO COMPLY WITH THIS SVC CHK THAT NIGHT. THE ROUTER THEN FAXED THE SVC CHK PAPERWORK AND ENTERED IT. THE TURN OVER REQUIRED THAT MECHS MUST COMPLY WITH THE SVC CHK ON NOV/WED/02. THIS ACFT STAYED OTS UNTIL NOV/XX/02. THE WORK PACKAGE WAS THEN SENT TO RECORDS WHO RECEIVED IT AND AUDITED IT ON NOV/SAT/02. AS SOON AS I DISCOVERED THAT THE SVC CHK WAS 3 DAYS OVERDUE, I INFORMED THE MAINT CTL TEAM LEAD. HE ARRANGED TO HAVE ZZZ1 MECHS GO AND COMPLY WITH THE SVC CHK ON THIS ACFT BEFORE IT MADE ITS FIRST FLT THAT MORNING OF NOV/SAT/02.

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.