 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A B737-300 was dispatched in non compliance with the #2 air data computer pitot and static lines not connected after an inertial reference unit change.
| Attributes | |
| ACN | 481392 |
| Time | |
| Date | 200008 |
| Day | Wed |
| 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 ground : parked |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | maintenance : lead technician |
| Qualification | technician : airframe technician : powerplant |
| Experience | maintenance avionics : 13 maintenance lead technician : 2 maintenance technician : 11 |
| ASRS Report | 481392 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : atp pilot : multi engine |
| Experience | flight time last 90 days : 220 flight time total : 12500 flight time type : 9000 |
| ASRS Report | 481956 |
| Events | |
| Anomaly | aircraft equipment problem : critical maintenance problem : improper maintenance non adherence : published procedure |
| Independent Detector | aircraft equipment other aircraft equipment : airspeed indicator other flight crewa other flight crewb |
| Resolutory Action | none taken : detected after the fact |
| Consequence | other other |
| Factors | |
| Maintenance | contributing factor : schedule pressure performance deficiency : inspection performance deficiency : installation performance deficiency : non compliance with legal requirements performance deficiency : repair performance deficiency : testing performance deficiency : unqualified personnel |
| Supplementary | |
| Problem Areas | Chart Or Publication Maintenance Human Performance Aircraft |
| Primary Problem | Maintenance Human Performance |
Narrative:
In order to change the #1 IRU on a boeing 737-300 you must remove the static lines to the #2 dadc. This is the incident which occurred to me. After reinstalling the #1 IRU, the static lines, which were laying beside the east/east rack, were 'out of sight, out of mind.' after leaving ZZZ airport and landing in XXX the crew had maintenance look at the aircraft because airspeed (first officer's) was inaccurate (+/-200 KTS). After completing a series of bite tests and #2 dadc bite, no discrepancies were noted. The flight crew again took the aircraft but returned to the gate this time. It was found that the 2 static liens to the #2 dadc were not connected.
Original NASA ASRS Text
Title: A B737-300 WAS DISPATCHED IN NON COMPLIANCE WITH THE #2 AIR DATA COMPUTER PITOT AND STATIC LINES NOT CONNECTED AFTER AN INERTIAL REF UNIT CHANGE.
Narrative: IN ORDER TO CHANGE THE #1 IRU ON A BOEING 737-300 YOU MUST REMOVE THE STATIC LINES TO THE #2 DADC. THIS IS THE INCIDENT WHICH OCCURRED TO ME. AFTER REINSTALLING THE #1 IRU, THE STATIC LINES, WHICH WERE LAYING BESIDE THE E/E RACK, WERE 'OUT OF SIGHT, OUT OF MIND.' AFTER LEAVING ZZZ ARPT AND LNDG IN XXX THE CREW HAD MAINT LOOK AT THE ACFT BECAUSE AIRSPD (FO'S) WAS INACCURATE (+/-200 KTS). AFTER COMPLETING A SERIES OF BITE TESTS AND #2 DADC BITE, NO DISCREPANCIES WERE NOTED. THE FLC AGAIN TOOK THE ACFT BUT RETURNED TO THE GATE THIS TIME. IT WAS FOUND THAT THE 2 STATIC LIENS TO THE #2 DADC WERE NOT CONNECTED.
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.