2024 Student Launch Handbook & Request for Proposal i

Table of Contents

Acronym Dictionary.......................................................................................................................iii

Statement of Work ..................................................................................................... 1

Design, Development, and Launch of a Reusable Rocket and Payload 

Statement of Work (SOW)........................................................................................................... 2

College/University SLI Division Handbook .............................................................. 3

Timeline for NASA USLI Division ............................................................................................... 4

General & Proposal Requirements ........................................................................................... 5

 Student Launch Requirements ............................................................................................... 6

 Proposal Requirements......................................................................................................... 15

 Project Deliverables .............................................................................................................. 17

Project Milestones: Criteria & Expectations........................................................................... 18

 Preliminary Design Review (PDR) ......................................................................................... 19

 Critical Design Review (CDR)................................................................................................ 23

 Flight Readiness Review (FRR)............................................................................................. 28

 Flight Readiness Review Addendum .................................................................................... 34

 Launch Readiness Review (LRR) .......................................................................................... 36

 Post-Launch Assessment Review (PLAR) ............................................................................ 37

STEM Engagement.................................................................................................................... 38

 STEM Engagement Activity Types ........................................................................................ 39

 STEM Engagement Activity Report ...................................................................................... 40

Safety.......................................................................................................................................... 44

 High-Power Rocket Safety Code.......................................................................................... 45

 Minimum Distance Table....................................................................................................... 46

Awards........................................................................................................................................ 47

 College and University Division Awards ............................................................................... 48

 Artemis Student Challenges Awards .................................................................................... 49

Middle/High School SLI Division Handbook .......................................................... 50

Timeline for NASA SLI Division ................................................................................................ 51

General & Proposal Requirements ......................................................................................... 52

 Student Launch Requirements ............................................................................................. 53

 Proposal Requirements......................................................................................................... 62

 Project Deliverables .............................................................................................................. 64
2024 Student Launch Handbook & Request for Proposal ii

Project Milestones: Criteria & Expectations........................................................................... 65

 Preliminary Design Review (PDR) ......................................................................................... 66

 Critical Design Review (CDR)................................................................................................ 70

 Flight Readiness Review (FRR)............................................................................................. 75

 Flight Readiness Review Addendum .................................................................................... 81

 Launch Readiness Review (LRR) .......................................................................................... 82

 Post-Launch Assessment Review (PLAR) ............................................................................ 83

STEM Engagement.................................................................................................................... 84

 STEM Engagement Activity Types ........................................................................................ 85

 STEM Engagement Activity Report ...................................................................................... 86

Safety.......................................................................................................................................... 90

 High-Power Rocket Safety Code.......................................................................................... 91

 Minimum Distance Table....................................................................................................... 92

Awards........................................................................................................................................ 93

 Middle and High School Division Awards............................................................................. 94

 Artemis Student Challenges Awards .................................................................................... 94

Note: For your convenience, this document identifies Web links when available. These links are correct as of this 

publishing; however, since Web links can be moved or disconnected at any time, we have also provided source 

information as available to assist you in locating the information.
2024 Student Launch Handbook & Request for Proposal iii

Acronym Dictionary

AGL Above Ground Level

APCP Ammonium Perchlorate Composite Propellant

ASC Artemis Student Challenges

CDR Critical Design Review

CG Center of Gravity

CP Center of Pressure

FAA Federal Aviation Administration

FMEA Failure Modes and Effects Analysis

FRR Flight Readiness Review

GPS Global Positioning System

LCO Launch Control Officer

LRR Launch Readiness Review

MSFC Marshall Space Flight Center

NAR National Association of Rocketry

NASA National Aeronautics and Space Administration

PDF Payload Demonstration Flight 

PDF Portable Document Format

PDR Preliminary Design Review

PHA Personnel Hazard Analysis

PLAR Post Launch Assessment Review

PPE Personal Protective Equipment

RFP Request for Proposal

RSO Range Safety Officer

SAIL STEMnauts Atmosphere Independent Lander

SDS Safety Data Sheet

SLI Student Launch Initiative

SLS Space Launch System

SME Subject Matter Expert

SOMD Space Operations Mission Directorate 

SOW Statement of Work

STEM Science, Technology, Engineering, and 

Mathematics

TRA Tripoli Rocketry Association

UAS Unmanned Aerial System

USLI University Student Launch Initiative

VDF Vehicle Demonstration Flight

WBS Work Breakdown Structure
1

Statement 

of Work
2024 Student Launch Handbook & Request for Proposal 2Statement of Work

Design, Development, and Launch of a Reusable Rocket 

and Payload Statement of Work (SOW)

Activity Name: NASA Student Launch

Governing Office: NASA Marshall Space Flight Center Office of STEM Engagement

Period of Performance: Nine (9) calendar months.

Introduction

The Office of STEM Engagement at NASA Marshall Space Flight Center (MSFC) seeks proposals from colleges 

and universities to conduct the NASA University Student Launch Initiative (USLI) and qualified high schools, middle 

schools, and informal education groups to conduct the NASA Student Launch Initiative (SLI) during the 2023 – 2024 

academic year. NASA Student Launch (SL) is one of nine Artemis Student Challenges whose mission is to build 

foundational knowledge and introduce students to topics, techniques, and technologies critical to the success of 

the agency’s Artemis program. NASA SL aims to inspire the newest generation of space explorers— the Artemis 

Generation. For more information regarding Artemis Student Challenges please visit stem.nasa.gov/artemis. 

NASA SL connects learners, educators, and communities in NASA-unique opportunities that align with Science, 

Technology, Engineering, and Mathematics (STEM) Challenges. The activity is supported by the Space Operations 

Mission Directorate (SOMD) and commercial industry.

Student Launch reaches a broad audience of colleges, universities, and secondary institutions across the nation in 

a 9-month commitment to design, build, launch, and fly a payload(s) and vehicle components that support NASA 

research on high-power rockets. The College/University Division teams are challenged with designing a STEMnaut 

Atmospheric Indepdent Lander (SAIL) capable of housing four STEMnauts that are able to be safely recovered 

upon landing in a predetermined orientation. Teams may incorporate additional research with a separate payload if 

desired. Secondary experiments shall be approved by NASA. In addition, the team shall provide documentation on 

additional components and systems in all reports and reviews. High School/Middle School Division teams may elect 

to tackle the College/University Division challenge, or they may design their own science or engineering experiment. 

Awards are presented to teams in both divisions. More information about awards is on pages 48 and 94.

Proposals to participate in the NASA Student Launch College/University Division may be submitted from any U.S. 

college or university. Proposals to participate in the High School/Middle School Division may only be submitted from 

teams who: 1) have qualified at the American Rocketry Challenge (Top 25) or Rockets For Schools (Top 5) in 2023 

and have completed the Advanced Rocketry Workshop (ARW); or 2) have previously qualified for Student Launch 

Journeyman status. Student Launch proposals and participation are limited to one team per school.

After the competitive proposal selection process, teams will complete a series of design reviews that mirror the 

NASA engineering design lifecycle. Teams shall successfully complete a Preliminary Design Review (PDR), Critical 

Design Review (CDR), and Flight Readiness Review (FRR), which include safety briefings, analysis of vehicle and 

payload systems, and flight test data. Teams coming to Huntsville will undergo a Launch Readiness Review (LRR). 

Each team shall pass a review in order to move to a subsequent review. Teams will present their PDR, CDR, and 

FRR to a review panel of scientists, engineers, technicians, and educators via video teleconference. Review panel 

members, the Range Safety Officer (RSO), and Subject Matter Experts (SME) provide feedback and ask questions 

in order to increase the fidelity between the team’s work and research objectives. Each College/University Division 

team is scored according to a standard scoring rubric. High School/Middle School Division teams complete the 

same milestones but are not in competition and are not scored.
3

College/University 

SLI Division Handbook
2024 Student Launch Handbook & Request for Proposal 4Timeline for USLI Division

Timeline for NASA USLI Division

(Dates are subject to change.)

August 2023

14 .......................... Request for Proposal (RFP) released.

September 2023

11 .......................... Please visit https://www.nasa.gov/stem/studentlaunch/handbook/index.html for instructions on 

submitting your proposal. Proposals are due 8:00 a.m. CST

October 2023

04 .......................... Awarded proposals announced

05 .......................... Kickoff and PDR Q&A

26 .......................... Preliminary Design Review (PDR) report, presentation slides, and flysheet submitted to NASA 

project management team by 8:00 a.m. CDT

November 2023

01 – 30 ................... PDR video teleconferences

December 2023

07 .......................... CDR Q&A

January 2024

08 .......................... Subscale Flight deadline

08 .......................... Critical Design Review (CDR) report, presentation slides, and flysheet submitted to NASA project 

management team by 8:00 a.m. CST

16 – Feb. 6 ............. CDR video teleconferences

February 2024

08 .......................... FRR Q&A

March 2024

04 .......................... Vehicle Demonstration Flight deadline

04 .......................... Flight Readiness Review (FRR) report, presentation slides, and flysheet submitted to NASA 

project management team by 8:00 a.m. CST

11 – 29 ................... FRR video teleconferences

April 2024

01 .......................... Launch window opens for teams not traveling to Launch Week. PLAR must be submitted within 

14 days of Launch

01 .......................... Payload Demonstration Flight and Vehicle Demonstration Re-flight deadlines

01 .......................... FRR Addendum submitted to NASA project management team by 8:00 a.m. CDT (Teams 

completing additional Payload Demonstration Flights and Vehicle Demonstration Re-flights only)

04 .......................... Launch Week Q&A

10 .......................... Teams arrive in Huntsville, AL

11 – 12 ................... All-day Launch Week Events

13 .......................... Launch Day

14 .......................... Backup Launch Day

23 .......................... Teams travelling to Launch Week: Post-Launch Assessment Review (PLAR) submitted to NASA 

project management team by 8:00 a.m. CDT

30 .......................... Launch window closes for teams not travelling to Huntsville for Launch Week. PLAR must be 

submitted within 7 days of launch.
5

General & Proposal 

Requirements
2024 Student Launch Handbook & Request for Proposal 6USLI General and Proposal Requirements

Student Launch Requirements

1. General Requirements

1.1. Students on the team will do 100% of the project, including design, construction, written reports, 

presentations, and flight preparation with the exception of assembling the motors and handling black 

powder or any variant of ejection charges, or preparing and installing electric matches (to be done by the 

team’s mentor). Student team members shall only be a part of one team in any capacity. Teams will submit 

new work. Excessive use of past work will merit penalties.

1.2. The team will provide and maintain a project plan to include, but not limited to the following items: project 

milestones, budget and community support, checklists, personnel assignments, STEM engagement 

events, and risks and mitigations.

1.3. Team members who will travel to the Huntsville Launch shall have fully completed registration in the NASA 

Gateway system before the roster deadline. Team members shall include:

1.3.1. Students actively engaged in the project throughout the entire year;

1.3.2. One mentor (see Requirement 1.13);

1.3.3. No more than two adult educators.

1.4. Teams shall engage a minimum of 250 participants in Educational Direct Engagement STEM activities. 

These activities can be conducted in-person or virtually. To satisfy this requirement, all events shall occur 

between project acceptance and the FRR addendum due date. A template of the STEM Engagement 

Activity Report can be found on pages 40 – 43.

1.5. The team shall establish and maintain a social media presence to inform the public about team activities.

1.6. Teams shall email all deliverables to the NASA project management team by the deadline specified in the 

handbook for each milestone. In the event that a deliverable is too large to attach to an email, inclusion of 

a link to download the file will be sufficient. Late submissions of PDR, CDR, FRR milestone documents will 

NOT be accepted. Teams that fail to submit the PDR, CDR, FRR milestone documents will be eliminated 

from the project.

1.7 Teams who do not satisfactorily complete each milestone review (PDR, CDR, FRR) will be provided action 

items needed to be completed following their review and will be required to address action items in a delta 

review session. After the delta session the NASA management panel will meet to determine the teams’ 

status in the program and the teams will be notified shortly thereafter.

1.8. All deliverables shall be in PDF format.

1.9. In every report, teams will provide a table of contents including major sections and their respective subsections.

1.10. In every report, the team shall include the page number at the bottom of the page.

1.11. The team shall provide any computer equipment necessary to perform a video teleconference with the 

review panel. This includes, but is not limited to, a computer system, video camera, speaker telephone, 

and a sufficient Internet connection. Cellular phones should be used for speakerphone capability only as a 

last resort.

1.12. All teams attending Launch Week shall be required to use the launch pads provided by Student Launch’s 

launch services provider. No custom pads will be permitted at the NASA Launch Complex. At launch, 

8-foot 1010 rails and 12-foot 1515 rails will be provided. The launch rails will be canted 5 – 10 degrees 

away from the crowd on Launch Day. The exact cant will depend on Launch Day wind conditions.
2024 Student Launch Handbook & Request for Proposal 7USLI General and Proposal Requirements

1.13. Each team shall identify a “mentor.” A mentor is defined as an adult who is included as a team member, 

who will be supporting the team (or multiple teams) throughout the project year, and may or may not be 

affiliated with the school, institution, or organization. The team mentor shall not be a student team member. 

The mentor shall maintain a current certification, and be in good standing, through the National Association 

of Rocketry (NAR) or Tripoli Rocketry Association (TRA) for the motor impulse of the launch vehicle and 

must have flown and successfully recovered (using electronic, staged recovery) a minimum of 2 flights in 

this or a higher impulse class, prior to PDR. The mentor is designated as the individual owner of the rocket 

for liability purposes and must travel with the team to Launch Week. One travel stipend will be provided per 

mentor regardless of the number of teams he or she supports. The stipend will only be provided if the team 

passes FRR and the team and mentor attend Launch Week in April.

1.14. Teams will track and report the number of hours spent working on each milestone.

2. Vehicle Requirements

2.1. The vehicle shall deliver the payload to an apogee altitude between 4,000 and 6,000 feet above ground 

level (AGL). Teams flying below 3,500 feet or above 6,500 feet on their competition launch will receive zero 

altitude points towards their overall project score and will not be eligible for the Altitude Award.

2.2. Teams shall declare their target altitude goal at the PDR milestone. The declared target altitude shall be 

used to determine the team’s altitude score.

2.3. The launch vehicle shall be designed to be recoverable and reusable. Reusable is defined as being able to 

launch again on the same day without repairs or modifications.

2.4. The launch vehicle shall have a maximum of four (4) independent sections. An independent section is 

defined as a section that is either tethered to the main vehicle or is recovered separately from the main 

vehicle using its own parachute.

2.4.1. Coupler/airframe shoulders which are located at in-flight separation points shall be at least 2 

airframe diameters in length. (One body diameter of surface contact with each airframe section).

2.4.2. Coupler/airframe shoulders which are located at non-in-flight separation points shall be at least 

1.5 airframe diameters in length. (0.75 body diameter of surface contact with each airframe 

section.)

2.4.3. Nosecone shoulders which are located at in-flight separation points shall be at least 1⁄2 body 

diameter in length.

2.5. The launch vehicle shall be capable of being prepared for flight at the launch site within 2 hours of the time 

the Federal Aviation Administration flight waiver opens.

2.6. The launch vehicle and payload shall be capable of remaining in launch-ready configuration on the pad for 

a minimum of 3 hours without losing the functionality of any critical on-board components, although the 

capability to withstand longer delays is highly encouraged.

2.7. The launch vehicle shall be capable of being launched by a standard 12-volt direct current firing system. 

The firing system shall be provided by the NASA-designated launch services provider.

2.8. The launch vehicle shall require no external circuitry or special ground support equipment to initiate launch 

(other than what is provided by the launch services provider).

2.9. Each team shall use commercially available ematches or igniters. Hand-dipped igniters shall not be 

permitted.

2.10. The launch vehicle shall use a commercially available solid motor propulsion system using ammonium 

perchlorate composite propellant (APCP) which is approved and certified by the National Association of 

Rocketry (NAR), Tripoli Rocketry Association (TRA), and/or the Canadian Association of Rocketry (CAR).

2.10.1. Final motor choice shall be declared by the Critical Design Review (CDR) milestone.
2024 Student Launch Handbook & Request for Proposal 8USLI General and Proposal Requirements

2.10.2. Any motor change after CDR shall be approved by the NASA Range Safety Officer (RSO). 

Changes for the sole purpose of altitude adjustment shall not be approved. A penalty against 

the team’s overall score will be incurred when a motor change is made after the CDR milestone, 

regardless of the reason.

2.11. The launch vehicle shall be limited to a single motor propulsion system.

2.12. The total impulse provided by a College or University launch vehicle shall not exceed 5,120 Newtonseconds (L-class).

2.13. Pressure vessels on the vehicle must be approved by the RSO and shall meet the following criteria:

2.13.1. The minimum factor of safety (Burst or Ultimate pressure versus Max Expected Operating 

Pressure) will be 4:1 with supporting design documentation included in all milestone reviews.

2.13.2. Each pressure vessel shall include a pressure relief valve that sees the full pressure of the tank and 

is capable of withstanding the maximum pressure and flow rate of the tank.

2.13.3. The full pedigree of the tank shall be described, including the application for which the tank 

was designed and the history of the tank. This will include the number of pressure cycles put 

on the tank, the dates of pressurization/depressurization, and the name of the person or entity 

administering each pressure event.

2.14. The launch vehicle shall have a minimum static stability margin of 2.0 at the point of rail exit. Rail exit is 

defined at the point where the forward rail button loses contact with the rail.

2.15. The launch vehicle shall have a minimum thrust to weight ratio of 5.0:1.0.

2.16. Any structural protuberance on the rocket shall be located aft of the burnout center of gravity. Camera 

housings will be exempted, provided the team can show that the housing(s) causes minimal aerodynamic 

effect on the rocket’s stability.

2.17. The launch vehicle shall accelerate to a minimum velocity of 52 fps at rail exit.

2.18. All teams shall successfully launch and recover a subscale model of their rocket prior to CDR. Success of 

the subscale is at the sole discretion of the NASA review panel. The subscale flight may be conducted at 

any time between proposal award and the CDR submission deadline. Subscale flight data shall be reported 

in the CDR report and presentation at the CDR milestone. Subscales are required to use a minimum motor 

impulse class of E (Mid Power motor).

2.18.1. The subscale model should resemble and perform as similarly as possible to the full-scale model; 

however, the full-scale shall not be used as the subscale model.

2.18.2. The subscale model shall carry an altimeter capable of recording the model’s apogee altitude.

2.18.3. The subscale rocket shall be a newly constructed rocket, designed and built specifically for this 

year’s project.

2.18.4. Proof of a successful flight shall be supplied in the CDR report.

2.18.4.1. Altimeter flight profile graph(s) OR a quality video showing successful launch, recovery 

events, and landing as deemed by the NASA management panel are acceptable 

methods of proof. Altimeter flight profile graph(s) that are not complete (liftoff through 

landing) will not be accepted.

2.18.4.2. Quality pictures of the as landed configuration of all sections of the launch vehicle shall 

be included in the CDR report. This includes but is not limited to nosecone, recovery 

system, airframe, and booster.

2.18.5. The subscale rocket shall not exceed 75% of the dimensions (length and diameter) of your 

designed full-scale rocket. For example, if your full-scale rocket is a 4” diameter, 100” length 

rocket, your subscale shall not exceed 3” diameter and 75” in length.
2024 Student Launch Handbook & Request for Proposal 9USLI General and Proposal Requirements

2.19. All teams shall complete demonstration flights as outlined below.

2.19.1. Vehicle Demonstration Flight— All teams shall successfully launch and recover their full-scale 

rocket prior to FRR in its final flight configuration. The rocket flown shall be the same rocket 

to be flown for their competition launch. The purpose of the Vehicle Demonstration Flight is to 

validate the launch vehicle’s stability, structural integrity, recovery systems, and the team’s ability 

to prepare the launch vehicle for flight. A successful flight is defined as a launch in which all 

hardware is functioning properly (i.e., drogue chute at apogee, main chute at the intended lower 

altitude, functioning tracking devices, etc.). The following criteria shall be met during the full-scale 

demonstration flight:

2.19.1.1. The vehicle and recovery system shall have functioned as designed.

2.19.1.2. The full-scale rocket shall be a newly constructed rocket, designed and built specifically 

for this year’s project.

2.19.1.3. The payload does not have to be flown during the full-scale Vehicle Demonstration 

Flight. The following requirements still apply:

2.19.1.3.1. If the payload is not flown, mass simulators shall be used to simulate the 

payload mass.

2.19.1.3.2. The mass simulators shall be located in the same approximate location on 

the rocket as the missing payload mass.

2.19.1.4. If the payload changes the external surfaces of the rocket (such as camera housings or 

external probes) or manages the total energy of the vehicle, those systems will be active 

during the full-scale Vehicle Demonstration Flight.

2.19.1.5. Teams shall fly the competition launch motor for the Vehicle Demonstration Flight. The 

team may request a waiver for the use of an alternative motor in advance if the home 

launch field cannot support the full impulse of the competition launch motor or in other 

extenuating circumstances.

2.19.1.6. The vehicle will be flown in its fully ballasted configuration during the full-scale test 

flight. Fully ballasted refers to the maximum amount of ballast that will be flown during 

the competition launch flight. Additional ballast shall not be added without a re-flight of 

the full-scale launch vehicle.

2.19.1.7. After successfully completing the full-scale demonstration flight, the launch vehicle 

or any of its components shall not be modified without the concurrence of the NASA 

Range Safety Officer (RSO).

2.19.1.8. Proof of a successful flight shall be supplied in the FRR report.

2.19.1.8.1. Altimeter flight profile data output with accompanying altitude and velocity 

versus time plots is required to meet this requirement. Altimeter flight profile 

graph(s) that are not complete (liftoff through landing) shall not be accepted.

2.19.1.8.2. Quality pictures of the as landed configuration of all sections of the launch 

vehicle shall be included in the FRR report. This includes but is not limited to 

nosecone, recovery system, airframe, and booster.

2.19.1.9. Vehicle Demonstration flights shall be completed by the FRR submission deadline. 

No exceptions will be made. If the Student Launch office determines that a Vehicle 

Demonstration Re-flight is necessary, then an extension may be granted. THIS 

EXTENSION IS ONLY VALID FOR RE-FLIGHTS, NOT FIRST TIME FLIGHTS. Teams 

completing a required re-flight shall submit an FRR Addendum by the FRR Addendum 

deadline.
2024 Student Launch Handbook & Request for Proposal 10USLI General and Proposal Requirements

2.19.2. Payload Demonstration Flight— All teams shall successfully launch and recover their full-scale 

rocket containing the completed payload prior to the Payload Demonstration Flight deadline. 

The rocket flown shall be the same rocket to be flown as their competition launch. The purpose 

of the Payload Demonstration Flight is to prove the launch vehicle’s ability to safely retain 

the constructed payload during flight and to show that all aspects of the payload perform as 

designed. A successful flight is defined as a launch in which the rocket experiences stable ascent 

and the payload is fully retained until it is deployed (if applicable) as designed. The following 

criteria shall be met during the Payload Demonstration Flight:

2.19.2.1. The payload shall be fully retained until the intended point of deployment (if applicable), 

all retention mechanisms shall function as designed, and the retention mechanism shall 

not sustain damage requiring repair.

2.19.2.2. The payload flown shall be the final, active version.

2.19.2.3. If the above criteria are met during the original Vehicle Demonstration Flight, occurring 

prior to the FRR deadline and the information is included in the FRR package, the 

