Flight Announcement for EOSS-183

Recap Maps | Frequencies | Flight Systems | Payload Config | I-Gates | T & R | Text Recaps | Photos | Audio | Video | Data | Charts

Flight Coordinator: Jim Langsted (mailto: kc0rps@eoss.org)
LAUNCH DATE: December 9TH, 2012 (wx delay +1 day)
LAUNCH TIME: 07:15 am MST (14:15 UTC)
LAUNCH SITE: Windsor, CO (driving directions)

EOSS Flight Day Frequencies:

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

  • Repeaters  (trimmed evening pre-flight)
    • 449.450 MHz (103.5 Hz Tone) RMRL PRIMARY
    • 145.295 MHz (100 Hz Tone) Sterling (Backup)
    • 147.500 MHz (No PL Tone) Sterling (Backup)
    • 146.955 MHz (No PL Tone) Holyoke (Backup)
    • 146.655 MHz (No PL Tone) Ovid (Backup)
    • 145.600 MHz Akron (123 Hz tone) Colorado Connection (Backup)
  • Field Simplex Frequencies  
    • 446.100 MHz simplex for field recovery operations for EOSS-181
    • 446.150 MHz simplex for field recovery operations for EOSS-182
    • 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.
    • 146.550 MHz Backup field simplex
  • 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
  • HF - Possible ops
    • 7.234 LSB
    • 3.810 USB (backup)


EOSS-183 Balloon Payload Frequencies  

  • Beacons
    • 147.555 MHz
      • CW ID: AE0SS
    • 147.420 MHz
      • ID:K0SCC-11
    • 445.975 MHz
      • ID:N0IX-11
  • APRS
    • 147.420 MHz
      • ID: K0SCC-11
    • 445.975 MHz
      • ID:N0IX-11
    • 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

Flight Systems:


Balloon Manufacturer Totex
Balloon Type latex
Balloon Size 1200 g
Neck Load 11.6 Lbs.
Neck Lift 15.22 Lbs.
Ascent Rate 1329 fpm estimated
Estimated Burst Alt 88,000 ft. ASL
Descent Rate 950 fpm estimated
Parachute 5 ft.


Payload Configuration:

Payload Experiment Designer

no info yet

Experimenters are welcome to submit websites for linking or overviews which I will post on a page on the EOSS website.

Internet Gateway Stations:

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.

Tracking and Recovery


Location Grid X Grid Y
Windsor Launch Point 20 30
Grid Test   40.33� N , 104.25� W 57.4 20.5


Tactical Call Signs







Rob and Doug

Tracking and Recovery







Steve and Parker




Jim and Harlan








'Darren and Sam'


Golf N0NDM,    



Marty and David