FAROUT Hybrid & Liquid Propulsion Mentor and Safety Official
- Problem
- How can student propulsion teams make readiness decisions from configuration-specific evidence?
- Role
- Hybrid/liquid propulsion technical mentor and safety reviewer.
- Method
- Reviewed hardware, fault cases, procedures, and readiness material; mentored teams through issue closure.
- Result
- Reported support for three teams in 2025 and five teams in the 2026 cycle.
- Status
- Ongoing mentorship; support does not constitute formal certification or independent verification.
Project Narrative
I serve as a hybrid and liquid propulsion safety and technical mentor for FAROUT (Friends of Amateur Rocketry: Oxidizers Uninhibited Tournament), a collegiate competition centered on student-developed propulsion systems. The role sits between design review and field operations: helping teams turn an engine concept, feed system, and test plan into evidence that can support a readiness decision.
My work has included reviewing propulsion hardware, pressure-fed architectures, procedures, fault cases, and flight-readiness material; mentoring teams through design iteration; and supporting static-fire and launch operations. The central challenge is not simply identifying a hazard. It is making the concern traceable to a component, an operating condition, an owner, and evidence of closure.
Review Scope
A useful safety review connects the schematic, physical hardware, procedure, and expected operator response.
I review how tanks, regulators, valves, lines, injectors, and controls behave as a system rather than as isolated parts. That means checking pressure and thermal margins alongside valve logic, vent and purge paths, instrumentation, abort conditions, and the sequence an operator is expected to follow. Single-fault questions are framed around concrete states: what changes, how the team detects it, and what action leaves the system in a safer configuration.
Mentorship Across Teams
Advice is most valuable when the team can own the reasoning and close the issue themselves.
My 2025 work included supporting three teams through static-fire and launch operations. For the 2026 cycle, my mentoring scope expanded to Columbia Rocketry and four international teams. Because each team brings a different design maturity, test history, and documentation culture, I focus on the reasoning behind a recommendation rather than prescribing one universal architecture.
Readiness as a Traceable Decision
"Go" is not a feeling; it is a claim supported by configuration-specific evidence.
The standard I apply is a short chain of evidence: identify the submitted configuration, record the technical question, name the required evidence, assign ownership, and verify closure against the current revision. This keeps unresolved work visible and separates mentorship from formal decision authority. It also makes later review possible when hardware or procedures change between a static fire and a launch attempt.
What the Record Can and Cannot Show
An incident-free event is an outcome, not proof that every hazard was eliminated.
Team counts describe mentoring scope, not engineering margin. Likewise, safe operations do not by themselves validate every calculation or control. Redacted checklists, dated revisions, and concrete closure examples are the next evidence package to add; until then, this page describes my role and review approach rather than certifying the teams' systems.