Blogs

Hello everyone,
a year and a half ago came Multipilot 1.0 an inertial platform for applications and semi-professional hobby. After the excellent results obtained from the marketing of these cards, and participation in development projects as open source and Aeroquad Arducopter and 'born www.virtualrobotix.com community.
Today our community is proud to present the evolution of our project: Multipilot 2.0 ST.

Stay tuned :

The characteristics of Multipilot 2.0 are:

• Hardware:
  • ARM7  Cortex-M3 processor STM32F103VET6. 72 Mhz
  • Flash 512 Kbytes RAM 64 Kbytes
  • 16-bit Timer 4
  • SPI 2 (ADC Interface, MicroSD connection)
  • I ² C 2 (First I2C (sensor), Second I2C control until ESC 12)
  • USART 5 (GPS, DEBUG Console, XBee Pro Telemetry)
  • USB 1 (Upload Firmware, Debug Console, Power Board for Debug)
  • CAN 1 (Interconnection with Professional ESC 1 Mbit update rate)
  • 6 PWM Output Bit 16 (ESC / Servo Control)
  • 8 PWM Input 16 Bit (RC Input Channel, accept PPM SUM)
  • 8 Analog Input 12 Bit.
  • Professional 4 layers PCB.
  • DC: DC 30 V (6s Lipo): 5 volts and 3.3 volts
• Sensor Board:
  • Diydrones OilPan . (High quality entry level board)
  • LN Professional Sensor Board: 3 Axis Accelerometer, 3 Axis Gyroscope, 3 Axis Magnetometer , 10 HZ Gps ,   High Quality Sensor for certify professional application.
• IDE and Development tools:
  • Arduino IDE.
  • Arm GCC Toolchain.
  • Fully compatible with arduino wiring language.
• Firmware:
  • On this platform will be available a lot of RC library developed by Virtualrobotix and Diydrones community.
  • Standard software will be an improved revision of Arducopter , Ardupilot , Multiwii , Aeroquad . The first revision of code will be Arducopter NG .
  • MultiFox Rev 4 special  Arm Edition.
• Special Feature :
  • Multipilot 2.0 is fully compatible with ArduPilotMega DiyDrones Board.
  • OEM revision of Multipilot 2.0 available.

A few weeks ago I was looking for a topic with pictures of the Project RQ-11 Raven in its entirety along with some close up shots of the fuselage but couldn't find one. To help you guys out, especially anyone here thinking of buying this model, I've decided to post some pictures of my almost finished Raven. 

A few comments about it:

+ there is barely enough wire provided so when you build, don't use more of it than you actually need (after using every single bit of it I ended up with only about 3 inches left over)

+ when you install the wires to the servos and the back, make them as tight as you can because if they're loose, you'll lose the ability to do some precise movements

+ the back pieces look like they might slide out, but they won't as long as you use a decent amount of epoxy on each side (not too much either because the wires will rub against it)

+ the two black screws holding the wing attached to the fuselage aren't enough, you might want to add a bit of epoxy under the wing (sure you lose the ability to detach the wing but there is no other way to reinforce the wing's attachment)

+ be careful when putting screws through the fuselage because it can crack if you put too much pressure when making the hole (I have a small 1 inch crack near the cover for the servos on the bottom)

+ this thing looks really nice and is quite strong, I think it can go through a rough landing without breaking or cracking

+ there is no paint job like others have commented, it's just a very light plastic film over the entire body and wings that is very delicate and is easy to peel off accidentally

+ there is a ton of room inside (measurements are 19 inches long, 5.5 inches wide, 3 inches height) and it is just empty space for the most part (I have a 4000mAh 3S battery, I think I can fit 4 of them inside easily along with all the other required parts)

Showing the entire plane (the bottle of water is there just for the size comparison):

