LAUNCH DATE: SUNDAY April 15th, 2007
LAUNCH TIME:
LAUNCH SITE: Windsor, CO (Driving Directions)
On Air Nets
Check into the weekly EOSS net every Tuesday evening, except the 2nd Tuesday of the month when we hold our face to face meetings.
Pre-Flight Coordination Net
The evening prior to flight we hold a coordination net at 20:00 Local Time to assign the grid information and tactical callsigns. Any last minute information, launch time changes, launch location changes, maybe even a cancellation will be announced on this net.
Global Frequencies
EOSS-116 Balloon Frequencies
EOSS-117 Balloon Frequencies
Colorado University Frequencies
Green, you should be able to work the payload systems.
Red, is the border of the received signal. Red appears jittery because it is depicted topographically. Thus, the red dots on the eastern half of the map but well within the maximum distance show hilly terrain behind (east) which reception is not possible.
This is a generic 95,000 ft ASL coverage map for flights that depart from the vicinity of our launch site. Flight day coverage may vary depending on upper air winds.
EOSS-116
Balloon Manufacturer | Kaysam |
Balloon Type | latex |
Balloon Size | 3000 gram |
Payload | 27.4 lbs. |
Free Lift % | calculated at fill |
Ascent Rate | 1100 fpm estimated |
Descent Rate | 950 fpm estimated |
Parachute | 8.5 ft |
Peak Altitude | determined after flight |
Launch Conditions | determined at launch |
EOSS-117
Balloon Manufacturer | Kaysam |
Balloon Type | latex |
Balloon Size | 3000 gram |
Payload | 27.5 lbs. |
Free Lift % | calculated at fill |
Ascent Rate | 1100 fpm estimated |
Descent Rate | 950 fpm estimated |
Parachute | 10 ft |
Peak Altitude | determined after flight |
Launch Conditions | determined at launch |
Grid
Location | X | Y |
---|---|---|
West intersection of SR 14 and 71 | 50 | 15 |
Touchdown (see Prediction Page) |
Tactical Callsigns
Tactical | Callsign | Name | Notes |
---|---|---|---|
Alpha | WA0GEH and KC0UUO | Marty and Rob | Tracking and Recovery Coordinator |
Bravo | K0SCC | Stephen and Whitney | |
Charlie | N0MPM and W0CBH | Mike and Benjie | |
Delta | KB0QQW | Chris and Caleb | |
Echo | KB0YRZ and KB0UBZ | Chris and Ben | |
Foxtrot | KC0RPS and W0NFW | Jim and George | |
Golf | WB0DKT and KC0ZIE | Glenn and Darren | |
India | N0NHJ | Chuck | |
Ground | AE0SS | Nick | Ground Station |
Teams below have reported they are not available for Sunday. Let us know if there are any changes.
Unassigned | Callsign | Name | Notes |
---|---|---|---|
KC0VJE | Lou | ||
AC7FY | Clint | ||
N0NDM | Larry | ||
WG0E | Clint |
Notes from the T&R coordinator:
Trackers be sure to bring DF antennas for the EOSS 116 K0ANI-11 DF/Cutter on 445.975.
Future I-Gaters:
EOSS is always in need of I-Gate stations. Check out the EOSS I-Gate page for information on how to participate and why we need you.
Current I-Gate Station:
If you are present at your iGate during the flight try and monitor the tracking and recovery frequency. The ground station likes to check the frequency prior to launch to find out if any stations are out there ready to igate the traffic onto the net for the FAA to monitor.
The prediction program used to determine the track of the balloon prior to flight can now output a prediction for the Rise, Closest Approach, and Set of the balloon for each of your stations. I have posted a prediction page for stations that I have been able to discover geographic coordinates. See the I-Gate prediction page for an example. The page will not be updated daily, however, it will be updated the evening prior to flight for I-gate planning purposes.
I have often been asked by iGaters when they should expect to either start receiving signals (AOS) or expect to see those signals disappear (LOS). This prediction page should answer all those questions for you.
Your Log Files
Our technical committee members would also request you open a log file and record all the packets you hear and forward onto APRS-IS. Whenever there is a technical failure of a package it is always helpful to have the most complete dataset possible to attempt to determine the cause of failure and possible fixes. After a flight send your data files to me (webmaster) and I will distribute them to the appropriate payload builders. They appreciate these logs even if all goes fine during a flight.
note: customers are welcome to submit detailed synopses of their flights or web links to their own web sites.