Home Creators Posts Import Register Favorites Logout
haven't archived this post yet. have a subscription? use the importer!

Downloads

  • Sprint_Flight_6_Failure_Analysis.pdf

Missing 1 file, as this post has not yet been imported.

Content

Hey folks! If you're like me, you like details.

I spent most of today writing up a formal evaluation of why Sprint's 6th flight failed. The TLDR is that I need to revise the full state feedback controller. It was sort of an axis reversal problem, but also sorta not...

Either way, enjoy! We'll be ready to fly again, likely in a few days :)

Blue skies,

Joe

Comments

Anonymous

The last sentence tripped me up: "The next flight attempt is expected to happen within one week from writing this - May 23, 2020." At first I parsed the date as the expected date for the next flight attempt and was excited (and a little confused). Then I realized that it was the date of write up.

Chris Silvia

This is cool to see. It's interesting that you're getting around a lot of the "fun" parts of measuring orientations by tracking the yz components. Also, I wonder what the latency of GPS measurements are?

Anonymous

If I would conclude the document, there should be a section of what scenario could trigger which behavior. E.g. a gust could lead to that deviation of track and the correction would take that amount of time. Classification of risks and avoidance