Recap of EOSS-116/117

photo by Chris Krengel - KB0YRZ

Stephen Meer, K0SCC, wrestles the payload train of EOSS-117 into submission

LAUNCH DATE: SUNDAY April 15th, 2007
LAUNCH TIME:

• EOSS-116 7:29 am MDT (13:29 UTC)
• EOSS-117 8:44 am MDT (14:44 UTC)

LAUNCH SITE: Windsor, CO (Driving Directions)

Pre-flight Prediction and Actual Track

EOSS-116

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
Jagged line = Relative Speed
Prediction and Actual tracks made with Balloon Track
Maps by Google Earth

Map files available in the data section

Launch Site - Windsor
-----------------------
Launch Point: 40.47367� lat.   -104.96233� long.
Grid: X=-17.42 Y=5.57
Ascent Rate: 1100 feet per minute
Descent Rate: 950 feet per minute
Altitude: 4931 feet
Predicted Landing Site
-----------------------
Landing Point: 40.66796� lat.  -103.97609� long.
Grid: X=34.3 Y=19.0
Altitude: 5000 feet
Flight Time: 122 Minutes
Bearing: 75.1� True
Range: 53.4 Mi.
Actual Landing Site
-----------------------
Landing Point: 40.75998� lat.  -104.13651� long.
Grid: X=25.8 Y=25.3
Bearing: 65.2� True
Range: 47.581 Mi.
Difference from Predicted to Actual Landing Site
--------------------------------------------------
Bearing: 307.2� True
Range: 10.527 Mi.

EOSS-117

The predicted track below was made using winds aloft data acquired during the ascent of EOSS-116. Since this prediction was made available prior to liftoff of 117, I think it's fair to use it instead of the early morning predictions. This doesn't qualify for the record books though as I submitted neither this nor the early morning predict.

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
Prediction and Actual tracks made with Balloon Track
Maps by Google Earth

Launch Site - Windsor
-----------------------
Launch Point: 40.47367� lat.   -104.96233� long.
Grid: X=-17.42 Y=5.57
Ascent Rate: 1100 feet per minute
Descent Rate: 950 feet per minute
Altitude: 4931 feet
Predicted Landing Site
-----------------------
Landing Point: 40.80729� lat.  -104.15274� long.
Grid: X=25.0 Y=28.6
Altitude: 5000 feet
Flight Time: 120 Minutes
Bearing: 61.2� True
Range: 48.3 Mi.
Actual Landing Site
-----------------------
Landing Point: 40.78613� lat.  -104.25854� long.
Grid: X=19.5 Y=27.1
Bearing: 59.4� True
Range: 42.724 Mi.
Difference from Predicted to Actual Landing Site
--------------------------------------------------
Bearing: 255.2� True
Range: 5.722 Mi.

EOSS Flight Day Frequencies:

Global Frequencies

• Tracking and Recovery Operations
  • 449.450 MHz RMRL Repeater (103.5 Hz Tone)
  • 146.550 MHz simplex (for both field ops and the launch site)
  • Repeater Coverage Pages - Listings of all repeaters available in the expected flight areas.

EOSS-116 Balloon Frequencies

• Beacon
  • 445.975 MHz (K0ANI-11 package)
    • CW ID: K0ANI
    • DF tracking tone
• APRS
  • 144.340 MHz
    • ID: AE�SS-11
    • DIGI: EOSS
    • Node: BALNOD
    • APRS Time Slotted Every 30 seconds at 0:00 and 0:30
    • Telemetry once a minute
      • power up at 58 seconds past the GPS minute to properly slot telemetry
    • Sample Data

• 445.975 MHz (K0ANI-11 package)

• ID: K0ANI-11

EOSS-117 Balloon Frequencies

• Beacon

• 147.555 MHz

• CW ID: AE0SS

• APRS

• 144.340 MHz

• ID: KC0YA-11
• DIGI: EOSS
• Node: BALND2
• APRS Time Slotted Every 30 seconds at 0:15 and 0:45

• power up at 13 seconds past the GPS minute to properly slot telemetry

