Pegasus-1 Mission Photos and Video

Photo Montage Video | Flight Video | Narrated Video | Mission Prep Video | Flickr | The Miracle of Pegasus-1 | Pegasus Prequel

MarkAndMatt
Mark Nichols and Matt Long – The Pegasus Mission Engineering Team
Mark and Matt the night before flight
Matt Long (foreground) and Mark Nichols check equipment the night before launch.
Mark
Mark Nichols making a preflight adjustment with a cutting tool.
Software check
Matt Long verifying flight operations software.
Mark and Matt tie off the delivery system
Matt Long and Mark Nichols tie of the delivery system, a high altitude balloon ~6.5′ in diameter, with 165 cubic feet of helium.
LaunchCrew1
Gupreet Singh Pegasus-1 Launch and Chase Team
LaunchCrew2
Rohit Puri Pegasus-1 Launch and Chase Team
Electronics
Sensor Payload for Pegasus-1
Payload Housing
Payload Housing
Preflight payload
Preflight payload assembly
Launch site from Pegasus-1
Launch site from Pegasus-1
Exiting the clouds
Pegasus-1 exiting the clouds in lower atmosphere
Sensor package
Sensor package

13-15 miles up
Pegaus-1 13-15 miles up
Mid-Level Flight
Mid-Level Flight of Pegasus-1
Entering the Stratosphere
Pegasus-1 entering the Stratosphere
Directional Ground Station
Directional Ground Station with extended range
Mark Nichols Directional Ground Station
Mark Nichols Directional Ground Station
Location, Location, Location
Ham Radio and GPS for tracking Pegasus-1
Getting Ready
Prep the launch site, Othello, WA 01/28/2015
Dragging the drogue
12″ Drogue parachute dragging behind Pegasus-1
~85,000 feet, 2.2% atm, -60 degrees
Flight APEX on Pegasus-1 ~85,000 feet, 2.2% atm, -60 degrees
Near Flight Apex
The beauty of our planet as seen from Pegasus-1

 

 

Upper1
A planet (we think) seen from Pegasus-1 during the daytime.
V__0039
Pegasus-1 recovered one week after flight.
BalloonRelease
Balloon released and caught on camera. It will burst at 26 foot diameter.

The Miracle of Pegasus-1  | Pegasus Prequel

Advertisements

Pegasus Mission – Prequel

It was 11/07/2014 when I sent an email to Mark Nichols, my partner in this adventure, which contained on the subject line “Must do this” and a link in the body of the message. About 5 minutes later a simple response, “Absolutely”. The Pegasus Mission was born, a real-time IOT experiment in the upper atmosphere with a high altitude balloon (HAB) as a delivery system.

The first days of imagining this experiment we documented a simple set of goals and technical objectives:

  • A photo of the curvature of the Earth, the edge of the atmosphere, and the blackness of space.
  • Real-time telemetry stream of metrological information and location.
  • Demonstrate real-time control over the in-flight craft.
  • Make others participants in the flight through real-time broadcasting of the telemetry.
  • Survive (implicit goal)

Pegasus is truly an intersection of STEM fields, where the “T” is only a part of the equation. There is a considerable amount of engineering involved to make it tangible, to make it fly, to recover the craft, and get communications with the craft in real-time (milliseconds). Mark knows devices and is a craftsman with mechanical things. He can design the electrical systems, the communications packages, and craft the payload and its mechanical devices. I would take care of the aeronautical engineering of the flight and the Operational Technology. We would cross multiple fields from electrical, mechanical, aeronautical, even civil engineering and coupling that with cloud services and an Operational Technology, Piraeus, truly on the frontiers boundaries of what is possible. AFAIK, the first real-time broadcast of IOT technology from the upper atmosphere of our planet.

You could put a payload on a high altitude balloon and with some tools on the Internet likely make it fly. However, you would not know what was going to happen. Its challenge rooted in the hostile environment of the upper atmosphere. We could cover the basics and understand the flight dynamics, but you cannot test something with plus 200mph wind velocities at minus 60 degrees Fahrenheit in your basement. We would have to do our best engineering, our best craftsmanship, and take our shot.

