stoy@lemmy.zip 1 week ago
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
schipelblorp@sh.itjust.works 1 week ago
That’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.
And 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.
stoy@lemmy.zip 1 week ago
US investigators?
What are you talking about?
This incident is investigated by India, France and Airbus:
en.wikipedia.org/…/Directorate_General_of_Civil_A…
en.wikipedia.org/…/Bureau_of_Enquiry_and_Analysis…
schipelblorp@sh.itjust.works 1 week ago
Oops. Read Boeing for Airbus for some reason. Carry on.
stoy@lemmy.zip 1 week ago
Hehe, it’s fine, I have done similar things