The FAA earlier called it a "damaged database file". I'm not convinced it was data entry exactly. For example, running "/some/script > data-file" instead of "

The FAA earlier called it a "damaged database file". I'm not convinced it was data entry exactly. For example, running "/some/script > data-file" instead of "/some/script < data file" still fits the very generic wording the FAA is sharing publicly. Could have been accidentally overwriting some idx/dat pair, or some raw database file, etc. Though, yeah, there should still be some controls, troubleshooting tools, logging, descriptive errors, etc, that would have made things more clear and recoverable.