...
- Go-nogo
- Full page of GO-NOGO that is very clear to see
- Is a checklist with checkboxes to fill and roles to call GO-NOGO for certain fields
- Multiple copies of this page in large print
- Launch attempt number: __ is a field
- New Fields:
- Altimeter state at launch
- number of satellite
- Temp/wind speed/direction at launch
- Time & date
- Some way to connect launch attempt with video files
- Altimeter startup time
- Camera startup time
- Liftoff time (seconds)
- Altimeter state at launch
- Tie roles in more distinctly throughout Launch Ops – Andrew
- Train people for their roles at rehearsals
- Define windows of "useful roles" vs "free hands"
- MUST BE DONE BY: XYZ? i.e. Julia calls FAA
- Ask Jakob & Julia
...
- Make quality/consistency integration checklists better across subteams – Assign to teamleads, Andrew & Jamie verify
- ENFORCING CHECKOUT PHOTOS
- Assign a role for that & have a "Master Key" of checkout photos needed for flight
- Checkout photos are GO-NOGO criteria
- AVI: More detail on programming of altimeters on the integration checklist
- Prop & Struc: Torque spec on bolts, Torque stripe all bolts
- Keep checkout photos in bold
- Get rid of ambiguity (e.g. what does "Secure" mean? Pull test? Wobble test? ??)
- Pad Cameras - changes to Launch Ops
- Identify Pad Cameras & order them (How much money do we have to do this???)
- ID each camera and show where it should be placed
- Enforce roles & train for roles
- Add in Camera setup if necessary
- Add in "take photo of camera running with your phone"
- Identify when pad cameras should be turned on and someone from the Pad should signal when that time is
- After altimeter & onboard camera startup complete
- Add in verbal walkthrough of integration checklists?
- Data Recovery
- Checkout photos - see above
- File management scheme: What do you name your files and where do they go so they can be found
- Expand post-launch checklist - add in roles for all subsystems
- Enforce roles!! Launch is not done until this is completed
- In the Event of...
- Premature loss of control in flight, etc... proceed to ballistic recovery
- Medical Emergency
- Rocket otherwise becomes dangerous?
- Go over failure modes at the launch site before flight – add to preflight on-site meeting / safety review thing (in a Kahoot?)
- Preflight Sims
- Split into RasAero & Recovery Sims
- Signatures for each one
- Upload to file, filename?
- List Mission Critical items – USE INTEGRATION CHECKLISTS
- Which things do we NEED to fly? e.g. 3 cameras vs all 5 or otherwise
- Which things can we leave out?
- Continencies for each thing
- Appendix with link & instructions
- Avionics
- Add in tables for Away team & Launch Line to review GO-NOGO parameters
- Choose GONOGO parameters - voltage limits, GPS Lock, Data Logging for Telemega
- Choose GO-NOGO parameters - Pyxida sensors - flight critical and science critical and not critical
- Define acceptable flight scenarios
- > 2 hours in window remaining, do all science-critical items
- < 2 hours in window remaining, only do flight-critical items so we can fly at all
- Replace "on loading to launch rail" to have Launch Line verify table completion
- Add in tables for Away team & Launch Line to review GO-NOGO parameters
...
- Fixed-direction antenna – can be borrowed
- Telephoto lens (95.2" parallax - likely 400mm-600mm needed) – need to be rented (~$100)
- Power bank/generator – need to be rented (available at Home Depot)
- Binoculars
- Emergency radio
- Survival supplies (food, water, shelter, first aid, etc.) -> for cold weather
- Vehicles – off-road capability likely needed
Action Items:
- Contact FAR and BLM (760-384-5400) re. feasibility/permits
...
- Update Launch Ops accordingly
- Order hard drives for data recovery