additional flight and FRR Addendum are not required.

2.19.2.4. Payload Demonstration Flights shall be completed by the FRR Addendum deadline. NO 

EXTENSIONS WILL BE GRANTED.

2.20. An FRR Addendum shall be required for any team completing a Payload Demonstration Flight or NASArequired Vehicle Demonstration Re-flight after the submission of the FRR Report.

2.20.1. Teams required to complete a Vehicle Demonstration Re-Flight and failing to submit the FRR 

Addendum by the deadline will not be permitted to fly a final competition launch.

2.20.2. Teams who complete a Payload Demonstration Flight which is not fully successful may petition the 

NASA RSO for permission to fly the payload at launch week. Permission will not be granted if the 

RSO or the Review Panel have any safety concerns.

2.21. The team’s name and Launch Day contact information shall be in or on the rocket airframe as well as in 

or on any section of the vehicle that separates during flight and is not tethered to the main airframe. This 

information shall be included in a manner that allows the information to be retrieved without the need to 

open or separate the vehicle.

2.22. All Lithium Polymer batteries shall be sufficiently protected from impact with the ground and will be brightly 

colored, clearly marked as a fire hazard, and easily distinguishable from other payload hardware.

2.23. Vehicle Prohibitions

2.23.1. The launch vehicle shall not utilize forward firing motors.

2.23.2. The launch vehicle shall not utilize motors that expel titanium sponges (Sparky, Skidmark, 

MetalStorm, etc.)

2.23.3. The launch vehicle shall not utilize hybrid motors.

2.23.4. The launch vehicle shall not utilize a cluster of motors.

2.23.5. The launch vehicle shall not utilize friction fitting for motors.

2.23.6. The launch vehicle shall not exceed Mach 1 at any point during flight.

2.23.7. Vehicle ballast shall not exceed 10% of the total unballasted weight of the rocket as it would sit on 

the pad (i.e., a rocket with an unballasted weight of 40 lbs. on the pad may contain a maximum of 

4 lbs. of ballast).

2.23.8. Transmissions from onboard transmitters, which are active at any point prior to landing, shall not 

exceed 250 mW of power (per transmitter).
2024 Student Launch Handbook & Request for Proposal 11USLI General and Proposal Requirements

2.23.9. Transmitters shall not create excessive interference. Teams shall utilize unique frequencies, 

handshake/passcode systems, or other means to mitigate interference caused to or received from 

other teams.

2.23.10. Excessive and/or dense metal shall not be utilized in the construction of the vehicle. Use of 

lightweight metal will be permitted but limited to the amount necessary to ensure structural 

integrity of the airframe under the expected operating stresses.

3. Recovery System Requirements

3.1. The full scale launch vehicle shall stage the deployment of its recovery devices, where a drogue

parachute is deployed at apogee, and a main parachute is deployed at a lower altitude. Tumble or

streamer recovery from apogee to main parachute deployment is also permissible, provided that kinetic 

energy during drogue stage descent is reasonable, as deemed by the RSO.

3.1.1. The main parachute shall be deployed no lower than 500 feet.

3.1.2. The apogee event shall contain a delay of no more than 2 seconds.

3.1.3. Motor ejection is not a permissible form of primary or secondary deployment.

3.2. Each team shall perform a successful ground ejection test for all electronically initiated recovery events 

prior to the initial flights of the subscale and full scale vehicles.

3.3. Each independent section of the launch vehicle shall have a maximum kinetic energy of 75 ft-lbf at landing. 

Teams whose heaviest section of their launch vehicle, as verified by vehicle demonstration flight data, stays 

under 65 ft-lbf will be awarded bonus points.

3.4. The recovery system shall contain redundant, commercially available barometric altimeters that are 

specifically designed for initiation of rocketry recovery events. The term “altimeters” includes both simple 

altimeters and more sophisticated flight computers.

3.5. Each altimeter shall have a dedicated power supply, and all recovery electronics shall be powered by 

commercially available batteries.

3.6. Each altimeter shall be armed by a dedicated mechanical arming switch that is accessible from the exterior 

of the rocket airframe when the rocket is in the launch configuration on the launch pad.

3.7. Each arming switch shall be capable of being locked in the ON position for launch (i.e. cannot be disarmed 

due to flight forces).

3.8. The recovery system, GPS and altimeters, electrical circuits shall be completely independent of any 

payload electrical circuits.

3.9. Removable shear pins shall be used for both the main parachute compartment and the drogue parachute 

compartment.

3.10. Bent eyebolts shall not be permitted in the recovery subsystem.

3.11. The recovery area shall be limited to a 2,500 ft. radius from the launch pads.

3.12. Descent time of the launch vehicle shall be limited to 90 seconds (apogee to touch down). Teams whose 

launch vehicle descent, as verified by vehicle demonstration flight data, stays under 80 seconds will be 

awarded bonus points.

3.13. An electronic GPS tracking device shall be installed in the launch vehicle and will transmit the position of 

the tethered vehicle or any independent section to a ground receiver.

3.13.1. Any rocket section or payload component, which lands untethered to the launch vehicle, shall 

contain an active electronic GPS tracking device.

3.13.2. The electronic GPS tracking device(s) shall be fully functional during the official competition 

launch.
2024 Student Launch Handbook & Request for Proposal 12USLI General and Proposal Requirements

3.14. The recovery system electronics shall not be adversely affected by any other on-board electronic devices 

during flight (from launch until landing).

3.14.1. The recovery system altimeters shall be physically located in a separate compartment within 

the vehicle from any other radio frequency transmitting device and/or magnetic wave producing 

device.

3.14.2. The recovery system electronics shall be shielded from all onboard transmitting devices to avoid 

inadvertent excitation of the recovery system electronics.

3.14.3. The recovery system electronics shall be shielded from all onboard devices which may generate 

magnetic waves (such as generators, solenoid valves, and Tesla coils) to avoid inadvertent 

excitation of the recovery system.

3.14.4. The recovery system electronics shalll be shielded from any other onboard devices which may 

adversely affect the proper operation of the recovery system electronics.

4. Payload Experiment Requirements

The Artemis program is fully underway with the successful launch and recovery of the Orion Capsule during the 

Artemis I mission. NASA’s next move is a crewed mission and eventual crewed landing on celestial bodies. With this 

push for deep space travel NASA will explore further than ever before. A landing system that is capable of landing in 

the varying atmospheres of multiple celestial bodies is necessary.

4.1. USLI Payload Mission objective: College/University Division — Teams shall design a STEMnauts 

Atmosphere Independent Lander (SAIL). SAIL is an in-air deployable payload capable of safely retaining 

and recovering a group of 4 STEMnauts in a unique predetermined orientation without the use of a 

parachute or streamer. The landing shall occur under acceptable descent and landing parameters for the 

safe recovery of human beings. A STEMnaut shall be defined as a non-living crew member, to be physically 

represented as the team chooses, and is assumed to have human astronaut survivability metrics. The 

method(s)/design(s) utilized to complete the payload mission shall be at the team’s discretion and will be 

permitted so long as the designs are deemed safe, obey FAA and legal requirements, and adhere to the 

intent of the challenge. NASA reserves the right to require modifications to a proposed payload.

4.2. SAIL Mission Requirements

4.2.1. Teams shall not use parachutes or streamers that are commercially available or custom made. A 

parachute is defined as an open-faced canopy whose primary function is to reduce descent speed 

or increase drag. A streamer is defined as a long, narrow strip of material (typically affixed at one 

end) whose primary function is to reduce descent speed or increase drag.

4.2.2. The SAIL shall be a minimum of 5 lbs inclusive of the jettisoned or separated landing capsule and 

the 4 STEMnauts.

4.2.3. Deployment of the SAIL shall occur between 400 and 800 feet AGL. See requirement 4.3.3 for 

deployment/jettison of payloads.

4.2.4.1. Chemical energetics will not be permitted below 500 feet AGL.

4.2.4. The team shall pre-determine and land in a unique landing orientation to be verified by NASA 

personnel in Huntsville or by a non-affiliated NAR/TRA rep for at-home launches.

4.2.5. Teams shall design and implement a method of retention and ingress/egress for the STEMnauts.

4.2.6. Teams shall determine acceptable descent and landing parameters, to be approved by NASA, and 

design their lander to meet those requirements.

4.2.6.1. Teams may, at their discretion, measure and verify the descent and landing parameters.

4.2.6.2. Teams shall at a minimum demonstrate and verify safe landing parameters as part of the 

Payload Demonstration Flight.
2024 Student Launch Handbook & Request for Proposal 13USLI General and Proposal Requirements

An additional experiment (limit of 1) is allowed, and may be flown, but will not contribute to scoring. If the team 

chooses to fly an additional experiment, they will provide the appropriate documentation in all design reports so the 

experiment may be reviewed for flight safety.

4.3. General Payload Requirements

4.3.1. Black Powder and/or similar energetics are only permitted for deployment of in-flight recovery 

systems. Energetics will not be permitted for any surface operations.

4.3.2. Teams shall abide by all FAA and NAR rules and regulations.

4.3.3. Any payload experiment element that is jettisoned during the recovery phase shall receive realtime RSO permission prior to initiating the jettison event, unless exempted from the requirement 

by the RSO or NASA.

4.3.4. Unmanned aircraft system (UAS) payloads, if designed to be deployed during descent, shall be 

tethered to the vehicle with a remotely controlled release mechanism until the RSO has given 

permission to release the UAS.

4.3.5. Teams flying UASs shall abide by all applicable FAA regulations, including the FAA’s Special Rule 

