 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A maintenance controller reports on the shortcomings of their aircraft status system not alerting controllers a B737-300 aircraft had extra flight legs added that had the aircraft still flying beyond time when maintenance was required.
| Attributes | |
| ACN | 796002 |
| Time | |
| Date | 200807 |
| Local Time Of Day | 0601 To 1200 |
| Place | |
| Locale Reference | airport : zzz.airport |
| State Reference | US |
| Altitude | agl single value : 0 |
| Environment | |
| Light | Dawn |
| 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 |
| Qualification | technician : powerplant technician : airframe |
| ASRS Report | 796002 |
| Events | |
| Anomaly | aircraft equipment problem : critical maintenance problem : improper maintenance non adherence : far non adherence : published procedure |
| Independent Detector | other other : 1 |
| Resolutory Action | none taken : detected after the fact |
| Consequence | other Other |
| Factors | |
| Maintenance | contributing factor : briefing contributing factor : manuals performance deficiency : scheduled maintenance performance deficiency : non compliance with legal requirements |
| Supplementary | |
| Problem Areas | Company Maintenance Human Performance Aircraft |
| Primary Problem | Company |
| Situations | |
| Publication | MAINT PROCEDURES POLICY |
Narrative:
Around XA00 the aircraft was routed to ZZZ with enough flight hours and cycles remaining. There was never an alert sent to my aircraft status stating that aircraft was being routed differently or that an alert was indicated. This is not the first time I have noticed the aircraft status system failing. There should be an alert system for cycle driven items set up to alert per cycle before dead date. Also there needs to be procedures in place that does not allow routing to grab an aircraft that is under short time limits and as far as that goes; the router on duty with me is a professional and also would not have grabbed aircraft and added extra legs to it. In the morning; I was alerted that the aircraft was over-flown from the night before. The aircraft was stopped in ZZZ1 to comply with monitor.
Original NASA ASRS Text
Title: A MAINT CONTROLLER REPORTS ON THE SHORTCOMINGS OF THEIR ACFT STATUS SYSTEM NOT ALERTING CONTROLLERS A B737-300 ACFT HAD EXTRA FLT LEGS ADDED THAT HAD THE ACFT STILL FLYING BEYOND TIME WHEN MAINT WAS REQUIRED.
Narrative: AROUND XA00 THE ACFT WAS ROUTED TO ZZZ WITH ENOUGH FLT HRS AND CYCLES REMAINING. THERE WAS NEVER AN ALERT SENT TO MY ACFT STATUS STATING THAT ACFT WAS BEING ROUTED DIFFERENTLY OR THAT AN ALERT WAS INDICATED. THIS IS NOT THE FIRST TIME I HAVE NOTICED THE ACFT STATUS SYS FAILING. THERE SHOULD BE AN ALERT SYS FOR CYCLE DRIVEN ITEMS SET UP TO ALERT PER CYCLE BEFORE DEAD DATE. ALSO THERE NEEDS TO BE PROCS IN PLACE THAT DOES NOT ALLOW ROUTING TO GRAB AN ACFT THAT IS UNDER SHORT TIME LIMITS AND AS FAR AS THAT GOES; THE ROUTER ON DUTY WITH ME IS A PROFESSIONAL AND ALSO WOULD NOT HAVE GRABBED ACFT AND ADDED EXTRA LEGS TO IT. IN THE MORNING; I WAS ALERTED THAT THE ACFT WAS OVER-FLOWN FROM THE NIGHT BEFORE. THE ACFT WAS STOPPED IN ZZZ1 TO COMPLY WITH MONITOR.
Data retrieved from NASA's ASRS site as of May 2009 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.