Advertisement
As you can see, that's a lot of stuff to look at. Particularly right after landing, it gives you a pretty
good idea of what happened. For example, we did a test in which we intentionally didn't install a
drogue charge and left out the motor eject, and turned on FailSafe as a test. (We don't recommend
that YOU do this, though...) We expected the Main to pop 3-4 seconds after apogee, but that didn't
happen, instead it came out at about 500' as if there was a drogue. When we looked at the Flight
Summary data, it turns out that it never fell fast enough to trigger FailSafe... it was a light Estes
rocket on an Aerotech F24, and the drag was enough to slow it down below the threshold.
We've had other flights in which we had FailSafe enabled as a safety measure, and it triggered when
we though it should not have. Turns out the drogueless rocket fell faster than we expected...
obviously we should have modeled it better! All of this data can tell you a lot... and help you model
your later flights better.
Viewing the Flight Settings
To see the flight settings that were used for this flight, click on the Settings link at the bottom of the
Flight Summary page.
Proton_2abcd
Flight Settings
Flight No.: 2
LDA Alt......................200 ft
Launch Samp/Sec.........20
Nose-Over Samp/Sec....2
Accel LD Time.............3 sec
Accel LD G's................3 G
CH1: Drogue
Delay.................0.0 sec
On-Time............1 sec
CH2: Main
Alt....................500 ft
Deploy..............Igniter
On-Time...........1 sec
Failsafe:............1000 ms
FS Velocity.......100 fps
CH3: OFF
CH4: OFF
CH5: OFF
CH6: OFF
Exit
1.01a
- 36 -
Advertisement
