Recap of EOSS-147/148

03/02/2012 15:50 (CDT): Class thank you photo added

by SamCam2

EOSS-148 descending to landing at Wind Farm

Flight Coordinator: Jim Langsted, kc0rps@eoss.org

LAUNCH DATE: November 7th, 2009 (wx delay +1 day)
LAUNCH TIME: 

• EOSS-147: 06:49 MST (13:49 UTC)
• EOSS-148: 07:14 MST (14:14 UTC)

LAUNCH SITE: Windsor, Colorado (directions)

Pre-flight Prediction and Actual Tracks

E0SS-147

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

Map Files available in the Data Section below

Launch Site - Windsor
-----------------------
Launch Point: 40.47367� lat.   -104.96233� long.
Grid: X=-7.40 Y=7.57
Ascent Rate: 1324 feet per minute
Descent Rate: 950 feet per minute
Altitude: 4931 feet
Predicted Landing Site
-----------------------
Landing Point: 40.92802� lat.  -103.75724� long.
Grid: X=55.5 Y=38.9
Altitude: 4500 feet
Flight Time: 129 Minutes
Bearing: 63.2� True
Range: 70.5 Mi.
Actual Landing Site
-----------------------
Landing Point: 40.8812� lat.  -104.11528� long.
Grid: X=36.9 Y=35.7
Bearing: 57.3� True
Range: 52.525 Mi.
Difference from Predicted to Actual Landing Site
--------------------------------------------------
Bearing: 260.3� True
Range: 18.964 Mi.

E0SS-148

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

Map Files available in the Data Section below

Launch Site - Windsor
-----------------------
Launch Point: 40.47367� lat.   -104.96233� long.
Grid: X=-7.40 Y=7.57
Ascent Rate: 1324 feet per minute
Descent Rate: 950 feet per minute
Altitude: 4931 feet
Predicted Landing Site
-----------------------
Landing Point: 40.92802� lat.  -103.75724� long.
Grid: X=55.5 Y=38.9
Altitude: 4500 feet
Flight Time: 129 Minutes
Bearing: 63.2� True
Range: 70.5 Mi.
Actual Landing Site
-----------------------
Landing Point: 40.9343� lat.  -104.05951� long.
Grid: X=39.7 Y=39.4
Bearing: 55.8� True
Range: 56.96 Mi.
Difference from Predicted to Actual Landing Site
--------------------------------------------------
Bearing: 271.7� True
Range: 15.776 Mi.

• Final Pre-Flight Prediction is available here
• Prediction History is available here

Payload Experiment Designer

• Colorado University

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

EOSS Flight Day Frequencies:

Tracking and Recovery Frequencies

• Preflight Net:
  • 147.225 MHz 8 pm local time the evening preceding the flight
    • 145.160 MHz simulcast in the Springs
  • 146.640 MHz will serve as a backup frequency
• Tracking and Recovery Operations
  • 449.450 MHz RMRL (103.5 Hz Tone)
  • 146.550 MHz simplex (same simplex for field and launch ops)
  • 146.580 MHz simplex (field ops for eoss-148 if needed)
  • 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.
  • 7.228 MHz HF

 

EOSS-147 Balloon Payload Frequencies

• Beacons
  • 147.555 MHz
    • CW ID: AE0SS

• 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

EOSS-148 Balloon Payload Frequencies

• Beacons
  • 145.600 MHz
    • CW ID: W5VSI

• 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

Flight Systems:

EOSS-147  

EOSS-148  

Payload Configuration: 

• Preflight
  • EOSS-147_Payload_Plan_Rev_E.pdf
  • EOSS-148_Payload_Plan_Rev_E.pdf
• At Launch (final weights)
  • EOSS-148_Payload_Plan_Rev_Final.pdf

Internet Gateway Stations:

as seen on Findu.Com

EOSS-147

AE0SS-11

• KB0TVJ - Russ Chadwick, at the launch site
• KC0D-3 - Mark Patton, Foxfield, CO
• KC0D-5 - Mark Patton, Foxfield, CO
• KC0MWM - Roger Hammond, Grand Island, NE
• KC0VJE - Louis Perley, Nunn, CO
• KG0W - Matthew Kassawara, Ft. Collins, CO

EOSS-148

KC0YA-11

• KB0TVJ - Russ Chadwick, at the launch site
• KC0D-3 - Mark Patton, Foxfield, CO
• KC0D-5 - Mark Patton, Foxfield, CO
• KC0VJE - Louis Perley, Nunn, CO
• KG0W - Matthew Kassawara, Ft. Collins, 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 29 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.

Tracking and Recovery 

Breakfast

• Johnson�s Corner (I-25 exit 254 east side)

• 04:30 and 05:15

• Need to depart to the field no later than 05:30.

EOSS Grid

Tactical Call Signs. 

Text Recaps

Photos

Thank you note from the Class of ASEN2500

Click HERE or on photo above for high rez version

Launch Site

• by Jose Lopez
• by Nick Hanks, N0LP
• by Tony Kalmbach

SamCam2 Airborne In Flight

Ascent Phase

• Looking Down
• Looking Out at Horizon
• Looking Up

Descent Phase

• Looking Down
• Looking Out at Horizon
• Looking Up

Recovery Site EOSS-147

• by Darren Kalmbach, KC0ZIE
• by Tony Kalmbach
• by Glenn Hetchler, WB0DKT

Recovery Site EOSS-148

• by Jose Lopez
• by Jim Langsted, KC0RPS
• by Miles Pappas, KD0JIT (Congratulations on the call sign, you got it Just In Time for the flight)
  • page 1 People
  • page 2 Payloads
• by Marty Griffin, WA0GEH
  • Page 1
  • Page 2
• by Tim Humphreys
  • page 1
  • page 2
• by Colin Glennan, WG0E
  • page 1
  • page 2

Audio

recorded but not yet edited

Video

Data

EOSS-147

AE0SS-11

Text

• eoss-147_ae0ss-11_findu.txt - Findu Log
• eoss-147_ae0ss-11_findu_ts.txt - Findu Log with findu timestamps
• eoss-147_ae0ss-11_airborne_log.txt- airborne only KPC3 Log
• eoss-147_ae0ss-11_kpc3_log.txt - Onboard KPC3 Log with annotation by w5vsi

Spread Sheets

• eoss-147_ae0ss-11_Flight_Data.csv - airborne only KPC3 Log ripped to spreadsheet format
• eoss-147_ae0ss-11_Telem_Data.csv - KPC3 Telemetry (internal temps channel being used for other data and is NOT accurate)

Mapping Files

• eoss-147_ae0ss-11_recap.ptm - MapPoint file of the above recap
• eoss-147_ae0ss-11_track.kml - Google Earth Track of the flight
• eoss-147_predict_track.kml - Google Earth Track of the predicted flight path

EOSS-148

KC0YA-11

Text

• eoss-148_kc0ya-11_findu.txt - Findu Log
• eoss-148_kc0ya-11_findu_ts.txt - Findu Log with findu timestamps
• eoss-148_kc0ya-11_airborn.txt - airborne only KPC3 Log
• eoss-148_kc0ya-11_KPC_log_annotated.txt - Onboard KPC3 Log with annotation by kc0ya

Spread Sheets

• eoss-148_kc0ya-11_Flight_Data.csv - airborne only KPC3 Log ripped to spreadsheet format

Mapping Files

• eoss-148_kc0ya-11_recap.ptm - MapPoint file of the above recap
• eoss-148_kc0ya-11_track.kml - Google Earth Track of the flight
• eoss-147_predict_track.kml - Google Earth Track of the predicted flight path (same as 147)