Mark and I were discussing mission parameters on the phone one day, when I laughed up the idea of releasing the delivery system and plummeting toward the surface of the Earth, only to deploy the parachute just above ground level. Mark said, “A HALO drop. Let’s do that”, to paraphrase. . I told Mark, “if you tell me that you can get that parachute out fast enough, then I am okay with it.” Hurling thousands of dollars of equipment toward the surface of the earth faster than a car can travel was spooky proposition, but compelling. We would go for it.

Complexity was high (probably too high) and time was short. We had until that last week of January 2015 to get Pegasus-1 ready. Only a few months from when we conjured up the experiment from our collective imaginations. Mark was spending nights designing the sensor package and craft, I was trying to work through the aeronautics and prep of Piraeus, our Operational Technology. Sensors, servos, radio transmission, control console, MiFi, Piraeus, and Web site all had to work together, it was serial reliability. If everything does not work, we would lose the craft.

We were constantly buying equipment, regulators, sensors, radio equipment, cameras, antennas, meteorological balloons, parachutes. Weight is the deciding the factor, and has weight began to increase, it got more complex and more equipment was shipped to us. Our “bag” of equipment for launch would weigh about 70 lbs to get the 4 lb payload airborne.

Time had run out and we had a week before the conference. We decided to try for a test flight the week before at a remote grass airfield in Kankakee, IL. Weather conditions were suboptimal, but within range of what we thought possible. There was much work to do, not only did Pegasus-1’s electronics have to work, we would need a software interface between the transmitter/receiver and Piraeus, running in Microsoft Azure. While Mark worked on the payload assembly and testing the electronics, I would work in the software interface. We had feverishly worked 19 hour days completing our respective tasks, but still did not have an integrated system. There were also the logistical considerations, getting the helium, FAA flight advisories, permission for a launch site, etc. It’s not a backyard type of experiment, you have to plan it in advance. Completely exhausted, we had missed our launch window for the test flight. The operation would now move from central Illinois to the conference in Seattle where we would perform our session, then try to fly the following day. The weather forecast was optimal for Othello, WA on 01/28/2015. We would attempt to resolve any remaining issues and get airborne in the treeless environment of eastern Washington State.

-Matt Long

Matt.Long@microsoft.com

Photos and Video | The Miracle of Pegasus-1

The Miracle of Pegasus-1

The Pegaus-1 Mission launch schedule 01/28/2015 from Othello, WA at 11AM PST and was delayed several hours. We eventually got airborne mid-afternoon. Several technical problems occurred, e.g. the Ham radio was not operational. This was the backup location system in case we lost the primary GPS, and now we were flying with only a single system to locate the craft. The tracking devices were a directional ground station and an omnidirectional mobile station that we used in the chase vehicle. The ground station had long theoretical range to maintain contact, while the mobile station was much shorter in range. Early in the flight the ground station, experienced some issues and lost contact with Pegasus-1. The shorter range mobile unit was all we had to maintain contact with Pegasus’s location. We had spent many hours trying to make sure we would have contact with Pegasus-1; otherwise we would lose her in a lonely field in a lonely place. Now we were hanging by a thread with only the primary GPS and the mobile unit. As Pegasus ascended and turned due East, the ground station came back online and we had 2 points of contact with the craft. Some relief, but still living only on primary GPS.

The telemetry stream was amazing as we could see the information streaming in every 2 seconds from Pegasus-1. The altitude on the GPS was not updating as fast as we expected, which also led to suspicions on the accuracy of the primary GPS. Was Pegasus-1 where we thought it was? The low hanging cloud layer gave us no visual on the craft, we just had to go with what we had. The ground units pushed the telemetry into Piraeus, our Operational Technology, where a Web site could instantly display not only the telemetry, but also the location of Pegasus-1 on Bing Map. Our chase team used the Bing Map updates to keep positioning and maintaining contact. This was very entertaining.

