3 ms·
I heard in the news that this was caused by a "bad flight plan". It is clear, even without any more information than that, it was a software failure (bad fligh
by worik 3y ago
I heard in the news that this was caused by a "bad flight plan".
It is clear, even without any more information than that, it was a software failure (bad flight plan?)
It will be interesting to see if Frequentis has to pay a price for causing this
- vachina 3y agoI think Frequentis will actually be paid more to “add feature to make the system more robust” and a bump in support schedules.
- anentropic 3y agoYeah it seems clear from the report that NATS published it wasn't a bad flight plan at all... the plan was valid to the relevant specifications But the specifications allow ambiguities (non-unique waypoint ids) and the software did not handle this particular ambiguity correctly