Showing the propeller attached to the motor (it doesn't work as I'd like it to so I'll be changing it a bit):

Showing the amount of space in the front:

Showing the amount of space in the back:

Showing the servos installed:

I've now had a chance to see and test virtually all the EasyStar clones out there, so this post will compare them all and make recommendations. There are a few others out there by different names, but I think most are just rebadged versions of the ones below. Bottom line: I think the HobbyKing Bixler (see below) is the best option.

First, the baseline: The classic Multiplex EasyStar ($72 for basic airframe, no electronics)

Pro: Lots of cockpit room, tough, flies well.

Con: Only 3 channels, comes with terrible brushed motor that must be upgraded, rudder too small and must be enlarged. Quite expensive once you add all the stuff you need. See our post on upgrading it here.

-----------------------------------------------------------------------------------------------------------------------------------------

HobbyKing Bixler

It's available as a kit, a RTF with a 4 channel radio, and an ARF without radio. I recommend the ARF version, which is just $52. Add a 20a ESC, battery (plus battery and motor connectors), a charger, a 7ch RC radio and the APM 2 autopilot and you've got a UAV for under $500.

Some of the advantages of the Bixler, compared to the EasyStar and the other clones:

• Ailerons
• Big cockpit area, with tail servos on the outside
• Decent brushless motor
• Available in ARF form with servos installed but not a useless radio that you have to throw away
• Inexpensive

This is a comparison the Bixler cockpit (left) with the EasyStar (right). The Bixler has a bit more room.

-----------------------------------------------------------------------------------------------------------------------------------------

Dynam HawkSky ($99 with everything you need: servos, brushless motor, LiPo and charger). See our review here.

Pro: As much interior room as the EasyStar, has ailerons, comes ready to fly.

Con: Plastic motor pylon is noisy. Included FM RC system should be thrown away and replaced with proper 7+ channel digital radio.

-------------------------------------------------------------------------------------------------------------------------------------------

Xen Phoenix ($48 for airframe with brushless motor. Servos etc not included). See our review here.

Pro: Brushless motor and ailerons

Con: Fuselage is too narrow. Not enough room for autopilot electronics. Fragile. Weird four-bladed prop.

-------------------------------------------------------------------------------------------------------------------------------------------

Sky Surfer ($130 with everything you need: servos , brushless motor, LiPo and charger, 2.4 RC system)

Pro: Comes with digital RC system (only 4ch, however, so must be replaced for UAV use). Solid design w/ailerons

Con: Sadly, the design has changed and what appears in the product listing to be servos on the outside of the body, like the EasyStar and HawkSky, are now on the inside, taking up valuable interior room. Here's a picture of what the current cockpit is actually like:

------------------------------------------------------------------------------------------------------------------------------

AXN Floater ($50 with servos and brushless motor). Formerly known as the Cloud Sky

Pro: Inexpensive, solid design w/ailerons

Con: servos on inside of cockpit like SkySurfer, robbing interior of valuable room for electronics. Narrow nose makes 2200 LiPo a tight fit.

Hi eveyone,

I received my first order from Batch PCB yesterday, it was my first foray into an actual drone. I designed the PCB myself, from scratch, so I was pretty proud when I plugged it in and it started working. It has been designed around the ArduIMU+ V2, the Locosys LS20031, an OpenLog, and of course, an Xbee.

The board is just a small step up from the Proto-Shield (SparkFun) version I built a while ago, except it has some capacitors, filtering the 5V power supply, and a voltage monitoring circuit.

I built it in the late hours of the night, and had it running my home-made auto-pilot code by 2am. Right now it has the same functionality as the proto-shield v1 I built before, except that the GPS is fully functional, and it is correcting the aileron and elevator values, with gains, to the required roll and pitch angles.

BTW if anyone has any constructive critisism, feel free!

I have already learned a few lessons from making this board, and V2 is already on the way.

Tell me what you think!

Many years ago, I tried building a model heli autopilot out of some old mouse position sensors, an 8031 micro, and my Hirobo shuttle.  The whole thing seemed to work on the bench, but quickly broke a few blades when I slammed the throttle on for an air test.  Such is life.

Now - its happening all over again, but this time, due to the excellent work done by the Ardupilot teams, I expect much better results.

So I got my APM for xmas, and its taken a month of playing to decide to put into a heli (as opposed to one of my planes).

So far, I have the following setup.

• APM with the shield.
• GPS (mediatek)
• EZ1 sonar sensor for low altitude above gnd. - Landing / takeoff assistance.
• Airspeed sensor with pitot tube (designed for plane but I think I'll put it on the heli too)
• Magnetometer
• Custom rotor RPM sensor

Airframe is Gohbee Stinger 50 (AKA JS models TZ50) - Raptor copy.

Radio is Spektrum DX7. RX is AR7000 with header board removed.

The plan is to build an autopilot system based on Arducopter, that lets you fly the @&#^$ out your heli, and not crash - regardless of your level of experience. (mine is pretty average, but I'm determined to get better).  This will be the tool for the job I hope.

When I get the hang of this blog thing, I'll post some pickys.

I finally got my mods to a point where I'm comfortable with others testing. I've only been using it with XPlane seen as it is so dang cold and snowy outside. You need to define OSD_PORT and OSD_MODE_CHANNEL. OSD_MODE_CHANNEL will allow you to assign a toggle switch to turn on and off the OSD overlay while in the air.

Some of the features included:

• Auto-home saving from init_home()
• Distance and direction to home
• Artificial horizon
• GPS LAT & LONG
• Control mode and next waypoint + distance (working on relaying takeoff, land, etc messages)
• Overlay on/off via Tx switch

Here are the Remzibi Mods:
+----------------+
|  APM_Config.h  |
+----------------+
#define OSD_PROTOCOL        OSD_PROTOCOL_REMZIBI
#define OSD_PORT            3
#define OSD_MODE_CHANNEL    7

+---------------------+
|  ArduPilotMega.pde  |
+---------------------+
Medium loop, case 3:
#if OSD_PROTOCOL != OSD_PROTOCOL_NONE
        print_osd_ahrs();
#endif

Slow loop, case 1:
// Output OSD Data slow loop
#if OSD_PROTOCOL != OSD_PROTOCOL_NONE
        print_osd_data();                       
#endif

// Read OSD Mode Switch
#if OSD_PROTOCOL == OSD_PROTOCOL_REMZIBI
        read_osd_switch();
#endif

+---------------+
|   defines.h   |
+---------------+
After GPS type defines:
// OSD type codes
#define OSD_PROTOCOL_NONE       -1
#define OSD_PROTOCOL_REMZIBI     0

+----------------+
|  commands.pde  |
+----------------+
After line 251, bottom of init_home():
// Save Home to OSD
// ----------------
#if OSD_PROTOCOL == OSD_PROTOCOL_REMZIBI       
        osd_init_home();
#endif

And finally add the following file into your APM folder:

OSD_Remzibi.pde <-Version 1

OSD_Remzibi.pde <-Version 2

And for my Remzibi layout:

APM.bin

Some nice custom foam design on the plane and camera pod here. Looking like they're going to be selling them. 

This is my school project as a Senior in high school, I am  designing, building, and flying my own UAV.

I will record short videos to document my project, the following videos:

sUAS News started as a way to get what I was doing and a couple of friends out into the world. I am sick of the endless military press releases that I keep posting. Sort of interesting but to a point.

Does the very lack of stories of civil sUAS doing useful things mean there are very few actually doing that?

If you are making waves doing something then drop me a line gary@suasnews.com

At very least your story will appear in the news feed on the right of this very site

Lets hear whats actually happening, GCS, airframes or photo jobs, I don't mind what it is.

Clearly those of you in the USA are on a sticky wicket advertising your commercial activites, not that any of you would be doing anything like that anyway ;-)

G

Follow sUAS News on

LinkedIn

Twitter

Facebook

I've got two way telemetry working on my Ardustation, talking to the ArduPilot Mega (APM) using the standard BinComm protocol (GCS_PROTOCOL_STANDARD). So far I can edit PID values and check essential mission following data, along with the standard summary of attitude, location and heartbeat data.

This should make life a lot easier, being able to tweak the plane whilst airborne and seeing what it's up to - without being required to sit down with the laptop.

To achieve this, I've modified the code in the ArdustationM branch that Michael Smith created. Michael has written an excellent bit of code here and already had the one way telemetry showing the main status page. I've also updated it to use the APM_BinComm library, keeping it in line with the latest APM code. 

The APM code was also modified; I merged the 1.0 Beta with the relevant bits from the BinComm branch and coded up broadcasting of values and setting of PID values.

I hope to add more functionality in the future, but will wait until I have used it in the field before deciding on what features will take priority!

--- Update ---

Here's the code

ArduStationM.zip

Most of my additions won't work on the stock APM beta code as it doesn't receive data. Here are my additions to the APM BinComm code

GCS.h GCS_Standard.pde

Or download the whole of my directory, less your config file

ArduPilotMega.zip

--- Update 2 ---

I've now used the Ardustation in the field and it's everything I could have wanted. Had my plane flying a mission on repeat, the transmitter on my neck strap and the Ardustation to tune the PID values. No more landing to plug into the laptop. It's also great not guessing what waypoint its headed for and remembering what it's going to do next, just glance at the display!

Here's a picture of my enclosure. Not my neatest drilling, but works nicely :-)

I have clinical multi-projectitis.

It's incurable.

After seeing the GRASP lab video sof quads literally jumping through hoops, I HAD to make one of my own.

The beginnings: 

Although everyone else seems to be going open-rotor, I want zero collateral damage to people, pets, and the living 

room walls, so I decided on a ducted-fan design.

4 EDF combos from Hobby King

https://www.hobbyking.com/hobbyking/store/uh_viewItem.asp?idProduct=11166

Combined thrust of 4400g.

Combined mass of 424g.

The 5Ah 4S 40C LiPo from my currently grounded Swift Heli:

https://www.hobbyking.com/hobbyking/store/uh_viewItem.asp?idProduct=10307

Mass: 578g.

For testing, the initial fuselage is a chunk of extruded poly insulation.

5 Deans connectors and a new soldering iron later (the old 30Watt one couldn't make a decent joint for the wiring harness), this is the result:

I christen her "The Ugly Pink Quad."

At present, she's brainless.   I just did a test with a little solderless breadboard sending the throttle signal to all EDFs simultaneously and, not surprisingly, things were learned:

1) With 4400grams of max thrust pushing 1220grams of pinkness, it only took about 1/3rd throttle position to hand-hover.

2) It wants to rotate.

