A reworked hypothesis about #Ingenuity's last #Flight72 explained with an animation. It is based on a number of assumptions, most of which come out of #NASA's statements.

Animation explained in alt text.

Processed, cropped MCZ_RIGHT, FL: 110mm
looking NW (320°) from RMC 50.1534
Sol 1067, LMST: 10:27:39

Original: https://mars.nasa.gov/mars2020-raw-images/pub/ods/surface/sol/01067/ids/edr/browse/zcam/ZR0_1067_0761655208_206EBY_N0501534ZCAM05186_1100LMJ01.png
Credit: #NASA/JPL-Caltech/ASU/65dBnoise

Thread
1/6

#Mars2020 #Solarocks #Space

Facts and/or assumptions:
• The #MarsHelicopter flew to an altitude of 12m
• At that altitude of 12m, it hovered for a while, sending telemetry
• It started looking for a clear spot to land
• After selecting the best spot for landing, it started its descent as usual
• During the descent, communication with #Perseverance was lost.

Other (almost) facts:
• Whatever was that caused the failure (mechanical, electrical or electronic), all rotor blades had their tips sheared while one of them

2/

detached from the assembly and flew 13-14m to the SW, bouncing once before it stopped.
• The elevation difference between the location of the helicopter and the broken off blade appears to be less than 0.5m, from the #USGS 1m DTM.
• It takes 0.37s for a body to drop 0.5m under the 3.72m/s² of Martian gravity. The initial velocity for a projectile to travel 13m in 0.37s would be ~35.5 m/s, without taking into consideration friction in the thin Martian air. If friction is to be considered for

3/

a very lightweight object with large surface, like the broken off part of #Ingenuity's blade, then the initial velocity should be significantly higher to cover the same distance.
• If however the blade broke off at a, let's say, 3m altitude, then the initial velocity would be ~14.5 m/s, which is much more logical, considering that a significant amount of kinetic energy would have been consumed by the tip of the blades being sheared before flying away, either by hitting the ground or by

4/

disintegrating in mid air. From a 12m altitude, which was the planned altitude for #Flight72, the initial velocity would need to be only 7.23 m/s.
• The fact that the ejected blade appears to have bounced only once and came to a stop a short distance away from the point of impact suggests that its velocity when it bounced was not high.

All the above appear to suggest that the failure occurred at a higher altitude rather than on the ground. The fact that NASA knows it

5/

lost communications *before* touchdown, as well as that there are no visible marks on the regolith, other than those probably made by the copter's feet (see https://mastodon.social/@65dBnoise/111992357079999905), seems to support this hypothesis. Is it the only possible explanation? Probably not. But it appears to me to be the most plausible one.

6/6

#MarsHelicopter #Ingenuity #Mars2020 #NASA #Solarocks #Space

@65dBnoise
The loss of communication is a puzzle, unless the sudden imbalance of the rotors triggered an emergency power shutdown.

If the rotors were still under power at that point, surely the loss of one blade would have caused the heli to spin, having lost the counter-rotation effect. But the footprints of where it bounced don't appear to show rotation.

@tom30519
True. They don't show marks of blades on the regolith either.

The broken blade's trajectory needs an explanation in both cases. A piece of thin blade thrown 13m away from the ground after hitting loose regolith needs some special conditions to happen. The impact would have absorbed most of the kinetic energy of the lightweight blade. Unless the grounding shock broke off its connection to the other blade and it flew off without hitting the ground. But we don't see it in one piece.

@tom30519 @65dBnoise
In one of the early press conferences after the incident it was said that one theory was that whatever happened to the blades caused a power demand surge in the motor which caused a "brown-out" and a system reboot. Another theory they said was that battery voltage dropped too low for other reasons triggering a shutdown/reboot during the flight.

@Undertow @65dBnoise
Oh, right. I'd forgotten about that brown-out having been mentioned.

I suppose that, if the severed blade had twisted to present a much greater resistance before breaking off, that would indeed cause a sudden spike in the motor's load.