To hit on a few things I read on this thread since I posted it...
First and foremost, Im a software engineer in SF, I know what Im doing with technology, and I can promise all of you I never touched Mission Planner, Tower, or any of those apps. I opened the Solo from the box, flew it 3 times using the Solo android app and the only thing I changed was the max altitude from 150ft to 250ft. Thats is it. After I sent the logs to 3DR I reviewed them myself and saw that the ARMING_CHECK was set to 0 on that final crash flight. The pixhawk doesnt seem to log param changes though, which is weird to me because it does log any and all SSH connections made to it. So You could see that all SSH connections were made by the controller, no connections were made by any other IP's or apps. So there is no way to see how or when the param was saved other then the fact that on the day of the flight, the logs show ARMING_CHECK set to 0 when the Solo turned on.
I agree, I don't think params like that can just change, as they are written to a file explicitly as a 1 or a 0. But I can assure you that I did no changing of params and the only time I downloaded the APM software for mac was the night of the crash because I wanted to see the logs myself after I had sent them off to 3DR.
Anyway, 3DR did see weird stuff in the logs, like a lot of users here saw on the flights leading up to that day so they are issuing an RMA and repairing the drone and gopro under warranty so I amd very glad about that and I look forward to flying the Solo again now that my anger has worn off a bit.
I will be very cautious after this though and will probbaly review the logs periodically to ensure ARMING_CHECK is always set to 1.