Next issues: Basic landing gear (The motors are outrunners), basic brains, and an IMU 

Dear Friends,

two years ago i developed a closed source Brushless Controller. It's based on ATmega 8 and support i2c,PWM,Serial Port. The ESC support until 20 Amp and the electronic is present a shunt resistor to evaluate the quantity of energy that the motor need in realtime.

So now I would to port a Arduino bootloader to this board and develop an opensoure code for it.

But i need help for this project ... There're some people that would join me in this project ? That's is good choice for Multipilot 2.0 / Ardupilot 32 platform.

Regards

Roberto

From I Heart Robotics: "More great work from Quentin Lindsey, Daniel Mellinger, and Vijay Kumar from the GRASP Lab at the University of Pennsylvania. They now have their quadrotor helicopters working in teams and building modular towers. This is from the same lab that built the acrobatic quadrotor capable of aggressive maneuvers."

March 27 - April 1, 2011

 Israel Unmanned Systems 2011

It's a long story that I will try to summarize. The latest revision of the magnetometer that had some design improvements including making it easier to manufacture to boost production using the pick and place machine, but that also came with a weird issue. 

When I was developing the APM Oilpan we had some noise issues on the 3.3V line caused by a missing 200K resistor on the Voltage Reference pin on the 5V side of the I2C translator (obviously this board never saw the light), if you don't populate this resistor it will introduce terrible noise on the line and cause the analog sensors to fail, this bug was found by Jose Julio (Thanks!). 

