You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 30 Next »

Scope

Overview

This document will analyze the flight of Hermes 1 at Friends of Amateur Rocketry in July of 2018. The document will outline the flight performance of the vehicle, calling specific attention to any deviances. These flight events will be discussed in roughly chronological order, by subsystem. Under-characterized or poorly understood behaviors will be noted for future efforts. A section at the end of this document will discuss lessons learned.

Methodologies

Times are indicated as T+ or T- from the first vertical motion on the rail (liftoff). Times are indexed off of the Telemetrum data.

Timeline

Time [s]Flight Event
T-3.83

Ignition

T+0.00Liftoff
0.27Tower Cleared
 Pierced Cloud Ceiling
6.75Burnout
43.79Apogee
48.60Drogue Inflation
298.20Main Release
300.5Main Inflation
363.00Touchdown

 

Flight Statistics

ParameterMetricImperialOther Units
Apogee10,187 m32,406 ft6.14 mi
Max Velocity557.7 m/s1830 fpsMach 1.7 (at 10kft MSL)
Max Acceleration116.6 m/s^2383 ft/s^211.9 G
Ground Impact Velocity9.6 m/s32 fps21.8 mph
Flight Duration363.0 s--

Simulation Accuracy

The last simulation before flight predicted an apogee of 31600', which proved to be very similar to the true performance of the rocket. At 2.5% error, it seems our model is accurate enough to predict future flights of comparable rockets.

Avionics

Payload

Propulsion

Thrust Curve

See the motor data page.

Long Startup Time

The motor took significantly longer to light than previous tests, including the second P motor test that used an identical igniter with significantly more propellant surface area. During static fires the igniter was retained by gravity until the motor had built up enough pressure to eject it. Video evidence shows that the igniter fell out of the motor within a second of firing.

 

Future efforts could faster-burning igniters (pyrogen or BKNO3), higher surface area propellants (pixie dust), or additional mechanical retention. While chuffing represents a minor issue on this flight, successful, rapid, and complete ignition is a necessary technical milestone for multistage flight. Care must still be taken to not over-pressurize the case or clog the nozzle with a large igniter.

Recovery

For a complete Recovery analysis, please visit the Hermes I Recovery Analysis.

Parachute Drag Coefficients

Here is a graph of the effective drag of the drogue as felt by the mission package between 7k-8k meters. This includes the drag on the mission package as well as influences from the fin can.

Here is a graph of the effective drag of the main as felt by the mission package:

 

 

Here is a graph of shock loading:

E-match voltage anomaly

Post flight data review notes abnormal voltage readings on Telemetrum apogee channel. Despite commanding an apogee event, the Telemetrum continued reading 4.2V across the channel for the remainder of flight. The e-match should register a significant increase in resistance within 10 mS of exceeding it's no-fire current of no fire current here. This suggests that the initiator misfired.  A fishbone analysis was conducted to classify the nature of the issue. Evidence collection is ongoing, however it appear probable that the Telemetrum e-match is internally shorted, either autogenously or to the piston.

We checked continuity post-flight and neither e-match had continuity. This suggests that the e-matches were not internally shorted to the piston. This is not a conclusive test because the wires could have been jostled during landing or travel.

Structures

 

 

Integration

Integration began at roughly 1:30 pm PST and the rocket arrived on the pad at roughly 3:00 pm PST.

Lessons Learned

  • Having a good checklist would have been beneficial, even though we likely wouldn't have been able to integrate the rocket in the amount of time that we were given before the end of the launch window if we had been following a strict checklist.
  • Regular batteries are NOT enough to fire 2 e-matches in parallel. We ran into this problem during the ground test, as well as a previous static fire.
  • No labels