Part 4: How to contact the FAA?

It’s Legal

The first thing to know is that it is legal. It’s regulated by the FAA under Part 101 Subpart D of their regulations.

If you read the whole Part 101 regulation you’ll notice at the very start that the regulation only applies to unmanned balloons with payloads heavier than 4 pounds. Note that  you should still follow all of the rules in Subpart D to make the experience as smooth as possible.

I was a little worried about talking with the FAA. Especially since I was not sure of the phone number and requirements.

If you were to send a big balloon to Near Space, you would have to contact the right ATC (air traffic control) office. But in our case, the ATC office doesn’t actually have anything to do with small unmanned balloons.

What you need to do is create a NOTAM (Notice To Airmen).

NOTAMs are notifications issued for hazardous reasons, such as:

  • Air-shows,
  • Parachute jumps
  • Closed runways
  • Erupting Volcanos

Who do I need to call?

The ATC office I talked to gave me the phone number for Prescott Flight Service Station (877-487-6867).

I believe that they handle all the NOTAM reporting for the West side of the US. Where does West start? No idea, you should call your ATC office to make sure. I know that many people launching  balloons from different states (CA, UT, NV, …) called that specific office.

What does the FAA need to know?

What they ask you differs from one person to another.

What they asked me was:

  • Date and time of the launch ?(You need to notify the FAA between 24 hours and 6 hours before the launch)
  • Location of the launch? (City, States + GPS coordinates in both Decimal Degree and DMS formats). Converter can be found here.
  • How far it is from any major city, airports, air force base? (It needs to be 5 miles away from everything)
  • What is the ascent rate?

That was it for me. It was pretty straightforward.

However depending on who you talk to, be prepared to be asked:

  • At what time will it reached 60,000ft up?
  • At what time will it reached 60,000ft down?
  • At what time will it land?
  • Where will it land?

Theoretically, you should also notify the NOTAM station when you actually reach 60k feet up and down, if you lose communication with your balloon, and when your payload has landed. Realistically, no one cared when I called and that was fine by me.

Why 60,000ft? Because most of the air traffic flies below this altitude.

How to choose your launch location and predict the flight’s trajectory?

When looking for your launch site, you need to think about 3 main factors:

  1. You must not have any fence, phone pole, electric pole, tall tree around you.
  2. You must take into consideration the winds (when you fill the balloon and during the flight) which can carry your payload up to 200 miles away.
  3. You must take into consideration the estimated landing area.
  4. You must take into consideration the estimated flight path.

1) You really do not want all your work to end up stuck in a tree or attached to a 100ft high electric line.

2) This is critical. There are 2 web tools: This one and that one. Their prediction are, of course, not 100% similar or accurate but they will give you a good idea of the flight direction.

3 & 4) Remember that you need to be able to recover the payload quickly (Batteries might die) and be able to receive signals from the landing location. Avoid highly populated areas or areas with lakes, mountains or dense vegetation.

Note that  you need to make sure your launch site is more than 5 miles away from any airport/AFB.

MSP-1 Recovered and Successful!

Against all odds, I recovered my first high altitude balloon (MSP-1) 26 days after its launch.

I launched it on December 31st 2010 and thought I had lost it. But out of the blue, on January 25th 2011 at 7:42am, I received a manual Check/In message from the SPOT messenger sent with MSP-1.

The location reported was: 38.00134 , -120.80861. About 60 miles south east from our launch site. I scrambled a recovery operation the next day to find it.

Once arrived, my assumptions were confirmed: it was a private property used to breed cows. I went to the closest farm to inquire about the balloon and get their permission to look for it. After waiting one hour and a half and seeing no one, I started to hike up towards the location reported. I quickly understood that cows do not like to be disturbed, especially when their calves are around.

As I was walking downhill and reaching the estimated position, I saw no signs of my balloon and started to despair… until I spotted the red fabric of the parachute.

landing Location Found Burst Balloon Payload and Parachute

Note the pieces of Styrofoam everywhere. They are too small and spread out to be due to the impact.

MSP-1 used a 6 foot wide parachute for a descent rate inferior than 15ft/s. Even if it landed hard on the only rock of the field, it would have not have created so much damage.

