Mavic crash

[SGM]

Looking for some help and information on my MP.
Flying a simple mission today and while bringing it straight down from 207' AGL, it suddenly slid left 124 feet into a tree.
3 broken arms, gimbal sheared off and not sure what other damage as it fell 80 ft into the ground .

My question, would someone kindly take a look at the flight data/record and see if they can figure out what the heck happened!? I have looked at Airdata but nothing that would tell me why the MP would all of a sudden veer off and I was sliding left at such a fast speed. Just before it happened I received a message my IPad -CPU overloaded.

Any help would be appreciated. Wont help on the repair bill but I need to know why.

Also, what is the URL or link for the flight dat analysis?

 

[Stan1915]

Give @Thunderdrones a shout about repairs. He can get you back to flying!

 

[SGM]

Thanks Stan1915 going to give a shout in the morning. just trying to figure this out now.

 

[Jacknet007]

I was on RTH and Mavic was descending in an area I flew several time before . At about 40 feet as it was doing precision landing it suddenly veered way off course with no stick inputs. Thankfully I was able to use stick to avoid a fence and land it. No explanation at all.

 

[SGM]

I've read a lot of flyaways for no reason but have yet to read of a good reason for them. Like I said, doesn't help with repair costs, but after 8 months of flying every one of my issues have been dji related.

 

[sar104]

It slid left because at 757 seconds, 9 seconds before it crashed, at an altitude of 170 ft, you applied full left aileron. It did what you told it to do, and moved to the north.

 

[Haloweenhamster]

I had a fly away, no hands on the sticks but log showed 100% down 100% left, it started on a video glitch on the phone so my thoughts were interference, dji said it can't have been and I was controlling it, at least I had no damage from mine

 

[rfc]

It slid left because at 757 seconds, 9 seconds before it crashed, at an altitude of 170 ft, you applied full left aileron. It did what you told it to do, and moved to the north.

View attachment 23798

What software/site did you use to make that plot?

 

[sar104]

What software/site did you use to make that plot?

The data are directly from the log file. Analysis and graphical visualization was done using Wavemetrics Igor Pro.

 

[SGM]

Thanks sar104, I realize you have only the data to go by and I appreciate it! By your graph it would appear I did in fact give it full left aileron. Was it pilot error? it would appear so, for what ever reason I cant imagine with the many hours never having done that before. Perhaps my attention was taken at that moment? and a good lesson for every pilot out there. (for me to figure out now) I am just having a hard time with it, I know I gave it "down" stick as I was bringing it down for a landing and my sticks had been calibrated. at this point whether pilot error, a "glitch" or combination of several events taking place?? Again I appreciate your time looking at this, you've been a great help!

 

[sar104]

Thanks sar104, I realize you have only the data to go by and I appreciate it! By your graph it would appear I did in fact give it full left aileron. Was it pilot error? it would appear so, for what ever reason I cant imagine with the many hours never having done that before. Perhaps my attention was taken at that moment? and a good lesson for every pilot out there. (for me to figure out now) I am just having a hard time with it, I know I gave it "down" stick as I was bringing it down for a landing and my sticks had been calibrated. at this point whether pilot error, a "glitch" or combination of several events taking place?? Again I appreciate your time looking at this, you've been a great help!

One followup question relating to the stick input: it headed left for 9 seconds before it crashed and you don't recall applying left aileron but, when it moved left, why did you not attempt to correct the movement with right aileron?

 

[SGM]

I received a message on the screen saying CPU overloaded and went into ATTI mode... I looked down! Wasn't worried since the MP was at 200+ when I looked up... Too late

 

[SGM]

To answer why I didn't apply right aileron, while I should have been looking the the a/c, I knew I was holding stick down and never expected it to slide period. Bad answer I know.

 

[sar104]

I received a message on the screen saying CPU overloaded and went into ATTI mode... I looked down! Wasn't worried since the MP was at 200+ when I looked up... Too late

It did not go into ATTI - it was in P-GPS through the end of the flight after exiting tripod mode at 750 s. What kind of iPad were you using?

 

[SGM]

Yes, you're right, don't know where I remembered it going into ATTI but that was incorrect.

I was using a iPad Air 2 version 10 The iPad wants me to update to 11 but I haven't done it yet. this happened a couple of weeks ago stating CPU was overloaded, when I went in to the iPad, it had loaded the update into my installed apps which took up I believe 1.6 gigs even though I hadn't downloaded it. Deleted the app and all was good until yesterday, got home and iPad did it again, I believe causing the overloaded issue. Could be wrong (I'm certainly no guru) and may be a coincidence, just don't have the money to buy a dedicated monitor.

Long story short and again I was incorrect about the ATTI, it was probably my error/in-attention at a critical moment so I ate it. When I get the money together I'll get it fixed.

 

[scjerry]

It slid left because at 757 seconds, 9 seconds before it crashed, at an altitude of 170 ft, you applied full left aileron. It did what you told it to do, and moved to the north.

Question from a newbie. This .txt file from the mobile device is one of two log files, the other being the .dat file from the flight controller. Are the stick (and other) commands also recorded in the dat file, and if so could they be different?

 

[sar104]

Question from a newbie. This .txt file from the mobile device is one of two log files, the other being the .dat file from the flight controller. Are the stick (and other) commands also recorded in the dat file, and if so could they be different?

I've not seen different values in the two files, but I cannot say that it is not possible.

 

[scjerry]

I've not seen different values in the two files, but I cannot say that it is not possible.

Do you have access to the column defs for the .txt to .csv conversion done by farraript's TXTLogtoCSVtool? They're not on Bud Walker's site. And I've asked ferraript.

 

[sar104]

Do you have access to the column defs for the .txt to .csv conversion done by farraript's TXTLogtoCSVtool? They're not on Bud Walker's site. And I've asked ferraript.

Sorry - I do not.

 

[scjerry]

Sorry - I do not.

OK, I've extracted the column headers for the benefit of the community. Maybe we can get defs somewhere. Some are obvious...some are not. I'm sure some are AC dependent and some columns may be mobile device dependent. Mine is iOS Mini 4 wifi+cell and the data for APP_GPS is filled in with lat/long data.
CUSTOM.updateTime
CUSTOM.isPhoto
CUSTOM.isVideo
CUSTOM.hSpeed [m/s]
CUSTOM.distance [m]
CUSTOM.travelled [m
CUSTOM.hSpeed.running_max [m/s]
CUSTOM.distance.running_max [m]
CUSTOM.height.running_max [m]
OSD.latitude
OSD.longitude
OSD.height [m]
OSD.altitude [m]
OSD.xSpeed [m/s]
OSD.ySpeed [m/s]
OSD.zSpeed [m/s]
OSD.pitch
OSD.roll
OSD.yaw
OSD.flycState
OSD.flycState.RAW
OSD.flycCommand
OSD.flycCommand.RAW
OSD.canIOCWork
OSD.groundOrSky
OSD.isMotorUp
OSD.isSwaveWork
OSD.goHomeStatus
OSD.goHomeStatus.RAW
OSD.isImuPreheated
OSD.isVisionUsed
OSD.voltageWarning
OSD.modeChannel
OSD.isGPSused
OSD.compassError
OSD.waveError
OSD.gpsLevel
OSD.batteryType
OSD.isAcceletorOverRange
OSD.isVibrating
OSD.isBarometerDeadInAir
OSD.isMotorBlocked
OSD.isNotEnoughForce
OSD.isPropellerCatapult
OSD.isGoHomeHeightModified
OSD.isOutOfLimit
OSD.gpsNum
OSD.flightAction
OSD.flightAction.RAW
OSD.motorStartFailedCause
OSD.motorStartFailedCause.RAW
OSD.nonGPSCause
OSD.nonGPSCause.RAW
OSD.isQuickSpin
OSD.battery
OSD.sWaveHeight [m]
OSD.flyTime
OSD.motorRevolution
OSD.flycVersion
OSD.droneType
OSD.imuInitFailReason
OSD.imuInitFailReason.RAW
OSD.motorFailReason
OSD.motorFailReason.RAW
OSD.ctrlDevice
OSD.ctrlDevice.RAW
GIMBAL.pitch
GIMBAL.roll
GIMBAL.yaw
GIMBAL.mode
GIMBAL.mode.RAW
GIMBAL.rollAdjust
GIMBAL.pitchAdjust
GIMBAL.yawAngle
GIMBAL.isAutoCalibration
GIMBAL.autoCalibrationResult
GIMBAL.isPitchInLimit
GIMBAL.isRollInLimit
GIMBAL.isYawInLimit
GIMBAL.isTopPosition
GIMBAL.isStuck
GIMBAL.version
GIMBAL.isSingleClick
GIMBAL.isDoubleClick
GIMBAL.isTripleClick
GIMBAL.timeStamp
RC.aileron
RC.elevator
RC.throttle
RC.rudder
RC.gimbal
RC.goHome
RC.mode
RC.isWheelChanged
RC.wheelOffset
RC.wheelClick
RC.record
RC.shutter
RC.playback
RC.custom1
RC.custom2
RC.bandwidth
CENTER_BATTERY.relativeCapacity
CENTER_BATTERY.currentPV [V]
CENTER_BATTERY.currentCapacity [mAh]
CENTER_BATTERY.fullCapacity [mAh]
CENTER_BATTERY.life
CENTER_BATTERY.loopNum
CENTER_BATTERY.errorType
CENTER_BATTERY.current [A]
CENTER_BATTERY.voltageCell1 [V]
CENTER_BATTERY.voltageCell2 [V]
CENTER_BATTERY.voltageCell3 [V]
CENTER_BATTERY.voltageCell4 [V]
CENTER_BATTERY.voltageCell5 [V]
CENTER_BATTERY.voltageCell6 [V]
CENTER_BATTERY.serialNo
CENTER_BATTERY.productDate
CENTER_BATTERY.temperature [C]
CENTER_BATTERY.connStatus
CENTER_BATTERY.totalStudyCycle
CENTER_BATTERY.lastStudyCycle
CENTER_BATTERY.isNeedStudy
CENTER_BATTERY.isBatteryOnCharge
SMART_BATTERY.usefulTime
SMART_BATTERY.goHomeTime
SMART_BATTERY.landTime
SMART_BATTERY.goHomeBattery
SMART_BATTERY.landBattery
SMART_BATTERY.safeFlyRadius
SMART_BATTERY.volumeConsume
SMART_BATTERY.status
SMART_BATTERY.status.RAW
SMART_BATTERY.goHomeStatus
SMART_BATTERY.goHomeStatus.RAW
SMART_BATTERY.goHomeCountdown
SMART_BATTERY.voltage [V]
SMART_BATTERY.battery
SMART_BATTERY.lowWarning
SMART_BATTERY.lowWarningGoHome
SMART_BATTERY.seriousLowWarning
SMART_BATTERY.seriousLowWarning
Landing
SMART_BATTERY.voltagePercent
DEFORM.isDeformProtected
DEFORM.isExceptionState
DEFORM.deformStatus
DEFORM.deformStatus.RAW
DEFORM.deformMode
DEFORM.deformMode.RAW
RC_GPS.startupTime
RC_GPS.latitude
RC_GPS.longitude
RC_GPS.xSpeed [m/s]
RC_GPS.ySpeed [m/s]
RC_GPS.gpsNum
RC_GPS.accuracy
RC_GPS.gpsStatus
HOME.latitude
HOME.longitude
HOME.height [m]
HOME.isHomeRecord
HOME.goHomeMode
HOME.aircraftHeadDirection
HOME.isDynamicHomePointEnabled
HOME.isReachedLimitDistance
HOME.isReachedLimitHeight
HOME.isMultipleModeOpen
HOME.goHomeStatus
HOME.hasGoHome
HOME.compassCeleStatus
HOME.isCompassCeleing
HOME.isBeginnerMode
HOME.isIOCEnabled
HOME.iocMode
HOME.goHomeHeight [m]
HOME.courseLockAngle
HOME.dataRecorderStatus
HOME.dataRecorderRemainCapacity
HOME.dataRecorderRemainTime
HOME.dataRecorderFileIndex
HOME.isFlycInSimulationMode
HOME.isFlycInNavigationMode
HOME.isWingBroken
HOME.isBigGale
HOME.isBigGaleWarning
HOME.isCompassInstallErr
HOME.isFanCurrentInAbnormalState
HOME.paddleState
HOME.heightLimitStatus
HOME.useAbsoluteHeight
HOME.motor1EscmState
HOME.motor2EscmState
HOME.motor3EscmState
HOME.motor4EscmState
HOME.motor5EscmState
HOME.motor6EscmState
HOME.motor7EscmState
HOME.motor8EscmState
HOME.forceLandingHeight [m]
RECOVER.droneType
RECOVER.appType
RECOVER.appVersion
RECOVER.aircraftSnBytes
RECOVER.aircraftName
RECOVER.activeTimestamp
RECOVER.cameraSn
RECOVER.rcSn
RECOVER.batterySn
RECOVER.gimbalType
FIRMWARE.version
DETAILS.street
DETAILS.citypart
DETAILS.city
DETAILS.area
DETAILS.isFavorite
DETAILS.isNew
DETAILS.needUpload
DETAILS.recordLineCount
DETAILS.timestamp
DETAILS.latitude
DETAILS.longitude
DETAILS.totalDistance [m]
DETAILS.totalTime
DETAILS.maxHeight [m]
DETAILS.maxHorizontalSpeed [m/s]
DETAILS.maxVerticalSpeed [m/s]
DETAILS.photoNum
DETAILS.videoTime
DETAILS.takeOffAltitude [m]
DETAILS.droneType
DETAILS.activeTimestamp
DETAILS.aircraftName
DETAILS.aircraftSnBytes
DETAILS.cameraSn
DETAILS.rcSn
DETAILS.batterySn
DETAILS.appType
DETAILS.appVersion
APP_GPS.latitude
APP_GPS.longitude
APP_GPS.accuracy