- Joined
- Apr 7, 2017
- Messages
- 24
- Reaction score
- 12
- Age
- 35
I thought I'd share my custom pre-flight paperwork with you all. I work for a county agency and we like to be very thorough and cover all of our bases. So in additional to just 'following the rules', we go above and beyond to pre-plan and document all of our flights. I created a UAS Operation Brief that outlines all of the information regarding the location (including a satellite image and VFR Sectional Chart), flight maneuvers, flight crew, weather reports, etc. One of these briefs is filled out before each flight and signed off on by our agency's director and the PIC (myself).
I've also created a custom pre-flight inspection and pre-flight checklist, which document the condition of the aircraft, batteries, transmitter and other systems as well as all the steps leading up to take-off.
It's an admittedly cumbersome process that can't really be done at the spur of the moment, but that's kind of the point. There's an abundance of pre-planning, caution, and double checking. All of this helps us fly out missions as effectively as possible. All of this information also helps in the event that someone complains about our flights or in the event of a crash - we can always point back to our brief and checklists and say "Here's how we know we can fly here" or "Here's why I believe the crash was an anomaly or software error"
These checklists aren't the final product. The more we fly, the more we learn. There's things to be added and things to be taken off.
But I wanted to throw these out there to see what you all think! (PDFs are attached)
I've also created a custom pre-flight inspection and pre-flight checklist, which document the condition of the aircraft, batteries, transmitter and other systems as well as all the steps leading up to take-off.
It's an admittedly cumbersome process that can't really be done at the spur of the moment, but that's kind of the point. There's an abundance of pre-planning, caution, and double checking. All of this helps us fly out missions as effectively as possible. All of this information also helps in the event that someone complains about our flights or in the event of a crash - we can always point back to our brief and checklists and say "Here's how we know we can fly here" or "Here's why I believe the crash was an anomaly or software error"
These checklists aren't the final product. The more we fly, the more we learn. There's things to be added and things to be taken off.
But I wanted to throw these out there to see what you all think! (PDFs are attached)