(December 22, 2013 – Cuyahoga Falls, OH )
Today’s post is a dual subject (rocket) post, and it kind of has to be. Enjoy the info!
Impressive data:
I finally inally got around to looking closer at the flight data from Nesaru’s first two flights from around a year ago, and was able to get very accurate data on its actual velocity on those flights.
Back of the napkin calculations at the time with a cursory glance at the data showed flight #1 (NLS-001) achieving a peak velocity of mach .75.
Official number?: Mach .76! (578 MPH).
Flight #2 (NLS-002): Mach .78 (593 MPH).
Between flight #1 and #2, a number of changes were made to the design as a result of an unsuccessful first flight, resulting in some weight reductions.
Flight #2 was also plagued with a problem. Both missions resulted in a “hard landing”, mission NLS-001 being the worst of them. Nesaru bears some of the scars from those two flights!
Since then, Nesaru has flown missions NLS-003 to 006 on lower impulse motors so it’s average speed has been around 450 MPH.
It wasn’t my intention to fly in the trans-sonic region of flight. The motor I had at the time (CTI-H255 wt) is a very punchy motor, and I knew the design was tough enough to take such a motor, but the XR6 wasn’t designed with “flying at or near Mach velocities” in mind, so it is interesting to see that it handled itself OK at velocities very close to Mach1.
I’m reviewing this data closely at this data, as the behavior of the XR6 under the stresses of trans-sonic flight were an important factor in the final design decisions for Comanche XR9C.
Being a full pound lighter than Nesaru XR6, Comanche stands an even greater chance of breaking Mach 1, though I will not try to go for that (intentionally) right away.
Comanche is set for a second attempt at a maiden launch December 28, 2013 — weather permitting.
So far, weather forecasts place launch conditions are within an acceptable range for launch. The window between the current weather front, and the next one leaves a 1 day window of opportunity (Dec 28th). If the front moves faster or slower then predicted, it will cause another scrub of the maiden launch attempt.
Stay tuned!
((( )))
