 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Md-11 flight crew reported that an erroneous tire failure warning resulted in a precautionary landing.
| Attributes | |
| ACN | 1740145 |
| Time | |
| Date | 202004 |
| Local Time Of Day | 0001-0600 |
| Environment | |
| Flight Conditions | VMC |
| Light | Night |
| Aircraft 1 | |
| Make Model Name | MD-11 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Descent |
| Flight Plan | IFR |
| Component | |
| Aircraft Component | Indicating and Warning - Landing Gear |
| Person 1 | |
| Function | Pilot Flying Captain |
| Qualification | Flight Crew Instrument Flight Crew Multiengine Flight Crew Air Transport Pilot (ATP) |
| Person 2 | |
| Function | First Officer Pilot Not Flying |
| Qualification | Flight Crew Multiengine Flight Crew Air Transport Pilot (ATP) Flight Crew Instrument |
| Events | |
| Anomaly | Aircraft Equipment Problem Less Severe Deviation - Procedural Published Material / Policy |
Narrative:
At cruise FL370 we had a momentary 'config' light flashing on the ead; so I selected the 'config' page and saw 'tire fail' indication with all of the wheels missing from the display; then it returned to normal immediately. There were no other alerts and CAWS did not alert either. Then about 10-15 minutes later in the descent; passing about fl 250 we got a CAWS 'tire failure' and a level 2 'tire fail' alert; which did not resolve itself. We ran the QRH for 'tire fail' but again suspected an erroneous indication since all of the wheels and pressures were missing from the config page. We planned for a flaps 50 landing for minimum speed at touchdown just in case. We also planned to extend the gear early so that if the indications did not return to normal with the gear down; we would then [advise ATC] to have the fire crews ready. It was still before dawn so we did not consider a low pass so the tower could look; given that they wouldn't be able to see if a wheel had failed; and the restriction in the QRH to not retract the gear. When the gear was extended the level 2 'tire fail' remained; and the config page did not show any wheels or pressures; so we [advised ATC] and assumed that we had one or more tires failed. Approach and landing were good; with a 1.14G touchdown and a normal rollout; so we taxied clear and waited for the fire chief to inspect all of our tires. Fire chief reported that all landing gear and tires looked good; and the airport safety vehicle reported no debris on the runway; so we continued taxi to the ramp. When maintenance came on board they found indications of a failed computer which they will attempt to replace.the CAWS alert 'tire failure' and level 2 'tire fail' were accompanied by a configuration display that was missing all of the wheels and pressures; so we suspected an erroneous indication; but proceeded as if we had an unknown tire failure. Maintenance troubleshot upon block in and they suspect a failed computer.
Original NASA ASRS Text
Title: MD-11 flight crew reported that an erroneous tire failure warning resulted in a precautionary landing.
Narrative: At Cruise FL370 we had a momentary 'config' light flashing on the EAD; so I selected the 'config' page and saw 'TIRE FAIL' Indication with all of the wheels missing from the display; then it returned to normal immediately. There were no other alerts and CAWS did not alert either. Then about 10-15 minutes later in the descent; passing about FL 250 we got a CAWS 'TIRE FAILURE' and a Level 2 'TIRE FAIL' alert; which did not resolve itself. We ran the QRH for 'TIRE FAIL' but again suspected an erroneous indication since ALL of the wheels and pressures were missing from the Config Page. We planned for a flaps 50 landing for minimum speed at touchdown just in case. We also planned to extend the gear early so that if the indications did not return to normal with the gear down; we would then [advise ATC] to have the fire crews ready. It was still before dawn so we did not consider a low pass so the tower could look; given that they wouldn't be able to see if a wheel had failed; and the restriction in the QRH to not retract the gear. When the gear was extended the Level 2 'TIRE FAIL' remained; and the config page did not show any wheels or pressures; so we [advised ATC] and assumed that we had one or more tires failed. Approach and landing were good; with a 1.14G touchdown and a normal rollout; so we taxied clear and waited for the fire chief to inspect all of our tires. Fire Chief reported that all landing gear and tires looked good; and the Airport Safety vehicle reported no debris on the runway; so we continued taxi to the ramp. When Maintenance came on board they found indications of a failed computer which they will attempt to replace.The CAWS alert 'TIRE FAILURE' and Level 2 'TIRE FAIL' were accompanied by a CONFIG Display that was missing all of the wheels and pressures; so we suspected an erroneous indication; but proceeded as if we had an unknown tire failure. Maintenance troubleshot upon block in and they suspect a failed computer.
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.