37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 944064 |
Time | |
Date | 201104 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | ZZZ.TRACON |
State Reference | US |
Environment | |
Flight Conditions | VMC |
Light | Dawn |
Aircraft 1 | |
Make Model Name | A319 |
Operating Under FAR Part | Part 121 |
Flight Phase | Climb |
Flight Plan | IFR |
Component | |
Aircraft Component | INS / IRS / IRU |
Person 1 | |
Function | Pilot Not Flying Captain |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Aircraft Equipment Problem Critical Ground Event / Encounter Other / Unknown |
Narrative:
During initial takeoff roll nose wheel hit a sharp bump that was apparently due to a change in the pavement in runway. During climb out about 10;000 ft. Autopilot disengaged. First officer was flying pilot and remained so during remainder of flight. Neither pilot had disengaged autopilot so captain ran ECAM. ECAM showed loss of autopilot and loss of autothrust. On completing ECAM items first officer noted that he could not track the navigation. Flight directors were not available. We were unable to recover any items lost. FMGC then noted loss of accuracy of ir 3. Position data lacked info for ir 3. No faults were noted and no other ecams were given. First officer continued flying manually controlling joystick and thrust with no flight director information. Visual approach accomplished at the nearest suitable airport. During landing rollout ir 2 failed followed in seconds by ir 3 for a dual ir 2 and 3 fault. No recovery was attempted during taxi to gate. ATC seemed to be somewhat confused about our condition and I tried to relate very simply that we had a loss of automation and a degraded navigation capability although we did have basic navigation. We were able to determine that nd 1 was showing an accurate track but nd 2 was giving bad data. Using heading and altitude seemed to work out well for the first officer while I worked ECAM; checklists and any suggested procedures from maintenance control. As it was a short flight we were unable to do much further trouble shooting but no other faults were presented during the flight. We were given headings by each subsequent controller until we were cleared for a visual approach for the runway. Landing and rollout were normal until we cleared runway. Then ir 2 faulted followed in seconds by ir 3 fault resulting in a dual ir 2 and 3 fault. No attempt was made to recover ir 2 or ir 3 as we were on the ground. Ir 1 remained stable. We hit a bump on initial take off roll. It is possible that this very sharp bump had something to do with the later loss of automation and eventual loss of ir 2 and 3. It needs to be determined if there is some way a bump like that could cause an ir problem.
Original NASA ASRS Text
Title: An A319 flight crew suffered a dual IR failure shortly after takeoff. A sharp bump on the takeoff roll may have been a contributing factor.
Narrative: During initial takeoff roll nose wheel hit a sharp bump that was apparently due to a change in the pavement in runway. During climb out about 10;000 FT. autopilot disengaged. First Officer was flying pilot and remained so during remainder of flight. Neither pilot had disengaged autopilot so Captain ran ECAM. ECAM showed loss of autopilot and loss of autothrust. On completing ECAM items First Officer noted that he could not track the NAV. Flight Directors were not available. We were unable to recover any items lost. FMGC then noted loss of accuracy of IR 3. Position data lacked info for IR 3. No FAULTS were noted and no other ECAMS were given. First Officer continued flying manually controlling joystick and thrust with no flight director information. Visual approach accomplished at the nearest suitable airport. During landing rollout IR 2 failed followed in seconds by IR 3 for a dual IR 2 and 3 FAULT. No recovery was attempted during taxi to gate. ATC seemed to be somewhat confused about our condition and I tried to relate very simply that we had a loss of automation and a degraded NAV capability although we did have basic NAV. We were able to determine that ND 1 was showing an accurate track but ND 2 was giving bad data. Using heading and altitude seemed to work out well for the First Officer while I worked ECAM; checklists and any suggested procedures from Maintenance Control. As it was a short flight we were unable to do much further trouble shooting but no other FAULTS were presented during the flight. We were given headings by each subsequent controller until we were cleared for a visual approach for the runway. Landing and rollout were normal until we cleared runway. Then IR 2 FAULTED followed in seconds by IR 3 FAULT resulting in a dual IR 2 and 3 FAULT. No attempt was made to recover IR 2 or IR 3 as we were on the ground. IR 1 remained stable. We hit a bump on initial take off roll. It is possible that this very sharp bump had something to do with the later loss of automation and eventual loss of IR 2 and 3. It needs to be determined if there is some way a bump like that could cause an IR problem.
Data retrieved from NASA's ASRS site as of April 2012 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.