• Telemetry once a minute
• Sample Data

Colorado University Frequencies

• APRS (aboard Peregrine Return Vehicle)

• 145.600 MHz

• ID: KC0YA-12

Radio Coverage:

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.

Flight Systems:

EOSS-116

EOSS-117

Payload Configuration:

• Payload_Plan_116-117c2.pdf

Tracking and Recovery Info:

Grid

Tactical Callsigns

Teams below have reported they are not available for Sunday. Let us know if there are any changes.

Notes from the T&R coordinator:

Trackers be sure to bring DF antennas for the EOSS 116 K0ANI-11 DF/Cutter on 445.975.

Internet Gateway Stations:

as seen on Findu.Com

EOSS-116

For AE0SS-11

• KC0VJE - Louis Perley, Erie, CO
• K0YG-3 - Mark Patton, Foxfield, CO
• KB0TVJ-3 - Russ Chadwick, Launch Site
• KC0LNO - Michael Skinner, Monument, CO
• KC0ZLS - Shaun Bryant, Commerce City
• N0EB-1 - Richard Beggs, Thornton, CO (formerly K0AEM, congrats on the upgrade)

For K0ANI-11

• KB0TVJ-3 - Russ Chadwick, Launch Site
• K0YG - Mark Patton, Foxfield, CO
• N0PSJ - Christopher Holmes, Arvada, CO

For KC0ZAP-11

• K0QED - Lee Inman, Colorado Springs, CO
• K0ANI - Larry Cerney, Denver, CO
• N0NHJ -Lloyd Kimball, Glenwood Springs, CO
• KD0H-11 - David Herman, Steamboat Springs, CO
• KC0LNO-1 - Michael Skinner, Monument, CO

EOSS-117

for KC0YA-11

• KC0VJE - Louis Perley, Erie, CO
• KC0VJE-2 - Louis Perley, Erie, CO
• K0YG-3 - Mark Patton, Foxfield, CO
• KC0LNO - Michael Skinner, Monument, CO
• KC0ZLS - Shaun Bryant, Commerce City
• N0EB-1 - Richard Beggs, Thornton, CO (formerly K0AEM, congrats on the upgrade)

for KC0YA-12

• KC0UUO - Rob Wright (this was from Saturday while Rob iGated the test flights)
• K0YG - Mark Patton, Foxfield, CO
• KB0TVJ-3 - Russ Chadwick, Launch Site
• N0PSJ - Christopher Holmes, Arvada, CO
• KI4GYZ - Art Hostmark, Thornton, CO

EOSS wishes to express our sincere appreciation to the stations above who iGated the balloon APRS telemetry onto the internet.

Of interest for this flight, we had a payload, KC0ZAP-11, on the national APRS frequency of 144.390 MHz. This essentially revealed several iGate stations around the state. N0NHJ who was actually on the chase teams left his home iGate up and running from Glenwood Springs, KD0H from Steamboat Springs, and K0QED from Colorado Springs. Cool.

Many of you have i-gated before but did you know I publish predictions for i-gates? I keep a list of everyone who has ever i-gated an EOSS balloon flight on frequencies other than the national 144.390 freq. If you have ever igated an EOSS balloon on any frequency other than the national, you're in the list. 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 28 i-gates. If you are a national frequency iGate and want to be added to the prediction list send me you callsign, latitude, longitude and latitude of your iGate and I'll include your station in future predictions.

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.

Customer

• Colorado University - Demosats and SD

• CU will fly a the Peregrine Return Vehicle.

• Approximately 20.3 LBs.
• Here is a link to the Peregrine web page.
• More links welcome CU!

note: customers are welcome to submit detailed synopses of their flights or web links to their own web sites.

Peregrine Pre-Flight Testing

• Photos by Chris Krengel, KB0YRZ
• Data from Findu, Processed by N0KKZ
• Data from Nick Hank's TrackPoint

Photos

Launch Site

• by Nick Hanks, N0LP
• by Robert Slate, N0TQN