We were expected a turn to the West in the upper atmosphere, almost reversing the course that we had traveled. This occurred as expected with a slight WNW heading from the lower altitude E heading. We had purposely not expected to take Pegasus-1 to burst altitude, instead we intended to control the descent with a remote release of the delivery system. As we moved further to the West and slightly North the craft was tracking further from the main road, US HWY 26. Given that the altitude had reached mission objectives and that ruggedness of the side roads, we decided to release the balloon and begin the descent stage. Our descent was to be a HALO drop to about 1,000 meters above the surface of the earth where the main parachute would be deployed. Our tiny 12″ drogue chute would keep Pegasus-1 in a vertical position to maintain contact during the rapid descent, expected to take 10-13 minutes from the apex of the flight. We released the delivery system and began the descent stage dropping at 212mph from about 85,000 feet.

Only a few seconds later, at 75,000 feet, we lost primary GPS, but kept streaming the other telemetry data. The chase vehicle was positioned on a gravel road approximately 1.5 miles to the SE of Pegasus-1 when we lost GPS. Our strategy was to move either North of South to intercept, but without GPS and the low hanging cloud layer, we had to get a visual. Time had passed and we continued to look for the craft in the agricultural fields East of Othello, WA. It was going to get dark and we needed to back to launch site and pack up for the drive back to Seattle. We had lost Pegasus-1, but had proved the technology Piraeus, command and control, much of the craft design, and we did have the telemetry…but we didn’t have the video from the onboard GoPro camera or our craft. Now packed up and getting dark, we began the 3+ hour drive back to Seattle, disappointed without the recovery of the Pegasus-1.

Several days later I was reviewing the telemetry and noticed an abnormality. It appeared the primary GPS had come back online with only 30 seconds of flight time left. The chase team was scanning the horizon for signs of the craft when this occurred. We would not have noticed, nor expected it. Could Pegasus-1 have called for help at the last stages of flight? I considered this a remote possibility and began to check path, air pressure, and other telemetry to determine whether this “burp” of location information could possibly be valid. The location “burp” was in a direct line from where the GPS cut out at 75,000 feet and in the expected path. Careful analysis lead us to believe that Pegasus-1 was about 1.5 miles due North of where we had stopped the chase vehicle. The probability cone as only about 600 feet from the last location. Had we found where the craft actually rests?

Our excitement was high and Mark Nichols, my partner in this adventure, had decided to stay an extra day in Seattle and make the 250 mile drive back to the site and try to recover Pegasus-1. He called me and said he was standing on the spot, but no sign of the craft. He wandered through the fields for a time, then decided to drive a short distance to a nearby business to see if anyone had seen a UFO in the field. The business informed him that they knew nothing and he began his disappointing drive back to Seattle. Mark pulled out of the business toward the same point that he had started and noticed some orange out the left side of the automobile. He stopped. He saw some green, it looked like trash in a field. If the drogue parachute was orange and white, what could be green. The shroud lines of the main parachute!!! Mark approached and there it was. Pegasus-1 fully intact and only 800 feet from where we thought it to be. The Operational Technology, Piraeus, not only was critical to real-time flight operations and distributing to others to view, it also saved Pegasus-1’s dying breaths of GPS location.

We now have the telemetry and incredible video of the flight. We are compiling and condensing the video about this amazing story to release soon.

While Mark and I may have been the tip of the spear for the Pegasus Mission, nothing happens with the help and support of others. Our launch and chase team (Rohit Puri, and Gupreet Singh) and the unwavering help and support of Microsoft Research’s Orleans team that guided us for over a year in the construction of Piraeus, the Operational Technology that puts the real-time IOT into the Pegasus Mission. It takes a village, a village of dreamers and innovators.

Pegasus-1 at 85,000 feet, 2.2% atm, -60 degrees
Pegasus-1 at 85,000 feet, 2.2% atm, -60 degrees

-Matt Long

Matt.Long@microsoft.com

Photos and Video | Pegasus Prequel

My thoughts on innovation compiled > 1 year ago, what I believe … here