Daniel F23 Template Concept

Owned by Daniel Puratich
2023-10-25
2 min read

Introduction

  • Prove x, y and z are functional subsystems

  • Characterize system flight characteristics

Logistics

  • John Doe

    • Role: Pilot

    • Justification: IPP license, TC license,

    • Availability: 11am to 2 pm 10/25/2023

  • Jane Doe

    • Role: Flight Test Requestor

    • Justification: requested this test and coordinating logistics in confluence and in discord thread!

    • Availability: All Day

  • who is going in what automobile

  • which human resources have cars? how many vehicles do they seat

  • are we taking the ion?

  • List possible locations for the test(s)

  • include possible weather deviations (check the weather)

  • list out times when we will be where

Procedure

  • What needs to be done (assign people by pinging them by name) if your assigned to a task, write updates here!

  • See past flight tests for good samples of what to put here!

  • What needs to be done (assign people by pinging them by name) if your assigned to a task, write updates here!

  • See past flight tests for good samples of what to put here!

  • briefing on whats gonna happen

  • What needs to be done (assign people by pinging them by name) if your assigned to a task, write updates here!

  • See past flight tests for good samples of what to put here!

  •  

  • What needs to be done (assign people by pinging them by name) if your assigned to a task, write updates here!

  • See past flight tests for good samples of what to put here!

  • what we actually want to be monitoring and doing in flight in flight

  • What needs to be done (assign people by pinging them by name) if your assigned to a task, write updates here!

  • See past flight tests for good samples of what to put here!

  • What needs to be done (assign people by pinging them by name) if your assigned to a task, write updates here!

  • See past flight tests for good samples of what to put here!

  • mostly discharge batteries and debrief

If things go poorly, flight test director should command (this is stated to avoid bystander effect):

  • Fire

    • Call 911

    • give location

  • Property Damage

    • if in e7, email Graeme

    • if at WRESTRC, email them

  • Fly away

    • call TC

  • Injury

    • first aid

    • call 911

Debrief

  • any questions that people have they can think of before the flight test occurs (i.e. flight characteristics we should be monitoring during the test) should be left here so the team can see them!

  • observations

  • links to logs

  •  

  •  

  •  

All of these major issues should be addressed via Root Cause Analysis Forms: Create a RCA

 

 

Â