A curious thing is that the first version of the magnetometer didn't have this resistor (it worked fine anyway), in the second revision i tried to do the right thing and follow what the datasheet suggested so I added the 200K resistor (same that caused terrible issues on the Oilpan because we didn't use it), expecting some improvement. 

When the boards arrived from the fab, we assemble some and they appeared to be fine, Cindy (our testing lady) added the observation that the sensors were slightly noisier, but we didn't listen (Sorry Cindy!). For the pressure of months of long waits we just released the boards. In just matter of days we received tons of complains.   

After days trying to solve the problem we finally discover that the 200K was the issue. The 2nd issue we have discovered but is not critical is that the voltage regulator will not perform well if you don't suck enough current from it, the magnetometer uses very, very low power and the best practice to solve this is to add a 200 ohms resistor from the 3.3V to GND to add enough load to it (Thanks to Nathan Siedle for this trick), we are not doing this right now, so you will see a power supply output of 3.7V, but the performance is perfect. 

All new boards have this fix, but for those who already got affected boards I would like to give a sincere apology to all our custumers and I would like to offer two resolutions to this problem:

1.- Send it back and we will repair it for you. We will cover all the shipping expenses. Please contact custumer support for more info: help[@]storediydrones.com 

2.-Repair it yourself (DIY) quickly and safely by following the following instructions.

