Airbus A380 flew for 300 hours with meter-long tool left inside engine

4 comments

• busterarm 2 hours ago

      Qantas personnel in Sydney even requested removal of the report as it was causing problems – in response, the tool's status was downgraded.
  

  Remind me never to fly Qantas.
• mensetmanusman 1 hour ago
  This is the type of edge case that will always eventually arise after enough hours. We have had nukes nearly go off after 10 fail safes were tripped.

  A medical issue followed by lack of sufficient follow up should not happen, but they statistically will eventually.
• ethbr1 2 hours ago
  First thought: if I left bad or useless code in a commit, how many levels of verification would it need to pass to make it to production?
  [-]
  • addaon 1 hour ago
    For code running in a commercial jet engine, so usually DAL A or DAL B? You should be caught by the first level of verification —- can’t even get past code review, because you don’t have a requirement to tag to trace the useless code back to. If that process failed (and any can), you have the whole climb up the right side of the V. And in the end, if the code is not /so/ useless as to be removed by the compiler, the final check that all generated bytes have traceability should catch it.
  • kenperkins 2 hours ago
    my thought was that if you get an alert that a key system is flapping in production, your first thought shouldn't be to squelch the alert.