03/27/2013 13:45 (CDT): Photos by Jim Langsted, Ben Baker and Mike Pappas added.
Flight Coordinator: Jim Langsted (kc0rps@eoss.org)
LAUNCH DATE: July 9th, 2011 (wx delay +1 day)
LAUNCH TIME: 07:10 am MDT (13:10 UTC)
LAUNCH SITE: Windsor, Colorado (Click Here for directions)
E0SS-166 AE0SS-11
Blue = Actual Track
Green = Predicted Ascent Phase
Red = Predicted Descent Phase
Map made with MapPoint
Prediction made with Balloon Track
Green Track = Ascent
Red Track = Descent (NO DESCENT TRACK)
Prediction and Actual tracks made with Balloon Track
Maps by Google Earth
E0SS-166 K0SCC-11
Blue = Actual Track
Green = Predicted Ascent Phase
Red = Predicted Descent Phase
Map made with MapPoint
Prediction made with Balloon Track
Green Track = Ascent
Red Track = Descent (NO DESCENT TRACK)
Prediction and Actual tracks made with Balloon Track
Maps by Google Earth
Above Map Files available in the Data Section below
Final Pre-Flight Prediction is available here
Prediction History is available hereLaunch Site - Windsor ----------------------- Launch Point: 40.47367� lat. -104.96233� long. Grid: X=2.62 Y=65.57 Ascent Rate: 1329 feet per minute Descent Rate: 950 feet per minute Altitude: 4931 feet Predicted Landing Site ----------------------- Landing Point: 40.77551� lat. -104.37358� long. Grid: X=33.4 Y=86.4 Altitude: 4500 feet Flight Time: 127 Minutes Bearing: 55.8� True Range: 37.2 Mi. Actual Landing Site ----------------------- Landing Point: 40.71811� lat. -104.57007� long. Grid: X=23.1 Y=82.4 Bearing: 50.5� True Range: 26.602 Mi. Difference from Predicted to Actual Landing Site -------------------------------------------------- Bearing: 249.0� True Range: 11.015 Mi.
Tracking and Recovery Frequencies
- Preflight Net:
- 147.225 MHz 8 pm MDT preceding night
- 146.640 MHz will serve as a backup frequency
- Tracking and Recovery Operations
- 449.450 MHz (103.5 Hz Tone) north track RMRL
- Field Simplex Frequencies
- 446.100 MHz simplex
- Note: Some radios insist on incorrectly placing a negative 5 MHz offset when selecting frequencies from the simplex portion of the 70 CM band. Check your radio and if this is the case. Consider programming in this simplex frequency to a memory channel as some radios have demonstrated the annoying habit of re-inserting the offset if you momentarily shift to a repeater then return to the simplex freq. Check the operation of your radio on this simplex freq to be ready for however your radio behaves.
- Repeater Coverage Pages - Listings of all repeaters available in the expected flight areas.
- There may be FRS operations see THIS PAGE for a list of channel numbers and their associated UHF Frequencies.
- Launch Site Simplex
- 146.550 MHz
EOSS-166 Balloon Payload Frequencies
- Beacons
- 147.420 MHz
- CW ID: K0SCC
- APRS
- 144.340 MHz
- ID: AE�SS-11
- DIGI: EOSS
- Node: BALNOD
- APRS Time Slotted Every 30 seconds at 0:00 and 0:30
- power up at 58 seconds past the GPS minute to properly slot telemetry
- Telemetry once a minute
- Sample Data
- 147.420 MHz
- ID: K0SCC-11
Video Might Be available, check http://www.eoss.tv
Various Online Live Tracking Pages
EOSS-166
Balloon Manufacturer | Totex |
Balloon Type | latex |
Balloon Size | 3000 g |
Neck Load | 26.3 lbs. |
Neck Lift | 31.2 lbs. |
Ascent Rate | 1329 fpm estimated |
Descent Rate | 950 fpm estimated |
Parachute | 10 ft. |
Peak Altitude | 95,000 ft. ASL estimated |
Launch Conditions | determined at launch |
CU SGC, Upward Bound
Experimenters are welcome to submit websites for linking or overviews which I will post on a page on the EOSS website.
as seen on Findu.Com (listed alphabetically)
EOSS-166, AE0SS-11
- K0SCC - Steve Meer
- KB0TVJ - Russ Chadwick, Boulder, CO
- KC0VJE - Louis Perley, Nunn, CO
- N0IX-12 - Doug Gentges, Tracking and Recovery Mobile iGate
- N0ZUQ-1 - Clifford Mikkelson - Windsor, CO
EOSS-166, K0SCC-11
- K0SCC - Steve Meer
- KB0TVJ-4 - Russ Chadwick, Ground Station
- KC0D-3 - Mark Patton, Foxfield, CO
- N0PSJ - Christopher Holmes, Arvada, CO
EOSS wishes to express our sincere appreciation to the stations above who iGated the balloon APRS telemetry onto the internet. Did you know I publish predictions for i-gates? I keep a list of everyone who has ever i-gated an EOSS balloon flight. You're all in the list so if you're wondering when the balloon will pop up over your horizon, check out this page for future flights. Currently predictions are being made for 30 i-gates.
We are relying heavily on real time position information available on the net to allow the FAA controllers to have up to the minute location data to assist them in air traffic control.
Redundant stations for the balloon iGating provide excellent coverage. If you are able to iGate we invite you to join the Internet Gateway Team. Contact me (webmaster@eoss.org) to be put in touch with the coordinator. By joining the team, you are giving peace of mind to the iGate coordinator for that flight. He knows you'll be there and he can rely on you.
Naturally, anyone can iGate data onto the net and even if you aren't a member of the team we will welcome your contribution to the internet based tracking effort. If you callsign appears on the findu.com log, you'll be shown as a contributing station as those above are.
Having more than one station covering each APRS beacon means that should a station drop out momentarily, the others can often maintain the data flow.
Thanks again guys! The FAA (and EOSS) are very grateful for your assistance in this endeavor.
Future I-Gaters:
Check out the EOSS I-Gate page for information on how to participate and why we need you.
Current I-Gate Stations:
Guys, the prediction program used to determine the track of the balloon prior to flight can now output a prediction for the Rise, Closest Approach or maximum elevation, 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.
Location
Grid X
Grid Y
Hwy 14 & 71 West 70 75 Test Coordinates 40� 30'N x 104� 15'W 40 67.5
Tactical Callsign Name Notes Alpha KB0YRZ, KB0UBZ Chris, Ben Tracking and Recovery Coordinator Bravo W9CN, KD0JIT Mike, Miles Trackers, Comm Coordinator Charlie WA0GEH, KC0D Marty and Mark Trackers Delta K0SCC, N0LP Steve and Nick and Parker Trackers Echo KC0ZIE, KG6HXM Darren, Sam Trackers Foxtrot W0CBH Benjie and Rose Trackers Golf KB0LP Dave Tracker Hotel KC0RPS Jim Flight Coordinator India N0NDM, KC0UUO Larry and Rob Launch Coordinator and President
Launch Site
Recovery Site
recorded, not posted
|
|
EOSS-166, AE0SS-11
Text
- eoss-166_ae0ss-11_findu.txt - Findu Log
- eoss-166_ae0ss-11_findu_ts.txt - Findu Log with findu timestamps - airborne only from KPC3 Log
- eoss-166_ae0ss-11_KPC3_airborne..txt - Airborne only from KPC3 Log
- eoss-166_ae0ss-11_KPC3_LTR.txt - Onboard KPC3 Log with annotation by w5vsi.
Spread Sheets
- eoss-166_ae0ss-11_Flight_Data.csv - airborne only Log ripped to spreadsheet format
- eoss-166_ae0ss-11_Telem_Data.csv - KPC3 Telemetry log
Mapping Files
- eoss-166_ae0ss-11_recap.ptm - MapPoint file of the above recap
- EOSS-166_ae0ss-11_track.kml - Google Earth Track of the flight
- EOSS-166_predict_track.kml - Google Earth Track of the predicted flight path
EOSS-166, K0SCC-11
Text
- eoss-166_k0scc-11_findu.txt - Findu Log
- eoss-166_k0scc-11_findu_ts.txt - Findu Log with findu timestamps
Spread Sheets
- eoss-166_k0scc-11_Flight_Data.csv - airborne only Findu data ripped to spreadsheet format
Mapping Files
- eoss-166_k0scc-11_recap.ptm - MapPoint file of the above recap
- eoss-166_k0scc-11_track.kml - Google Earth Track of the flight