Since you question the accuracy of the logs etc. I would be inclined to test things.
Instead of using the automated motor start, use the CSC to start the motors and hold that CSC for several seconds after the motors have started then release the sticks and then give a second CSC to stop them. Repeat several times.
Look at the logs via uploading them to Phantom help's log viewer and check whether the CSC's are shown.
I use Phantomhelp's log viewer to decrypt my
Mini 2 flight logs and it is my recollection that they catch the motor start CSC. I suspect they would also catch the motor stop CSC but If they don't I am fairly sure they will catch some of the movement of the sticks towards the motor stop CSC.
I do not normally use the CSC to stop the motors when the drone is on the ground, rather I just hold the throttle closed so I can not check 'how much' of a motor stopping CSC the logs capture in those circumstances.
Additionally, if you are feeling brave and have a good grip, hand hold the Mavic Air, start the motors and, retaining a good grip of the drone, give it some throttle, enough to have it try to take off.
After it has fought you for a second to two, give it a CSC. If you move your hand during that attempted CSC I suspect the drone will continue to fight you. Release the sticks, hold you hand still and then close the throttle and hold it closed until the motors stop.
Check the log for that test.
I did the latter with a
Mavic 2 Zoom whilst investigating the CSC response thing.
With the
M2Z's response to a CSC set to "Breakdown"/"Emergency Only" and my hand moving, the CSC would not stop the motors. With the response to a CSC set to "Anytime" or whatever the word, the drone stopped it motors after the CSC had been held for, from memory, around 2 seconds.
If you try the hand holding thing DO NOT leave the drone fighting you for a prolonged period, you may get the ESC's hot.
You could also calibrate the controller, I assume the Mavic Air's Go4 has some means of depicting the movement of the sticks whilst you a 'playing' with them.
If so the calibration will do two things
1) show you if the controller currently indicates the correct response to stick position and movement and
2) possibly corrects that response it is currently in error.
With regards to your 'solutions' 1 to 3.
Regarding the training bit of 1) WERE you aware of the consequence of the CSC if the CSC response setting is "Breakdown"/"Emergency Only"?
If not there is no shame in saying you were not, many people do not know about it.
Besides which there are TWO CSC positions: a) both down and inward & b) both down and outward.
I assume that you fly with the CSC response set to "Breakdown"/"Emergency Only". I assume the Mavic Air behaves in the same way as the
M2Z i.e. the 'Anytime' 'delay' is very short and that, if you knew about this, then you either are a VERY careful flyer or consider "anytime" to risky to use all the time.
Regarding the memory bit of 1) we all make mistakes.
Regarding 2) I suppose it is possible for the logs to be incorrect but if so you have happened upon the "one in a million" occurrence of that, hence my suggesting the testing. However see *
Regarding 3) A possibility, hence the checking of the logs of check flights and the suggested calibration.
*From the reported heights I suspect there was at least a barometer glitch, that glitch? may have caused other problems or have been a consequence of other problems but I am not skilled enough to pick such information out of the logs.
@slup,
@Meta4,
@sar104 etc. probably are skilled enough, hence my trying to attract them to this thread.