Hacker News new | past | comments | ask | show | jobs | submit login

I'd start with any one who decided not to ground the planes and deflected responsibility a soon as the first crash happened. They have direct responsibility over the second crash.

The I'd go over all the certification process. Any person who concealed information or misled in an official capacity goes to jail. That's the whole point of requiring titled engineers signatures. The buck stops with them.




They were very likely assured by their program managers that the crash was a fluke, presented with convincing test data, and pressured by their bosses, the board, etc etc.

These things rarely happen by individual malfeasance. They are part of a system of small mistaken assumptions that compound into big lies.


I agree with you but out of curiosity what do you suggest as a solution ? You believe all we need is the fine and then the company goes under ? If that's true then all the individuals who failed could just as easily go to another company and repeat their failures.

For doctors a failure can make their license get revoked (even tho it doesn't seem to happen very often in practice). Wonder if there could be something similar but indeed it is very hard to find "a person to blame", maybe the CEO? CTO? :)


> You believe all we need is the fine and then the company goes under ?

No I don't believe that. There will be firings, demotions, lost bonuses, etc. Maybe there should be more of that, maybe not. A CEO may step down and have trouble finding a similar position, etc.

I don't actually have a suggestion of a better way, I just agree that you can't automatically throw one person into jail.


wouldn't it be the engineers the get the test data though? (at least directly) instead of the program manager?




Consider applying for YC's Spring batch! Applications are open till Feb 11.

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

Search: