First off - fair warning, I am a
complete rookie at analyzing flight logs, but here is what I can see in . I expect
@sar104 to be able to give you far more detailed view after he looks at the file. And yes - this is a LONG note, I tried to relay everything that may be of interest from the files.....
- manual takeoff, home point recorded.
- full throttle and full elevator for first part of flight
- at 2 minutes 23 seconds into the flight, you reach maximum altitude of 400 feet.
- from there you proceed with full elevator, level flight, crossing the A12 motorway.
- at 2 m 45 s, shortly after crossing the A12 you get a high wind warning, and are advised to fly with caution. You are already a long ways from the park.
- at 3 m 50 s, you have crossed Watenden Road, and are almost 5,000 feet from takeoff point. Here you get a warning that you are approaching a No Fly Zone, and that RTH may be affected. There does not appear to be any immediate change in your input via the RC.
- about 1.5 seconds later at 3 m 51 s you get a second message - that "your aircraft is at a boundary of an Authorization Zone, please fly away."
- abut 4 seconds later you start some left rudder input, until you have completed approximately a 90 degree left turn.
- a few seconds later at 4 m 18 s, you ask for a change to Sport Mode, but it appears that communication is lost, so my guess is that the drone never received that command.
- about 6.8 seconds later (4 m 25 s) you get a message that downlink has been restored, after being lost for 6.8 seconds. You get a second warning about high wind speeds and are advised to land ASAP. Aircraft mode is still P.
- flight continues with full elevator input for another 27 seconds or so, and then you get a final warning about signal: "Weak signal. Avoid blocking the antennas and keep the antennas parallel to and facing toward the aircraft during flight.".
- That is the last transmission I can see in the log, and places the aircraft over what looks like a parking garage over top of a rail station. You say that it flew into a building - the log does not show that. At the time of last transmission, the bird was 1745 m from launch point (as the crow flies), and had covered a distance of 2345 m in the flight.
- I can't see any indication that RTH was ever initiated, either automatically or by your command, or that the bird ever turned back towards the launch point. Also, the log seems to indicate that the flight was in P mode the entire time.
- I see no indication that the flight ever exited the Authorization Zone, so not clear to me what impact that might have had on the RTH function. We saw a case in the USA last week where a Temporary Flight Restriction came into effect during a flight and that caused the drone to land immediately - into the water. I do not know how that works in Europe.
- I don't know what variables to look at in the verbose CCVS file to understand status of the optical sensors, but in P mode, I believe they default to on.
That is nowhere near a nice an analysis as
@sar104 will undoubtedly produce, and lacks the graphical representation of the different variables in the log file.
A few questions - did you recover the drone, and if so, can you share lat/long where you recovered it? What leads you to believe that it flew into a building, it would have been challenging to see the drone given its distance from you (assuming you stayed at the takeoff point)??
To the experts - I am more than happy to have your view of this analysis. Like I said up top, I am new to this, and am interested in learning to get better at it.......
Thanks...
