If they know exactly why it happened and the probability of it happening again is within tolerance, there’s no reason to ground the entire fleet.
post
Right, this is obviously a terrible thing to happen, there is no denying that.
But we the public have too little information about the aircraft to demand any change yet.
They may already have identified the cause, and have found it to only affect a small percentage of the A320neo fleet, with a relatively simple fix, that is easy enough to install that it doesn't notably impact scheduling.
We don't know, and at this point we need to trust the investigators
> at this point we just need to trust the investigators
hat's just it, I don't know we should trust any US federal regulators at this point, especially not when there's a lot of money at stake.
nd we already had the global aviation community bitching about the last time a US planes computer bug crashed a plane into a mountain and the FAA was dragging its feet.
US investigators?
What are you talking about?
This incident is investigated by India, France and Airbus:
https://en.wikipedia.org/wiki/Directorate_General_of_Civil_Aviation_(India)
https://en.wikipedia.org/wiki/Bureau_of_Enquiry_and_Analysis_for_Civil_Aviation_Safety
It wasn't in cruise. It was in a -1G manoeuvre as part of stall recovery, and recovered the systems within 4s. Definitely not a normal flight.
From Wikipedia:
The chief pilot later tested positive twice for THC.
I don't think it's related, as they seem to have reacted correctly, but interesting to know.
all 17 comments