Here is a fresh animation of images captured by #Ingenuity from 06:06 to 09:17 AM tosol, Sol 1043, showing clearly that at least two of the 4 rotor blades were damaged during #Flight72.
14 processed HELI_NAV images
captured from RMC 72.0001/54
Sol 1043, LMST: 06:06 to 09:17
@shom
It has been expected since a long time ago. I find it very fortunate that Ingenuity is upright and fully functional otherwise. I guess in a way, it releases most of the team members to attain other tasks, while (hopefully) keeping the daily routines of the rover team the same, gathering data from it and passing it to the designers of the #SRH .
@65dBnoise
I would expect all 4 rotor blades to be similarly damaged, given the rotation speed.
If the impact energy goes into breaking off the tips rather than stopping the spin, then wouldn't all the blades be likely to hit the ground, perhaps many times each?
@tom30519
Ah, but there's other helis coming soon after it, more powerful and equipped with arms and wheels! And maybe they'll fly not at 12m or 20m alt but at 50 and 100m. 😀
@tom30519
OK. But maybe next Martian year, while the air density will still be high and temperatures high too, Ingenuity will try to fly in short hops using high rpm instead of low rpm, or will even try to push rpm even further. It'll have to cover a significant distance flying up the Jezero rim to rejoin the rover, but it'll have nothing else to do at that point, so, there's that 😎
@tom30519
Well, if I were in NASA's payroll and dealing with the design of SRHs I wouldn't mind at all the awe factor created by the resurrection of Ingenuity after staying in survival mode during its second Martian winter. Just imagine the headlines 🙃
@tom30519
Back of the envelope calculation of loss over a 5km distance at that frequency is 102dB. With a 108dB receive threshold, that means a 6dB margin for reception, which is doable, if my numbers and formulas are OK.
@tom30519
Are they going to explore Neretva Vallis? I think they are going up the rim of Jezero, southwest of Neretva Vallis; at least that's what the planned route showed in that MEPAG presentation that I copied the route from.
Add comment