NOTE: Before you repair your board, check if your board has a resistor marked "204". This means it has not been fixed (see the first two photos of the repair steps for reference), and if you see instead a resistor marked "0" your board is fine.

If you choose to repair it yourself and something gets messed up, you cannot then return the board. If you are unwilling to take this risk or are feeling a little uncertain about your soldering ability, do not do this. Just return the board for replacement.

1- Locate the 200k resistor, it is marked with "204."

2- With a soldering iron, heat either of the resistor's solder points
and wait a few seconds for the heat to reach both solder points. Weak solder irons may not work very well. 

3- Without applying too much force as no not damage the pads, gently
nudge the resistor with the tip of the soldering iron. 

4-The resistor

5- Make sure you the pad are still there. 

6- To create the solder bridge place the tip of the soldering iron
over both pads and apply enough solder to brigde the pads.

7- If the solder ball is touching both pads then your are done. 

Lots of good stuff in this report, titled "Factory @ Home", which was commissioned by the White House Office of Science and Technology Policy. 

It ends with these recommendations:

This report recommends the following actions be taken.

1. Put a personal manufacturing lab in every school

2. Offer teacher education in basic design and manufacturing technologies in 

relation to STEM education

3. Create high quality, modular curriculum with  optional manufacturing 

components

4. Enhance after school learning to involve design and manufacturing

5. Allocate federal support for pilot MEPs programs to introduce digital 

manufacturing to regional manufacturing companies

6. Promote published and open hardware standards and specifications

7. Develop  standard file formats for electronic blueprints design files

8. Create a database of CAD files used by government agencies

9. Mandate open geometry/source for unclassified government supplies

10. Establish an “Individual Innovation Research Program”  for DIY entrepreneurs

11. Give RFP priority to rural manufacturers that use personal manufacturing

12. Establish an IP “Safe Harbor” for aggregators and one-off producers

13. Explore micropatents as a smaller, simpler, and more agile unit of intellectual 

property

14. Re-visit consumer safety regulations for personally-fabricated products

15. Introduce a more granular definition of a “small” manufacturing business

16. Pass the National Fab Lab Network Act of 2010, HR 6003

17. “Clean company” tax benefits should include efficient manufacturing

18. Offer a tax break for personal manufacturing businesses on raw materials19. Fund a Department of Education study on personal manufacturing in STEM 

education

20. Learn more about user-led product desig

From the released ARC document:

The AMA recommends removing section 3 in its entirety, leaving only the CBO (AMA) rules.

Note that FPV and atonomous systems are fully acceptable within LOS. The AMA prohibits all autonomous and FPV is allowed only with a budy box. "not operated in accordance with accepted standards" means nonAMA members.

"3. Model Aircraft Not Operated in Accordance with Accepted Set of Standards

3.1 Applicability
The following general requirements and limitations apply to Model Aircraft which are not perated in accordance with an FAA accepted set of standards, but are operated by hobbyists for the sole purpose of sport, recreation, and/or competition.

3.2 General Requirements
(1) Model Aircraft shall be flown in open spaces and in a manner that does not endanger the life and property of others.
(2) Model Aircraft shall yield the right of way to all manned aircraft.
(3) Model Aircraft shall not interfere with operations and traffic patterns at airports,heliports, and seaplane bases.
(4) Model Aircraft shall not be operated at locations where Model Aircraft activities are prohibited.
(5) Model Aircraft are limited to unaided visual line-of-sight operations. The Model Aircraft pilot must be able to see the aircraft throughout the entire flight well enough to maintain control, know its location, and watch the airspace it is operating in for other air traffic. Unaided visual line-of-sight does not preclude the use of prescribed corrective lenses.
(6) Model Aircraft shall be designed, equipped, maintained and/or operated in a manner in which the aircraft remains within the intended area of flight during all operations.
(7) Model Aircraft pilots may not intentionally drop any object from a Model Aircraft that creates a hazard to persons or property.
(8) Model Aircraft shall be operated in a manner that respects property rights and avoids the direct overflight of individuals, vessels, vehicles, or structures.
(9) Model Aircraft shall not be operated in a careless or reckless manner.
(10) Model Aircraft pilots shall not operate their aircraft while under the influence of alcohol or while using any drug that affects the person’s faculties in any way contrary to safety.
(11) Model fixed-wing and rotorcraft aircraft shall not use metal-blade propellers.
(12) Model Aircraft shall not use gaseous boosts.
(13) Model Aircraft shall not use fuels containing tetranitronmethane or hydrazine.
(14) Model Aircraft shall not use turbine-powered engines (e.g., turbo-fan, turbo-jet) as a propulsion source.

