summaryrefslogtreecommitdiff
path: root/Meeting05Nov2002.mdwn
blob: 16bb000ea47700dbc030eb135e5e6e77c466f6dd (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
## <a name="General Meeting on Tuesday Novem"></a> General Meeting on Tuesday November 05, 2002

### <a name="Proposed Schedule"></a> Proposed Schedule

Although many folks were missing from the meeting, the following schedule seemed reasonable:

<table border=1 cellpadding=0 cellspacing=0>
  <tr>
    <td> Sunday May 4, 2003 </td>
    <td> Almost T-45 days to launch. Final go/no go decision (based on a finished avionics package) before filing for a FAA waiver. </td>
  </tr>
  <tr>
    <td> Weekend of June 21, 2003 </td>
    <td> Launch LV2 with avionics using an M and N motor in Brothers, OR.<br>Proposed purpose of launch: Avionics system test. </td>
  </tr>
  <tr>
    <td> Septemeber 2003 </td>
    <td> Launch of LV2 on P motor (if ready) in the Black Rock Desert of Nevada (at &quot;BALLS 2003&quot;)<br> Proposed purpose of launch: More altitude. And, of course, to get white dust all over everything. </td>
  </tr>
</table>

### <a name="Work necessary to be done before"></a> Work necessary to be done before May 4th 2003

**Airframe:**

The current airframe needs to have the damaged from the last launch fixed. Apparently the holes in the motor canister were "wowed" out due to the impact of LV2 hitting the ground on the main parachute. The repairs should be quick. There's some talk of having a few more airframes done by the June launch as well.

**Avionics:**

Finish up of the current hardware. Debugging of the FC software framework. Implementation of the flight state machine. There's a lot of work to be done, but a working system is very close.