Close-up Payload and Parachute

The Spot messenger was hanging out of the tracking module’s remains by a piece of scotch tape. You can also see what was the on-board computer system.

Close-up Payload

The payload was divided in two parts. The camera module and the tracking module.

The first was almost intact, just covered with the usual dirt and mud after 26 days in a field. The tracking module was however completely destroyed. I found pieces of Styrofoam 20 ft away from each other. Moreover I found the USB battery charger, a USB key and some cables several feet away from each other and they had been pushed into the ground.

So the only explanation I have is that the cows trampled on it a lot. It freed the SPOT messenger which somehow sent me a message.

I retrieved the SD cards and log files and here are the results: The balloon flew 96 minutes before it burst. With a theoretical ascent rate of 320m/min. We reached over 100,000 ft (30km) high.

img_0930

A few seconds after the launch

img_0964

Under the clouds

img_1054

Above the clouds

img_1298

Facing the sun at max altitude
(Note how low the sun is. It’s 4pm in December)

img_1312

Facing East getting dark

img_1356

At 100,000ft #1

img_1368

At 100,000ft #2

img_1390

Snapshot #1 from the on-board video camera

img_1391

Snapshot #2 from the on-board video camera

img_1392

The balloon burst and is now hanging from the payload

Some pictures are blurry because the payload was severely spinning  the whole time. Despite everything, most of the equipment (cameras, trackers, main PCB) can be re-used, which will be a huge cost relief for MSP-2.

I have a lot of open questions right now:

  • Why did the camera stopped working on the way down?
  • Why did the computer system stopped recording the external temperature?
  • Why was payload spinning so badly?
  • Why did the transmissions stop before the launch?

It will take me some time to collect and analyze all the data and understand what exactly happened but this maiden flight brings a lot of knowledge and exciting new opportunities!

MSP-1 Found?

Great new hope this morning!

I received at 7:42am a manual Check/In message from the SPOT messenger sent with MSP-1.

The location reported is: 38.00134 , -120.80861. About 60 miles south east from our launch site.

The location really is in the middle of nowhere. It’s in the middle of an unworkable field 1.5 mile away from the nearest paved road. There is a dirt road about half a mile away. This area is protected all along by a fence and I have seen cows on Google street view archives which makes me think that it’s a private property used for livestock farming.

Fortunately there are only 3 farms around including one less than 2 miles away.

So my plan is:

  1. Go directly to this farm tomorrow morning.
  2. Ask if they found the payload
  3. If not, whose field it is and ask its owner
  4. If the owner has not found it, ask to check out the location
  5. If not found at the location, ask at 3rd Farm
  6. If the 3rd farm has not found it, post reward poster with contact information

I hope to have more news tomorrow evening.

Part 3: How to take pictures in Near Space?

To take pictures in Near Space, you can either:

  • Program a system with servo to push the camera’s shutter automatically or remotely
  • Program the camera to take pictures automatically

The latter is by far the easiest way to take pictures in Near Space.

The most famous way to program your camera is to use CHDK. CHDK (Canon Hack Development Kit) is basically a firmware enhancement software allowing you to control additional features and options of your camera.

The tool supports a lot of Canon digital cameras. So you really want to use a Canon camera. You can find the supported list here.

Note that it’s an enhancement tool, it is non-permanent and non-destructive. You load it from your SD card and it makes no actual changes to your camera and firmware.

Installing CHDK is pretty straightforward if you have an SD card of 4GB or less. You can find the step by step instructions here.

CHDK was created to run on FAT partitions and SD cards that are higher than 4 GB run on FAT32 partitions. For 8GB SD card or larger, things get more complicated. You can find how to install it here.

Note that despite all my best efforts, I have not been able to make it work on my 8GB SD card. It just would not work. (Maybe due to my SD Card brand…)

Once installed, you can create a script to take pictures with the desired settings every X seconds until the SD card is full or until the battery dies. You can find some intervalometer scripts here. Another interesting feature is that you can save the battery voltage and the different temperatures recorded by the camera sensors (optical elements , battery and charge coupled device (CCD)) in a log file. More info under get_temperature.