3.3 General Limitations
(1) Model Aircraft shall not exceed 55 pounds (lbs).
(2) Model Aircraft shall remain clear of clouds.
(3) Model Aircraft will not operate in Class B airspace without the permission of the ATC authority.
(4) Model Aircraft shall not be operated within 3 NM miles of an airport, heliport, or seaplane base without the permission of the ATC authority or airport manager.
(5) Model Aircraft shall operate in close proximity to the ground, at or below 400 feet (ALG) above ground level, and shall at all times remain below and well clear of all manned aircraft.
(6) Notwithstanding the above limitations, Model Aircraft weighing less than or equal to two lbs incapable of reaching speeds greater than 60 miles per hour (mph)
(52 knots), and powered by electric motor or mechanical stored energy (e.g.,rubber-band powered) may operate within 3 NM of a military or public-use airport or heliport; if they remain a safe distance from the airport or heliport, remain well clear of all manned aircraft, and remain below 400' AGL.
(7) Model Aircraft will not be flown at an airspeed that would cause the aircraft to
inadvertently leave the prescribed maneuvering area. !
(8) Model Aircraft cannot launch pyrotechnic devices which explode or burn.
(9) Excluding take-off and landing, no powered Model Aircraft may be flown closer than 25 feet to any individual, except for the pilot and the pilots helper located at the flight line.

The AMA rules may well end up being the only FAA approved rules for recreational use of an sUAS (AMA membership may become mandatory as well).

This is the AMA rule for FPV:

"First Person View (FPV) Operations

1. An FPV-equipped model must be flown by two AMA members utilizing
a buddy-box system. The pilot in command must be on the primary
transmitter, maintain visual contact, and be prepared to assume
control in the event of a problem.

2. The operational range of the model is limited to the pilot in command’s
visual line of sight as defined in the Official AMA National Model
Aircraft Safety Code (see Radio Control, item 9).

3. The flight path of model operations shall be limited to the designated
flying site and approved overfly area.

4. The model weight and speed shall be limited to a maximum of 10
pounds and 60 miles per hour."

This is their official stance on autonomous and semi-autonomous flight:

"Autonomous flight, as it pertains to RC operations under AMA’s programs, infers usage of a navigational system that allows the model to fly a pre-determined mission from point A to point B, point C, etc.  Autonomous flight is navigating a model aircraft autonomously."

Note that the last sentence is a tautology and not a definition. Autonomous is autonomous? Big help there. Hopefully this kind of language will be a red flag to the FAA that the AMA does not  know how to write the proper documentation required by law for CBO standards. They do not even know the definition of the centuries old word "autonomous".

Hi all.  Been lurking around here and the RCGroups site for a long time and finally got around to actually starting a multi-copter build.  I built my first Sig Cadet way back in the day, but got caught up doing other things for about 20 years.  Back to RC now and loving it.  And thanks to all in and around these projects that are making the community tick.  Open Source only works if you have kick ass people like Chris and a big team of supporters.  Nice job!

The MCopter is built on an RC Carbon frame from RC Hobby Helicopter (Thanks John!) and will be running 4 Hacker 20-22L's with 10 x 3.8 props.  Once I get the four motor version running we may bump it to eight in coax config to have more margin.  I have ArduPiratesNG on the APM right now so I can test the two axis camera mount with the GoPro Hero.  Once we get closer to the first test flight I'll decide which code base we fly.

Here's a few pics from Flickr

UPDATE: 2/16/10

Finally got the first version built and went for a maiden.  I am flying the latest ArduPirates code, but I did not do any PID tuning as I was tired of waiting and wanted to see how close it was stock settings.  This version is still a bit under-powered so I am going to switch from 10x3.8 to 10x4.7 SF props to see if it will help a bit.  I just want to get a feel for the thing before I strap four more motors on.  I'll spend much more time PID tuning before the next flight.

I added a few more pics to the Flickr set and am still waiting for the youtube video to show up...