Flight Coordinator: Nick Hanks
LAUNCH DATE: June 15th, 2013 (wx delay +1 day)
LAUNCH TIME EOSS-187: unknown
LAUNCH SITE: Pella IA
Tracking and Recovery Frequencies
Tracking and Recovery Operations
Ground Stations Frequencies
EOSS-188 Balloon Payload Frequencies
Beacons
APRS
EOSS-188
Balloon Manufacturer | Totex |
Balloon Type | latex |
Balloon Size | 1200 g |
Neck Load | 7.69 Lbs. |
Neck Lift | 10.27 Lbs. |
Ascent Rate | 1329 fpm estimated |
Estimated Burst Alt | 95,000 ft. ASL |
Descent Rate | 950 fpm estimated |
Parachute | 5.8 ft. |
Edge of Space Sciences
Experimenters are welcome to submit websites for linking or overviews which I will post on a page on the EOSS website.
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.
|
|