Unit timeline, storyline & project files

Monday, 16 Mar

Objective: Evaluate progress towards project benchmarks; articulate strengths and needs

Agenda:

1. Welcome and overview
2. Review project benchmarks
3. Evaluate status of progress
  1. Systems: facilitate a conversation at your team
    1. identify strengths
    2. identify stuck points
    3. brainstorm ways to help around those stuck points
  2. Communications: record team's responses
4. Make a plan to address these priorities
  1. graphs and distances
  2. summary data table
  3. summary graph
  4. narrative... with technical language and reference to lift equation
  5. predictions (except for people who tests flaps)
5. For folks who need / want support making predictions by using trendlines
  1. Warm-up
    1. Consider the trendline of takeoff distance vs. temperature.
      1. By how does the takeoff distance change with temperature?
      2. For the range we tested (40 deg F to 10 deg F), our linear model seems pretty accurate; what would happen if you extended the trendline to a VERY cold temperature?
      3. Is this model still reasonable outside the range we tested?
    2. Consider the trendline of takeoff distance vs. thrust.
      1. By how does the takeoff distance change with thrust?
      2. For the range we tested (90% to 100%), our linear model seems pretty accurate; what would happen if you extended the trendline to a VERY low thrust?
      3. Is this model still reasonable outside the range we tested?
  2. Experiment with the meaning of sample mathematical models
    1. Make a copy of this sheet; save it to your 2025 - 26 > Science > Flight folder
    2. Review the linear example; experiment by changing some of the values
    3. Review the polynomial example; experiment by changing some of the values
    4. Review the exponential example; experiment by changing some of the values
  3. Attend to this presentation about finding patterns in data.
  4. Use model
    1. Articulate trend
      1. Linear: For every x change in manipulated variable, takeoff distance [increases or decreases] by yyy feet.
      2. Polynomial, exponential: Between x and xx value of manipulated variable, takeoff distance [increases or decreases] by yyy feet. Between xxx and xxxx value of manipulated variable, takeoff distance [increases or decreases] by yyy feet.
    2. Identify limitations of model: All models are wrong; some models are useful. We just identified how it's useful; how is it wrong?
      1. In real life, what would happen as you tested more and more extreme values for your manipulated variable? Would it even be possible?
    3. DELIVERABLE:
      1. Edit your data summary. Ensure that it includes (a) mathematical model and (b) trend
  5. Experiment with the meaning of YOUR mathematical model
    1. Add YOUR data to one of the tabs
    2. Add the model to your graph
    3. Experiment with different values to evaluate how well the mathematical model matches our data and our expectations, particularly at extreme values
6. Next steps and closing

Tuesday, 17 Mar

Objective: Build on strengths; address areas for growth

Agenda:

1. Welcome and overview
2. Review mathematical model for lift and complete problem set
3. Share and compare your results
4. In your data summary and analysis, refine your analysis to reflect your new understanding.
5. Next steps and closing

Plan ahead:

due block @ start of class complete Quantifying Lift problem set if you have not already done so

due Friday, 20 Mar If you have not already done so, finish refining your analysis

Wednesday, 18 Mar / Thursday, 19 Mar

Objective: research and summarize safety concerns while conducting flight test; refine oral summary and visual presentation

Agenda:

1. Welcome and overview
2. Research and summarize key safety protocols flight test teams use to ensure the safety of the crew, people on the ground, and property.
  1. Rationale: The audience of our work will be flight test pilots and flight test engineers. Safety is of paramount importance to them.
  2. Goal: Identify ways to mitigate and alleviate dangerous situations that may occur during flight test.
  3. Method:
    1. Have one person in your team make a copy of this template and save it to your team's Flight Test folder.
    2. Define terms mitigate and alleviate
    3. Divide up work
3. Make a plan with your team for remaining portions of the oral presentation and visual summary
  1. Identify your own areas of strength
  2. Identify gaps and areas where you may need help
  3. Coordinate your time and efforts
4. Work individually and with your team to make progress.
5. Next steps and closing

Plan ahead:
due Friday, 27 Mar HARD DEADLINE The completed rough draft of your flight test report due at the start of class

Friday, 20 Mar

Objective: Refine our hypotheses; compile different elements of the project into a cohesive set of documentation

Agenda:

1. Welcome & overview
2. Review responses to lift problem set
3. Review rubric for rough draft of flight test
4. Review flight test report outline
5. Documentation template
  1. Operations
    1. Make a copy of this template; save it to your flight folder
    2. Share it with your teammates
  2. Others
    1. Save a shortcut in your Flight folder
6. Refine your documentation
  1. Systems engineer & operations: identify gaps and make a plan to fill those gaps
  2. Science & communication: review explanations and offer ways to improve them
7. Work your plan
8. Next steps and closing

Plan ahead:
due Friday, 27 Mar Bring a completed first draft of your documentation @ start of class