Yeah ... as already said, you didn't have any GPS assisted horizontally hold & it was too dark in order for the VPS sensor to be able to lock on to the ground surface giving you OPTI mode's horizontally hold. All this means ATTI mode with only height hold but no horizontally hold at all & no auto brake after stick release.
If unused to ATTI it can be very confusing ... the last thing you want to do is to use full stick deflections, but you did & your
MA1 speed up & you lost control.
All this is clear when going into the TXT log message stream ... most of these messages was shown on you screen device also, so you should have been aware of the risk.
(Click on all pics below to make them larger)
View attachment 136608
Looking at your flight with some chosen telemetry data depicted on a chart where:
The pink & grey background color to the left is motor start & take-off
The blue background color is ATTI mode
& the grey background color to the right in an error message saying "notEnoughForce"
The red graph is the height
The green graph is pitch angle
The blue graph is roll angle
The purple & yellow graph (invisible as they have value 0) is the satellite count & navHealth
... shows this.
View attachment 136609
It confirms that this flight was only in ATTI mode ... 0 satellites locked with 0 in navHealth as the flight controller didn't have any GPS positional data to evaluate.
Starting at 38sec into the flight you hit something ... the roll angle goes to 94,4 degrees but it recovers, but at 41,4sec you either hit something again or a prop became damaged earlier & now failed completely & your
MA1 turns upside down, loses height fast & a "notEnoughForce" error flag comes up.
But ...
Besides that you took the risk to launch even though all the warning messages ... I suspect something else can be going on regarding your GPS, Have marked that in blue in the TXT log message stream shown above. This can indicate that your GPS unit wasn't functioning as it should.