The .txt is what I was needing. The PhantomHelp link will show a page with a link that will allow the original .txt to be downloaded.Appreciate the help but you're looking at it wrong.
I am an experienced flier. First, you can't fly a WP in ATTI. The third mission for all intense and purposes began at R where it says "Starting Waypoint Mission" and entered NaviGo. Until the crash, and right before it, the only notice I got was right before the crash where it said "altitude limit mode".
Look from R. That was the third round and it says "Starting waypoint mission". No warning from there. Sometimes I switch to sport mode or atti mode to get it back to the area that is near the first WP mission. Again, 3 WP missions here, not one, for purposes of ease, I've just posted the part where it went from WP mode to the crash.
Thanks for looking into it!
@JohnnyB
EDIT: For reference, look at this. I just copy and pasted but it should show you what I mean. I was in atti and/or sport to return to the WP first point, and then switched to and began the WP mission which it flew correctly two times on this flight before it.
So as you can see, I was most certainly in GPS WP mode when it crashed. I would love to see what I was doing on the sticks at that time but don't know how. I was aware at that moment because it didn't go through the two trees that it did the last two times the something was up. It HAD to be the Altitude Limit Mode or just maybe interference or just a freak out on the board? I have no idea which is why I am so perplexed. If I knew why, I wouldn't post this. So frustrating now knowing why it acted this way.
P 07m 09s 128.6 ft 41 ft Mode Mode changed to GPS_Atti
Q 07m 36s 128.3 ft 41 ft Tip Waypoint Mission Started__Return-to-Home Altitude:492FT
R 07m 36s 128.3 ft 41 ft Mode Mode changed to Waypoint
S 07m 50s 75.8 ft 12 ft Tip Arrived at Start Point. Starting Waypoint Mission
T 09m 39s 132.5 ft 926 ft Warning Warning:Altitude Limited Mode Entered
U 09m 41s 136.2 ft 943 ft Warning Warning:Altitude Limited Mode Entered
V 09m 43s 139.1 ft 958 ft Warning Warning:Altitude Limited Mode Entered
W 10m 00s 169.6 ft 1,078 ft Warning Warning:Altitude Limited Mode Entered
X 10m 46s 134.2 ft 781 ft Warning Warning:Altitude Limited Mode Entered
Y 10m 49s 130.6 ft 761 ft Warning Warning:Motor Obstructed
It began the WP mission at 7m 36s
and first warning was "altitude limit mode entered" which frankly didn't scare me. Thought it was just some safety mode that I was unaware of.
A couple minutes later and less than a minute from the crash I got the first warning. The crash happened at about X and Y. I did' realize it was heading for that tree until W and that 46 seconds wasn't enough time to correct what was wrong although I was calm the whole time. I almost, as evidenced by the video escaped the tree but missed it by a nano inch.
Thanks again
This .txt had two WP missions. Possibly the first WP mission is in a separate .txt; a new .txt is created when the P4 is landed. In this .txt it appears that the WP missions are identical, but the first WP mission was aborted and the P4 was brought back to the home point and the second WP mission was initiated.
At time 647.86 it appears that the P4 while still in WP mode stopped and started thrashing around.
The GE image doesn't show anything that it would've hit. Maybe the image is off some.
You asked about the control inputs. Might be a little hard to interpret.
This shows that the throttle had just been pushed all the way forward. The elevator was pushed all the way forward a few seconds later.
It looks to me like the WP mission path took it directly into what ever it hit. The first WP was aborted before it got that far. The flight actually lasted for another 36 seconds. When the RTH button was pressed at 674 secs it couldn't. From your description I'm supposing that it was hung up in the tree.