Just a suggestion:
From the many posts about crashes here I find some additional infos very important on each crash to find a possible cause or to give Parrot hints (for software/hardware improvements):
- flying constellation: smartphone alone, with SC3?
- smartphone: model, operating system?
- any background software running: ______ (virus scanner, screen recorder, battery watch ...) or FF6 running as single app?
- a crash happened WITH THIS DRONE before (No.: link in table) J/N
- battery level at takeoff
- battery level at crash time
- flight area temperature
- battery at room temperature or higher before flight J/N
- "disconnected" warning appeared before crash J/N
- "low battery" warning appeared before crash J/N
- "motor error" warning appeared before crash J/N
- any other error warning before crash: ______ (which?)
- the crash flight was logged completely or broken mid-air
- a crash is logged/counted in FF6 (on the drone's page) J/N
- "shaking propeller noise" heard directly after crash J/N (normally this is identical with the "a crash logged/counted in FF6" point above)
- a drone contact with obstacles happend before crash J/N
- propellers ok and without damages before flight J/N
- life-feed active before/after crash: ______
- last pilot action before crash/problem: ______
- man. piloting mode or autonomous mode before crash: ______ (which mode? part of the autonom. flight, in which crash happened?)
- RTH active while crashing J/N
Of course these elementary infos could be found in the report of the pilot, but who remembers to answer all the relevant points?
In addition a column for most of these infos would improve the possibility to compare crashes and crash causes.
Hi!
Apologies for my late response - I am mostly offline these days.
Thank you very much for your feedback, I tried to keep it as simple as possible but I added the suggested columns in the spreadsheet. All Columns are optional anyway.
Best Regards
Vassilis