|
| |
Recap of EOSS-136/137
05/09/2010 17:33 (CDT):
RocketSat Team Letter added
EOSS-136/137 Flight Coordinator: Jim Langsted, KC0RPS
LAUNCH DATE: April 11th, 2009 (wx +8, SUNDAY, April 19th)
LAUNCH TIME:
- EOSS-136: 06:45 MDT (12:45 UTC)
- EOSS-137: 07:06 MDT (13:06 UTC)
LAUNCH SITE: Windsor, CO (see
directions)
Pre-flight Prediction and Actual Tracks
E0SS-136 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
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=10.01 Y=10.00
Ascent Rate: 1400 feet per minute
Descent Rate: 1070 feet per minute
Altitude: 4931 feet
Predicted Landing Site
-----------------------
Landing Point: 41.06785° lat. -104.4027° long.
Grid: X=39.1 Y=51.0
Altitude: 4500 feet
Flight Time: 86 Minutes
Bearing: 35.3° True
Range: 50.4 Mi.
Actual Landing Site
-----------------------
Landing Point: 41.13986° lat. -104.35928° long.
Grid: X=41.3 Y=56.0
Bearing: 34.2° True
Range: 55.757 Mi.
Difference from Predicted to Actual Landing Site
--------------------------------------------------
Bearing: 24.4° True
Range: 5.464 Mi.
GLL = Gill CO, CYS = Cheyenne WY
E0SS-137 KC0YA-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
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=10.01 Y=10.00
Ascent Rate: 1400 feet per minute
Descent Rate: 1070 feet per minute
Altitude: 4931 feet
Predicted Landing Site
-----------------------
Landing Point: 41.09999° lat. -104.26123° long.
Grid: X=46.4 Y=53.2
Altitude: 4500 feet
Flight Time: 117 Minutes
Bearing: 40.1° True
Range: 56.7 Mi.
Actual Landing Site
-----------------------
Landing Point: 41.12828° lat. -104.11482° long.
Grid: X=54.0 Y=55.2
Bearing: 44.1° True
Range: 63.283 Mi.
Difference from Predicted to Actual Landing Site
--------------------------------------------------
Bearing: 75.6° True
Range: 7.861 Mi.
Prediction History is available here
Final Pre-Flight Prediction is available here
Payload Experiment Designer
- Colorado University Rocket Sat AirCore
- NOAA Dropsonde
- Colorado University Demo Sats
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 MDT the evening prior to flight day
- 145.160 MHz simulcast in the Springs
- 145.460 MHz simulcast in Boulder
- 146.640 MHz will serve as a backup frequency
- Tracking and Recovery Operations
- Primary Frequencies
- 449.450 MHz RMRL (103.5 Hz tone)
Windsor Launch site
- 447.275 MHz NCARC (100 Hz tone)
North of Fort Collins into Wyoming
- Backup/End Game Frequencies
- 449.300 MHz (131.8 Hz tone) Lat/long: 41.14/-104.76, eastern
Cheyenne, great coverage south of I-80 and into the recovery area, may
use this in lieu of 146.55 as it would provide good coverage in hilly
terrain.
- 147.105 MHz (114.8 Hz tone)
Eastern
Cheyenne, linked to Albin repeater on 147.165+, runs weather net in
morning
- 147.165 MHz (114.8 Hz tone) WY/NE border, north of I-80, linked to
Cheyenne 147.105, runs weather net in morning
- 146.550 MHz simplex (same simplex for field and launch ops)
- 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.
EOSS-136 Balloon Payload Frequencies
EOSS Operational Frequencies
- Beacons
- 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
NOAA Frequencies
- Dropsonde Telemetry
- 438.250 MHz Wideband FM (~250 KHz wide at 100 mW)
EOSS-137 Balloon Payload Frequencies
- Beacons
- 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
145.600 MHz
Flight Systems:
EOSS-136
| Balloon Manufacturer |
Kaysam |
| Balloon Type |
latex |
| Balloon Size |
3000 gram |
| Neck Load |
26.3 lbs. |
| Neck Lift |
31.6 lbs |
| Ascent Rate |
1400 fpm estimated |
| Descent Rate |
1000 fpm estimated |
| Parachute |
8.5 ft. |
| Peak Altitude |
70,113 ft. ASL forced cutdown |
| Launch Conditions |
determined at launch |
EOSS-137
| Balloon Manufacturer |
Kaysam |
| Balloon Type |
latex |
| Balloon Size |
3000 gram |
| Neck Load |
23.7 lbs. |
| Neck Lift |
30.8 lbs |
| Ascent Rate |
1400 fpm estimated |
| Descent Rate |
950 fpm estimated |
| Parachute |
10 ft |
| Peak Altitude |
95,718 ft. ASL burst |
| Launch Conditions |
determined at launch |
Payload Configuration:
Tracking and Recovery Info:
submitted by Marty Griffin, WA0GEH (Alpha) and Nick Hanks, N0LP
Hello Trackers,
The upcoming EOSS-136/137 adventure is pretty complex. Nick and I have been
chatting about the logistics of getting everyone into the field where they need
to be at the right time. This will take unique tracker participation from Mike
W9CN, Chris KB0YRZ and Larry K0ANI. Here’s the current scoop.
First, as most of you now know the balloons are going north and most likely
out of range of the trusty 449.450 MHz repeater. Our current planning is to use
a 70 cm repeater operated by the Northern Colorado Amateur Radio Club. The
repeater is located northwest of Fort Collins at 7727 ft.. We know it has
coverage in Cheyenne and some folks will be testing it for us on I-80 towards
the WY-NE state line. It’s on 447.275 MHz, negative shift, and 100 Hz PL tone.
EOSS 136: This flight will be the first one on Saturday. Currently launch
time is 06:50 AM. It has three payloads sponsored by NOAA. A prototype, 38 gram
(0.1 lb.) dropsonde designed to be dropped from a UAV into a hurricane, a
prototype meteorological package meant to support future NOAA missions, and a
variation on the AirCore sampler we flown before only this one is destined to
fly on a rocket from Wallops Island this summer. Since the dropsonde is not
designed for very high altitude operation, we’re going to cut the payload string
loose at 70,000 ft. Post-flight turnoff instructions on the met package and the
AirCore will be provided on the net Friday night. The dropsonde will be turned
off by the design team, ARA. The ARA folks will be collecting data from the
dropsonde using two cars. We need to support their data collection.
EOSS-136 ARA Dropsonde
The ARA dropsonde teams will deployed as tactical “ARA Car 1” and “ARA
Car 2”. Both cars will be using mag mount antennas to receive the dropsonde
signal on 438 MHz.
For ARA Car 1, the intent is to pre-deploy into the field at about the
projected burst point and about 10 miles north to northwest to avoid being
directly under the dropsonde. The ARA Car 1 team’s objective is to acquire
and capture as much data as possible without blanking out the received
signal with our 70 cm net transmissions. ARA Car 1 will have Brian Zadler (ARA,
ph number redacted) and Tim Samaras WJ0G on-board. The plan is for ARA Car 1
to meet us at the breakfast site and then trail Chris KB0YRZ to the point
described above. Chris and the ARA guys will determine where to position
themselves after reviewing N0KKZ’s prediction from either Friday night
and/or Saturday morning. Chris will communicate with ARA Car 1 via WJ0G on
146.55 MHz and with our net on 447.275. He will lead about ¼ mile ahead of
ARA Car 1. The ARA Car 1 team will set up a 70 cm beam to receive signals
from the dropsonde, probably from a high point just off I-80. Chris will
assist with this by providing periodic updates of the balloon’s elevation
angle and bearing. Shortly after cut away or just before, Chris will lead
the ARA Car 1 team to the predicted recovery area where they will attempt to
continue to receive the dropsonde signal during final descent. If ARA Car 2
is receiving data well, ARA Car 1 could depart for the landing area before
cutaway. That’s an ARA call. The decent data is very important for this
experiment is it will allow evaluation of the impact of component warming.
ARA Car 2 will bring the dropsonde to the launch site, assist with
getting the dropsonde on the flight string and checked-out, monitor the
launch, and then verify the signal from the dropsonde. After the launch and
verification, Mike W9CN will lead the ARA Car 2 towards the balloon (via
I-25 and I-80 hopefully), but will lag behind and to the north of the
balloon trajectory to avoid 70 cm interference from net transmissions. On
board the ARA Car 2 is Doug Meegan, the ARA lead (ARA, ph number removed),
and a driver or two. Mike and the ARA Car 2 will communicate via FRS radio.
He’ll be on the 447.275 net also. Mike will also need the latest predict
file and know how to quickly get to the predicted landing site. At burst,
Mike will lead the ARA Car2 to the recovery site while trying to maintain
dropsonde reception in ARA Car 2. Tough assignment, but Mike’s “driver” can
get it done.
During the operations, the ARA Car 2 may choose to “leap frog” over ARA
Car 1. This choice is up to the ARA folks during operations time.
EOSS 136: NOAA/CU AirCore Team
On EOSS 136 will be the NOAA/CU AirCore experiment to collect an
atmospheric sample and to test the closure of the AirCore intake valve at
30K feet. The team (tactical AirCore Team) of 4-5 CU students will be
advised by the ground station as to where to go to meet a tracker team in
the field. Alpha (Marty and Mark) will provide this data via the 447.275
net. Most likely the students will go up I-25 and then to the East on I-80.
Alpha will advise who to meet and any meeting location change via the
447.275 net and maintain telephone contact with the AirCore Team. This team
needs to arrive at the landing site as soon after landing as possible to
check the AirCore valve and to turn-off the met payload.
EOSS 137: University of Colorado DemoSats
EOSS 137 will launch about 15 minutes after EOSS 136. This flight will
carry a string of CU DemoSats similar to what we’ve flown in the past. The
students for the DemoSats will launch and then travel to the recovery site.
Larry K0ANI will first assist with payload string preparation and launch,
and then he will lead the CU students to the recovery site which will be
about 10 miles further out than EOSS 136 since this balloon will be allowed
to burst. Larry will communicate with Alpha on the 70 cm net. Steve K0SCC
will bring his new APRS module to the launch site, assist with launch, and
then will be leaving after -137 is away. He will be conducting some
commanding experiments with his payload K0SCC-11 on 145.600 MHz. Once in the
landing area ,he will assist in the recovery of EOSS 137.
As Ross Perot would say, “It’s just that simple.”
Comments are welcome.
Breakfast
- Johnson's Corner (Exit 254)
- 5:00 AM
Grid
|
Location |
Grid X |
Grid Y |
|
Launch Site,
Windsor
lat = 40°
28.420' long = -104° 57.740'
|
10 |
10 |
|
TrackPoint Test 40°
45' N, 104° 30' W
|
34.1 |
29.0 |
Tactical Call Signs
|
Tactical |
Callsign |
Name |
Notes |
|
Alpha |
WA0GEH, KC0D |
Marty & Mark |
Tracking and Recovery Coordinator |
|
Bravo |
KB0YRZ |
Chris |
W/ ARA Car 1 |
|
Charlie |
W9CN |
Mike |
W/ ARA Car 2 |
|
Delta |
WB0DKT & KG6HXM |
Glenn, Sam |
Glenn, Loren,
Andrea, David,
Sam,
Suzanna - Family Affair! |
|
Echo |
KC0RPS |
Jim |
Remaining at the launch site |
|
Foxtrot |
K0SCC |
Steve & Daryl |
Launch and Chase |
|
Golf |
N0IX, N0SSW |
Doug, Harlan |
|
|
Hotel |
KC0UUO |
Rob |
Presidential Limo |
|
India |
KB0LP |
Dave |
|
|
|
N0NDM |
Larry |
Launch Coordinator…tentative tracking |
|
|
AE0SS |
Nick |
Ground Station |
Internet Gateway Stations:
as seen on Findu.Com
EOSS-136
AE0SS-11
- K0ANI-14 - Larry Cerney, Mobile in the chase team
- K0UT-1 - Bill Beach, Fort Collins CO
- KB0TVJ-4 - Russ Chadwick, at the launch site
- KC0D-4 - Mark Patton, Foxfield, CO
- KC0VJE - Louis Perley, Nunn, CO
- KG0W - Matthew Kassawara, Fort Collins CO
- N0PSJ - Christopher Holmes, Arvada, CO
- N0SPB-10 - Shaun Bryant, Commerce City, CO
EOSS-137
KC0YA-11
- KB0TVJ-4 - Russ Chadwick, at the launch site
- KC0D-4 - Mark Patton, Foxfield, CO
- KC0VJE - Louis Perley, Nunn, CO
- KG0W - Matthew Kassawara, Fort Collins CO
- N0SPB-10 - Shaun Bryant, Commerce City, CO
- K0ANI-14 - Larry Cerney, Mobile in the chase team
- K0UT-1 - Bill Beach, Fort Collins CO
- N0EB-1 - Richard Beggs, Northglenn, CO
- N0PSJ - Christopher Holmes, Arvada, CO
K0SCC-11
- KC0D-3 - Mark Patton, Foxfield, CO
- KC0VJE - Louis Perley, Nunn, CO
- N0SPB - Shaun Bryant, Commerce City, CO
New station, KG0W, sort of. I see Matthew has iGated for us before but I've
not added him to the prediction database for iGates. Matthew, in the future your
station will be predicted for. I'm using the position for KG0W as reported on
eoss-136/137 flight day.
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.
Text Recaps
Photos
Letter
- The RocketSat team sent along a thank you letter. It is
POSTED HERE for your review.
Launch Site
Recovery Site
Audio
recorded. will be posted when edited.
Video
none yet
Data
EOSS-136
AE0SS-11
Text
Spread Sheets
Mapping Files
EOSS-137
KC0YA-11
Text
Spread Sheets
Mapping Files
K0SCC-11
Text
Spread Sheets
Mapping Files
Charts
|
