Thanks so much for taking the time to evaluate. In the horizontal distance stream, (highlighted in yellow above), I don't understand the. "horizontal distance to subject too short". I never manually put it into Active Track.You made several mistakes during this flight & the lack of knowledge over how your craft works made you panic ... you could easily have saved your MA2 but you let it descend into the water unfortunately. All this should be classified as a pilot error nothing else.
-You drained your battery way to far, deliberately canceled the Low battery RTH prompt
-You didn't know anything about the Low battery forced auto landing, when it should kick in or how to stay airborne once activated.
-You was in a semi automated flight mode (Active track) which here & there had some influence over the horizontal speed of your craft, and this would have been clearly indicated on your screen ... you could have easily got out of that by just flipping the mode switch back & forth.
-Once the Low battery forced auto landing was active you panicked ... applied all sorts of stick inputs besides the correct ones. You should have aimed your craft towards closest solid ground, applied forward speed in that direction ... & during this applied throttle for ascent to stop the auto descent.
This shows the erratic & panicked flight path you commanded your MA2 to take ... red X indicate start of Low battery forced auto landing & crash into the water ...
View attachment 142544
You had 3 shorter moment of Active track in the beginning of the flight ... & one long instance starting at 1078sec into the flight which was auto cancelled when the auto landing started.
Checking off how well your stick commands actually worked in the charts below ...
Starting with the Elevator stick (right stick, forward/backward):
The slightly grayer light blue background color to the left = GPS mode with APAS active
The lighter blue background = Low battery forced auto landing active
The red graph = Height above your HP
The green graph = Heading speed
The dashed blue graph = your elevator stick command (right stick, forward/backward, value 1024 is stick neutral)
It's seen in several places before the Low battery auto landing kick in that this movement is somewhat restrained ... this due to you being in Active track mode.
In the logs message stream we find this that could have been the reason ...
View attachment 142546
(Elevator stick vs. heading speed ... click on the chart to make it larger)
View attachment 142545
In the rudder commands we see nothing odd ... the craft responds well & accurate.
Red graph = Height again
Green graph = Adding & subtracting yaw angle
Dashed Blue graph = Rudder stick command (left stick, left/right, value 1024 is stick neutral)
(Rudder stick vs. yaw angle change ... click on the chart to make it larger)
View attachment 142547
When it comes to the throttle inputs they respond as usual before the Low battery auto landing ... when the landing is active the craft will descend with neutral stick ... but slowly ascend with stick at max for ascend. It's easy to see that this you didn't know, when you do the right thing your craft gains altitude ... but you mostly didn't apply enough throttle for ascend so your craft mostly drop it's height & eventually hit the water.
Red graph = Height
Green graph = vertical speed where negative values is ascend & positive is descend
Dashed blue graph = Throttle stick command (left stick, forward/backwards, value 1024 is stick neutral)
(Throttle stick vs. vertical speed ... click on the chart to make it larger)
View attachment 142548
Here below the sad facts about your battery management ...
Red graph = height
Green graph = Battery percentage
Blue graph = Low battery RTH threshold in percent which is distance from HP dependent
Purple graph = Low battery RTH countdown seen on your app screen
Black graph = Low battery forced auto landing threshold in percent which is height dependent
(Click on the chart to make it larger)
View attachment 142549
When the MA2 autolands, is the downward sensor still on, to avoid hitting anything below it? Looking to learn as much as I can from this incident, and safety is priority.The plot is an overlay on google earth I think.
The log doesn't reveal why or how a flight mode was initiated ... but it's no doubt that it was in active track mode, the log is clear about that. You had 3 very short instances of active track mode in the beginning of the flight & one longer which lasted until the low battery forced auto landing started.... "horizontal distance to subject too short". I never manually put it into Active Track.
If your battery is empty no sensor in the world will keep it flying ... this security feature with low battery forced auto landing is height dependent, it will start at a charge percentage that see to that the drone can reach solid ground before the battery is totally dead ... all this to prevent a "dead in the air free fall" situation.When the MA2 autolands, is the downward sensor still on, to avoid hitting anything below it? Looking to learn as much as I can from this incident, and safety is priority.
That's correct ... it's a screenshot from a 3D view from Google Earth with your flight path overlayedNever mind.... guess its not a "real picture" with the red X. Never had one go down before, so all new to me.
I think it would be on but it is not an anti collision sensor. It's more a height sensor and suitability or the landing site sensor. Presumably the suitability bit is ultimately over ridden at some point as the battery is drained.When the MA2 autolands, is the downward sensor still on, to avoid hitting anything below it? Looking to learn as much as I can from this incident, and safety is priority.
beeflyin said:
When the MA2 autolands, is the downward sensor still on, to avoid hitting anything below it? Looking to learn as much as I can from this incident, and safety is priority.
The MA2 downward sensors ARE anti-collision. The MA2 will move around to avoid things it thinks are obstacles. It makes landing on my table top landing zone pretty interesting when the winds are not reasonably still. If not perfectly centered as the drone descends the drone will see the table edge and dart off to avoid it.I think it would be on but it is not an anti collision sensor. It's more a height sensor and suitability or the landing site sensor. Presumably the suitability bit is ultimately over ridden at some point as the battery is drained.
But...... water can confuse the sensor, for future reference low flights over water can be risky and you need to be ready to throttle up if you see it start to descend.
I've considered floats , but what happens if the wind, tide or current take it away from the shore your standing on and out to sea or beyond sight into the middle of a lake ?I have read many post with drones ending up in the water. There are also many reason why it happens. Some on this forum will tell you they never had any problems but for me I will not take a chance and will install the float. I would rather have the security plus the option to land on if I want or have to.
View attachment 142689
We use essential cookies to make this site work, and optional cookies to enhance your experience.