Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Which may have been a very reasonable conclusion based on what they knew of the issue. The letter sent out reported a split of the bearing race. A split bearing race won't prevent it from supporting the load. It's easily possible that Boeing's simulation of an aircraft operating with a split bearing race was fine.

The NTSB investigation found that for this crash, not only did the bearing race crack, but also that the bearing lugs, which hold the bearing in place, were fractured. I don't have access to the original text of the letter Boeing sent out, but based on the NTSB report, it sounds like only the issue with the bearing race was previously identified. The two may very well be related, but that doesn't mean that the lug fractures are an expected result of the race failure - perhaps some contributing factor made the lugs more susceptible than predicted. It also remains possible that the bearing damage is a red herring; the aircraft was nearing the end of its service life and had known structural issues in other parts of the pylon. The fact is that for more than a decade after the bearing race issue was reported, it didn't result in a safety of flight condition.

The insinuation that Boeing was deliberately trying to hide or downplay a known issue is simply unwarranted. It would be irresponsible for the NSTB not to mention a known issue that could have potentially been relevant, it's not evidence the issue was improperly handled.





Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: