Can someone help me sort out what went wrong? Which Bin files should I upload from my flight logs? (I see 1 thru 9, but the crash didn't happen on the most recent flight.)
For background, I have my Part 107 but I'm a relatively new pilot. I've had Solo's slow baby settings on for the last 15 to 20 flights while I learn the sticks.
I was flying at my mom's place in rural Oregon earlier this summer. I launched from her pasture which is surrounded by trees. Solo was flying great and I basically just took it up a ways, looked around, then descended. As I neared the ground, Solo made a beeline for a workshop that was about 15 feet away. I didn't tell it to move in that direction. I also couldn't act fast enough to stop it. The video is pretty hilarious, actually. My whole family waves at Solo as it's graciously descended. Then it suddenly flies sideways for a few seconds and slams into the building.
This also wasn't the first time this has happened. Solo took off toward a building earlier this summer when a friend was flying and a similar thing happened in slow motion.
But during that Oregon crash, Solo's hdmi cable port very slightly ripped off the gimbal circuit board thingy. I've flown several times since then and I still get video feed, but the gimbal can't stabilize.
I submitted a ticket to 3DR several weeks ago, and after much hassle (Solo couldn't send the logs for some reason/Tech support went MIA for more than a week) I finally got a ruling today. 3DR says I didn't act to avoid an obstacle in time. I'd be grateful if someone took a look at my logs to help explain what happened. If this was operator error, at the very least, I'd like to know what I could have done different. My gut suspects this was a GPS issue.
Here's 3DR's email:
For background, I have my Part 107 but I'm a relatively new pilot. I've had Solo's slow baby settings on for the last 15 to 20 flights while I learn the sticks.
I was flying at my mom's place in rural Oregon earlier this summer. I launched from her pasture which is surrounded by trees. Solo was flying great and I basically just took it up a ways, looked around, then descended. As I neared the ground, Solo made a beeline for a workshop that was about 15 feet away. I didn't tell it to move in that direction. I also couldn't act fast enough to stop it. The video is pretty hilarious, actually. My whole family waves at Solo as it's graciously descended. Then it suddenly flies sideways for a few seconds and slams into the building.
This also wasn't the first time this has happened. Solo took off toward a building earlier this summer when a friend was flying and a similar thing happened in slow motion.
But during that Oregon crash, Solo's hdmi cable port very slightly ripped off the gimbal circuit board thingy. I've flown several times since then and I still get video feed, but the gimbal can't stabilize.
I submitted a ticket to 3DR several weeks ago, and after much hassle (Solo couldn't send the logs for some reason/Tech support went MIA for more than a week) I finally got a ruling today. 3DR says I didn't act to avoid an obstacle in time. I'd be grateful if someone took a look at my logs to help explain what happened. If this was operator error, at the very least, I'd like to know what I could have done different. My gut suspects this was a GPS issue.
Here's 3DR's email:
Thanks for your patience. We were able to get the logs and check them, finding the incident on the RECENT-9.BIN file.
We checked the sensors and motors and found no issues with them, they all were working correctly. We also checked the autopilot and found it was properly following the user inputs. It seems like the pilot was unable to avoid the obstacle in time while landing, the inputs show the pilot tried going forward just a second before the unit crashed (green line) and before that, it only instructed Solo to rotate (orange line).
<6725.jpg>
Since the logs show the unit followed the user inputs until the moment it crashed and the incident wasn't caused by a hardware malfunction, I'm afraid we won't be able to cover the damage under warranty.
In this case, I recommend you to reach the repair center and get a replacement Gimbal, you can find their information below:
CURRENT UAS
www.currentuas.com
Phone: 619-880-7827