My goal is to create a plane capable of perpetual flight.
None I can foresee, since I know absolutely nothing about plane-building!
So I’ve got a lot of things to learn. Thankfully though, we live in a day and age when many people on the planet (my lucky self included!) have access to the sum of human knowledge at our fingertips. This’ll make things easier. I’ll attempt to work on both the textbook (theoretical) and field (practical) fronts.
I’m breaking this down into 3 pieces that I will work on in parallel. These pieces all relate to their “power role” in the plane:
Makes sense? You bet it does.
Now, if we can find out how much power the plane will need to stay in the air, we can determine how much storage we’ll need to keep it up at night (when we can’t generate power). We’ll also need to know how much power we can actually generate during the day. If it’s not enough to cover the power consumption PLUS recharge the depleted batteries, then we’re not going to make it.
Before getting lost in the details of each individual box, it’s worth highlighting an issue I noticed from the beginning. Take a look at the figure below, which shows the interaction between all the different design parameters we’ll need to pick:
You may have noticed a couple of circular references there. Here’s one:
Total Weight -> Total Power -> Battery capacity required -> Battery Weight -> Total Weight (and so on …)
Essentially, we need the total weight to find the total weight. Catch 22
The solution to this would be to simply plug some numbers in and play with them. You can use loops to simulate a range of meaningful values for power, weight, etc. and then see what combinations work.
Having briefly mentioned the different systems involved, it’s a good idea to state a clear goal for our plane. Ours is to use up as little power as possible. The less power we use (on the motor), the less we have to store (via batteries) and the less we have to genereate (via solar cells).
So that’s the goal: reduce the power consumption on the plane. The bit that uses up the most power on our plane will undoubtedly be the motor.
But why do we need a motor in the first place? To overcome drag. Not to keep the plane in the air (that’s what lift does), but to keep it moving forward (so it can generate the lift it needs to stay in the air).
So let’s revisit that goal … in order to reduce the power required for the plane, we need to reduce the opposing drag. The lower the drag, the less work we need to do to overcome it.
So that’s our specific goal then: to design a plane with the least possible drag.
So here you go:
. <– This speck has super-low drag.
Unfortunately, it doesn’t generate any useful lift either. See it turns out that you can’t really eliminate drag at all while also doing useful work. We need ot make sure that we’re not just reducing drag, but also that we’re able to generate enough lift to keep the plane in the air (and not fall).
This means that our Lift must be greater than the Weight of the plane:
We can’t generate any Lift without moving, and we need to overcome drag in order to start (and continue) moving. So that’s it. We need to figure out what the weight is, play around with various parameters in order to give us the minimum drag (while generating this minimum lift requirement) and then repeat.
Our new goal becomes: design a plane that generates enough lift to support it’s weight, at the least possible drag
Of course, things get more complicated when you realize that everything changes during the flight (Lift, Drag, etc.) based on the airspeed, weather, angle of attack and a few other things.
Note: All of this was put together based on alot of reading from here, here and talking to a friend with a PhD in Aeronautics. If something’s wrong, let me know.
Here’s an initial, high-level list:
Sounds simplistic, I know. But each of those check boxes is a project in its own right. Still we’re going to go through these one by one and strike them off.
Also, this list will change a lot — I’ll be tracking progress of the project on the main Perpetual page.