| Section |
Format Required |
Additional Information |
COVER
PAGE
(Page 1) |
- title of the experiment
- topic area addressed
- team name
- team logo (optional)
- academic institution name/address
- designated student team contact name, e-mail address and phone
number
- faculty supervisor name, e-mail address and phone number
- each team member's name, role (flyer, alternate flyer, ground
crew), academic year (freshman, sophomore, junior, senior), academic
major, and e-mail address. Previous program participants should
be designated with an asterisk (*) and crew/program date listed
- Faculty advisor's / signature required at bottom
|
- team contact must be a student team member
- SAMPLE:
*MacPherson, Jennifer (macpher@hotmail.com).
Flyer / Sophomore / Electrical Engr / AUG99 (alt flyer)
- The statement at the bottom of the cover page indicates that
the team's faculty advisor endorses the proposal being submitted.
Additionally, the Faculty Advisor Statement is required in the
administrative section of the proposal.
|
TABLE OF CONTENTS
(Page 2) |
- Table of Contents should reflect the arrangement of the proposal with sections clearly noted
- pages should be numbered
|
|
FLIGHT WEEK
PREFERENCE |
- Include team's top three preferences for flight dates.
|
|
ADVISOR/
MENTOR REQUEST |
- Occasionally, teams request the services of
a JSC scientist or engineer to augment the guidance given by faculty
members and/or the Student Flight Program staff. If teams want to request
a JSC scientist or engineer as a mentor for their group, they can
do so in their proposal.
|
|
| SYNOPSIS/ABSTRACT |
- a brief (up to 300 words) summary that touches upon the elements
of the research being proposed
|
|
| TEST OBJECTIVES |
- a description of the team's objectives in conducting the experiment
proposed
- describe the aim of the experiment being flown
- mention whether or not the experiment is a follow-up to a previous experiment
- state hypothesis
|
|
| TEST DESCRIPTION |
A brief, but detailed, description of the test being proposed. It
should be written so that a practicing engineer or scientist can understand
the experiment. Goals should be presented along with a description of
the expected results.
- Expected or actual results for accompanying ground-based
experiments should also be presented here. Describe the quantitative/qualitative
data to be collected and how it will be analyzed.
- What does the team expect to learn as a result
of the experiment?
- Exactly how will the test be conducted?
- Describe the quantitative/ qualitative data to
be collected and how it will be analyzed.
- Why is a reduced gravity environment necessary
for this experiment?
|
Note on free-floating experiments:
- No more than 2 free-floating experiments will be accepted for
each flight week.
|
| JUSTIFICATION FOR FOLLOW-UP FLIGHT |
- Brief summary (less than 300 words) of any previous related
experiment flown as part of the RGSFOP which is directly related
to the experiment being proposed. (A Phase II or Part II experiment)
- Include information regarding any continuation, modification,
or expansion of the previously flown experiment and justification
for its re-flight.
- Clearly justify the need for re-flying the experiment.
- What were the previous results? What was the conclusion?
|
- Proposals for follow-up flights which do not include the justification
summary will not be considered.
|
REFERENCES/
BIBLIOGRAPHY |
Standard MLA
format |
- Referenced works should be cited in the text of the proposal
and in a "Bibliography."
- Do not include Web sites.
- References must be relevant! Prefereably one-half of references should come from research journals
- SAMPLE:
Howell, John R. Fundamentals of Engineering Thermodynamics,
McGraw-Hill, 1992.
|
| |
|
Example of how the technical portion of your proposal will be EVALUATED |
