03/10/2014 09:59 (CDT): The picture below and a link to video of the landing
Montclair Scientists |
by Bob Haldeman forwarded to EOSS by Jim Langsted |
URL: ftp.eoss.org
username: photos@eoss.org
password: photosFor details on how to use FTP and general information about sending in materials see:
Not a compensated flight
Flight Coordinator: Jim Langsted
LAUNCH DATE: February 22nd, 2014 (wx delay +1 day)
LAUNCH TIME: 07:10 am MST (14:10 UTC)
LAUNCH SITE: Windsor, CO (Driving Directions to Windsor Launch Site)
E0SS-193 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
Launch Site - Windsor ----------------------- Launch Point: 40.47367� lat. -104.96233� long. Grid: X=-62.00 Y=70.61 Ascent Rate: 1329 feet per minute Descent Rate: 1000 feet per minute Altitude: 4931 feet Predicted Landing Site ----------------------- Landing Point: 40.15473� lat. -103.1854� long. Grid: X=31.5 Y=48.6 Altitude: 4589 feet Flight Time: 118 Minutes Bearing: 102.7� True Range: 96.1 Mi. Actual Landing Site ----------------------- Landing Point: 40.12802� lat. -103.20843� long. Grid: X=30.3 Y=46.7 Bearing: 103.9� True Range: 95.39 Mi. Difference from Predicted to Actual Landing Site -------------------------------------------------- Bearing: 213.4� True Range: 2.207 Mi.
Final Pre-Flight Prediction is available here
Prediction History is available here
Tracking and Recovery Frequencies
Tracking and Recovery Operations
Ground Stations Frequencies
EOSS-193 Balloon Payload Frequencies
EOSS-193
Balloon Manufacturer | Totex |
Balloon Type | latex |
Balloon Size | 1200 g |
Neck Load | 11.3 Lbs. |
Neck Lift | 14.7 Lbs. |
Ascent Rate | 1329 fpm estimated |
Estimated Burst Alt | 90,000 ft. ASL |
Descent Rate | 950 fpm estimated |
Parachute | 5 ft. |
EOSS payload qualifications
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-193,AE0SS-11
- AD0HC - Garold Maier, Pueblo, CO
- AE0SS - Nick Hanks, Ground Station (using club callsign)
- K0JSC-1 - Jeffrey Carrier, Ca�on City, CO
- KD0MBL - Neal Tew, Pueblo, CO
- KD0SEM - Dave Lanning, Hudson, CO
- N0EB-1 - Richard Beggs, Thornton, CO
- N0SPB - Shaun Bryant, Commerce City, CO
EOSS-193, KC0UUO-11
- KC0D-2 - Mark Patton
- KD0MBL - Neal Tew, Pueblo, CO
EOSS-193, N0IX-11
- AE0SS - Nick Hanks, Ground Station (using club callsign)
- N0SPB-10 - Shaun Bryant, Commerce City, CO
In addition to our crew of regulars, welcome to Pueblo and Canon city stations. Thanks for the coverage. The FAA always likes a good reliable track and you guys helped out with that on this flight.
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.
Hello Trackers!
We will be launching our annual EOSS qualification flight on Saturday Morning, 2/22 with a weather date of 2/23. It appears this will be a very long flight heading over 100 miles downrange to about 10 miles east of Akron. Nick and Mike have advised me that Jack Roland, KE0VH, has installed an APRS Digi-peater (KE0VH-4) near Akron. EOSS thanks Jack for taking that initiative. We may need to get an early start so we can be closer to the prediction by 7:00. Sorry Jim, KC0RPS will not join us. Hope to see you at the launch site?
As a reminder, at the recovery site, be sure to meet and greet the 4th grade students and learn about their experiment. These are students from Montclair School of Academics who are flying an �Enrichment Biological� environmental survival experiment. We thank Jim, KC0RPS for persisting with their teacher Karl Horeis, KB7UPC. Let�s make it fun for the young scientists.
Shaun, N0SPB plans to Shadow N0JPS and W9CN and fly his �Quadcoptor�. It is a DJI Phantom Vision with a 1080p camera for recording and a lower resolution down link for live view. Once he has a good idea of the landing location, he will launch. As it stands he has about 1 hour of time in the air in 25 minute segments. Should be interesting for the students. We will need to hilltop the RMRL 449.450 repeater to reach the ground station operators. I will take the responsibility to straddle the unknown second repeater and the RMRL repeater as best I can. Stay tuned for some research on the second repeater. Ideas? Here�s the scoop. Please advise Rick, N0KKZ (for the Web site updates) and me of any omissions or corrections.
For breakfast, we can convene at the McDonalds in Ft Morgan at 5:45. Post-flight meal will probably be destined for the Digger�s in Brush where we get the finest service in eastern Colorado.
Tracking and Recovery Grid
TrackPoint Grid Reference Location
Grid X
Grid Y
Last Chance
10 20
Grid Test N 39.800, W103.100
36.1
24.1
Tactical Call Signs
Tactical
Call sign
Name
Notes
Alpha
WA0GEH, KC0D
Marty, Mark
Tracking and Recovery Coordinators (HF)
Bravo
W9CN, N0JPS, KD0JIT
Mike, John, Miles
Tracking, Recovery
Charlie
KE7KCK
Tom
Tracking, Recovery
Delta
K0SCC, N0IX
Stephen, Doug
Tracking, Recovery (HF)
Echo
KD0SEM
Dave
Tracking, Recovery
Foxtrot
WA9WWS, KD0OXS
Don, Dan
Tracking, Recovery (HF)
Golf
KC0L
John
Tracking, Recovery, Friday Net Control
Hotel
KB0LP
Dave
Tracking, Recovery (HF)
India
N0NDM, W0CBH
Larry, Benjie
Launch, Tracking, Recovery
Juliet
W0NFW, N0ZTO George, Greg Tracking, Recovery
none
Launch Site
Landing Sequence
Recovery Operations
recorded by not uploaded
Pre-Flight Prediction Files
Findu Full Packet Log for vicinity of flight
EOSS-193 AE0SS-11
Text
- eoss193/eoss-193_ae0ss-11_findu.txt - Findu Log
- eoss193/eoss-193_ae0ss-11_findu_ts.txt - Findu Log with findu timestamps
- eoss193/eoss-193_ae0ss-11_kpc3_airborne.txt - Airborne only
Spread Sheets
- eoss193/eoss-193_ae0ss-11_Flight_Data.csv - airborne only Log ripped to spreadsheet format
Mapping Files
- eoss193/eoss-193_ae0ss-11_recap.ptm - MapPoint file of the above recap
- eoss193/eoss-193_ae0ss-11_track.kml - Google Earth Track of the flight
- eoss193/eoss-193_predict_track.kml - Google Earth Track of the predicted flight path
EOSS-193 KC0UUO-11
Text
- eoss193/eoss-193_kc0uuo-11_findu.txt - Findu Log
- eoss193/eoss-193_kc0uuo-11_findu_ts.txt - Findu Log with findu timestamps
- eoss193/n0ix_EOSS193-KC0UUO-11.TXT - on board log file
Mapping Files
- eoss193/n0ix_EOSS-193-KC0UUO-11.kmz from the on board log file
EOSS-193 N0IX-11
Text
- eoss193/eoss-193_n0ix-11_findu.txt - Findu Log
- eoss193/eoss-193_n0ix-11_findu_ts.txt - Findu Log with findu timestamps
- eoss193/n0ix_EOSS193-N0IX-11.TXT - on board log file
Mapping Files
- eoss193/n0ix_EOSS-193-N0IX-11.kmz from the on board log file
Charts
by Nick Hanks, N0LP