• Launch of EOSS-116
• Launch of EOSS-117
• Activities at the launch site

Landing Sites

• by Chris Krengel, KB0YRZ

• Page 1
• Page 2

• by Jim Langsted, KC0RPS
• By Team Alpha, Marty Griffin WA0GEH and Rob Wright KC0UUO

A screen capture of the N0KKZ prediction central desktop during the flight.

Audio

Tracking and Recovery operations on the Rocky Mountain Radio League's 449.450 MHz repeater. The audio was recorded with VOX active so time has been compressed by the removal of silence on the repeater. Events unfold in their true sequential order.

• 1_eoss116_launch.mp3 - (4.2 MB)
• 2_eoss117_launch.mp3 - (1 MB)
• 3_eoss116_burst.mp3 - (4 MB)
• 4_eoss116_touchdown.mp3 - (2.1 MB)
• 5_eoss117_burst.mp3 - (3.5 MB)
• 6_eoss117_touchdown.mp3 - (2.5 MB)

I'm attempting to capture snippets of audio from various payloads that have something semi distinctive beyond just a packet bleep.  So ...

• ae0ss_sound_clip.mp3 - A brief explanation and audio of one cycle of the AE0SS cut down beacon.

Video

Recap from the Launch site by Roger Hanson, N0EXA

Data

Combined Files

• EOSS116-17GndLog.txt - Log recorded at the EOSS ground station, everything heard on 144.340 MHz

EOSS-116

Text

• eoss-116_ae0ss-11_findu.txt - findu log
• eoss-116_ae0ss-11_findu_ts.txt - findu log with time stamps
• EOSS116_KPC3_LTR.txt - KPC3 airborne TNC log file
• eoss-116_ae0ss-11_combo.txt - combined files above (only GGA and RMC)
• eoss-116_k0ani-11_findu.txt - findu log
• eoss-116_k0ani-11_findu_ts.txt - findu log with time stamps
• eoss-116_kc0zap-11_findu.txt - findu log
• eoss-116_kc0zap-11_findu_ts.txt - findu log with time stamps

Spreadsheet

• eoss-116_ae0ss-11_combo_Flight_Data.csv - extracted from the above combo file
• eoss-116_ae0ss-11_Telem_Data.csv - extracted from the above findu.com file
• eoss-116_kc0zap-11_Flight_Data.csv - extracted and edited from the above findu.com timestamped file

Maps

• EOSS-116_predict_track.kml - Google Earth File of the prediction
• eoss-116_recap.ptm - MapPoint file of the recap. Used to create the recap map at the top of this page
• EOSS-116_track.kml - Google Earth File of the actual flight track
• eoss-116_kc0zap-11_LastTrackMap.ptm - MapPoint file of KC0ZAP-11 track.

Charts

• by Rick von Glahn, N0KKZ

EOSS-117

Text

Combo data files created with data from Findu, KC0RPS, KI4GYZ, K0SCC, WA0GEH, and N0EB and N0LP

• eoss-117_kc0ya-11_findu.txt - findu log
• eoss-117_kc0ya-11_findu_ts.txt - findu log with time stamps
• eoss-117_kc0ya-11_combo.txt - combined files
• eoss-117_kc0ya-12_pere_findu.txt - findu log
• eoss-117_kc0ya-12_pere_findu_ts.txt - findu log with time stamps
• eoss-117_kc0ya-12_pere_combo.txt - combined files

Spreadsheet

• eoss-117_kc0ya-11_combo_Flight_Data.csv - extracted from the above combo file
• eoss-117_kc0ya-11_Telem_Data.csv - extracted from the above findu.com file
• eoss-117_kc0ya-12_pere_combo_Flight_Data.csv - extracted from the above combo file

Maps

• EOSS-117_predict_track.kml - Google Earth File of the prediction
• EOSS-117_track.kml - Google Earth File of the actual flight track
• eoss-117_kc0ya-11_recap.ptm - MapPoint file of the recap. Used to create the recap map at the top of this page

Charts

• by Rick von Glahn, N0KKZ