37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1517120 |
Time | |
Date | 201802 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Aircraft 1 | |
Make Model Name | Citation Excel (C560XL) |
Operating Under FAR Part | Part 91 |
Flight Phase | Parked |
Route In Use | None |
Flight Plan | None |
Component | |
Aircraft Component | GPWS |
Person 1 | |
Function | Inspector |
Qualification | Maintenance Inspection Authority |
Events | |
Anomaly | Deviation - Procedural FAR Deviation - Procedural Maintenance Deviation - Procedural Published Material / Policy |
Narrative:
During a routine inspection of the aircraft; CE560XL; and while prepping to accomplish the [engineering order] task; [which] upgrades the honeywell egpws computer; we encountered multiple issues of concern.the first issue is this task was not applicable to this tail number because of prior accomplishment of two service bulletins; and to arrive at this conclusion required extensive time and research by repair station avionics and management personnel. The second issue was the operator required the repair station to sign-off tasks that were previously complied with. To achieve the desired result; and to arrive at this conclusion required extensive time and research by repair station avionics and management personnel.this is a good example of the operator failing to properly document completion of tasks previously accomplished; and for placing the responsibility for researching those tasks on the end-user (the maintenance technician). What I was able to deduct from this research is that; during the migration from one maintenance tracking software to another; visibility to those completed tasks were deliberately omitted from populating as historical records. Regardless of the reason; tasks such as this that were previously complied with triggered the repair station organization to consume needless amounts of time; which in turn prevents us from remaining competitive to other vendors.
Original NASA ASRS Text
Title: A Maintenance Inspector working on a Cessna Citation reported that the Owner/Operator failed to properly document completion of tasks previously accomplished.
Narrative: During a routine inspection of the Aircraft; CE560XL; and while prepping to accomplish the [Engineering Order] task; [which] upgrades the Honeywell EGPWS computer; we encountered multiple issues of concern.The first issue is this task was not applicable to this tail number because of prior accomplishment of two Service Bulletins; and to arrive at this conclusion required extensive time and research by repair station avionics and management personnel. The second issue was the Operator required the repair station to sign-off tasks that were Previously Complied With. To achieve the desired result; and to arrive at this conclusion required extensive time and research by repair station avionics and management personnel.This is a good example of the Operator failing to properly document completion of tasks previously accomplished; and for placing the responsibility for researching those tasks on the end-user (the maintenance technician). What I was able to deduct from this research is that; during the migration from one maintenance tracking software to another; visibility to those completed tasks were deliberately omitted from populating as historical records. Regardless of the reason; tasks such as this that were previously complied with triggered the repair station organization to consume needless amounts of time; which in turn prevents us from remaining competitive to other vendors.
Data retrieved from NASA's ASRS site 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.