for Model Aircraft (Public Law 112–95 Section 336; see https://www.faa.gov/uas/faqs).

4.3.6. Any UAS weighing more than .55 lbs. shall be registered with the FAA and the registration number 

marked on the vehicle.

5. Safety Requirements

5.1. Each team shall use a launch and safety checklist. The final checklists shall be included in the FRR report 

and used during the Launch Readiness Review (LRR) and any Launch Day operations.

5.2. Each team shall identify a student safety officer who will be responsible for all items in Section 5.3.

5.3. The role and responsibilities of the safety officer shall include, but are not limited to:

5.3.1. Monitor team activities with an emphasis on safety during:

5.3.1.1. Design of vehicle and payload

5.3.1.2. Construction of vehicle and payload components

5.3.1.3. Assembly of vehicle and payload

5.3.1.4. Ground testing of vehicle and payload

5.3.1.5. Subscale launch test(s)

5.3.1.6. Full-scale launch test(s)

5.3.1.7. Competition Launch

5.3.1.8. Recovery activities

5.3.1.9. STEM Engagement Activities

5.3.2. Implement procedures developed by the team for construction, assembly, launch, and recovery 

activities.

5.3.3. Manage and maintain current revisions of the team’s hazard analyses, failure modes analyses, 

procedures, and SDS/chemical inventory data.

5.3.4. Assist in the writing and development of the team’s hazard analyses, failure modes analyses, and 

procedures.
2024 Student Launch Handbook & Request for Proposal 14USLI General and Proposal Requirements

5.4. During test flights, teams shall abide by the rules and guidance of the local rocketry club’s RSO. The 

allowance of certain vehicle configurations and/or payloads at the NASA Student Launch does not give 

explicit or implicit authority for teams to fly those vehicle configurations and/or payloads at other club 

launches. Teams shall communicate their intentions to the local club’s President or Prefect and RSO before 

attending any NAR or TRA launch.

5.5. Teams shall abide by all rules set forth by the FAA.

6. Final Flight Requirements

Teams shall conduct the final flight in Huntsville during Launch Week (NASA Launch Complex) or at a local launch 

field (Commercial Spaceport Launch Site) by the applicable deadlines as outlined in the Timeline for NASA 

Student Launch.

6.1. NASA Launch Complex

6.1.1. Teams are not permitted to show up at the NASA Launch Complex outside of launch day without 

permission from the NASA management team.

6.1.2. Teams shall complete and pass the Launch Readiness Review conducted during Launch Week.

6.1.3. The team mentor shall be present and oversee rocket preparation and launch activities.

6.1.4. The scoring altimeter shall be presented to the NASA scoring official upon recovery.

6.1.5. Teams may launch only once. Any launch attempt resulting in the rocket exiting the launch pad, 

regardless of the success of the flight, will be considered a launch. Additional flights beyond the 

initial launch, will not be scored and will not be considered for awards.

6.2. Commercial Spaceport Launch Site

6.2.1. The launch shall occur at a NAR or TRA sanctioned and insured club launch. Exceptions may be 

approved for launch clubs who are not affiliated with NAR or TRA but provide their own insurance, 

such as the Friends of Amateur Rocketry. Approval for such exceptions shall be granted by NASA 

prior to the launch.

6.2.2. Teams shall submit their rocket and payload to the launch site Range Safety Officer (RSO) prior to 

flying the rocket. The RSO shall inspect the rocket and payload for flightworthiness and determine 

if the project is approved for flight. The local RSO shall have final authority on whether the team’s 

rocket and payload may be flown.

6.2.3. The team mentor shall be present and oversee rocket preparation and launch activities.

6.2.4. BOTH the team mentor and the Launch Control Officer shall observe the flight and report any offnominal events during ascent or recovery on the Launch Certification and Observations Report.

6.2.5. The scoring altimeter shall be presented to BOTH the team’s mentor and the Range Safety Officer.

6.2.6. The mentor, the Range Safety Officer, and the Launch Control Officer must be three separate 

individuals who must ALL complete the applicable sections of the Launch Certification and 

Observations Report. The Launch Certification and Observations Report document will be 

provided by NASA upon completion of the FRR milestone and shall be returned to NASA by the 

team mentor upon completion of the launch.

6.2.7. The Range Safety Officer and Launch Control Officer certifying the team’s flight shall be impartial 

observers and shall not be affiliated with the team, individual team members, or the team’s 

academic institution.

6.2.8. Teams may launch only once. Any launch attempt resulting in the rocket exiting the launch pad, 

regardless of the success of the flight, will be considered a launch. Additional flights beyond the 

initial launch will not be scored and will not be considered for awards.
2024 Student Launch Handbook & Request for Proposal 15USLI General and Proposal Requirements

NASA will maintain a Frequently Asked Questions (FAQ) list on the Student Launch Web site (www.nasa.gov/ 

studentlaunch). This list will include important changes and/or clarifications to project requirements. Changes and 

clarifications appearing in the FAQ supersede what is written in this handbook. It is the team’s responsibility to check 

the FAQ and be aware of any changes to the challenge.

Proposal Requirements

At a minimum, the proposing team shall identify the following in a written proposal due to NASA MSFC by the date 

specified in the project timeline.

1. General Information

a. Please visit https://www.nasa.gov/stem/studentlaunch/handbook/index.html for instructions on submitting 

your proposal.

b. A cover page that includes the name of the college/university or secondary education institution, mailing 

address, title of the project, and the date. The mailing address provided will be used if we need to mail 

anything throughout the project year to the team.

c. Name, title and contact information (including email address and phone number) for up to two adult educators 

(minimum of one required).

d. Name, title, and contact information (including email address and phone number) for the team mentor. Team 

mentor NAR or TRA flyer number shall be included along with the level of certification they currently hold (see 

requirement 1.13).

e. Name and email address for the student team leader.

f. Name and email address for the student team member who will take responsibility for implementation of the 

safety plan (Safety Officer).

g. Approximate number of student participants who will be committed to the project and their proposed duties. 

Include an outline of the project organization that identifies the key managers and technical personnel.

h. Name of the NAR/TRA section(s) the team is planning to work with for purposes of mentoring, review of 

designs and documentation, and launch assistance.

i. Document the number of hours spent on the proposal. This includes time spent brainstorming, attending 

meetings, and the actual writing of the proposal.

2. Facilities/Equipment

a. Description of facilities and hours of accessibility, necessary personnel, equipment, and supplies that are 

required to design and build the rocket and payload(s). Specify what is on hand and what will need to be 

acquired.

3. Safety

The Federal Aviation Administration (FAA) [www.faa.gov] has specific laws governing the use of airspace. A 

demonstration of the understanding and intent to abide by the applicable federal laws (especially as related to the 

use of airspace at the launch sites and the use of combustible/flammable material), safety codes, guidelines, and 

procedures for building, testing, and flying large model rockets is crucial. The procedures and safety regulations of 

the NAR [www.nar.org/safety-information/] shall be used for flight design and operations. The NAR/TRA mentor and 

Safety Officer shall oversee launch operations and motor handling.

a. Provide a written safety plan addressing the safety of the materials used, facilities involved, and student 

responsible, i.e., Safety Officer, for ensuring that the plan is followed. A risk assessment should be done for all 

these aspects in addition to proposed mitigations. Identification of risks to the successful completion of the 

project should be included.
2024 Student Launch Handbook & Request for Proposal 16USLI General and Proposal Requirements

b. Provide a description of the procedures for NAR/TRA personnel to perform. Ensure the following:

i. Compliance with NAR High Power Safety Code requirements [http://www.nar.org/safety-information/highpower-rocket-safety-code/].

ii. Performance of all hazardous materials handling and hazardous operations.

c. Describe the plan for briefing students on hazard recognition and accident avoidance, as well as for 

conducting pre-launch briefings.

d. Describe methods to include necessary caution statements in plans, procedures, and other working 

documents, including the use of proper Personal Protective Equipment (PPE).

e. Each team shall provide a plan for complying with federal, state, and local laws regarding unmanned rocket 

launches and motor handling. Specifically, regarding the use of airspace, Federal Aviation Regulations 14 CFR, 

Subchapter F, Part 101, Subpart C; Amateur Rockets, Code of Federal Regulation 27 Part 55: Commerce in 

Explosives; and fire prevention, NFPA 1127 “Code for High Power Rocket Motors.”

f. Provide a plan for NAR/TRA mentor purchase, storage, transportation, and use of rocket motors and energetic 

devices.

g. Include a written statement that all team members understand and will abide by the following safety 

regulations:

i. Range safety inspections will be conducted on each rocket before it is flown. Each team shall comply with 

the determination of the safety inspection or may be removed from the program.

ii. The Range Safety Officer has the final say on all rocket safety issues. Therefore, the Range Safety Officer 

has the right to deny the launch of any rocket for safety reasons.

iii. The team mentor is ultimately responsible for the safe flight and recovery of the team’s rocket. Therefore, a 

team shall not fly a rocket until the mentor has reviewed the design, examined the build and is satisfied the 

rocket meets established amateur rocketry design and safety guidelines.

iv. Any team that does not comply with the safety requirements shall not be allowed to launch their rocket.

4. Technical Design

a. A proposed and detailed approach to rocket and payload design.

i. Include general vehicle dimensions, preliminary material selection and justification, and construction

methods.

ii. Include projected altitude and describe how it was calculated.

iii. Include planned recovery system design.

iv. Include projected motor brand and designation.

v. Include detailed description of the team’s projected payload.

vi. Address the General, Vehicle, Recovery, Payload, and Safety requirements outlined on pages 6 – 14 of this 

handbook.

vii. Identify major technical challenges and solutions.

5. STEM Engagement

a. Include plans and evaluation criteria for required STEM engagement activities. (See Project requirement 1.4 on 

page 6.)
2024 Student Launch Handbook & Request for Proposal 17USLI General and Proposal Requirements

6. Project Plan

a. Provide a detailed development schedule/timeline or work breakdown structure (WBS) covering all aspects 

necessary to complete the project successfully.

b. Provide a detailed budget to cover all aspects necessary to complete the project successfully, including team 

travel to the launch.

c. Provide a detailed funding plan.

d. Develop a clear plan for sustainability of the rocket project in the local area. This plan should include how to 

provide and maintain established partnerships and regularly engage successive classes of students in rocketry. 

It should also include partners (industry/community), recruitment of team members, funding, sustainability, and 

STEM engagement activities.

Project Deliverables

a. A reusable rocket with required payload system ready for official launch.

b. A scale model of the rocket design shall be flown during the PDR or CDR milestones and the altimeter flight 

profile data or a quality video encompassing the entire liftoff and flight, and quality pictures of the landed 

configuration of the launch vehicle shall be reported in the CDR.

c. A full-scale Vehicle Demonstration Flight and Payload Demonstration Flight shall be flown and raw altimeter 

flight data file in csv or xlsx along with the flight profile graph, and quality pictures of the landed configuration 

of the launch vehicle shall be reported in the FRR and/or FRR Addendum.

d. A team social media presence established and maintained/updated throughout the project year.

e. Reports, PDF slideshows, and Milestone Review Flysheets completed and submitted to the Student Launch 

Projects management team by due dates.

f. Electronic copies of the STEM Engagement form(s) submitted after acceptance and prior to FRR addendum. 

g. Successful completion of PDR, CDR, FRR, FRR addendum (if applicable), LRR, and PLAR.
18

Project Milestones: 

Criteria & Expectations
2024 Student Launch Handbook & Request for Proposal 19USLI Project Milestones: Criteria and Expectations

Preliminary Design Review (PDR)

The PDR demonstrates that the overall preliminary design meets all requirements with acceptable risk, within the 

cost, schedule, and technical performance constraints, and establishes the basis for proceeding with detailed 

design. It shows that the correct design options have been selected, and interfaces have been identified. Full 

baseline cost and schedules, as well as all risk assessment, management systems, and metrics, are presented. The 

panel will be expecting a professional and polished report that follows the order of sections as they appear below.

Preliminary Design Review Report

Page Limit: PDRs will only be scored using the first 250 pages of the report (not including title page). 

Any additional content will not be considered while scoring.

I. Summary of PDR report (1 page maximum)

Team Summary

• Team name and mailing address

• Name of mentor, NAR/TRA number and certification level, and contact information

• Indication of plans to launch in Huntsville during launch week or at home during the launch window of April 

1st – April 30th

• Document the number of hours spent working on the PDR milestone

• Team social media presence established. Include a table listing all social media handles.

Launch Vehicle Summary

• Official target altitude (ft.)

• Preliminary motor choice(s)

• Size and mass of individual sections

• Recovery system

Payload Summary

• Payload title

• Summarize payload experiment

II. Changes made since Proposal (1 – 2 pages maximum)

Highlight all changes made since the proposal and the reason for those changes.

• Changes made to vehicle criteria

• Changes made to payload criteria

• Changes made to project plan

III. Vehicle Criteria

Selection, Design, and Rationale of Launch Vehicle

• Include unique mission statement and mission success criteria.

• Review the design at a system level, going through each system’s alternative designs, and evaluating the pros 

and cons of each alternative.

• For each alternative, present research on why that alternative should or should not be chosen.

• For each alternative, conduct a feasibility study.

• For each alternative, locate points of separation on each design and show location(s) of energetic materials
2024 Student Launch Handbook & Request for Proposal 20USLI Project Milestones: Criteria and Expectations

• After evaluating all alternatives, present a vehicle design with the current leading alternatives, and explain why 

they are the leading choices.

– Describe each subsystem and the components within those subsystems.

– Provide detailed dimensional drawings using the leading design.

– Provide estimated masses for each subsystem.

– Provide sufficient justification for design selections.

• Review different motor alternatives and present data on each alternative.

Recovery Subsystem

• Review the design at a component level, going through each components’ alternative designs, and evaluating 

the pros and cons of each alternative.

• For each alternative, present research on why that alternative should or should not be chosen.

• Using the estimated mass of the launch vehicle, perform a preliminary analysis on parachute sizing, and 

determine what size is required for a safe descent.

• Include drawings/sketches, wiring diagrams, and electrical schematics.

• Choose leading components amongst the alternatives, present them, and explain why they are the current 

leaders.

• Prove that redundancy exists within the system.

Mission Performance Predictions

• Declare the team’s official Competition Launch target altitude (ft.).

• Show flight profile simulations. This includes altitude, velocity, and acceleration versus time predictions with 

simulated vehicle data, component weights, and simulated motor thrust curve. Verify that the vehicle is robust 

enough to withstand the expected loads.

• Show stability margin and simulated Center of Pressure (CP)/Center of Gravity (CG) relationship and locations.

• Calculate the kinetic energy at landing for each independent and tethered section of the launch vehicle.

• Calculate the expected descent time for the rocket and any section that descends untethered from the rest of 

the vehicle.

• Calculate the drift for each independent section of the launch vehicle from the launch pad for five different 

cases: no wind, 5-mph wind, 10-mph wind, 15-mph wind, and 20-mph wind. The drift calculations should be 

performed with the assumption that apogee is reached directly above the launch pad.

• Present data from a different calculation method to verify that original results are accurate.

• Discuss any differences between the different calculations.

• Perform multiple simulations to verify that results are precise.

IV. Payload Criteria

Selection, Design, and Rationale of Payload

• Describe what the objective of the payload is and what experiment it will perform. What results will qualify as a 

successful experiment?

• Review the design at a system level, going through each system’s alternative designs, and evaluating the pros 

and cons of each alternative.

• For each alternative, present research on why that alternative should or should not be chosen.

• For each alternative, conduct a feasibility study.

• After evaluating all alternatives, present a payload design with the current leading alternatives and explain why 

they are the leading choices.

• Include drawings and electrical schematics for all elements of the preliminary payload. List estimated masses 

for components.
2024 Student Launch Handbook & Request for Proposal 21USLI Project Milestones: Criteria and Expectations

• Describe the justification used when making design selections.

• Describe the preliminary interfaces between the payload and launch vehicle.

• Describe the preliminary design of the payload retention system.

V. Safety

• Demonstrate an understanding of all components needed to complete the project and how risks/delays impact 

the project.

• Provide a preliminary Personnel Hazard Analysis. The focus of the Hazard Analysis at PDR is identification 

of hazards, their causes, and the resulting effects. Preliminary mitigations and controls can be identified, but 

do not need to be implemented at this point unless they are specific to the construction and launching of the 

subscale rocket or are hazards to the success of the SL program (i.e., cost, schedule, personnel availability). 

Rank the risk of each hazard for both likelihood and severity.

– Include data indicating that the hazards have been researched (especially personnel).Examples: NAR 

regulations, operator’s manuals, SDS, etc.

• Provide preliminary Failure Modes and Effects Analysis (FMEA) of the proposed design of the rocket, 

payload, payload integration, launch support equipment, and launch operations. Again, the focus for PDRis 

identification of hazards, causes, effects, and proposed mitigations. Rank the risk of each hazard for both 

likelihood and severity.

• Discuss any environmental concerns using the same format as the Personnel Hazard Analysis and FMEA.

– This should include how the vehicle affects the environment and how the environment can affectthe vehicle.

• Define the risks (time, resource, budget, scope/functionality, etc.) associated with the project. Assign a 

likelihood and impact value to each risk. Keep this part simple (i.e., low, medium, high likelihood, and low, 

medium, high impact). Develop mitigation techniques for each risk. Start with the risks with higher likelihood 

and impact, and work down from there. If possible, quantify the mitigation and impact. For example, including 

extra hardware to increase safety will have a quantifiable impact on budget. Including this information in a 

table is highly encouraged.

VI. Project Plan

Requirements Verification

• Create team derived requirements in the following categories: Vehicle, Recovery, and Payload. These are 

requirements for mission success that are beyond the minimum success requirements presented in this 

handbook. Demonstrate that the requirements are not arbitrary and are required for the team’s unique project.

Budgeting and Timeline

• Provide a line item budget for all aspects of the project with market values for individual components, material 

vendors, and applicable taxes or shipping/handling fees.

• Provide a funding plan describing sources of funding, allocation of funds, and material acquisition plan.

• Provide a timeline including all team activities and expected activity durations. The schedule should be 

complete and encompass the full term of the project. Deliverables should be defined with reasonable activity 

duration. GANTT or milestones charts are encouraged.
2024 Student Launch Handbook & Request for Proposal 22USLI Project Milestones: Criteria and Expectations

Preliminary Design Review Presentation

Please include the following in your presentation:

• Vehicle dimensions and justification

• Vehicle materials and justification

• Static stability margin and CP/CG locations

• Visually show points of separation along with location of energetic materials and all recovery components clearly 

labeled.

• Preliminary motor selection and justification

• Thrust-to-weight ratio and rail exit velocity

• Discussion of alternative designs and why each should or should not be chosen

• Drawing/discussion of each major component and subsystem, especially the recovery subsystem

• Discussion of current Mission Performance Predictions

• Preliminary payload design

• Preliminary payload retention system design

• Requirements compliance plan

The PDR will be presented to a panel that may be comprised of scientists, engineers, safety experts, education 

specialists and industry partners. The purpose of this review is to convince the NASA Review Panel that the 

preliminary design will meet all requirements, has a high probability of meeting the mission objectives, and can be 

safely constructed, tested, launched, and recovered. Upon successful completion of the PDR, the team is given the 

authority to proceed into the final design phase of the life cycle that will culminate in the Critical Design Review.

It is expected that the team participants deliver the report and answer all questions. The mentor or faculty advisor 

shall not participate in the presentation.

The presentation of the PDR shall be well prepared with an overall professional appearance. This includes, but is not 

limited to, the following: easy-to-read slides; appropriate placement of pictures, graphs, and videos; professional 

appearance of the presenters; speaking clearly and loudly; looking into the camera; referring to the slides rather than 

reading them; and communicating to the panel in an appropriate and professional manner. The slides should use 

dark text on a light background.
2024 Student Launch Handbook & Request for Proposal 23USLI Project Milestones: Criteria and Expectations

Critical Design Review (CDR)

The CDR establishes that the maturity of the design is appropriate to support proceeding to full-scale fabrication, 

assembly, and integration. It demonstrates that the technical effort is on track to complete the flight and ground 

system development and mission operations in order to meet overall performance requirements within the identified 

cost schedule, and technical performance constraints. Progress against management plans, budget, and schedule, 

as well as risk assessment, are presented. The CDR is a review of the final design of the launch vehicle and payload 

system.

All analyses should be complete, and some critical testing should be complete. The CDR Report and Presentation 

should be independent of the PDR Report and Presentation. However, the CDR Report and Presentation may have 

the same basic content and structure as the PDR documents, but with final design information that may or may 

not have changed since PDR. Although there should be discussion of subscale models, the CDR documents are to 

primarily discuss the final design of the full-scale launch vehicle and subsystems.

The panel expects a professional and polished report that follows the order of sections as they appear below.

Critical Design Review Report

Page Limit: CDRs will only be scored using the first 250 pages of the report (not including title page). 

Any additional content will not be considered while scoring.

I. Summary of CDR report (1 page maximum)

Team Summary

• Team name and mailing address

• Name of mentor, NAR/TRA number and certification level, and contact information

• If planning to conduct the final competition launch at home, teams shall provide anticipated primary and 

backup launch locations and dates.

• Document the number of hours spent working on the CDR milestone.

Launch Vehicle Summary

• Target altitude (ft.)

• Final motor choice

• Size and mass of individual sections

• Dry mass of launch vehicle without ballast

• Dry mass of launch vehicle with ballast (if applicable)

• Wet mass of launch vehicle

• Burnout mass of launch vehicle

• Landing mass of launch vehicle

• Recovery system

• Rail size

Payload Summary

• Payload title

• Summarize payload experiment

II. Changes made since PDR (1 – 2 pages maximum)

Highlight all changes made since PDR and the reason for those changes.

• Changes made to vehicle criteria

• Changes made to payload criteria

• Changes made to project plan
2024 Student Launch Handbook & Request for Proposal 24USLI Project Milestones: Criteria and Expectations

III. Vehicle Criteria

Design and Verification of Launch Vehicle

Flight Reliability and Confidence

• Include unique mission statement and mission success criteria

• Identify which of the design alternatives from PDR were chosen as the final components for the launch vehicle. 

Describe why those alternatives are the best choices.

• Using the final designs, create dimensional and computer-aided design (CAD) drawings to illustrate the final 

launch vehicle, its subsystems, and its components.

• Using the final designs, create dimensional cross sectional views of each airframe and coupler component.

• Using the final designs, locate points of separation and show location(s) of energetic materials.

• Demonstrate that the designs are complete and ready to manufacture.

• Discuss the integrity of design.

– Suitability of shape and fin style for mission

– Proper use of materials in fins, bulkheads, and structural elements

– Sufficient motor mounting and retention

– Estimate the final mass of the launch vehicle as well as the individual subsystems

• Provide justification for material selection, dimensioning, component placement, and other unique design 

aspects.

Subscale Flight Results

• At least one data gathering device shall be onboard the launch vehicle during the test launch. At a minimum, 

this device shall record the apogee of the rocket. If the device can record more than apogee, please include 

the actual flight data in the report.

• Altimeter flight profile graph(s) OR a quality video showing successful launch, recovery events, and landing as 

deemed by the NASA management panel are acceptable methods of proof. Altimeter flight profile graph(s) that 

are not complete (liftoff through landing) will not be accepted.

• Quality pictures of the as landed configuration of all sections of the launch vehicle. This includes but is not 

limited to nosecone, recovery system, airframe, and booster.

• Describe the scaling factors used when scaling the rocket. What variables were kept constant and why? What 

variables do not need to be constant and why?

• Describe launch day conditions and perform a simulation using those conditions.

• Perform an analysis of the subscale flight.

– Compare the predicted flight model to the actual flight data. Discuss the results.

– Discuss any error between actual and predicted flight data.

– Estimate the drag coefficient of the full-scale rocket with subscale data.

• Discuss how the subscale flight data has impacted the design of the full-scale launch vehicle.

Recovery Subsystem

• Identify which of the design alternatives from PDR were chosen as the final components for the recovery 

subsystem. Describe why those alternatives are the best choices.

• Include a Concept of Operations (CONOPS) of your recovery system.

• Describe the parachutes, harnesses, bulkheads, and attachment hardware.

• Discuss the electrical components and prove that redundancy exists within the system.

• Include drawings/sketches, wiring diagrams, and electrical schematics.

• Provide the operating frequency of the locating tracker(s).
2024 Student Launch Handbook & Request for Proposal 25USLI Project Milestones: Criteria and Expectations

Mission Performance Predictions (using the most up-to-date model)

• Show flight profile simulations. This includes altitude, velocity, and acceleration versus time predictions with 

simulated vehicle data, component weights, and simulated motor thrust curve. Verify that the vehicle is robust 

enough to withstand the expected loads

• Show stability margin and simulated Center of Pressure (CP)/Center of Gravity (CG) relationship and locations.

• Calculate the kinetic energy at landing for each independent and tethered section of the launch vehicle.

• Calculate the expected descent time for the rocket and any section that descends untethered from the rest of 

the vehicle.

• Calculate the drift for each independent section of the launch vehicle from the launch pad for five different 

cases: no wind, 5-mph wind, 10-mph wind, 15-mph wind, and 20-mph wind. The drift calculations should be 

performed with the assumption that apogee is reached directly above the launch pad.

• Present data from a different calculation method to verify that the original results are accurate.

• Discuss any differences between the different calculations.

• Perform multiple simulations to verify that results are precise.

IV. Payload Criteria

Design of Payload Experiment

• Identify which of the design alternatives from PDR was chosen for the payload. Describe why that alternative 

and its components were chosen.

• Include a Concept of Operations (CONOPS) of your payload system.

• Review the design at a system level.

– Include drawings and specifications for each component of the payload, as well as the entire payload 

assembly.

– Describe how the payload components interact with each other.

– Describe how the payload integrates within the launch vehicle.

– Describe the payload retention system.

• Demonstrate that the design is complete.

• Discuss the payload electronics with special attention given to safety switches and indicators. Include the 

following:

– Drawings and schematics

– Block diagrams

– Batteries/power

– Switch and indicator wattages and locations

• Provide justification for all unique aspects of your payload (like materials, dimensions, placement, etc.)

V. Safety

Launch concerns and operation procedures

Submit a draft of final assembly and launch procedures/checklists including:

• Recovery preparation

• Payload preparation

• Electronics preparation

• Rocket preparation

• Motor preparation

• Setup on the launch pad

• Igniter installation
2024 Student Launch Handbook & Request for Proposal 26USLI Project Milestones: Criteria and Expectations

• Launch procedure

• Troubleshooting

• Post-flight inspection

These procedures/checklists should include specially demarcated steps related to safety. Examples include:

• Warnings of hazards that can result from missing a step

• PPE required for a step in the procedure (identified BEFORE the step)

• Required personnel to complete a step or to witness and sign off verification of a step.

Safety and Environment (Vehicle and Payload)

• Update the Personnel Hazard Analysis, the Failure Modes and Effects Analysis, and the Environmental

 Hazard Analysis to include:

– Finalized hazard descriptions, causes, and effects. These should specifically identify the mechanisms for the 

hazards, and uniquely identify them from other hazards. Ambiguity is not useful in safety work.

– A near-complete list of mitigations, addressing the hazards and/or their causes

– A preliminary list of verifications for the identified mitigations. These should include methods of verifying 

the mitigations and controls are (or will be) in place, and how they will serve to ensure the mitigation. These 

do not need to be finalized at this time, but they will be required for FRR. Example verifications include: 

test data, written procedures and checklists, design analysis, as-built configuration drawings, and Personal 

Protective Equipment.

VI. Project Plan

Testing

• Identify all tests required to prove the integrity of the design.

• For each test, present the test objective and success criteria, as well as testing variable and methodology.

• Justify why each test is necessary to validate the design of the launch vehicle and payload.

• Discuss how the results of a test can cause any necessary changes to the launch vehicle and payload.

• Present results of any completed tests.

– Describe the test plan and whether or not the test was a success.

– How do the results drive the design of the launch vehicle and/or payload?

Requirements Compliance

• Create a verification plan for every requirement from Sections 1 – 5 of the project requirements listed in this 

handbook. Identify if test, analysis, demonstration, or inspection are required to verify the requirement. After 

identification, describe the associated plan needed for verification.

• Update the ongoing list of team derived requirements in the following categories: Vehicle, Recovery, and 

Payload. These are a set of requirements for mission success that are beyond the minimum success 

requirements presented in this handbook. Create a verification plan for each team derived requirement 

identifying whether test, analysis, demonstration, or inspection is required with an associated plan.

Budgeting and Timeline

• Provide an updated line item budget for all aspects of the project with market values for individual 

components, material vendors, and applicable taxes or shipping/handling fees.

• Provide an updated funding plan describing sources of funding, allocation of funds, and material acquisition 

plan.

• Provide an updated timeline, including all team activities and expected activity durations. The schedule should 

be complete and encompass the full term of the project. Deliverables should be defined with reasonable 

activity duration. GANTT or milestone charts are encouraged.
2024 Student Launch Handbook & Request for Proposal 27USLI Project Milestones: Criteria and Expectations

Critical Design Review Presentation

Please include the following information in your presentation:

• Final launch vehicle and payload dimensions

• Discuss key design features

• Visually show points of separation along with location of energetic materials and all recovery components clearly 

labeled.

• Final motor choice

• Rocket flight stability in static margin diagram

• Thrust-to-weight ratio and rail exit velocity

• Mass Statement and mass margin

• Parachute sizes, recovery harness type, size, length, and descent rates

• Recovery System CONOPS

• Kinetic energy at key phases of the mission, especially landing

• Predicted drift from the launch pad with 5-, 10-, 15-, and 20-mph wind

• Test plans and procedures

• Scale model flight test data

• Tests of the staged recovery system

• Final payload design overview

• Payload integration plans

• Payload retention system

• Interfaces (internal within the launch vehicle and external to the ground)

• Status of requirements verification

The CDR will be presented to a panel that may be comprised of scientists, engineers, safety experts, education 

specialists and industry partners. The team is expected to present and defend the final design of the launch vehicle 

and payload, proving the design meets the mission objectives and requirements and can be safely constructed, 

tested, launched, and recovered. Upon successful completion of the CDR, the team is given the authority to proceed 

into the construction and verification phase of the life cycle that will culminate in a Flight Readiness Review.

It is expected that the team participants deliver the report and answer all questions. The mentor or faculty advisor 

shall not participate in the presentation.

The presentation of the CDR shall be well prepared with an overall professional appearance. This includes, but is not 

limited to, the following: easy-to-read slides; appropriate placement of pictures, graphs, and videos; professional 

appearance of the presenters; speaking clearly and loudly; looking into the camera; referring to the slides rather than 

reading them; and communicating to the panel in an appropriate and professional manner. The slides should be 

made with dark text on a light background.
2024 Student Launch Handbook & Request for Proposal 28USLI Project Milestones: Criteria and Expectations

Flight Readiness Review (FRR)

The FRR examines tests, demonstrations, analyses, and audits that determine the overall system (all subsystems 

working together) readiness for a safe and successful flight/launch and for subsequent flight operations of the asbuilt rocket and payload system. It also ensures that all flight hardware, software, personnel, and procedures are 

operationally ready.

The panel will be expecting a professional and polished report that follows the order of sections as they appear 

below.

Flight Readiness Review Report

Page Limit: FRRs will only be scored using the first 250 pages of the report (not including title page).

Any additional content will not be considered while scoring.

I. Summary of FRR report (1 page maximum)

Team Summary

• Team name and mailing address

• Declared final launch location. If flying at a local launch, identify the launch club, national affiliation, name and 

contact information of a club officer who will attend the launch, and anticipated date of launch. Provide this 

information for both the primary and back up launch plans.

• Name of mentor, NAR/TRA number and certification level, and contact information

• Document the number of hours spent working on the FRR milestone

Launch Vehicle Summary

• Size and mass of individual sections

• Dry mass of launch vehicle without ballast

• Dry mass of launch vehicle with ballast (if applicable)

• Wet mass of launch vehicle

• Burnout mass of launch vehicle

• Landing mass of launch vehicle

• Competition Launch Motor

• Target altitude (ft.)

• Recovery system

• Rail size

Payload Summary

• Payload title

• Summarize payload experiment

II. Changes made since CDR (1 – 2 pages maximum)

Highlight all changes made since CDR and the reason for those changes.

• Changes made to vehicle criteria

• Changes made to payload criteria

• Changes made to project plan
2024 Student Launch Handbook & Request for Proposal 29USLI Project Milestones: Criteria and Expectations

III. Vehicle Criteria

Design and Construction of Vehicle

• Describe any changes in the launch vehicle design from CDR and explain why those changes are necessary.

• Discuss final locations of separation along with where black powder or energetics will be located.

• Describe features that will enable the vehicle to be launched and recovered safely.

– Structural elements (such as airframe, fins, bulkheads, attachment hardware, etc.)

– Electrical elements (wiring, switches, battery retention, retention of avionics boards, etc.)

• Discuss flight reliability confidence. Demonstrate that the design can meet mission success criteria.

• Prove that the vehicle is fully constructed and fully document the construction process.

• Include schematics of the AS-BUILT rocket. There is a good chance dimensions have changed slightly due to 

the construction process.

• Discuss how and why the constructed rocket differs from earlier models.

Recovery Subsystem

• Describe and defend the robustness of the as-built and as-tested recovery system.

– Structural elements (such as bulkheads, harnesses, attachment hardware, etc.)

– Electrical elements (such as altimeters/computers, switches, connectors)

– Redundancy features

– As-built parachute sizes and descent rates

– Drawings, diagrams and schematics of the as-built electrical and structural assemblies

– Rocket-locating transmitters with a discussion of frequency, wattage, and range

• Discuss the sensitivity of the recovery system to onboard devices that generate electromagnetic fields (such as 

transmitters). This topic should also be included in the Safety and Failure Analysis section.

Mission Performance Predictions

• Show flight profile simulations. This includes altitude, velocity, and acceleration versus time predictions with 

simulated vehicle data, component weights, and simulated motor thrust curve. Verify that the vehicle is robust 

enough to withstand the expected loads.

• Show stability margin and as-built Center of Pressure (CP)/Center of Gravity (CG) relationship and locations.

• Calculate the kinetic energy at landing for each independent and tethered section of the launch vehicle.

• Calculate the expected descent time for the rocket and any section that descends untethered from the rest of 

the vehicle.

• Calculate the drift for each independent section of the launch vehicle from the launch pad for five different 

cases: no wind, 5-mph wind, 10-mph wind, 15-mph wind, and 20-mph wind. The drift calculations should be 

performed with the assumption that apogee is reached directly above the launch pad.

• Present data from a different calculation method to verify that original results are accurate.

• Discuss any differences between the different calculations.

• Perform multiple simulations to verify that results are precise.

IV. Payload Criteria

Payload Design and Testing

• Describe any changes in the payload design from CDR and explain why those changes are necessary.

• Describe unique features of the payload. Include the following:

– Structural elements

– Electrical elements

• Discuss flight reliability confidence. Demonstrate that the design can meet mission success criteria.
2024 Student Launch Handbook & Request for Proposal 30USLI Project Milestones: Criteria and Expectations

• Prove that the payload is fully constructed and fully document the construction process.

• Include schematics of the AS-BUILT payload. There is a good chance dimensions have changed slightly due to 

the construction process.

• Discuss how and why the constructed payload differs from earlier models.

• Discuss the planned or completed Payload Demonstration Flight. Include the following:

– Date of flight or planned future flight

– Success criteria

– Results of flight

– Analysis of payload retention system to the launch vehicle prior to jettison.

V. Demonstration Flights

Provide for all flights:

• Identify whether the flight was conducted to fulfill the requirements for the Vehicle Demonstration Flight,

Payload Demonstration Flight, or both.

• Date of flight

• Location of flight

• Launch conditions

• Motor flown (brand and designation)

• Ballast flown (lbs.)

• Final payload flown (Y/N)

• Air brake system status during test flight (if design incorporates airbrakes)

• Official target altitude (ft.)

• Predicted altitude from simulations (ft.)

• Measured altitude (ft.)

• Altimeter flight profile data output with accompanying altitude and velocity versus time plots. Altimeter flight 

profile graph(s) that are not complete (liftoff through landing) shall not be accepted.

• Raw altimeter data in csv or xlsx format (subscale flight is exempt from this requirement).

• Quality pictures of the as landed configuration of all sections of the launch vehicle. This includes but is not 

limited to nosecone, recovery system, airframe, and booster.

• Identify all vehicle and recovery systems that functioned as intended.

• Identify and discuss any vehicle or recovery hardware or software that failed to function as intended.

• Calculate the kinetic energy at landing for each independent and tethered section of the launch vehicle.

• If the payload was not present, describe how the payload was simulated during the flight.

• Perform an analysis of the Vehicle Demonstration Flight. Update your simulated flight model with launch day 

condition data and compare the predicted flight performance to the actual flight data. Discuss the results.

• Estimate the drag coefficient of the full-scale rocket utilizing launch data. Use this value to run a post-flight 

simulation.

• Discuss any error between actual and predicted flight data.

• Discuss the similarities and differences between the full-scale and subscale flight results.

• Identify any hardware that was damaged and required repair or replacement and discuss the plan of action.

• Discuss lessons learned from the flight.

• Identify any off-nominal events during mission execution.
2024 Student Launch Handbook & Request for Proposal 31USLI Project Milestones: Criteria and Expectations

If the final, active payload was flown (i.e., the flight qualified as a Payload Demonstration Flight), also 

provide:

• Identify all retention systems that functioned as intended.

• Identify and discuss any retention hardware or software that failed to function as intended.

• Identify any retention hardware that was damaged and required repair or replacement and discuss the plan of 

action.

• Discuss retention system lessons learned from the flight.

• Summarize the designed payload mission sequence, from activation or deployment through mission 

completion.

• Identify all payload systems that functioned as intended.

• Identify and discuss any payload hardware or software that failed to function as intended.

• Identify any payload hardware that was damaged and required repair or replacement and discuss the plan of 

action.

• Discuss payload lessons learned from the flight.

Provide a list of any planned future demonstration flights. Include a summary of the team’s objectives for 

each launch.

VI. Safety and Procedures

Safety and Environment (Vehicle and Payload)

• Update the Personnel Hazard Analysis, the Failure Modes and Effects Analysis, and the Environmental Hazard 

Analysis to include:

– Finalized hazard descriptions, causes, and effects for the rocket and payload the team has built.

Note: These sections can change from CDR to FRR if there are design related changes made as a result 

of subscale and full-scale test flights, and refined modeling and analysis. These should specify the 

mechanisms for the hazards and uniquely identify them from other hazards. Ambiguity is not useful 

in safety work.

– A completed list of mitigations addressing the hazards and/or their causes.

– A completed list of verifications for the identified mitigations. This should include methods of verifying the 

mitigations and controls are (or will be) in place, and how they will serve to ensure the mitigation.

• Be sure to discuss any concerns that remain as the project moves into the operational phase of the lifecycle. 

Emphasize concerns related to your procedures as well as the environment.

Launch Operations Procedures

Provide detailed procedures and checklists for each of the following (at a minimum):

• Recovery preparation

• Payload preparation

• Electronics preparation

• Rocket preparation

• Motor preparation

• Setup on launch pad

• Igniter installation

• Launch procedure

• Troubleshooting

• Post-flight inspection

These procedures and checklists should include specially demarcated steps related to safety. Examples include:

• Warnings of hazards that can result from missing a step
2024 Student Launch Handbook & Request for Proposal 32USLI Project Milestones: Criteria and Expectations

• PPE required for a step in the procedure (identified BEFORE the step)

• Required personnel to complete a step or to witness and sign off verification of a step

VII. Project Plan

Testing

• Prove that all testing is complete and provide test methodology and discussion of results.

• Discuss whether each test was successful or not.

• Discuss lessons learned from the tests conducted.

• Discuss any differences between predicted and actual results of the tests conducted.

Requirements Compliance

• Review and update the verification plan. Describe how each handbook requirement was verified using testing, 

analysis, demonstration, or inspection.

• Review and update the team derived requirements for the vehicle, recovery system, and payload. Describe 

how each team derived requirement was verified using testing, analysis, demonstration, or inspection.

Budgeting and Funding Summary

• Provide an updated line item budget with market values for individual components, material vendors, and 

applicable taxes or shipping/handling fees.

• Provide an updated funding plan describing sources of funding, allocation of funds, and a material acquisition 

plan for any items that have not yet been obtained.
2024 Student Launch Handbook & Request for Proposal 33USLI Project Milestones: Criteria and Expectations

Flight Readiness Review Presentation

Please include the following information in your presentation:

• Launch vehicle design and dimensions

• Visually show points of separation along with location of energetic materials and all recovery components clearly 

labeled

• Discuss key design features of the launch vehicle

• Motor description

• Rocket flight stability in static margin diagram

• Launch thrust-to-weight ratio and rail exit velocity

• Mass statement

• Parachute sizes and descent rates

• Kinetic energy at key phases of the mission, especially at landing

• Predicted altitude of the launch vehicle with a 5-, 10-, 15-, and 20-mph wind

• Predicted drift from the launch pad with a 5-, 10-, 15-, and 20-mph wind

• Test plans and procedures

• Vehicle Demonstration Flight results. Present and discuss the actual flight test data, as well as any issues or 

failures encountered.

• Recovery system tests

• Summary of requirements verification (launch vehicle)

• Payload design and dimensions

• Key design features of the payload

• Payload integration into the vehicle

• Payload retention system design

• Payload Demonstration Flight plans. If complete, discuss the actual flight test results, as well as any issues or 

failures encountered.

• Summary of requirements verification (payload)

• Interfaces with ground systems (vehicle and payload)

The FRR will be presented to a panel that may be comprised of scientists, engineers, safety experts, education 

specialists, and industry partners. The team is expected to present and defend the as-built launch vehicle and 

payload, showing that the launch vehicle and payload meet all requirements and mission objectives and that the 

design can be safely launched and recovered. Upon successful completion of the FRR, the team is given the 

authority to proceed into the Launch and Operational phases of the life cycle.

It is expected that the team participants deliver the report and answer all questions. The mentor or faculty advisor 

shall not participate in the presentation.

The presentation of the FRR shall be well prepared with an overall professional appearance. This includes, but is not 

limited to, the following: easy-to-read slides; appropriate placement of pictures, graphs, and videos; professional 

appearance of the presenters; speaking clearly and loudly; looking into the camera; referring to the slides, not 

reading them; and communicating to the panel in an appropriate and professional manner. The slides should be 

made with dark text on a light background.
2024 Student Launch Handbook & Request for Proposal 34USLI Project Milestones: Criteria and Expectations

Flight Readiness Review Addendum

The FRR Addendum is a required submission for any team completing a Payload Demonstration Flight or NASArequired Vehicle Demonstration Re-flight after the submission of the FRR Report. It is expected to be a brief but 

informative document highlighting the success or failure of the new flight(s) and any updates or changes to the 

vehicle or payload design. The information reported in the FRR Addendum will be reviewed by NASA to determine 

eligibility of each team to perform their competition launch. 

Flight Readiness Review Addendum Document Outline

Page Limit: The FRR Addendum is not scored and does not have a specific minimum or maximum page 

count, but each requested item listed below shall be sufficiently addressed.

I. Summary of FRR Addendum

Team Summary

• Team name, mailing address, and contact information

• Document the number of hours spent working on the FRR addendum milestone

Purpose of Flight(s)

• Identify whether the flight(s) conducted were conducted to fulfill the requirements for the Payload 

Demonstration Flight, Vehicle Demonstration Re-flight, or both.

Flight Summary Information (for each flight)

• Date of flight

• Location of flight

• Launch conditions

• Motor flown (brand and designation)

• Ballast flown (lbs.)

• Final payload flown (Y/N)

• Air brake system status during test flight (list N/A if your vehicle does not contain an air brake system)

• Official target altitude (ft.)

• Predicted altitude from simulations (ft.)

• Measured altitude (ft.)

• Identify any off-nominal events during mission execution

Changes made since FRR

• Describe changes made to the vehicle design and explain why those changes are necessary.

• Describe changes made to the payload design and explain why those changes are necessary.

II. Payload Demonstration Flight Results (if applicable) 

Summarize the retention system and mission of the payload, along with discussing its successes and 

failures.

• Summarize the designed payload mission sequence, from activation or deployment through mission 

completion

• Summarize the design of the payload retention system

• Provide altimeter flight profile data

• Identify all systems that functioned as intended

• Identify and discuss any hardware or software that failed to function as intended

• Identify any hardware that was damaged and required repair or replacement and discuss the plan of action

• Discuss payload lessons learned from the flight
2024 Student Launch Handbook & Request for Proposal 35USLI Project Milestones: Criteria and Expectations

III) Vehicle Demonstration Re-flight (if applicable)

Summarize the flight of the rocket and discuss its successes and failures.

• Identify all systems that functioned as intended.

• Identify and discuss any hardware or software that failed to function as intended.

• If the payload was not present, describe how the payload was simulated during the flight.

• Altimeter flight profile data output with accompanying altitude and velocity versus time plots. Altimeter flight 

profile graph(s) that are not complete (liftoff through landing) shall not be accepted.

• Include quality pictures of the as landed configuration of all sections of the launch vehicle. This includes but is 

not limited to nosecone, recovery system, airframe, and booster.

• Calculate the kinetic energy at landing for each independent and tethered section of the launch vehicle.

• Perform an analysis of the Vehicle Demonstration Flight. Update your simulated flight model with launch day 

condition data and compare the predicted flight performance to the actual flight data. Discuss the results.

• Estimate the drag coefficient of the full-scale rocket utilizing launch data. Use this value to run a post-flight 

simulation.

• Identify any hardware that was damaged and required repair or replacement and discuss the plan of action.

• Discuss lessons learned from the flight.
2024 Student Launch Handbook & Request for Proposal 36USLI Project Milestones: Criteria and Expectations

Launch Readiness Review (LRR)

The Launch Readiness Review (LRR) will be conducted by NASA and the National Association of Rocketry (NAR), 

our launch services provider. These inspections are only open to team members and mentors. These names 

were submitted as part of your team list. All rockets/payloads will undergo a detailed, deconstructive, hands-on 

inspection. 

Your team should bring all components of the rocket and payload except for the motor, black powder, and electric 

matches. Be able to present: anchored flight predictions, anchored drift predictions (15-mph crosswind), procedures 

and checklists, and CP and CG with loaded motor marked on the airframe. The rockets will be assessed for 

structural and electrical integrity, as well as safety concerns. At a minimum, all teams shall have:

• An airframe prepared for flight with the exception of energetic materials

• Data from the previous flight(s)

• A list of any flight anomalies that occurred on the previous full-scale flight(s) and the mitigation actions

• A list of any changes to the airframe since the last flight

• Flight simulations

• Pre-flight checklist(s) and Fly Sheet

• Team name and contact info in or on the airframe and any untethered section of the vehicle

Each team will demonstrate these tasks to the NAR Review Team. The RSO has final word on whether the rocket 

and/or payload may be flown on Launch Day.

A “punch list” will be generated for each team. Items identified on the punch list must be corrected and verified by 

NAR/NASA prior to Launch Day. A flight card will be provided to teams and is to be completed and submitted at the 

LCO booth on Launch Day.
2024 Student Launch Handbook & Request for Proposal 37USLI Project Milestones: Criteria and Expectations

Post-Launch Assessment Review (PLAR)

The PLAR is an assessment of system in-flight and payload mission performance from your final competition launch. 

All scientific and engineering results and findings shall be reported along with a cumulative summary of your teams’ 

experience on the project as a whole. 

Page Limit: PLARs will only be scored using the first 25 pages of the report (not including title page).

Any additional content will not be considered while scoring. 

• Team name

• Motor used

• Vehicle dimensions

• Altitude reached (ft.)

• Official target altitude (ft.)

• Competition Launch altimeter flight profile data

• Vehicle summary

• Payload summary

• Data analysis and results of the vehicle and payload

• Altimeter flight profile data output with accompanying altitude and velocity versus time plots is required to meet 

this requirement. Altimeter flight profile graph(s) that are not complete (liftoff through landing) will not be accepted.

• Raw altimeter data in csv or xlsx format.

• Quality pictures of the as landed configuration of all sections of the launch vehicle. This includes but is not limited 

to nosecone, recovery system, airframe, and booster.

• Describe separation events and state altitude of events

• Ascent and descent analysis and metrics of the launch vehicle

• Scientific value achieved

• Visual data observed

• Lessons learned for vehicle, payload, and overall project

• Discussion of successes and failures of individual subsystems

• Summary of overall experience (what you attempted to do versus the results; how valuable you felt the 

experience was)

• A table which totals the number of hours spent on SL broken down by the following categories: Proposal, PDR, 

CDR, FRR, FRR addendum (if applicable), PLAR, STEM Engagement, Social Media, and launch activities.

• STEM Engagement summary

• Final Budget summary
38

STEM 

Engagement
2024 Student Launch Handbook & Request for Proposal 39USLI STEM Engagement

As part of the STEM Engagement requirement for completion of the NASA Student Launch activity, teams shall 

engage a minimum of 250 participants in direct educational, hands-on science, technology, engineering and 

mathematics (STEM) activities. These activities can be conducted in-person or virtually. To satisfy this requirement

• All events shall occur between project acceptance and the FRR addendum due date.

• The STEM Engagement Activity Report shall be submitted via email for all events by the FRR due date.

• A template of the STEM Engagement Activity Report can be found on pages 40-43.

• Teams shall engage a minimum of 250 participants in Educational Direct Engagement activities in order 

to be eligible for STEM Engagement awards. For a definition of what constitutes an Educational— Direct 

Engagement Activity, see below. These definitions are also found in the STEM Engagement Activity Report for 

reference.

• Teams are encouraged to engage as many participants as possible in the STEM Engagement activity types listed 

below.

STEM Engagement Activity Types:

• Education — Direct Engagements (minimum 250 participants required)

This type of interaction will count towards your project/STEM Engagement requirement. Instructional, hands-on 

activities where participants engage in learning a STEM related concept by actively participating in an activity. 

This includes instructor-led facilitation or inquiry around an activity regardless of media (e.g., face-to-face, video, 

conference, etc.). 

Example: Students learn to identify the occurrence of Newton’s Laws through building and flying a model rocket 

or students learn about basic rocketry through designing and launching their own rockets in simulation software.

• Education — Indirect Engagements

Participants are engaged in learning a STEM concept through instructor-led facilitation or presentation. 

Example: Students learn about the occurrence of Newton’s Laws in basic rocketry through a presentation or 

students learn about the Space Launch System (SLS) through SLS activity/materials provided on www.nasa.gov/

SLS (under SLS public Engagement).

• Outreach — Direct Engagements

Participants do not learn a STEM concept but are able to get hands-on exposure to STEM related hardware.

Example: The team does a presentation for students about their Student Launch project, brings their rocket and 

components to the event, and demonstrates a launch of their rocket for the students.

• Outreach — Indirect Engagements

Participants interact with the team in an informal setting. 

Example: the team sets up a display at a local museum during science night. Students come by, talk to the team 

and learn about their project.

STEM Engagement Activity Reports

Each activity reports submitted should represent one activity. There may be multiple events listed for the same 

activity.

• Activity report shall be fully completed and list all the event dates and information for an activity.

• The STEM Engagement Activity Type shall be correctly identified for the activity. The NASA Review Panel reserves 

the right to change the activity type if the activity is categorized incorrectly.

• Activity descriptions should be clear and thorough.

• Learning targets should be clear and specific.

• Include with your report any documents, evaluations, surveys, questionnaires, handouts, videos or presentations, 

etc., used in your activity.
2024 Student Launch Handbook & Request for Proposal 40USLI STEM Engagement

STEM Engagement Activity Report

Please complete and submit this form for each STEM Engagement activity that your team completes. If you hold 

multiple events utilizing the same activity, only one report needs to be submitted.

For numerous NASA STEM engagement ideas, educational resources, games, videos, and PowerPoint presentations 

visit https://www.nasa.gov/education/materials/. NASA educational resources can be searched and filtered by 

subject (e.g., space science, NASA history, technology, etc.). Please attach any pictures, presentations, or feedback 

documents which you would like to share to the end of the document.

Activity Title: ________________________________________________________________________________

Type of Activity:______________________________________________________________________________

For activity type, choose from one of the Types of Engagement Activities below:

• Education/Direct Engagements

 This type of interaction will count towards your project/STEM Engagement requirement.

 A count of participants in instructional, hands-on activities where participants engage in learning a STEM topic 

by actively participating in an activity. This includes instructor-led facilitation around an activity regardless of 

media (e.g., face-to-face, video conference, etc.). 

 Example: Students learn about Newton’s Laws through building and flying a rocket.

• Education/Indirect Engagements

 A count of participants engaged in learning a STEM topic through instructor- led facilitation or presentation.

 Example: Students learn about Newton’s Laws through a PowerPoint presentation, or students learn about 

the Space Launch System (SLS) through a SLS activity/materials provided on www.NASA.gov/SLS (under SLS 

Public Engagement).

• Outreach/Direct Engagements

 A count of participants who do not necessarily learn a STEM topic but are able to get a hands-on look at 

STEM hardware. 

 Example, the team does a presentation to students about their Student Launch project, brings their rocket and 

components to the event, and flies a rocket at the end of the presentation.

• Outreach/Indirect Engagements

 A count of participants that interact with the team. 

 Example: The team sets up a display at the local museum during Science Night. Students come by and talk to 

the team about their project.

Learning Target for the Activity (Describe the learning target for this activity. What did you want your participants to 

learn from this activity? Be specific.)
2024 Student Launch Handbook & Request for Proposal 41USLI STEM Engagement

Describe your activity with this group. (Attach additional pages if more information is needed. Please attach any 

pictures, presentations, or documents which you would like to share to the end of the document.)
2024 Student Launch Handbook & Request for Proposal 42USLI STEM Engagement

Did you conduct an evaluation of your learning target? If so, what were the results? (Please include a copy of 

your evaluation and a summary of your results.)

Describe any feedback received from your participants about your activity overall. (Please include any feedback 

forms or surveys that were used. Use this space or attach actual feedback from participants.)
2024 Student Launch Handbook & Request for Proposal 43USLI STEM Engagement

Event Information

For each event that was held for this activity, please enter the information in the table below. Each participant for 

each event should only be counted once. If you need additional space, please attach to the document before 

submission.

Event 

Date Name of Group

Total 

Number of 

Participants

Number 

of 

Preschool 

– 4 Grade

Number 

of

5 – 9

Grade

Number 

of

10 – 12

Grade

Number

of

Undergrad

Number

of 

Educators

Number

of

Noneducators

Additional Notes/Comments:
44

Safety
2024 Student Launch Handbook & Request for Proposal 45USLI Safety

High-Power Rocket Safety Code

Provided by the National Association of Rocketry

1. Certification. I will only fly high power rockets or possess high power rocket motors that are within the scope 

of my user certification and required licensing.

2. Materials. I will use only lightweight materials such as paper, wood, rubber, plastic, fiberglass, or when 

necessary ductile metal, for the construction of my rocket.

3. Motors. I will use only certified, commercially made rocket motors, and will not tamper with these motors or 

use them for any purposes except those recommended by the manufacturer. I will not allow smoking, open 

flames, nor heat sources within 25 feet of these motors.

4. Ignition System. I will launch my rockets with an electrical launch system, and with electrical motor igniters 

that are installed in the motor only after my rocket is at the launch pad or in a designated prepping area. My 

launch system will have a safety interlock that is in series with the launch switch that is not installed until my 

rocket is ready for launch, and will use a launch switch that returns to the “off” position when released. The 

function of onboard energetics and firing circuits will be inhibited except when my rocket is in the launching 

position.

5. Misfires. If my rocket does not launch when I press the button of my electrical launch system, I will remove 

the launcher’s safety interlock or disconnect its battery and will wait 60 seconds after the last launch attempt 

before allowing anyone to approach the rocket.

6. Launch Safety. I will use a 5-second countdown before launch. I will ensure that a means is available to warn 

participants and spectators in the event of a problem. I will ensure that no person is closer to the launch pad 

than allowed by the accompanying Minimum Distance Table. When arming onboard energetics and firing 

circuits, I will ensure that no person is at the pad except safety personnel and those required for arming 

and disarming operations. I will check the stability of my rocket before flight and will not fly it if it cannot be 

determined to be stable. When conducting a simultaneous launch of more than one high power rocket, I will 

observe the additional requirements of NFPA 1127.

7. Launcher. I will launch my rocket from a stable device that provides rigid guidance until the rocket has 

attained a speed that ensures a stable flight, and that is pointed to within 20 degrees of vertical. If the wind 

speed exceeds 5 miles per hour, I will use a launcher length that permits the rocket to attain a safe velocity 

before separation from the launcher. I will use a blast deflector to prevent the motor’s exhaust from hitting the 

ground. I will ensure that dry grass is cleared around each launch pad in accordance with the accompanying 

Minimum Distance table, and will increase this distance by a factor of 1.5 and clear that area of all combustible 

material if the rocket motor being launched uses titanium sponge in the propellant.

8. Size. My rocket will not contain any combination of motors that total more than 40,960 N-sec (9,208 poundseconds) of total impulse. My rocket will not weigh more at liftoff than one-third of the certified average thrust 

of the high power rocket motor(s) intended to be ignited at launch.

9. Flight Safety. I will not launch my rocket at targets, into clouds, near airplanes, nor on trajectories that take 

it directly over the heads of spectators or beyond the boundaries of the launch site, and will not put any 

flammable or explosive payload in my rocket. I will not launch my rockets if wind speeds exceed 20 miles per 

hour. I will comply with Federal Aviation Administration airspace regulations when flying and will ensure that 

my rocket will not exceed any applicable altitude limit in effect at that launch site.

10. Launch Site. I will launch my rocket outdoors, in an open area where trees, power lines, occupied buildings, 

and persons not involved in the launch do not present a hazard, and that is at least as large on its smallest 

dimension as one-half of the maximum altitude to which rockets are allowed to be flown at that site or 1,500 

feet, whichever is greater, or 1,000 feet for rockets with a combined total impulse of less than 160 N-sec, a 

total liftoff weight of less than 1,500 grams, and a maximum expected altitude of less than 610 meters (2000 

feet).
2024 Student Launch Handbook & Request for Proposal 46USLI Safety

11. Launcher Location. My launcher will be 1,500 feet from any occupied building or from any public highway on 

which traffic flow exceeds 10 vehicles per hour, not including traffic flow related to the launch. It will also be no 

closer than the appropriate Minimum Personnel Distance from the accompanying table from any boundary of 

the launch site.

12. Recovery System. I will use a recovery system such as a parachute in my rocket so that all parts of my rocket 

return safely and undamaged and can be flown again, and I will use only flame-resistant or fireproof recovery 

system wadding in my rocket.

13. Recovery Safety. I will not attempt to recover my rocket from power lines, tall trees, or other dangerous 

places, fly it under conditions where it is likely to recover in spectator areas or outside the launch site, nor 

attempt to catch it as it approaches the ground.

Minimum Distance Table

Installed Total Impulse 

(Newton-Seconds)

Equivalent High Power 

Motor Type

Minimum Diameter of 

Cleared Area (ft.)

Minimum Personnel 

Distance (ft.)

Minimum Personnel 

Distance (Complex Rocket) 

(ft.)

0 – 320.00 H or smaller 50 100 200

320.01 – 640.00 I 50 100 200

640.01 – 1,280.00 J 50 100 200

1,280.01 – 2,560.00 K 75 200 300

2,560.01 – 5,120.00 L 100 300 500

5,120.01 – 10,240.00 M 125 500 1,000

10,240.01 – 20,480.00 N 125 1,000 1,500

20,480.01 – 40,960.00 O 125 1,500 2,000

Note: A Complex rocket is one that is multi-staged or that is propelled by two or more rocket motors

Revision as of August 2012

Provided by the National Association of Rocketry (www.nar.org)
47

Awards
2024 Student Launch Handbook & Request for Proposal 48USLI Awards

College and University Division Awards

Award Award Description Determined By When Awarded

Vehicle Design 

Award

Awarded to the team with the most creative and innovative overall vehicle design for 

their intended payload while still maximizing safety and efficiency. NASA Panel Awards Ceremony

Experiment Design 

Award

Awarded to the team with the most creative and innovative payload design while 

maximizing safety and science value. NASA Panel Awards Ceremony

Safety Award Awarded to the team that demonstrates the highest level of safety according to the 

scoring rubric. NASA Panel Awards Ceremony

Project Review 

(PDR/CDR/FRR) 

Award

Awarded to the team that is viewed to have the best combination of written reviews 

and formal presentations. NASA Panel Awards Ceremony

STEM Engagement 

Award

Awarded to the team that is determined to have best inspired the study of rocketry 

and other science, technology, engineering, and math (STEM) related topics in their 

community. This team not only presented a high number of activities to a large 

number of people, but also delivered quality activities to a wide range of audiences.

NASA Panel Awards Ceremony

Social Media Award Awarded to the team that has the most active and creative social media presence 

throughout the project year. NASA Panel Awards Ceremony

Altitude Award Awarded to the team that comes closest to their declared target altitude on their 

competition launch. NASA Panel After PLAR Milestone

Best Looking Rocket 

Award* Awarded to the team that is judged by their peers to have the “Best Looking Rocket”. Peers Awards Ceremony

Rookie Award

Awarded to the top overall rookie team using the same criteria as the Overall Winner 

Award. If a rookie team is the Overall Winner, this award will go to the 2nd place 

Rookie Team.

NASA Panel After PLAR 

Milestone

Overall Winner Awarded to the top overall team. Design reviews, outreach, safety, and a successful 

flight will all factor into the Overall Winner. NASA Panel After PLAR Milestone

2nd Place Winner Awarded to the second overall team. Design reviews, outreach, safety, and a 

successful flight will all factor into the Runner Up Award winner. NASA Panel After PLAR Milestone

3D Printed Award Awarded to the team with the best consideration, design, and implementation in 

regards to 3D printing of launch vehicle and payload. NASA Panel Awards Ceremony

Service Academy 

Award

Awarded to the highest finishing service academy in the College and University 

Division. NASA Panel After PLAR Milestone

* Only teams traveling to NASA Launch Complex event are eligible.
2024 Student Launch Handbook & Request for Proposal 49USLI Awards

Artemis Student Challenges Awards

The Artemis Student Challenges (ASC) are foundational learning opportunities for middle school through graduate 

level students, preparing them to learn and engage in Artemis-focused challenges that align with mission needs. 

ASC is comprised of eight challenges including the App Development Challenge, BIG Idea Challenge, First Nations 

Launch, Human Exploration Rover Challenge, Lunabotics, Micro-g NExT, SUITS, and Student Launch. New this year, 

the Artemis Student Challenges will select teams across all challenges to receive prestigious awards in the three 

categories below.

Pay It Forward Award

This award is given to teams that best conduct impactful educational engagement events in their community or 

further. Educational engagement includes instructional, hands-on activities where participants engage in learning a 

STEM-related concept by actively participating in an activity.

Innovation Award

This award is given to teams that best create new, innovative ideas and/or solutions within the scope of their 

respective challenge. Ingenuity, creativity, and inventiveness in either technology or nontechnology focused ideas are 

awarded for their original ideas, creating efficiency, effective results, and/or solving a problem.

Artemis Educator Award

This award is given to educators/faculty/mentors in each challenge as nominated by student team members. Student 

team members will recognize their faculty/mentor(s) who inspire learners and motivate them to work hard, achieving 

more than the team members thought possible. The award acknowledges the time and dedication educators/faculty/

mentors take to be exceptional teachers. Educators/faculty/mentors are noted for their commitment to learning and 

their valuable efforts for motivating and inspiring others. The NASA management team shall share the nomination 

process after the FRR milestone.
2024 Student Launch Handbook & Request for Proposal 50Middle/High School General and Proposal Requirements

2024 Student Launch Handbook & Request for Proposal

Timeline for Middle/High School Division

50

Middle/High School 

SLI Division Handbook
2024 Student Launch Handbook & Request for Proposal 51Middle/High School General and Proposal Requirements

2024 Student Launch Handbook & Request for Proposal

Timeline for Middle/High School Division

Timeline for NASA SLI Division

(Dates are subject to change.)

August 2023

14 .................Request for Proposal (RFP) released

September 2023

11..................Please visit https://www.nasa.gov/stem/studentlaunch/handbook/index.html for instructions on 

submitting your proposal. Proposals are due 8:00 a.m. CST

October 2023

04..................Awarded proposals announced

05..................Kickoff and PDR Q&A

26..................Preliminary Design Review (PDR) report, presentation slides, and flysheet submitted to NASA project 

management team by 8:00 a.m. CDT

November 2023

01 – 30 ...........PDR video teleconferences

December 2023

07..................CDR Q&A

January 2024

08..................Subscale Flight deadline

08..................Critical Design Review (CDR) report, presentation slides, and flysheet submitted to NASA project 

management team by 8:00 a.m. CST

16 – Feb. 6 ....CDR video teleconferences

February 2024

08..................FRR Q&A

March 2024

04..................Vehicle Demonstration Flight deadline

04..................Flight Readiness Review (FRR) report, presentation slides, and flysheet submitted to NASA project 

management team by 8:00 a.m. CST

11 – 29 ...........FRR video teleconferences

April 2024

01..................Launch window opens for teams not traveling to Launch Week. PLAR must be submitted within 14 

days of Launch

01..................Payload Demonstration Flight and Vehicle Demonstration Re-flight deadlines

01..................FRR Addendum submitted to NASA project management team by 8:00 a.m. CDT (Teams completing 

additional Payload Demonstration Flights and Vehicle Demonstration Re-flights only.)

04..................Launch Week Q&A

10..................Teams arrive in Huntsville, AL

11 – 12 ...........All-day Launch Week Events

13..................Launch Day

14..................Backup Launch Day

23..................Teams travelling to Launch Week: Post-Launch Assessment Review (PLAR) submitted to NASA project 

management team by 8:00 a.m. CDT

30..................Launch window closes for teams not travelling to Huntsville for Launch Week. PLAR must be 

submitted within 7 days of launch.
2024 Student Launch Handbook & Request for Proposal 52Middle/High School General and Proposal Requirements

2024 Student Launch Handbook & Request for Proposal

Timeline for Middle/High School Division

52

General & Proposal 

Requirements
2024 Student Launch Handbook & Request for Proposal 53Middle/High School General and Proposal Requirements

Student Launch Requirements

1. General Requirements

1.1. Students on the team will do 100% of the project, including design, construction, written reports, 

presentations, and flight preparation with the exception of assembling the motors and handling black 

powder or any variant of ejection charges, or preparing and installing electric matches (to be done by the 

team’s mentor). Student team members shall only be a part of one team in any capacity. Teams will submit 

new work. Excessive use of past work will merit penalties.

1.2. The team will provide and maintain a project plan to include, but not limited to the following items: project 

milestones, budget and community support, checklists, personnel assignments, STEM engagement 

events, and risks and mitigations.

1.3. Team members who will travel to the Huntsville Launch shall have fully completed registration in the NASA 

Gateway system before the roster deadline. Team members shall include:

1.3.1. Students actively engaged in the project throughout the entire year.

1.3.2. One mentor (see requirement 1.13).

1.3.3. No more than two adult educators.

1.4. Teams shall engage a minimum of 250 participants in Educational Direct Engagement STEM activities. 

These activities can be conducted in-person or virtually. To satisfy this requirement, all events shall occur 

between project acceptance and the FRR addendum due date. A template of the STEM Engagement 

Activity Report can be found on pages 86 – 89. 

1.5. The team shall establish and maintain a social media presence to inform the public about team activities.

1.6. Teams shall email all deliverables to the NASA project management team by the deadline specified in the 

handbook for each milestone. In the event that a deliverable is too large to attach to an email, inclusion of 

a link to download the file will be sufficient. Late submissions of PDR, CDR, FRR milestone documents will 

be accepted up to 72 hours after the submission deadline. Late submissions will incur an overall penalty. 

No PDR, CDR, FRR milestone documents will be accepted beyond the 72-hour window. Teams that fail to 

submit the PDR, CDR, FRR milestone documents will be eliminated from the project.

1.7. Teams who do not satisfactorily complete each milestone review (PDR, CDR, FRR) shall be provided action 

items needed to be completed following their review and shall be required to address action items in a 

delta review session. After the delta session the NASA management panel shall meet to determine the 

teams’ status in the program and the team shall be notified shortly thereafter.

1.8. All deliverables shall be in PDF format.

1.9. In every report, teams shall provide a table of contents including major sections and their respective subsections.

1.10. In every report, the team shall include the page number at the bottom of the page.

1.11. The team shall provide any computer equipment necessary to perform a video teleconference with the 

review panel. This includes, but is not limited to, a computer system, video camera, speaker telephone, 

and a sufficient Internet connection. Cellular phones should be used for speakerphone capability only as a 

last resort.

1.12. All teams attending Launch Week shall be required to use the launch pads provided by Student Launch’s 

launch services provider. No custom pads shall be permitted at the NASA Launch Complex. At launch, 

8-foot 1010 rails and 12-foot 1515 rails will be provided. The launch rails will be canted 5 – 10 degrees 

away from the crowd on Launch Day. The exact cant will depend on Launch Day wind conditions.
2024 Student Launch Handbook & Request for Proposal 54Middle/High School General and Proposal Requirements

1.13. Each team shall identify a “mentor.” A mentor is defined as an adult who is included as a team member, 

who will be supporting the team (or multiple teams) throughout the project year, and may or may not be 

affiliated with the school, institution, or organization. The team mentor shall not be a student team member 

The mentor shall maintain a current certification, and be in good standing, through the National Association 

of Rocketry (NAR) or Tripoli Rocketry for the motor impulse of the launch vehicle and must have flown and 

successfully recovered (using electronic, staged recovery) a minimum of 2 flights in this or a higher impulse 

class, prior to PDR. The mentor is designated as the individual owner of the rocket for liability purposes 

and must travel with the team to Launch Week. One travel stipend will be provided per mentor regardless 

of the number of teams he or she supports. The stipend will only be provided if the team passes FRR and 

the team and mentor attend Launch Week in April.

1.14. Teams will track and report the number of hours spent working on each milestone.

2. Vehicle Requirements

2.1. The vehicle shall deliver the payload to an apogee altitude between 3,500 and 5,500 feet above ground 

level (AGL). Teams flying below 3,000 feet or above 6,000 feet on their competition launch will receive zero 

altitude points towards their overall project score and will not be eligible for the Altitude Award.

2.2. Teams shall declare their target altitude goal at the PDR milestone. The declared target altitude shall be 

used to determine the team’s altitude score.

2.3. The launch vehicle shall be designed to be recoverable and reusable. Reusable is defined as being able to 

launch again on the same day without repairs or modifications.

2.4. The launch vehicle shall have a maximum of four (4) independent sections. An independent section is 

defined as a section that is either tethered to the main vehicle or is recovered separately from the main 

vehicle using its own parachute.

2.4.1. Coupler/airframe shoulders which are located at in-flight separation points shall be at least 2 airframe diameters in length. (One body diameter of surface contact with each airframe section.)

2.4.2. Coupler/airframe shoulders which are located at non-in-flight separation points shall be at least 

1.5 airframe diameters in length. (0.75 body diameter of surface contact with each airframe 

section.)

2.4.3. Nosecone shoulders which are located at in-flight separation points shall be at least 1⁄2 body 

diameter in length.

2.5. The launch vehicle shall be capable of being prepared for flight at the launch site within 2 hours of the time 

the Federal Aviation Administration flight waiver opens.

2.6. The launch vehicle and payload shall be capable of remaining in launch-ready configuration on the pad for 

a minimum of 3 hours without losing the functionality of any critical on-board components, although the 

capability to withstand longer delays is highly encouraged.

2.7. The launch vehicle shall be capable of being launched by a standard 12-volt direct current firing system. 

The firing system will be provided by the NASA-designated launch services provider.

2.8. The launch vehicle shall require no external circuitry or special ground support equipment to initiate launch 

(other than what is provided by the launch services provider).

2.9. The launch vehicle shall use a commercially available solid motor propulsion system using ammonium 

perchlorate composite propellant (APCP) which is approved and certified by the National Association of 

Rocketry (NAR), Tripoli Rocketry Association (TRA), and/or the Canadian Association of Rocketry (CAR).

2.9.1. Final motor choice shall be declared by the Critical Design Review (CDR) milestone.

2.9.2. Any motor change after CDR shall be approved by the NASA Range Safety Officer (RSO). 

Changes for the sole purpose of altitude adjustment shall not be approved. A penalty against the 

team’s overall score shall be incurred when a motor change is made after the CDR milestone, 

regardless of the reason.
2024 Student Launch Handbook & Request for Proposal 55Middle/High School General and Proposal Requirements

2.10. The launch vehicle shall be limited to a single motor propulsion system.

2.11. The total impulse provided by a High School or Middle School launch vehicle shall not exceed 2,560

Newton-seconds (K-class).

2.12. Pressure vessels on the vehicle must be approved by the RSO and shall meet the following criteria:

2.12.1. The minimum factor of safety (Burst or Ultimate pressure versus Max Expected Operating

Pressure) will be 4:1 with supporting design documentation included in all milestone reviews.

2.12.2. Each pressure vessel shall include a pressure relief valve that sees the full pressure of the tank and 

is capable of withstanding the maximum pressure and flow rate of the tank.

2.12.3. The full pedigree of the tank shall be described, including the application for which the tank was 

designed and the history of the tank. This will include the number of pressure cycles put on the 

tank, the dates of pressurization/depressurization, and the name of the person or entity

administering each pressure event.

2.13. The launch vehicle shall have a minimum static stability margin of 2.0 at the point of rail exit. Rail exit is 

defined at the point where the forward rail button loses contact with the rail.

2.14. The launch vehicle shall have a minimum thrust to weight ratio of 5.0 : 1.0.

2.15. Any structural protuberance on the rocket shall be located aft of the burnout center of gravity. Camera 

housings will be exempted, provided the team can show that the housing(s) causes minimal

aerodynamic effect on the rocket’s stability.

2.16. The launch vehicle shall accelerate to a minimum velocity of 52 fps at rail exit.

2.17. All teams shall successfully launch and recover a subscale model of their rocket prior to CDR. Success of 

the subscale is at the sole discretion of the NASA review panel. The subscale flight may be conducted at 

any time between proposal award and the CDR submission deadline. Subscale flight data shall be reported 

in the CDR report and presentation at the CDR milestone. Subscales are required to use a minimum motor 

impulse class of E (Mid Power motor).

2.17.1. The subscale model should resemble and perform as similarly as possible to the full-scale model; 

however, the full-scale will not be used as the subscale model.

2.17.2. The subscale model shall carry an altimeter capable of recording the model’s apogee altitude.

2.17.3. The subscale rocket shall be a newly constructed rocket, designed and built specifically for this 

year’s project.

2.17.4. Proof of a successful flight shall be supplied in the CDR report.

2.17.4.1. Altimeter flight profile graph(s) OR a quality video showing successful launch and 

recovery events as deemed by the NASA management panel are acceptable methods 

of proof. Altimeter flight profile graph(s) that are not complete (liftoff through landing) will 

not be accepted.

2.17.4.2. Quality pictures of the as landed configuration of all sections of the launch vehicle shall 

be included in the CDR report. This includes but is not limited to nosecone, recovery 

system, airframe, and booster.

2.17.5. The subscale rocket shall not exceed 75% of the dimensions (length and diameter) of your 

designed full-scale rocket. For example, if your full-scale rocket is a 4” diameter 100” length 

rocket, your subscale shall not exceed 3” diameter and 75” in length.

2.18. All teams shall complete demonstration flights as outlined below.
2024 Student Launch Handbook & Request for Proposal 56Middle/High School General and Proposal Requirements

2.18.1. Vehicle Demonstration Flight—All teams shall successfully launch and recover their full-scale 

rocket prior to FRR in its final flight configuration. The rocket flown shall be the same rocket 

to be flown as their competition launch. The purpose of the Vehicle Demonstration Flight is to 

validate the launch vehicle’s stability, structural integrity, recovery systems, and the team’s ability 

to prepare the launch vehicle for flight. A successful flight is defined as a launch in which all 

hardware is functioning properly (i.e., drogue chute at apogee, main chute at the intended lower 

altitude, functioning tracking devices, etc.) The following criteria shall be met during the full-scale 

demonstration flight:

2.18.1.1. The vehicle and recovery system shall have functioned as designed.

2.18.1.2. The full-scale rocket shall be a newly constructed rocket, designed and built specifically 

for this year’s project.

2.18.1.3. The payload does not have to be flown during the full-scale Vehicle Demonstration 

Flight. The following requirements still apply:

2.18.1.3.1. If the payload is not flown, mass simulators shall be used to simulate the 

payload mass.

2.18.1.3.2. The mass simulators shall be located in the same approximate location on 

the rocket as the missing payload mass.

2.18.1.4. If the payload changes the external surfaces of the rocket (such as camera housings or 

external probes) or manages the total energy of the vehicle, those systems will be active 

during the full-scale Vehicle Demonstration Flight.

2.18.1.5. Teams shall fly the competition launch motor for the Vehicle Demonstration Flight. The 

team may request a waiver for the use of an alternative motor in advance if the home 

launch field cannot support the full impulse of the competition launch motor or in other 

extenuating circumstances.

2.18.1.6. The vehicle will be flown in its fully ballasted configuration during the full-scale test 

flight. Fully ballasted refers to the maximum amount of ballast that will be flown during 

the competition launch flight. Additional ballast shall not be added without a re-flight of 

the full-scale launch vehicle.

2.18.1.7. After successfully completing the full-scale demonstration flight, the launch vehicle 

or any of its components shall not be modified without the concurrence of the NASA 

Range Safety Officer (RSO).

2.18.1.8. Proof of a successful flight shall be supplied in the FRR report.

2.18.1.8.1. Altimeter flight profile data output with accompanying altitude and velocity 

versus time plots is required to meet this requirement. Altimeter flight profile 

graph(s) that are not complete (liftoff through landing) shall not be accepted.

2.18.1.8..2. Quality pictures of the as landed configuration of all sections of the launch 

vehicle shall be included in the FRR report. This includes but is not limited to 

nosecone, recovery system, airframe, and booster.

2.18.1.9. Vehicle Demonstration flights shall be completed by the FRR submission deadline. 

No exceptions will be made. If the Student Launch office determines that a Vehicle 

Demonstration Re-flight is necessary, then an extension may be granted. THIS 

EXTENSION IS ONLY VALID FOR RE-FLIGHTS, NOT FIRST TIME FLIGHTS. Teams 

completing a required re-flight shall submit an FRR Addendum by the FRR Addendum 

deadline.

2.18.2. Payload Demonstration Flight—All teams shall successfully launch and recover their full-scale 

rocket containing the completed payload prior to the Payload Demonstration Flight deadline. 

The rocket flown shall be the same rocket to be flown as their competition launch. The purpose 

of the Payload Demonstration Flight is to prove the launch vehicle’s ability to safely retain 
2024 Student Launch Handbook & Request for Proposal 57Middle/High School General and Proposal Requirements

the constructed payload during flight and to show that all aspects of the payload perform as 

designed. A successful flight is defined as a launch in which the rocket experiences stable ascent 

and the payload is fully retained until it is deployed (if applicable) as designed. The following 

criteria shall be met during the Payload Demonstration Flight:

2.18.2.1. The payload shall be fully retained until the intended point of deployment (if applicable), 

all retention mechanisms shall function as designed, and the retention mechanism shall 

not sustain damage requiring repair.

2.18.2.2. The payload flown shall be the final, active version.

2.18.2.3. If the above criteria are met during the original Vehicle Demonstration Flight, occurring 

prior to the FRR deadline and the information is included in the FRR package, the 

additional flight and FRR Addendum are not required.

2.18.2.4. Payload Demonstration Flights shall be completed by the FRR Addendum deadline. NO 

EXTENSIONS WILL BE GRANTED.

2.19. An FRR Addendum shall be required for any team completing a Payload Demonstration Flight or NASArequired Vehicle Demonstration Re-flight after the submission of the FRR Report.

2.19.1. Teams required to complete a Vehicle Demonstration Re-Flight and failing to submit the FRR 

Addendum by the deadline shall not be permitted to fly a final competition launch.

2.19.2. Teams who complete a Payload Demonstration Flight which is not fully successful may petition the 

NASA RSO for permission to fly the payload at launch week. Permission shall not be granted if the 

RSO or the Review Panel have any safety concerns.

2.20. The team’s name and Launch Day contact information shall be in or on the rocket airframe as well as in 

or on any section of the vehicle that separates during flight and is not tethered to the main airframe. This 

information shall be included in a manner that allows the information to be retrieved without the need to 

open or separate the vehicle.

2.21. All Lithium Polymer batteries shall be sufficiently protected from impact with the ground and will be brightly 

colored, clearly marked as a fire hazard, and easily distinguishable from other payload hardware.

2.22. Vehicle Prohibitions

2.22.1. The launch vehicle shall not utilize forward firing motors.

2.22.2. The launch vehicle shall not utilize motors that expel titanium sponges (Sparky, Skidmark, MetalStorm, etc.)

2.22.3. The launch vehicle shall not utilize hybrid motors.

2.22.4. The launch vehicle shall not utilize a cluster of motors.

2.22.5. The launch vehicle shall not utilize friction fitting for motors.

2.22.6. The launch vehicle shall not exceed Mach 1 at any point during flight.

2.22.7. Vehicle ballast shall not exceed 10% of the total unballasted weight of the rocket as it would sit on 

the pad (i.e., a rocket with an unballasted weight of 40 lbs. on the pad may contain a maximum of 

4 lbs. of ballast).

2.22.8. Transmissions from onboard transmitters, which are active at any point prior to landing, shall not 

exceed 250 mW of power (per transmitter.)

2.22.9. Transmitters shall not create excessive interference. Teams shall utilize unique frequencies, handshake/passcode systems, or other means to mitigate interference caused to or received from 

other teams.
2024 Student Launch Handbook & Request for Proposal 58Middle/High School General and Proposal Requirements

2.23.10. Excessive and/or dense metal shall not be utilized in the construction of the vehicle. Use of

lightweight metal will be permitted but limited to the amount necessary to ensure structural

integrity of the airframe under the expected operating stresses.

3. Recovery System Requirements

3.1. The full scale launch vehicle shall stage the deployment of its recovery devices, where a drogue parachute 

is deployed at apogee, and a main parachute is deployed at a lower altitude. Tumble or streamer recovery 

from apogee to main parachute deployment is also permissible, provided that kinetic energy during drogue 

stage descent is reasonable, as deemed by the RSO.

3.1.1. The main parachute shall be deployed no lower than 500 feet.

3.1.2. The apogee event shall contain a delay of no more than 2 seconds.

3.1.3. Motor ejection is not a permissible form of primary or secondary deployment.

3.2. Each team shall perform a successful ground ejection test for all electronically initiated recovery events 

prior to the initial flights of the subscale and full-scale vehicles.

3.3. Each independent section of the launch vehicle shall have a maximum kinetic energy of 75 ft-lbf at landing.

3.4. The recovery system shall contain redundant, commercially available barometric altimeters that are 

specifically designed for initiation of rocketry recovery events. The term “altimeters” includes both simple 

altimeters and more sophisticated flight computers.

3.5. Each altimeter shall have a dedicated power supply, and all recovery electronics shall be powered by 

commercially available batteries.

3.6. Each altimeter shall be armed by a dedicated mechanical arming switch that is accessible from the exterior 

of the rocket airframe when the rocket is in the launch configuration on the launch pad.

3.7. Each arming switch shall be capable of being locked in the ON position for launch (i.e., cannot be disarmed 

due to flight forces).

3.8. The recovery system, GPS and altimeters, electrical circuits shall be completely independent of any 

payload electrical circuits.

3.9. Removable shear pins shall be used for both the main parachute compartment and the drogue parachute 

compartment.

3.10. Bent eyebolts shall not be permitted in the recovery subsystem.

3.11. The recovery area shall be limited to a 2,500 ft. radius from the launch pads.

3.12. Descent time of the launch vehicle shall be limited to 90 seconds (apogee to touch down).

3.13. An electronic tracking device shall be installed in the launch vehicle and will transmit the position of the 

tethered vehicle or any independent section to a ground receiver.

3.13.1. Any rocket section or payload component, which lands untethered to the launch vehicle, shall 

contain an active electronic tracking device.

3.13.2. The electronic tracking device(s) shall be fully functional during the official competition launch.

3.14. The recovery system electronics shall not be adversely affected by any other on-board electronic devices 

during flight (from launch until landing).

3.14.1. The recovery system altimeters shall be physically located in a separate compartment within 

the vehicle from any other radio frequency transmitting device and/or magnetic wave producing 

device.

3.14.2. The recovery system electronics shall be shielded from all onboard transmitting devices to avoid 

inadvertent excitation of the recovery system electronics.
2024 Student Launch Handbook & Request for Proposal 59Middle/High School General and Proposal Requirements

3.14.3. The recovery system electronics shall be shielded from all onboard devices which may generate 

magnetic waves (such as generators, solenoid valves, and Tesla coils) to avoid inadvertent 

excitation of the recovery system.

3.14.4. The recovery system electronics shall be shielded from any other onboard devices which may 

adversely affect the proper operation of the recovery system electronics.

4. Payload Experiment Requirements 

All payload designs shall be approved by NASA. NASA reserves the authority to require a team to modify or 

change a payload, as deemed necessary by the Review Panel, even after a proposal has been awarded.

4.1. High School/Middle School Division— Teams may design their own science or engineering experiment 

or may choose to complete the College/University Division mission stated below. Data from the science 

or engineering experiment will be collected, analyzed, and reported by the team following the scientific 

method.

4.2. USLI Payload Mission Objective: College/University Division— Teams shall design a STEMnauts 

Atmosphere Independent Lander (SAIL). SAIL is an in-air deployable payload capable of safely retaining 

and recovering a group of 4 STEMnauts in a unique predetermined orientation without the use of a 

parachute or streamer. The landing shall occur under acceptable descent and landing parametersfor the 

safe recovery of human beings. A STEMnaut shall be defined as a non-living crew member, to be physically 

represented as the team chooses, and is assumed to have human astronaut survivability metrics. The 

method(s)/design(s) utilized to complete the payload mission shall be at the team’s discretion and will be 

permitted so long as the designs are deemed safe, obey FAA and legal requirements, and adhere to the 

intent of the challenge. NASA reserves the right to require modifications to a proposed payload.

4.3. SAIL Mission Requirements

4.3.1. Teams shall not use parachutes or streamers that are commercially available or custom made. A 

parachute is defined as an open-faced canopy whose primary function is to reduce descent speed 

or increase drag. A streamer is defined as a long, narrow strip of material (typically affixed at one 

end) whose primary function is to reduce descent speed or increase drag.

4.3.2. The SAIL shall be a minimum of 5 lbs inclusive of the jettisoned or separated landing capsule and 

the 4 STEMnauts.

4.3.3. Deployment of the SAIL shall occur between 400 and 800 feet AGL. See requirement 4.3.3 for 

deployment/jettison of payloads.

4.3.4.1 Chemical energetics will not be permitted below 500 feet AGL.

4.3.4. The team shall pre-determine and land in a unique landing orientation to be verified by NASA 

personnel in Huntsville or by a non-affiliated NAR/TRA rep for at-home launches.

4.3.5. Teams shall design and implement a method of retention and ingress/egress for the STEMnauts.

4.3.6. Teams shall determine acceptable descent and landing parameters, to be approved by NASA, and 

and design their lander to meet those requirements.

4.3.7.1. Teams may, at their discretion, measure and verify the descent and landing parameters.

4.3.7.2. Teams shall at a minimum demonstrate and verify safe landing parameters as part of the 

Payload Demonstration Flight. 

An additional experiment (limit of 1) is allowed, and may be flown, but will not contribute to scoring.If the team 

chooses to fly an additional experiment, they will provide the appropriate documentation in all design reports so the 

experiment may be reviewed for flight safety.

4.4. General Payload Requirements

4.4.1. Black Powder and/or similar energetics are only permitted for deployment of in-flight recovery 

systems. Energetics will not be permitted for any surface operations.

4.4.2. Teams shall abide by all FAA and NAR rules and regulations.
2024 Student Launch Handbook & Request for Proposal 60Middle/High School General and Proposal Requirements

4.4.3. Any secondary payload experiment element that is jettisoned during the recovery phase shall 

receive real-time RSO permission prior to initiating the jettison event, unless exempted from the 

requirement the CDR milestone by NASA.

4.4.4. Unmanned aircraft system (UAS) payloads, if designed to be deployed during descent, shall be 

tethered to the vehicle with a remotely controlled release mechanism until the RSO has given 

permission to release the UAS.

4.4.5. Teams flying UASs shall abide by all applicable FAA regulations, including the FAA’s Special Rule 

for Model Aircraft (Public Law 112-95 Section 336; see https://www.faa.gov/uas/faqs).

4.4.6. Any UAS weighing more than .55 lbs. shall be registered with the FAA and the registration number 

marked on the vehicle.

5. Safety Requirements

5.1. Each team shall use a launch and safety checklist. The final checklists shall be included in the FRR report 

and used during the Launch Readiness Review (LRR) and any Launch Day operations.

5.2. Each team shall identify a student safety officer who will be responsible for all items in Section 5.3.

5.3. The role and responsibilities of the safety officer shall include, but are not limited to:

5.3.1. Monitor team activities with an emphasis on safety during:

5.3.1.1. Design of vehicle and payload

5.3.1.2. Construction of vehicle and payload components

5.3.1.3. Assembly of vehicle and payload

5.3.1.4. Ground testing of vehicle and payload

5.3.1.5. Subscale launch test(s)

5.3.1.6. Full-scale launch test(s)

5.3.1.7. Competition Launch

5.3.1.8. Recovery activities

5.3.1.9. STEM Engagement Activities

5.3.2. Implement procedures developed by the team for construction, assembly, launch, and recovery 

activities.

5.3.3. Manage and maintain current revisions of the team’s hazard analyses, failure modes analyses, 

procedures, and SDS/chemical inventory data.

5.3.4. Assist in the writing and development of the team’s hazard analyses, failure modes analyses, and 

procedures.

5.4. During test flights, teams shall abide by the rules and guidance of the local rocketry club’s RSO. The 

allowance of certain vehicle configurations and/or payloads at the NASA Student Launch does not give 

explicit or implicit authority for teams to fly those vehicle configurations and/or payloads at other club 

launches. Teams shall communicate their intentions to the local club’s President or Prefect and RSO before 

attending any NAR or TRA launch.

5.5. Teams shall abide by all rules set forth by the FAA.
2024 Student Launch Handbook & Request for Proposal 61Middle/High School General and Proposal Requirements

6. Final Flight Requirements 

Teams shall conduct the final flight in Huntsville during Launch Week (NASA Launch Complex) or at a local launch 

field (Commercial Spaceport Launch Site) by the applicable deadlines as outlined in the Timeline for NASA 

Student Launch.

6.1. NASA Launch Complex

6.1.1. Teams are not permitted to show up at the NASA Launch Complex outside of launch day without 

permission from the NASA management team.

6.1.2. Teams shall complete and pass the Launch Readiness Review conducted during Launch Week.

6.1.3. The team mentor shall be present and oversee rocket preparation and launch activities.

6.1.4. The scoring altimeter shall be presented to the NASA scoring official upon recovery.

6.1.5. Teams may launch only once. Any launch attempt resulting in the rocket exiting the launch pad, 

regardless of the success of the flight, will be considered a launch. Additional flights beyond the 

initial launch, will not be scored and will not be considered for awards.

6.2. Commercial Spaceport Launch Site

6.2.1. The launch shall occur at a NAR or TRA sanctioned and insured club launch. Exceptions may be 

approved for launch clubs who are not affiliated with NAR or TRA but provide their own insurance, 

such as the Friends of Amateur Rocketry. Approval for such exceptions shall be granted by NASA 

prior to the launch.

6.2.2. Teams shall submit their rocket and payload to the launch site Range Safety Officer (RSO) prior to 

flying the rocket. The RSO shall inspect the rocket and payload for flightworthiness and determine 

if the project is approved for flight. The local RSO shall have final authority on whether the team’s 

rocket and payload may be flown.

6.2.3. The team mentor shall be present and oversee rocket preparation and launch activities.

6.2.4. BOTH the team mentor and the Launch Control Officer shall observe the flight and report any offnominal events during ascent or recovery on the Launch Certification and Observations Report.

6.2.5. The scoring altimeter shall be presented to BOTH the team’s mentor and the Range Safety 

impartial observers and shall not be affiliated with the team, individual team members, or the 

team’s academic institution.

6.2.6. The mentor, the Range Safety Officer, and the Launch Control Officer must be three separate 

individuals who must ALL complete the applicable sections of the Launch Certification and 

Observations Report. The Launch Certification and Observations Report document will be 

provided by NASA upon completion of the FRR milestone and shall be returned to NASA by the 

team mentor upon completion of the launch.

6.2.7. The Range Safety Officer and Launch Control Officer certifying the team’s flight shall be impartial 

observers and shall not be affiliated with the team, individual team members, or theteam’s 

academic institution.

6.2.8. Teams may launch only once. Any launch attempt resulting in the rocket exiting the launch pad,

regardless of the success of the flight, will be considered a launch. Additional flights beyond the 

initial launch will not be scored and will not be considered for awards.

NASA will maintain a Frequently Asked Questions (FAQ) list on the Student Launch Web site (www.nasa.gov/ 

studentlaunch). This list will include important changes and/or clarifications to project requirements. Changes and 

clarifications appearing in the FAQ supersede what is written in this handbook. It is the team’s responsibility to check 

the FAQ and be aware of any changes to the challenge.
2024 Student Launch Handbook & Request for Proposal 62Middle/High School General and Proposal Requirements

Proposal Requirements

At a minimum, the proposing team shall identify the following in a written proposal due to NASA MSFC by the date 

specified in the project timeline.

1. General Information

a. Please visit https://www.nasa.gov/stem/studentlaunch/handbook/index.html for instructions on submitting 

your proposal.

b. A cover page that includes the name of the college/university or secondary education institution, mailing 

address, title of the project, and the date. The mailing address provided will be used if we need to mail 

anything throughout the project year to the team.

c. Name, title and contact information (including email address and phone number) for up to two adult educators 

(minimum of one required).

d. Name, title, and contact information (including email address and phone number) for the team mentor. Team 

mentor NAR or TRA certification number shall be included along with the level of certification they currently 

hold (see requirement 1.13).

e. Name and email address for the student team leader.

f. Name and email address for the student team member who will take responsibility for implementation of the 

safety plan (Safety Officer).

g. Approximate number of student participants who will be committed to the project and their proposed duties. 

Include an outline of the project organization that identifies the key managers and technical personnel.

h. Name of the NAR/TRA section(s) the team is planning to work with for purposes of mentoring, review of 

designs and documentation, and launch assistance.

i. Document the number of hours spent on the proposal. This includes time spent brainstorming, attending 

meetings, and the actual writing of the proposal.

j. List at a minimum 3 available time slots (in 1-hour increments) to meet for design review presentations with 

the NASA management panel. List all times using Central time zone. Design review presentations shall occur 

Monday – Friday between 8:00 a.m. and 5:00.p.m. Central time.

i. For example, Monday 3 p.m. – 4 p.m., Wednesday 11:30 a.m. — 12:30 p.m., Thursday 8:15 a.m. – 9:15 a.m.

k. Include a letter of administrative support that includes an agreement administration shall allow students to 

meet for presentations when needed.

2. Facilities/Equipment

a. Description of facilities and hours of accessibility, necessary personnel, equipment, and supplies that are 

required to design and build the rocket and payload(s). Specify what is on hand and what will need to be 

acquired.

3. Safety

The Federal Aviation Administration (FAA) [www.faa.gov] has specific laws governing the use of airspace. A 

demonstration of the understanding and intent to abide by the applicable federal laws (especially as related to the 

use of airspace at the launch sites and the use of combustible/flammable material), safety codes, guidelines, and 

procedures for building, testing, and flying large model rockets is crucial. The procedures and safety regulations of 

the NAR [www.nar.org/safety-information/] shall be used for flight design and operations. The NAR/TRA mentor and 

Safety Officer shall oversee launch operations and motor handling.

a. Provide a written safety plan addressing the safety of the materials used, facilities involved, and student 

responsible, i.e., Safety Officer, for ensuring that the plan is followed. A risk assessment should be done for all 

these aspects in addition to proposed mitigations. Identification of risks to the successful completion of the 

project should be included.
2024 Student Launch Handbook & Request for Proposal 63Middle/High School General and Proposal Requirements

b. Provide a description of the procedures for NAR/TRA personnel to perform. Ensure the following:

i. Compliance with NAR High Power Safety Code requirements [http://www.nar.org/safety-information/highpower-rocket-safety-code/].

ii. Performance of all hazardous materials handling and hazardous operations.

c. Describe the plan for briefing students on hazard recognition and accident avoidance as well as for conducting 

pre-launch briefings.

d. Describe methods to include necessary caution statements in plans, procedures, and other working 

documents, including the use of proper Personal Protective Equipment (PPE).

e. Each team shall provide a plan for complying with federal, state, and local laws regarding unmanned rocket 

launches and motor handling. Specifically, regarding the use of airspace, Federal Aviation Regulations 14 CFR, 

Subchapter F, Part 101, Subpart C; Amateur Rockets, Code of Federal Regulation 27 Part 55: Commerce in 

Explosives; and fire prevention, NFPA 1127 “Code for High Power Rocket Motors.”

f. Provide a plan for NAR/TRA mentor purchase, storage, transportation, and use of rocket motors and energetic 

devices.

g. Include a written statement that all team members understand and will abide by the following safety 

regulations:

i. Range safety inspections will be conducted on each rocket before it is flown. Each team shall comply with 

the determination of the safety inspection or may be removed from the program.

ii. The Range Safety Officer has the final say on all rocket safety issues. Therefore, the Range Safety Officer 

has the right to deny the launch of any rocket for safety reasons.

iii. The team mentor is ultimately responsible for the safe flight and recovery of the team’s rocket. Therefore, a 

team shall not fly a rocket until the mentor has reviewed the design, examined the build and is satisfied the 

rocket meets established amateur rocketry design and safety guidelines.

iv. Any team that does not comply with the safety requirements shall not be allowed to launch their rocket.

4. Technical Design

a. A proposed and detailed approach to rocket and payload design.

i. Include general vehicle dimensions, preliminary material selection and justification, and construction 

methods.

ii. Include projected altitude and describe how it was calculated.

iii. Include planned recovery system design.

iv. Include projected motor brand and designation.

v. Include detailed description of the team’s projected payload.

vi. Address the General, Vehicle, Recovery, Payload, and Safety requirements outlined on pages 53 – 60 of this 

handbook.

vii. Identify major technical challenges and solutions.

5. STEM Engagement

a. Include plans and evaluation criteria for required STEM engagement activities. (See project requirement 1.4 on 

page 53.)
2024 Student Launch Handbook & Request for Proposal 64Middle/High School General and Proposal Requirements

6. Project Plan

a. Provide a detailed development schedule/timeline or work breakdown structure (WBS) covering all aspects 

necessary to complete the project successfully.

b. Provide a detailed budget to cover all aspects necessary to complete the project successfully, including 

team travel to the launch.

c. Provide a detailed funding plan.

d. Develop a clear plan for sustainability of the rocket project in the local area. This plan should include how 

to provide and maintain established partnerships and regularly engage successive classes of students 

in rocketry. It should also include partners (industry/community), recruitment of team members, funding, 

sustainability, and STEM engagement activities.

Project Deliverables

a. A reusable rocket with required payload system ready for official launch.

b. A scale model of the rocket design shall be flown during the PDR or CDR milestones and the altimeter 

flight profile data or a quality video encompassing the entire liftoff and flight, and quality pictures of the 

landed configuration of the launch vehicle shall be reported in the CDR.

c. A full-scale Vehicle Demonstration Flight and Payload Demonstration Flight shall be flown and raw 

altimeter flight data file in csv or xlsx along with the flight profile graph, and quality pictures of the landed 

configuration of the launch vehicle shall be reported in the FRR and/or FRR Addendum. 

d. A team social media presence established and maintained/updated throughout the project year.

e. Reports, PDF slideshows, and Milestone Review Flysheets completed and submitted to the Student 

Launch Projects management team by due dates.

f. Electronic copies of the STEM Engagement form(s) submitted after proposal acceptance and prior to FRR 

addendum.

g. Successful completion of PDR, CDR, FRR, FRR addendum (if applicable), LRR, and PLAR.
2024 Student Launch Handbook & Request for Proposal 65Middle/High School General and Proposal Requirements

2024 Student Launch Handbook & Request for Proposal

Timeline for Middle/High School Division

65

Project Milestones: 

Criteria & Expectations
2024 Student Launch Handbook & Request for Proposal 66Middle/High School Project Milestones: Criteria and Expectations

Preliminary Design Review (PDR)

The PDR demonstrates that the overall preliminary design meets all requirements with acceptable risk, within the 

cost, schedule, and technical performance constraints, and establishes the basis for proceeding with detailed 

design. It shows that the correct design options have been selected, and interfaces have been identified. Full 

baseline cost and schedules, as well as all risk assessment, management systems, and metrics, are presented.

The panel will be expecting a professional and polished report that follows the order of sections as they appear 

below.

Preliminary Design Review Report

Page Limit: PDR reports are to be no longer than 250 pages in length (not including title page).

Any additional content will not be considered while reviewing.

I. Summary of PDR report (1 page maximum)

Team Summary

• Team name and mailing address

• Name of mentor, NAR/TRA number and certification level, and contact information

• Indication of plans to launch in Huntsville during launch week or at home during the launch window of April 

1st–April 30th

• Document the number of hours spent working on the PDR milestone

• Team social media presence established. Include a table listing all social media handles.

Launch Vehicle Summary

• Official target altitude (ft.)

• Preliminary motor choice(s)

• Size and mass of individual sections

• Recovery system

Payload Summary

• Payload title

• Summarize payload experiment

II. Changes made since Proposal (1 – 2 pages maximum)

Highlight all changes made since the proposal and the reason for those changes.

• Changes made to vehicle criteria

• Changes made to payload criteria

• Changes made to project plan

III. Vehicle Criteria

Selection, Design, and Rationale of Launch Vehicle

• Include unique mission statement and mission success criteria.

• Review the design at a system level, going through each system’s alternative designs, and evaluating the pros 

and cons of each alternative.

• For each alternative, present research on why that alternative should or should not be chosen.

• For each alternative, conduct a feasibility study.

• For each alternative, locate points of separation on each design and show location(s) of energetic materials
2024 Student Launch Handbook & Request for Proposal 67Middle/High School Project Milestones: Criteria and Expectations

• After evaluating all alternatives, present a vehicle design with the current leading alternatives, and explain why 

they are the leading choices.

– Describe each subsystem and the components within those subsystems.

– Provide detailed dimensional drawings using the leading design.

– Provide estimated masses for each subsystem.

– Provide sufficient justification for design selections.

• Review different motor alternatives and present data on each alternative.

Recovery Subsystem

• Review the design at a component level, going through each components’ alternative designs, and evaluating 

the pros and cons of each alternative.

• For each alternative, present research on why that alternative should or should not be chosen.

• Using the estimated mass of the launch vehicle, perform a preliminary analysis on parachute sizing, and 

determine what size is required for a safe descent.

• Include drawings/sketches, wiring diagrams, and electrical schematics.

• Choose leading components amongst the alternatives, present them, and explain why they are the current 

leaders.

• Prove that redundancy exists within the system.

Mission Performance Predictions

• Declare the team’s official competition launch target altitude (ft.).

• Show flight profile simulations. This includes altitude, velocity, and acceleration versus time predictions with 

simulated vehicle data, component weights, and simulated motor thrust curve. Verify that the vehicle is robust 

enough to withstand the expected loads.

• Show stability margin and simulated Center of Pressure (CP)/Center of Gravity (CG) relationship and locations.

• Calculate the kinetic energy at landing for each independent and tethered section of the launch vehicle.

• Calculate the expected descent time for the rocket and any section that descends untethered from the rest of 

the vehicle.

• Calculate the drift for each independent section of the launch vehicle from the launch pad for five different 

cases: no wind, 5-mph wind, 10-mph wind, 15-mph wind, and 20-mph wind. The drift calculations should be 

performed with the assumption that apogee is reached directly above the launch pad.

• Present data from a different calculation method to verify that original results are accurate.

• Discuss any differences between the different calculations.

• Perform multiple simulations to verify that results are precise.

IV. Payload Criteria

Selection, Design, and Rationale of Payload

• Describe what the objective of the payload is and what experiment it will perform. What results will qualify as a 

successful experiment?

• Review the design at a system level, going through each system’s alternative designs, and evaluating the pros 

and cons of each alternative.

• For each alternative, present research on why that alternative should or should not be chosen.

• For each alternative, conduct a feasibility study.

• After evaluating all alternatives, present a payload design with the current leading alternatives and explain why 

they are the leading choices.

• Include drawings and electrical schematics for all elements of the preliminary payload. List estimated masses 

for components.

• Describe the justification used when making design selections.
2024 Student Launch Handbook & Request for Proposal 68Middle/High School Project Milestones: Criteria and Expectations

• Describe the preliminary interfaces between the payload and launch vehicle.

• Describe the preliminary design of the payload retention system.

V. Safety

• Demonstrate an understanding of all components needed to complete the project and how risks/delays impact 

the project.

• Provide a preliminary Personnel Hazard Analysis. The focus of the Hazard Analysis at PDR is identification 

of hazards, their causes, and the resulting effects. Preliminary mitigations and controls can be identified, but 

do not need to be implemented at this point unless they are specific to the construction and launching of the 

subscale rocket or are hazards to the success of the SL program (i.e., cost, schedule, personnel availability). 

Rank the risk of each hazard for both likelihood and severity.

• Include data indicating that the hazards have been researched (especially personnel). Examples: NAR 

regulations, operator’s manuals, SDS, etc.

• Provide preliminary Failure Modes and Effects Analysis (FMEA) of the proposed design of the rocket, 

payload, payload integration, launch support equipment, and launch operations. Again, the focus for PDR 

is identification of hazards, causes, effects, and proposed mitigations. Rank the risk of each hazard for both 

likelihood and severity.

• Discuss any environmental concerns using the same format as the Personnel Hazard Analysis and FMEA.

– This should include how the vehicle affects the environment and how the environment can affectthe vehicle.

• Define the risks (time, resource, budget, scope/functionality, etc.) associated with the project. Assign a 

likelihood and impact value to each risk. Keep this part simple (i.e., low, medium, high likelihood, and low, 

medium, high impact). Develop mitigation techniques for each risk. Start with the risks with higher likelihood 

and impact, and work down from there. If possible, quantify the mitigation and impact. For example, including 

extra hardware to increase safety will have a quantifiable impact on budget. Including this information in a 

table is highly encouraged.

VI. Project Plan

Requirements Verification

• Create team derived requirements in the following categories: Vehicle, Recovery, and Payload. These are 

requirements for mission success that are beyond the minimum success requirements presented in this 

handbook. Demonstrate that the requirements are not arbitrary and are required for the team’s unique project.

Budgeting and Timeline

• Provide a line item budget for all aspects of the project with market values for individual components, material 

vendors, and applicable taxes or shipping/handling fees.

• Provide a funding plan describing sources of funding, allocation of funds, and material acquisition plan.

• Provide a timeline including all team activities and expected activity durations. The schedule should be 

complete and encompass the full term of the project. Deliverables should be defined with reasonable activity 

duration. GANTT or milestones charts are encouraged.
2024 Student Launch Handbook & Request for Proposal 69Middle/High School Project Milestones: Criteria and Expectations

Preliminary Design Review Presentation

Please include the following in your presentation:

• Vehicle dimensions and justification

• Vehicle materials and justification

• Static stability margin and CP/CG locations

• Visually show points of separation along with location of energetic materials and all recovery components clearly 

labeled.

• Preliminary motor selection and justification

• Thrust-to-weight ratio and rail exit velocity

• Discussion of alternative designs and why each should or should not be chosen

• Drawing/discussion of each major component and subsystem, especially the recovery subsystem

• Discussion of current Mission Performance Predictions

• Preliminary payload design

• Preliminary payload retention system design

• Requirements compliance plan

The PDR will be presented to a panel that may be comprised of scientists, engineers, safety experts, education 

specialists and industry partners. The purpose of this review is to convince the NASA Review Panel that the 

preliminary design will meet all requirements, has a high probability of meeting the mission objectives, and can be 

safely constructed, tested, launched, and recovered. Upon successful completion of the PDR, the team is given the 

authority to proceed into the final design phase of the life cycle that will culminate in the Critical Design Review.

It is expected that the team participants deliver the report and answer all questions. The mentor or faculty advisor 

shall not participate in the presentation. 

The presentation of the PDR shall be well prepared with an overall professional appearance. This includes, but is not 

limited to, the following: easy-to-read slides; appropriate placement of pictures, graphs, and videos; professional 

appearance of the presenters; speaking clearly and loudly; looking into the camera; referring to the slides rather than 

reading them; and communicating to the panel in an appropriate and professional manner. The slides should use 

dark text on a light background.
2024 Student Launch Handbook & Request for Proposal 70Middle/High School Project Milestones: Criteria and Expectations

Critical Design Review (CDR)

The CDR establishes that the maturity of the design is appropriate to support proceeding to full-scale fabrication, 

assembly, and integration. It demonstrates that the technical effort is on track to complete the flight and ground 

system development and mission operations in order to meet overall performance requirements within the identified 

cost schedule, and technical performance constraints. Progress against management plans, budget, and schedule, 

as well as risk assessment, are presented. The CDR is a review of the final design of the launch vehicle and payload 

system.

All analyses should be complete, and some critical testing should be complete. The CDR Report and Presentation 

should be independent of the PDR Report and Presentation. However, the CDR Report and Presentation may have 

the same basic content and structure as the PDR documents, but with final design information that may or may 

not have changed since PDR. Although there should be discussion of subscale models, the CDR documents are to 

primarily discuss the final design of the full-scale launch vehicle and subsystems.

The panel expects a professional and polished report that follows the order of sections as they appear below. 

Critical Design Review Report

Page Limit: CDR reports are to be no longer than 250 pages in length (not including title page).

Any additional content will not be considered while reviewing.

I. Summary of CDR report (1 page maximum)

Team Summary

• Team name and mailing address

• Name of mentor, NAR/TRA number and certification level, and contact information

• If planning to conduct the final competition launch at home, teams shall provide anticipated primary and 

backup launch locations and dates.

• Document the number of hours spent working on the CDR milestone.

Launch Vehicle Summary

• Target altitude (ft.)

• Final motor choice

• Size and mass of individual sections

• Dry mass of launch vehicle without ballast

• Dry mass of launch vehicle with ballast (if applicable)

• Wet mass of launch vehicle

• Burnout mass of launch vehicle

• Landing mass of launch vehicle

• Recovery system

• Rail size

Payload Summary

• Payload title

• Summarize payload experiment

II. Changes made since PDR (1–2 pages maximum)

Highlight all changes made since PDR and the reason for those changes.

• Changes made to vehicle criteria

• Changes made to payload criteria

• Changes made to project plan
2024 Student Launch Handbook & Request for Proposal 71Middle/High School Project Milestones: Criteria and Expectations

III. Vehicle Criteria

Design and Verification of Launch Vehicle

Flight Reliability and Confidence

• Include unique mission statement and mission success criteria

• Identify which of the design alternatives from PDR were chosen as the final components for the launch vehicle. 

Describe why those alternatives are the best choices.

• Using the final designs, create dimensional and computer-aided design (CAD) drawings to illustrate the final 

launch vehicle, its subsystems, and its components.

• Using the final designs, create dimensional cross sectional views of each airframe and coupler component.

• Using the final designs, locate points of separation and show location(s) of energetic materials.

• Demonstrate that the designs are complete and ready to manufacture.

• Discuss the integrity of design.

– Suitability of shape and fin style for mission

– Proper use of materials in fins, bulkheads, and structural elements

– Sufficient motor mounting and retention

– Estimate the final mass of the launch vehicle as well as the individual subsystems

• Provide justification for material selection, dimensioning, component placement, and other unique design 

aspects.

Subscale Flight Results

• At least one data gathering device shall be onboard the launch vehicle during the test launch. At a minimum, 

this device shall record the apogee of the rocket. If the device can record more than apogee, please include 

the actual flight data in the report.

• Altimeter flight profile graph(s) OR a quality video showing successful launch, recovery events, and landing as 

deemed by the NASA management panel are acceptable methods of proof. Altimeter flight profile graph(s) that 

are not complete (liftoff through landing) will not be accepted.

• Quality pictures of the as landed configuration of all sections of the launch vehicle. This includes but is not 

limited to nosecone, recovery system, airframe, and booster.

• Describe the scaling factors used when scaling the rocket. What variables were kept constant and why? What 

variables do not need to be constant and why?

• Describe launch day conditions and perform a simulation using those conditions.

• Perform an analysis of the subscale flight.

– Compare the predicted flight model to the actual flight data. Discuss the results.

– Discuss any error between actual and predicted flight data.

– Estimate the drag coefficient of the full-scale rocket with subscale data.

• Discuss how the subscale flight data has impacted the design of the full-scale launch vehicle.

Recovery Subsystem

• Identify which of the design alternatives from PDR were chosen as the final components for the recovery 

subsystem. Describe why those alternatives are the best choices.

• Include a Concept of Operations (CONOPS) of your recovery system.

• Describe the parachutes, harnesses, bulkheads, and attachment hardware.

• Discuss the electrical components and prove that redundancy exists within the system.

• Include drawings/sketches, wiring diagrams, and electrical schematics.

• Provide the operating frequency of the locating tracker(s).
2024 Student Launch Handbook & Request for Proposal 72Middle/High School Project Milestones: Criteria and Expectations

Mission Performance Predictions (using the most up-to-date model)

• Show flight profile simulations. This includes altitude, velocity, and acceleration versus time predictions with 

simulated vehicle data, component weights, and simulated motor thrust curve. Verify that the vehicle is robust 

enough to withstand the expected loads.

• Show stability margin and simulated Center of Pressure (CP)/Center of Gravity (CG) relationship and locations.

• Calculate the kinetic energy at landing for each independent and tethered section of the launch vehicle.

• Calculate the expected descent time for the rocket and any section that descends untethered from the rest of 

the vehicle.

• Calculate the drift for each independent section of the launch vehicle from the launch pad for five different 

cases: no wind, 5-mph wind, 10-mph wind, 15-mph wind, and 20-mph wind. The drift calculations should be 

performed with the assumption that apogee is reached directly above the launch pad.

• Present data from a different calculation method to verify that the original results are accurate.

• Discuss any differences between the different calculations.

• Perform multiple simulations to verify that results are precise.

IV. Payload Criteria

Design of Payload Experiment

• Identify which of the design alternatives from PDR was chosen for the payload. Describe why that alternative 

and its components were chosen.

• Include a Concept of Operations (CONOPS) of your payload system.

• Review the design at a system level.

– Include drawings and specifications for each component of the payload, as well as the entire payload 

assembly.

– Describe how the payload components interact with each other.

– Describe how the payload integrates within the launch vehicle.

– Describe the payload retention system.

• Demonstrate that the design is complete.

• Discuss the payload electronics with special attention given to safety switches and indicators. Include the 

following:

– Drawings and schematics

– Block diagrams

– Batteries/power

– Switch and indicator wattages and locations

• Provide justification for all unique aspects of your payload (like materials, dimensions, placement, etc.)

V. Safety

Launch concerns and operation procedures

Submit a draft of final assembly and launch procedures/checklists including:

• Recovery preparation

• Payload preparation

• Electronics preparation

• Rocket preparation

• Motor preparation

• Setup on the launch pad

• Igniter installation
2024 Student Launch Handbook & Request for Proposal 73Middle/High School Project Milestones: Criteria and Expectations

• Launch procedure

• Troubleshooting

• Post-flight inspection

These procedures/checklists should include specially demarcated steps related to safety. Examples include:

• Warnings of hazards that can result from missing a step

• PPE required for a step in the procedure (identified BEFORE the step)

• Required personnel to complete a step or to witness and sign off verification of a step

Safety and Environment (Vehicle and Payload)

• Update the Personnel Hazard Analysis, the Failure Modes and Effects Analysis, and the Environmental 

Hazard Analysis to include:

– Finalized hazard descriptions, causes, and effects. These should specifically identify the mechanisms 

for the hazards, and uniquely identify them from other hazards. Ambiguity is not useful in safety work.

– A near-complete list of mitigations, addressing the hazards and/or their causes

– A preliminary list of verifications for the identified mitigations. These should include methods of verifying 

the mitigations and controls are (or will be) in place, and how they will serve to ensure the mitigation. 

These do not need to be finalized at this time, but they will be required for FRR. Example verifications 

include: test data, written procedures and checklists, design analysis, as-built configuration drawings, 

and Personal Protective Equipment.

VI) Project Plan

Testing

• Identify all tests required to prove the integrity of the design.

• For each test, present the test objective and success criteria, as well as testing variable and methodology.

• Justify why each test is necessary to validate the design of the launch vehicle and payload.

• Discuss how the results of a test can cause any necessary changes to the launch vehicle and payload.

• Present results of any completed tests.

– Describe the test plan and whether or not the test was a success.

– How do the results drive the design of the launch vehicle and/or payload?

Requirements Compliance

• Create a verification plan for every requirement from Sections 1 – 5 of the project requirements listed in 

this handbook. Identify if test, analysis, demonstration, or inspection are required to verify the requirement. 

After identification, describe the associated plan needed for verification.

• Update the ongoing list of team derived requirements in the following categories: Vehicle, Recovery, and 

Payload. These are a set of requirements for mission success that are beyond the minimum success 

requirements presented in this handbook. Create a verification plan for each team derived requirement 

identifying whether test, analysis, demonstration, or inspection is required with an associated plan.

Budgeting and Timeline

• Provide an updated line item budget for all aspects of the project with market values for individual 

components, material vendors, and applicable taxes or shipping/handling fees.

• Provide an updated funding plan describing sources of funding, allocation of funds, and material 

acquisition plan.

• Provide an updated timeline, including all team activities and expected activity durations. The schedule 

should be complete and encompass the full term of the project. Deliverables should be defined with 

reasonable activity duration. GANTT or milestone charts are encouraged.
2024 Student Launch Handbook & Request for Proposal 74Middle/High School Project Milestones: Criteria and Expectations

Critical Design Review Presentation

Please include the following information in your presentation:

• Final launch vehicle and payload dimensions

• Discuss key design features

• Visually show points of separation along with location of energetic materials and all recovery components clearly 

labeled

• Final motor choice

• Rocket flight stability in static margin diagram

• Thrust-to-weight ratio and rail exit velocity

• Mass Statement and mass margin

• Parachute sizes, recovery harness type, size, length, and descent rates

• Recovery system CONOPS

• Kinetic energy at key phases of the mission, especially landing

• Predicted drift from the launch pad with 5-, 10-, 15-, and 20-mph wind

• Test plans and procedures

• Scale model flight test data

• Tests of the staged recovery system

• Final payload design overview

• Payload integration plans

• Payload retention system

• Interfaces (internal within the launch vehicle and external to the ground)

• Status of requirements verification

The CDR will be presented to a panel that may be comprised of scientists, engineers, safety experts, education 

specialists and industry partners. The team is expected to present and defend the final design of the launch vehicle 

and payload, proving the design meets the mission objectives and requirements and can be safely constructed, 

tested, launched, and recovered. Upon successful completion of the CDR, the team is given the authority to proceed 

into the construction and verification phase of the life cycle that will culminate in a Flight Readiness Review.

It is expected that the team participants deliver the report and answer all questions. The mentor or faculty advisor 

shall not participate in the presentation. 

The presentation of the CDR shall be well prepared with an overall professional appearance. This includes, but is not 

limited to, the following: easy-to-read slides; appropriate placement of pictures, graphs, and videos; professional 

appearance of the presenters; speaking clearly and loudly; looking into the camera; referring to the slides rather than 

reading them; and communicating to the panel in an appropriate and professional manner. The slides should be 

made with dark text on a light background.
2024 Student Launch Handbook & Request for Proposal 75Middle/High School Project Milestones: Criteria and Expectations

Flight Readiness Review (FRR)

The FRR examines tests, demonstrations, analyses, and audits that determine the overall system (all subsystems 

working together) readiness for a safe and successful flight/launch and for subsequent flight operations of the asbuilt rocket and payload system. It also ensures that all flight hardware, software, personnel, and procedures are 

operationally ready.

The panel will be expecting a professional and polished report that follows the order of sections as they appear 

below.

Flight Readiness Review Report

Page Limit: FRR reports are to be no longer than 250 pages in length (not including title page).

Any additional content will not be considered while reviewing.

I. Summary of FRR report (1 page maximum)

Team Summary

• Team name and mailing address

• Declared final launch location. If flying at a local launch, identify the launch club, national affiliation, name and 

contact information of a club officer who will attend the launch, and anticipated date of launch. Provide this 

information for both the primary and back up launch plans.

• Name of mentor, NAR/TRA number and certification level, and contact information

• Document the number of hours spent working on the FRR milestone

Launch Vehicle Summary

• Size and mass of individual sections

• Dry mass of launch vehicle without ballast

• Dry mass of launch vehicle with ballast (if applicable)

• Wet mass of launch vehicle

• Burnout mass of launch vehicle

• Landing mass of launch vehicle

• Competition Launch Motor

• Target altitude (ft.)

• Recovery system

• Rail size

Payload Summary

• Payload title

• Summarize payload experiment

II. Changes made since CDR (1 – 2 pages maximum)

Highlight all changes made since CDR and the reason for those changes.

• Changes made to vehicle criteria

• Changes made to payload criteria

• Changes made to project plan
2024 Student Launch Handbook & Request for Proposal 76Middle/High School Project Milestones: Criteria and Expectations

III. Vehicle Criteria

Design and Construction of Vehicle

• Describe any changes in the launch vehicle design from CDR and explain why those changes are necessary.

• Discuss final locations of separation along with where black powder or energetics will be located.

• Describe features that will enable the vehicle to be launched and recovered safely.

• Structural elements (such as airframe, fins, bulkheads, attachment hardware, etc.)

• Electrical elements (wiring, switches, battery retention, retention of avionics boards, etc.)

• Discuss flight reliability confidence. Demonstrate that the design can meet mission success criteria.

• Prove that the vehicle is fully constructed and fully document the construction process.

• Include schematics of the AS-BUILT rocket. There is a good chance dimensions have changed slightly due to 

the construction process.

• Discuss how and why the constructed rocket differs from earlier models.

Recovery Subsystem

• Describe and defend the robustness of the as-built and as-tested recovery system.

– Structural elements (such as bulkheads, harnesses, attachment hardware, etc.)

– Electrical elements (such as altimeters/computers, switches, connectors)

– Redundancy features

– As-built parachute sizes and descent rates

– Drawings, diagrams and schematics of the as-built electrical and structural assemblies

– Rocket-locating transmitters with a discussion of frequency, wattage, and range

• Discuss the sensitivity of the recovery system to onboard devices that generate electromagnetic fields (such as 

transmitters). This topic should also be included in the Safety and Failure Analysis section.

Mission Performance Predictions

• Show flight profile simulations. This includes altitude, velocity, and acceleration versus time predictions with 

simulated vehicle data, component weights, and simulated motor thrust curve. Verify that the vehicle is robust 

enough to withstand the expected loads.

• Show stability margin and as-built Center of Pressure (CP)/Center of Gravity (CG) relationship and locations.

• Calculate the kinetic energy at landing for each independent and tethered section of the launch vehicle.

• Calculate the expected descent time for the rocket and any section that descends untethered from the rest of 

the vehicle.

• Calculate the drift for each independent section of the launch vehicle from the launch pad for five different 

cases: no wind, 5-mph wind, 10-mph wind, 15-mph wind, and 20-mph wind. The drift calculations should be 

performed with the assumption that apogee is reached directly above the launch pad.

• Present data from a different calculation method to verify that original results are accurate.

• Discuss any differences between the different calculations.

• Perform multiple simulations to verify that results are precise.

IV. Payload Criteria

Payload Design and Testing

• Describe any changes in the payload design from CDR and explain why those changes are necessary.

• Describe unique features of the payload. Include the following:

– Structural elements

– Electrical elements

• Discuss flight reliability confidence. Demonstrate that the design can meet mission success criteria.
2024 Student Launch Handbook & Request for Proposal 77Middle/High School Project Milestones: Criteria and Expectations

• Prove that the payload is fully constructed and fully document the construction process.

• Include schematics of the AS-BUILT payload. There is a good chance dimensions have changed slightly due to 

the construction process.

• Discuss how and why the constructed payload differs from earlier models.

• Discuss the planned or completed Payload Demonstration Flight. Include the following:

– Date of flight or planned future flight

– Success criteria

– Results of flight

– Analysis of payload retention system performance (if applicable)

V. Demonstration Flights

Provide for all flights:

• Identify whether the flight was conducted to fulfill the requirements for the Vehicle Demonstration Flight, 

Payload Demonstration Flight, or both.

• Date of flight

• Location of flight

• Launch conditions

• Motor flown (brand and designation)

• Ballast flown (lbs.)

• Final payload flown (Y/N)

• Air brake system status during test flight (if design incorporates airbrakes)

• Official target altitude (ft.)

• Predicted altitude from simulations (ft.)

• Measured altitude (ft.)

• Altimeter flight profile data output with accompanying altitude and velocity versus time plots is required to 

meet this requirement. Altimeter flight profile graph(s) that are not complete (liftoff through landing) shall not be 

accepted.

• Raw altimeter data in csv or xlsx format (subscale flight is exempt from this requirement).

• Quality pictures of the as landed configuration of all sections of the launch vehicle. This includes but is not 

limited to nosecone, recovery system, airframe, and booster.

• Identify all vehicle and recovery systems that functioned as intended.

• Identify and discuss any vehicle or recovery hardware or software that failed to function as intended.

• Calculate the kinetic energy at landing for each independent and tethered section of the launch vehicle.

• If the payload was not present, describe how the payload was simulated during the flight.

• Perform an analysis of the Vehicle Demonstration Flight. Update your simulated flight model with launch day 

condition data and compare the predicted flight performance to the actual flight data. Discuss the results.

• Estimate the drag coefficient of the full-scale rocket utilizing launch data. Use this value to run a post-flight 

simulation.

• Discuss any error between actual and predicted flight data.

• Discuss the similarities and differences between the full-scale and subscale flight results.

• Identify any hardware that was damaged and required repair or replacement and discuss the plan of action.

• Discuss lessons learned from the flight.

• Identify any off-nominal events during mission execution.
2024 Student Launch Handbook & Request for Proposal 78Middle/High School Project Milestones: Criteria and Expectations

If the final, active payload was flown (i.e., the flight qualified as a Payload Demonstration Flight), also 

provide:

• Identify all retention systems that functioned as intended.

• Identify and discuss any retention hardware or software that failed to function as intended.

• Identify any retention hardware that was damaged and required repair or replacement and discuss the plan of 

action.

• Discuss retention system lessons learned from the flight.

• Summarize the designed payload mission sequence, from activation or deployment through mission 

completion.

• Identify all payload systems that functioned as intended.

• Identify and discuss any payload hardware or software that failed to function as intended.

• Identify any payload hardware that was damaged and required repair or replacement and discuss the plan of 

action.

• Discuss payload lessons learned from the flight.

Provide a list of any planned future demonstration flights. Include a summary of the team’s objectives for 

each launch.

VI. Safety and Procedures

Safety and Environment (Vehicle and Payload)

• Update the Personnel Hazard Analysis, the Failure Modes and Effects Analysis, and the Environmental Hazard 

Analysis to include:

– Finalized hazard descriptions, causes, and effects for the rocket and payload the team has built.

Note: These sections can change from CDR to FRR if there are design related changes made as a result 

of subscale and full-scale test flights, and refined modeling and analysis. These should specify the 

mechanisms for the hazards and uniquely identify them from other hazards. Ambiguity is not useful 

in safety work.

– A completed list of mitigations addressing the hazards and/or their causes.

– A completed list of verifications for the identified mitigations. This should include methods of verifying the 

mitigations and controls are (or will be) in place, and how they will serve to ensure the mitigation.

• Be sure to discuss any concerns that remain as the project moves into the operational phase of the lifecycle. 

Emphasize concerns related to your procedures as well as the environment.

Launch Operations Procedures

Provide detailed procedures and checklists for each of the following (at a minimum):

• Recovery preparation

• Payload preparation

• Electronics preparation

• Rocket preparation

• Motor preparation

• Setup on launch pad

• Igniter installation

• Launch procedure

• Troubleshooting

• Post-flight inspection

These procedures and checklists should include specially demarcated steps related to safety. Examples include:

• Warnings of hazards that can result from missing a step
2024 Student Launch Handbook & Request for Proposal 79Middle/High School Project Milestones: Criteria and Expectations

• PPE required for a step in the procedure (identified BEFORE the step)

• Required personnel to complete a step or to witness and sign off verification of a step

VII. Project Plan

Testing

• Prove that all testing is complete and provide test methodology and discussion of results.

• Discuss whether each test was successful or not.

• Discuss lessons learned from the tests conducted.

• Discuss any differences between predicted and actual results of the tests conducted.

Requirements Compliance

• Review and update the verification plan. Describe how each handbook requirement was verified using testing, 

analysis, demonstration, or inspection.

• Review and update the team derived requirements for the vehicle, recovery system, and payload. Describe 

how each team derived requirement was verified using testing, analysis, demonstration, or inspection.

Budgeting and Funding Summary

• Provide an updated line item budget with market values for individual components, material vendors, and 

applicable taxes or shipping/handling fees.

• Provide an updated funding plan describing sources of funding, allocation of funds, and a material acquisition 

plan for any items that have not yet been obtained.
2024 Student Launch Handbook & Request for Proposal 80Middle/High School Project Milestones: Criteria and Expectations

Flight Readiness Review Presentation

Please include the following information in your presentation:

• Launch vehicle design and dimensions

• Visually show points of separation along with location of energetic materials and all recovery components clearly 

labeled

• Discuss key design features of the launch vehicle

• Motor description

• Rocket flight stability in static margin diagram

• Launch thrust-to-weight ratio and rail exit velocity

• Mass statement

• Parachute sizes and descent rates

• Kinetic energy at key phases of the mission, especially at landing

• Predicted altitude of the launch vehicle with a 5-, 10-, 15-, and 20-mph wind

• Predicted drift from the launch pad with a 5-, 10-, 15-, and 20-mph wind

• Test plans and procedures

• Vehicle Demonstration Flight results. Present and discuss the actual flight test data, as well as any issues or 

failures encountered.

• Recovery system tests

• Summary of requirements verification (launch vehicle)

• Payload design and dimensions

• Key design features of the payload

• Payload integration into the vehicle

• Payload retention system design

• Payload Demonstration Flight plans. If complete, discuss the actual flight test results, as well as any issues or 

failures encountered.

• Summary of requirements verification (payload)

• Interfaces with ground systems (vehicle and payload)

The FRR will be presented to a panel that may be comprised of scientists, engineers, safety experts, education 

specialists, and industry partners. The team is expected to present and defend the as-built launch vehicle and 

payload, showing that the launch vehicle and payload meet all requirements and mission objectives and that the 

design can be safely launched and recovered. Upon successful completion of the FRR, the team is given the 

authority to proceed into the Launch and Operational phases of the life cycle.

It is expected that the team participants deliver the report and answer all questions. The mentor or faculty advisor 

shall not participate in the presentation.

The presentation of the FRR shall be well prepared with an overall professional appearance. This includes, but is not 

limited to, the following: easy-to-read slides; appropriate placement of pictures, graphs, and videos; professional 

appearance of the presenters; speaking clearly and loudly; looking into the camera; referring to the slides, not 

reading them; and communicating to the panel in an appropriate and professional manner. The slides should be 

made with dark text on a light background.
2024 Student Launch Handbook & Request for Proposal 81Middle/High School Project Milestones: Criteria and Expectations

Flight Readiness Review Addendum

The FRR Addendum is a required submission for any team completing a Payload Demonstration Flight or NASArequired Vehicle Demonstration Re-flight after the submission of the FRR Report. It is expected to be a brief but 

informative document highlighting the success or failure of the new flight(s) and any updates or changes to the 

vehicle or payload design. The information reported in the FRR Addendum will be reviewed by NASA to determine 

eligibility of each team to perform their competition launch. 

Flight Readiness Review Addendum Document Outline

Page Limit: The FRR Addendum is not scored and does not have a specific minimum or maximum page 

count, but each requested item listed below shall be sufficiently addressed.

I. Summary of FRR Addendum

Team Summary

• Team name, mailing address, and contact information

• Document the number of hours spent working on the FRR addendum milestone

Purpose of Flight(s)

• Identify whether the flight(s) conducted were conducted to fulfill the requirements for the Payload 

Demonstration Flight, Vehicle Demonstration Re-flight, or both.

Flight Summary Information (for each flight)

• Date of flight

• Location of flight

• Launch conditions

• Motor flown (brand and designation)

• Ballast flown (lbs.)

• Final payload flown (Y/N)

• Air brake system status during test flight (list N/A if your vehicle does not contain an air brake system)

• Official target altitude (ft.)

• Predicted altitude from simulations (ft.)

• Measured altitude (ft.)

• Identify any off-nominal events during mission execution

Changes made since FRR

• Describe changes made to the vehicle design and explain why those changes are necessary.

• Describe changes made to the payload design and explain why those changes are necessary.

II. Payload Demonstration Flight Results (if applicable) 

Summarize the retention system and mission of the payload, along with discussing its successes and 

failures.

• Summarize the designed payload mission sequence, from activation or deployment through mission 

completion

• Summarize the design of the payload retention system

• Provide altimeter flight profile data

• Identify all systems that functioned as intended

• Identify and discuss any hardware or software that failed to function as intended

• Identify any hardware that was damaged and required repair or replacement and discuss the plan of action

• Discuss payload lessons learned from the flight
2024 Student Launch Handbook & Request for Proposal 82Middle/High School Project Milestones: Criteria and Expectations

III. Vehicle Demonstration Re-flight (if applicable)

Summarize the flight of the rocket and discuss its successes and failures.

• Identify all systems that functioned as intended. 

• Identify and discuss any hardware or software that failed to function as intended. 

• If the payload was not present, describe how the payload was simulated during the flight. 

• Altimeter flight profile data output with accompanying altitude and velocity versus time plots. Altimeter flight 

profile graph(s) that are not complete (liftoff through landing) shall not be accepted. 

• Include quality pictures of the as landed configuration of all sections of the launch vehicle. This includes but is 

not limited to nosecone, recovery system, airframe, and booster. 

• Calculate the kinetic energy at landing for each independent and tethered section of the launch vehicle. 

• Perform an analysis of the Vehicle Demonstration Flight. Update your simulated flight model with launch day 

condition data and compare the predicted flight performance to the actual flight data. Discuss the results. 

• Estimate the drag coefficient of the full-scale rocket utilizing launch data. Use this value to run a post-flight 

simulation. 

• Identify any hardware that was damaged and required repair or replacement and discuss the plan of action. 

• Discuss lessons learned from the flight.

Launch Readiness Review (LRR)

The Launch Readiness Review (LRR) will be conducted by NASA and the National Association of Rocketry (NAR), 

our launch services provider. These inspections are only open to team members and mentors. These names 

were submitted as part of your team list. All rockets/payloads will undergo a detailed, deconstructive, hands-on 

inspection.

Your team should bring all components of the rocket and payload except for the motor, black powder, and electric 

matches. Be able to present: anchored flight predictions, anchored drift predictions (15-mph crosswind), procedures 

and checklists, and CP and CG with loaded motor marked on the airframe. The rockets will be assessed for 

structural and electrical integrity, as well as safety concerns. At a minimum, all teams shall have:

• An airframe prepared for flight with the exception of energetic materials

• Data from the previous flight(s)

• A list of any flight anomalies that occurred on the previous full-scale flight(s) and the mitigation actions

• A list of any changes to the airframe since the last flight

• Flight simulations

• Pre-flight checklist(s) and Fly Sheet

• Team name and contact info in or on the airframe and any untethered section of the vehicle

Each team will demonstrate these tasks to the NAR Review Team. The RSO has final word on whether the rocket 

and/or payload may be flown on Launch Day.

A “punch list” will be generated for each team. Items identified on the punch list must be corrected and verified by 

NAR/NASA prior to Launch Day. A flight card will be provided to teams and is to be completed and submitted at the 

LCO booth on Launch Day.
2024 Student Launch Handbook & Request for Proposal 83Middle/High School Project Milestones: Criteria and Expectations

Post-Launch Assessment Review (PLAR)

The PLAR is an assessment of system in-flight and payload mission performance from your final competition launch. 

All scientific and engineering results and findings shall be reported along with a cumulative summary of your teams’ 

experience on the project as a whole. 

Page Limit: PLAR reports are to be no longer than 25 pages in length (not including title page).

Any additional content will not be considered while reviewing.

• Team name

• Motor used

• Vehicle dimensions

• Altitude reached (ft.)

• Official target altitude (ft.)

• Competition Launch altimeter flight profile data

• Vehicle summary

• Payload summary

• Data analysis and results of the vehicle and payload

• Altimeter flight profile data output with accompanying altitude and velocity versus time plots is required to meet 

this requirement. Altimeter flight profile graph(s) that are not complete (liftoff through landing) will not be accepted

• Raw altimeter data in csv or xlsx format

• Quality pictures of the as landed configuration of all sections of the launch vehicle. This includes but is not limited 

to nosecone, recovery system, airframe, and booster

• Describe separation events and state altitude of events

• Ascent and descent analysis and metrics of the launch vehicle

• Data analysis and results of the payload. Include the gridded numbered map with the location of the launch pad 

along with what box your launch vehicle landed in

• Scientific value achieved

• Visual data observed

• Lessons learned for vehicle, payload, and overall project

• Discussion of successes and failures of individual subsystems

• Summary of overall experience (what you attempted to do versus the results; how valuable you felt the 

experience was)

• A table which totals the number of hours spent on SL broken down by the following categories: Proposal, PDR, 

CDR, FRR, FRR addendum (if applicable), PLAR, STEM Engagement, Social Media, and launch activities

• STEM Engagement summary

• Final Budget summary
2024 Student Launch Handbook & Request for Proposal 84Middle/High School General and Proposal Requirements

2024 Student Launch Handbook & Request for Proposal

Timeline for Middle/High School Division

84

STEM 

Engagement
2024 Student Launch Handbook & Request for Proposal 85Middle/High School STEM Engagement

As part of the STEM Engagement requirement for completion of the NASA Student Launch activity, teams shall 

engage a minimum of 250 participants in direct educational, hands-on science, technology, engineering and 

mathematics (STEM) activities. These activities can be conducted in-person or virtually. To satisfy this requirement:

• All events shall occur between project acceptance and the FRR due date.

• The STEM Engagement Activity Report shall be submitted via email for all events by the FRR addendum due 

date.

• A template of the STEM Engagement Activity Report can be found on pages 86 – 89.

• Teams shall engage a minimum of 250 participants in Educational Direct Engagement activities in 

orderto be eligible for STEM Engagement awards. For a definition of what constitutes an Educational—Direct 

Engagement Activity, see below. These definitions are also found in the STEM Engagement Activity Report for 

reference.

• Teams are encouraged to engage as many participants as possible in the STEM Engagement activity types listed 

below.

STEM Engagement Activity Types

• Education — Direct Engagements (minimum 250 participants required)

This type of interaction will count towards your project/STEM Engagement requirement. Instructional, hands-on 

activities where participants engage in learning a STEM related concept by actively participating in an activity. 

This includes instructor-led facilitation or inquiry around an activity regardless of media (e.g., face-to-face, video, 

conference, etc.) 

Example: Students learn to identify the occurrence of Newton’s Laws through building and flying a model rocket 

or students learn about basic rocketry through designing and launching their own rockets in simulation software.

• Education — Indirect Engagements

Participants are engaged in learning a STEM concept through instructor-led facilitation or presentation. 

Example: Students learn about the occurrence of Newton’s Laws in basic rocketry through a presentation or 

students learn about the Space Launch System (SLS) through SLS activity/materials provided on www.nasa.gov/

SLS (under SLS public Engagement.)

• Outreach — Direct Engagements

Participants do not learn a STEM concept but are able to get hands-on exposure to STEM related hardware.

Example: The team does a presentation for students about their Student Launch project, brings their rocket and 

components to the event, and demonstrates a launch of their rocket for the students.

• Outreach — Indirect Engagements

Participants interact with the team in an informal setting. 

Example: the team sets up a display at a local museum during science night. Students come by, talk to the team 

and learn about their project.

STEM Engagement Activity Reports

Each activity report submitted should represent one activity. There may be multiple events listed for the same 

activity.

• Activity reports shall be fully completed and list all the event dates and information for an activity.

• The STEM Engagement Activity Type shall be correctly identified for the activity. The NASA Review Panel reserves 

the right to change the activity type if the activity is categorized incorrectly.

• Activity descriptions should be clear and thorough.

• Learning targets should be clear and specific.

• Include with your report any documents, evaluations, surveys, questionnaires, handouts, videos or presentations , 

etc., used in your activity.
2024 Student Launch Handbook & Request for Proposal 86Middle/High School STEM Engagement

STEM Engagement Activity Report

Please complete and submit this form for each STEM Engagement activity that your team completes. If you hold 

multiple events utilizing the same activity, only one report needs to be submitted.

For numerous NASA STEM engagement ideas, educational resources, games, videos, and PowerPoint presentations 

visit https://www.nasa.gov/education/materials/. NASA educational resources can be searched and filtered by 

subject (e.g., space science, NASA history, technology, etc.) Please attach any pictures, presentations, or feedback 

documents which you would like to share to the end of the document.

Activity Title: ________________________________________________________________________________

Type of Activity:______________________________________________________________________________

For activity type, choose from one of the Types of Engagement Activities below:

• Education/Direct Engagements

 This type of interaction will count towards your project/STEM Engagement requirement.

 A count of participants in instructional, hands-on activities where participants engage in learning a STEM topic 

by actively participating in an activity. This includes instructor-led facilitation around an activity regardless of 

media (e.g., face-to-face, video conference, etc.) 

 Example: Students learn about Newton’s Laws through building and flying a rocket.

• Education/Indirect Engagements

 A count of participants engaged in learning a STEM topic through instructor- led facilitation or presentation.

 Example: Students learn about Newton’s Laws through a PowerPoint presentation, or students learn about 

the Space Launch System (SLS) through a SLS activity/materials provided on www.NASA.gov/SLS (under SLS 

Public Engagement.)

• Outreach/Direct Engagements

 A count of participants who do not necessarily learn a STEM topic but are able to get a hands-on look at 

STEM hardware.

 Example, the team does a presentation to students about their Student Launch project, brings their rocket and 

components to the event, and flies a rocket at the end of the presentation.

• Outreach/Indirect Engagements

 A count of participants that interact with the team. 

 Example: The team sets up a display at the local museum during Science Night. Students come by and talk to 

the team about their project.

Learning Target for the Activity (Describe the learning target for this activity. What did you want your participants to 

learn from this activity? Be specific.)
2024 Student Launch Handbook & Request for Proposal 87Middle/High School STEM Engagement

Describe your activity with this group. (Attach additional pages if more information is needed. Please attach any 

pictures, presentations, or documents which you would like to share to the end of the document.)
2024 Student Launch Handbook & Request for Proposal 88Middle/High School STEM Engagement

Did you conduct an evaluation of your learning target? If so, what were the results? (Please include a copy of 

your evaluation and a summary of your results.)

\

Describe any feedback received from your participants about your activity overall. (Please include any feedback 

forms or surveys that were used. Use this space or attach actual feedback from participants.)
2024 Student Launch Handbook & Request for Proposal 89Middle/High School STEM Engagement

Event Information

For each event that was held for this activity, please enter the information in the table below. Each participant for 

each event should only be counted once. If you need additional space, please attach to the document before 

submission.

Event 

Date Name of Group

Total 

Number 

of Participants

Number 

of 

Preschool 

– 4 Grade

Number 

of

5 – 9

Grade

Number 

of

10 – 12

Grade

Number

of

Undergrad

Number

of 

Educators

Number

of

Noneducators

Additional Notes/Comments:
2024 Student Launch Handbook & Request for Proposal 90Middle/High School General and Proposal Requirements

2024 Student Launch Handbook & Request for Proposal

Timeline for Middle/High School Division

90

Safety
2024 Student Launch Handbook & Request for Proposal 91Middle/High School Safety

High-Power Rocket Safety Code

Provided by the National Association of Rocketry

1. Certification. I will only fly high power rockets or possess high power rocket motors that are within the scope 

of my user certification and required licensing.

2. Materials. I will use only lightweight materials such as paper, wood, rubber, plastic, fiberglass, or when 

necessary ductile metal, for the construction of my rocket.

3. Motors. I will use only certified, commercially made rocket motors, and will not tamper with these motors or 

use them for any purposes except those recommended by the manufacturer. I will not allow smoking, open 

flames, nor heat sources within 25 feet of these motors.

4. Ignition System. I will launch my rockets with an electrical launch system, and with electrical motor igniters 

that are installed in the motor only after my rocket is at the launch pad or in a designated prepping area. My 

launch system will have a safety interlock that is in series with the launch switch that is not installed until my 

rocket is ready for launch, and will use a launch switch that returns to the “off” position when released. The 

function of onboard energetics and firing circuits will be inhibited except when my rocket is in the launching 

position.

5. Misfires. If my rocket does not launch when I press the button of my electrical launch system, I will remove 

the launcher’s safety interlock or disconnect its battery and will wait 60 seconds after the last launch attempt 

before allowing anyone to approach the rocket.

6. Launch Safety. I will use a 5-second countdown before launch. I will ensure that a means is available to warn 

participants and spectators in the event of a problem. I will ensure that no person is closer to the launch pad 

than allowed by the accompanying Minimum Distance Table. When arming onboard energetics and firing 

circuits, I will ensure that no person is at the pad except safety personnel and those required for arming 

and disarming operations. I will check the stability of my rocket before flight and will not fly it if it cannot be 

determined to be stable. When conducting a simultaneous launch of more than one high power rocket, I will 

observe the additional requirements of NFPA 1127.

7. Launcher. I will launch my rocket from a stable device that provides rigid guidance until the rocket has 

attained a speed that ensures a stable flight, and that is pointed to within 20 degrees of vertical. If the wind 

speed exceeds 5 miles per hour, I will use a launcher length that permits the rocket to attain a safe velocity 

before separation from the launcher. I will use a blast deflector to prevent the motor’s exhaust from hitting the 

ground. I will ensure that dry grass is cleared around each launch pad in accordance with the accompanying 

Minimum Distance table, and will increase this distance by a factor of 1.5 and clear that area of all combustible 

material if the rocket motor being launched uses titanium sponge in the propellant.

8. Size. My rocket will not contain any combination of motors that total more than 40,960 N-sec (9,208 poundseconds) of total impulse. My rocket will not weigh more at liftoff than one-third of the certified average thrust 

of the high power rocket motor(s) intended to be ignited at launch.

9. Flight Safety. I will not launch my rocket at targets, into clouds, near airplanes, nor on trajectories that take 

it directly over the heads of spectators or beyond the boundaries of the launch site, and will not put any 

flammable or explosive payload in my rocket. I will not launch my rockets if wind speeds exceed 20 miles per 

hour. I will comply with Federal Aviation Administration airspace regulations when flying and will ensure that 

my rocket will not exceed any applicable altitude limit in effect at that launch site.

10. Launch Site. I will launch my rocket outdoors, in an open area where trees, power lines, occupied buildings, 

and persons not involved in the launch do not present a hazard, and that is at least as large on its smallest 

dimension as one-half of the maximum altitude to which rockets are allowed to be flown at that site or 1,500 

feet, whichever is greater, or 1,000 feet for rockets with a combined total impulse of less than 160 N-sec, a 

total liftoff weight of less than 1,500 grams, and a maximum expected altitude of less than 610 meters (2000 

feet).
2024 Student Launch Handbook & Request for Proposal 92Middle/High School Safety

11. Launcher Location. My launcher will be 1,500 feet from any occupied building or from any public highway on 

which traffic flow exceeds 10 vehicles per hour, not including traffic flow related to the launch. It will also be no 

closer than the appropriate Minimum Personnel Distance from the accompanying table from any boundary of 

the launch site.

12. Recovery System. I will use a recovery system such as a parachute in my rocket so that all parts of my rocket 

return safely and undamaged and can be flown again, and I will use only flame-resistant or fireproof recovery 

system wadding in my rocket.

13. Recovery Safety. I will not attempt to recover my rocket from power lines, tall trees, or other dangerous 

places, fly it under conditions where it is likely to recover in spectator areas or outside the launch site, nor 

attempt to catch it as it approaches the ground.

Minimum Distance Table

Installed Total Impulse 

(Newton-Seconds)

Equivalent High Power 

Motor Type

Minimum Diameter of 

Cleared Area (ft.)

Minimum Personnel 

Distance (ft.)

Minimum Personnel 

Distance (Complex Rocket) 

(ft.)

0 – 320.00 H or smaller 50 100 200

320.01 – 640.00 I 50 100 200

640.01 – 1,280.00 J 50 100 200

1,280.01 – 2,560.00 K 75 200 300

2,560.01 – 5,120.00 L 100 300 500

5,120.01 – 10,240.00 M 125 500 1,000

10,240.01 – 20,480.00 N 125 1,000 1,500

20,480.01 – 40,960.00 O 125 1,500 2,000

Note: A Complex rocket is one that is multi-staged or that is propelled by two or more rocket motors

Revision as of August 2012

Provided by the National Association of Rocketry (www.nar.org)
2024 Student Launch Handbook & Request for Proposal 93Middle/High School General and Proposal Requirements

2024 Student Launch Handbook & Request for Proposal

Timeline for Middle/High School Division

93

Awards
2024 Student Launch Handbook & Request for Proposal 94Middle/High School Awards

Middle and High School Division Awards

Award Award Description Determined By When Awarded

STEM Engagement 

Award

Awarded to the team that is determined to have best inspired the study of rocketry 

and other science, technology, engineering, and math (STEM) related topics in their 

community. This team not only presented a high number of activities to a large 

number of people, but also delivered quality activities to a wide range of audiences.

NASA Panel Awards Ceremony

Social Media Award Awarded to the team that has the most active and creative social media presence 

throughout the project year. NASA Panel Awards Ceremony

Altitude Award Awarded to the team that comes closest to their declared target altitude on their 

competition launch. NASA Panel After PLAR Milestone

Best Looking Rocket 

Award* Awarded to the team that is judged by their peers to have the “Best Looking Rocket” Peers Awards Ceremony

Vehicle Design 

Award

Awarded to the team with the most creative and innovative overall vehicle design for 

their intended payload while still maximizing safety and efficiency. NASA Panel Awards Ceremony

Experiment Design 

Award

Awarded to the team with the most creative and innovative payload design while 

maximizing safety and science value. NASA Panel Awards Ceremony

Judges’ Choice 

Award

Selected during Launch Week by a panel of guest judges and awarded

for the best combination of payload innovation, vehicle design and

construction, and public engagement

VIP Panel Awards Ceremony

3D Printed Award Awarded to the team with the best consideration, design, and implementation in 

regards to 3D printing of launch vehicle and payload. NASA Panel Awards Ceremony

* Only teams traveling to NASA Launch Complex event are eligible.

Artemis Student Challenges Awards

The Artemis Student Challenges (ASC) are foundational learning opportunities for middle school through graduate 

level students, preparing them to learn and engage in Artemis-focused challenges that align with mission needs. 

ASC is comprised of eight challenges including the App Development Challenge, BIG Idea Challenge, First Nations 

Launch, Human Exploration Rover Challenge, Lunabotics, Micro-g NExT, SUITS, and Student Launch. New this year, 

the Artemis Student Challenges will select teams across all challenges to receive prestigious awards in the three 

categories below.

Pay It Forward Award

This award is given to teams that best conduct impactful educational engagement events in their community or 

further. Educational engagement includes instructional, hands-on activities where participants engage in learning a 

STEM-related concept by actively participating in an activity.

Innovation Award

This award is given to teams that best create new, innovative ideas and/or solutions within the scope of their 

respective challenge. Ingenuity, creativity, and inventiveness in either technology or nontechnology focused ideas are 

awarded for their original ideas, creating efficiency, effective results, and/or solving a problem.

Artemis Educator Award

This award is given to educators/faculty/mentors in each challenge as nominated by student team members. Student 

team members will recognize their faculty/mentor(s) who inspire learners and motivate them to work hard, achieving 

more than the team members thought possible. The award acknowledges the time and dedication educators/faculty/

mentors take to be exceptional teachers. Educators/faculty/mentors are noted for their commitment to learning and 

their valuable efforts for motivating and inspiring others. The NASA management team shall share the nomination 

process after the FRR milestone.
National Aeronautics and Space Administration

George C. Marshall Space Flight Center

Huntsville, AL 35812

www.nasa.gov/marshall

www.nasa.gov NP-2023-07-129-MSFC G–614678