I replied elsewhere in the thread with a bit more detail, but my UAV checklists contain 100% material learned from experience only. They've grown a little (espe

I replied elsewhere in the thread with a bit more detail, but my UAV checklists contain 100% material learned from experience only. They've grown a little (especially the packing list) as I've gotten out to the field and realized I didn't have a tool that would be useful to have, but they've also shrunk as I've eliminated equipment I no longer need (e.g. a programming cable for an ESC that I no longer use). It's pretty disappointing to hear that that's how checklists work in your org. I feel like it's doubly negative: not only does it pretty much guarantee that they won't be followed because they're not particularly useful in that form; it also helps to ensure that the folks that have to use them will push back against checklists in general at their next job! [I suppose that's what happened with me and JIRA too... it might be a decent product, but every org I've used it in has done a very bad job with it]