One more thing to point out in reply to some posts. Yes, our wings were providing most of the lift when the rotor was slowed down. That is the only way we can slow the rotor down and keep it stable. It's not "cheating." It's a method to efficiently fly fast (high aspect ratio wings providing lift) and still get efficient vertical takeoff and landing (large diameter rotor providing lift). Because the rotor can provide all of the lift at slow speeds, the wings can be sized smaller than for airplanes of comparable size, so the combination of our slowed rotor and small wings gives just about the same amount of total drag as a conventional airplane with wings sized for landing.
I'm one of the engineers for Carter Aviation Technologies. I'm also the webmaster. I've been reading through a bunch of the comments above, and thought that I'd just comment on a few of them. I know I'm not keeping all of the threads together, and that this post is rather long, but I have a lot of work to do today, and don't have time to keep track of a lot of threads. This will be my only post. If you want to specifically ask me anything, my e-mail address is jrlewis_at_wf.net.
The significance of mu-1 is that it allows you to slow down the rotor blade to reduce rotational drag, and keep the advancing blade from going so fast as to get into compressibility effects (close to the speed of sound). This lets you fly a whole lot faster on less power. The reason we don't just stop the blades is explained in our FAQ. But basically, keeping the rotor spinning gives you centrifugal force to help support the blade. If you stop the rotor, it becomes a wing, and then needs all of the same structural requirements of a wing, which adds a lot of weight. For high speed subsonic flight, the added weight more than offsets the drag savings.
The CarterCopter was only a technology demonstrator, meant to prove the high speed portion of the flight. For that regime, we plan for the rotor to be in autorotation, so we designed our prototype as a gyroplane. We figured, why add all the extra components to our demonstrator when hovering flight with a rotor is already a well understood concept? Future production versions probably will have true helicopter capabilities, but the rotor will still be in autorotation at high speed. That's not to say that a gyroplane isn't practical. Most uses of helicopters are for their vertical takeoff and landing ability, not their hovering. Only specialized missions, like search and rescue, require hover. As was demonstrated back in the 30's and 40's, autogyros are capable of "jump" takeoffs by prerotating the rotor prior to takeoff, and can easily perform zero roll landings.
When we say that the retreating blade has reverse flow, we are looking at it from the frame of reference of the rotor blade. With no forward speed, air flows over the rotor blade from leading edge to trailing edge. As you start moving forward, inboard portions of the retreating blade see airflow from trailing edge to leading edge. At mu-1, all airflow inboard of the tip is from trailing edge to leading edge, which makes the blade unstable. So we've devised and demonstrated a way to keep the blade stable with total "reverse" flow on the retreating blade.
I saw someone mention world speed records of helicopters. The thing to remember is that speed records aren't always set by efficient machines, which is what we're trying to accomplish. The official record was the British Westland Lynx, at 249 mph. The unofficial highest speed I've heard of is a heavily modified Bell Huey. It was so inefficient that it could only fly at high speed for about 15 minutes before running out of fuel. It's top speed was somewhere around 315 mph. But, what we've accomplished is efficient high speed flight. We think that future versions (jet powered) will be able to fly at 300-400 mph.
Finally, regarding the website, I apologize for the site going down this morning. We were not expecting to be on/. and get a lot of traffic. A couple months ago, we were on 60 Minutes, and the producers told us to expect millions of hits. I did a lot of work, temporarily moving the site to a different server, and we got jack sh_t for traffic. Now, all of a sudden, we get on/. and I get caught with my pants down. But what're ya gonna do?
Slashdot Mirror
One more thing to point out in reply to some posts. Yes, our wings were providing most of the lift when the rotor was slowed down. That is the only way we can slow the rotor down and keep it stable. It's not "cheating." It's a method to efficiently fly fast (high aspect ratio wings providing lift) and still get efficient vertical takeoff and landing (large diameter rotor providing lift). Because the rotor can provide all of the lift at slow speeds, the wings can be sized smaller than for airplanes of comparable size, so the combination of our slowed rotor and small wings gives just about the same amount of total drag as a conventional airplane with wings sized for landing.
I'm one of the engineers for Carter Aviation Technologies. I'm also the webmaster. I've been reading through a bunch of the comments above, and thought that I'd just comment on a few of them. I know I'm not keeping all of the threads together, and that this post is rather long, but I have a lot of work to do today, and don't have time to keep track of a lot of threads. This will be my only post. If you want to specifically ask me anything, my e-mail address is jrlewis_at_wf.net.
The significance of mu-1 is that it allows you to slow down the rotor blade to reduce rotational drag, and keep the advancing blade from going so fast as to get into compressibility effects (close to the speed of sound). This lets you fly a whole lot faster on less power. The reason we don't just stop the blades is explained in our FAQ. But basically, keeping the rotor spinning gives you centrifugal force to help support the blade. If you stop the rotor, it becomes a wing, and then needs all of the same structural requirements of a wing, which adds a lot of weight. For high speed subsonic flight, the added weight more than offsets the drag savings.
The CarterCopter was only a technology demonstrator, meant to prove the high speed portion of the flight. For that regime, we plan for the rotor to be in autorotation, so we designed our prototype as a gyroplane. We figured, why add all the extra components to our demonstrator when hovering flight with a rotor is already a well understood concept? Future production versions probably will have true helicopter capabilities, but the rotor will still be in autorotation at high speed. That's not to say that a gyroplane isn't practical. Most uses of helicopters are for their vertical takeoff and landing ability, not their hovering. Only specialized missions, like search and rescue, require hover. As was demonstrated back in the 30's and 40's, autogyros are capable of "jump" takeoffs by prerotating the rotor prior to takeoff, and can easily perform zero roll landings.
When we say that the retreating blade has reverse flow, we are looking at it from the frame of reference of the rotor blade. With no forward speed, air flows over the rotor blade from leading edge to trailing edge. As you start moving forward, inboard portions of the retreating blade see airflow from trailing edge to leading edge. At mu-1, all airflow inboard of the tip is from trailing edge to leading edge, which makes the blade unstable. So we've devised and demonstrated a way to keep the blade stable with total "reverse" flow on the retreating blade.
I saw someone mention world speed records of helicopters. The thing to remember is that speed records aren't always set by efficient machines, which is what we're trying to accomplish. The official record was the British Westland Lynx, at 249 mph. The unofficial highest speed I've heard of is a heavily modified Bell Huey. It was so inefficient that it could only fly at high speed for about 15 minutes before running out of fuel. It's top speed was somewhere around 315 mph. But, what we've accomplished is efficient high speed flight. We think that future versions (jet powered) will be able to fly at 300-400 mph.
Finally, regarding the website, I apologize for the site going down this morning. We were not expecting to be on /. and get a lot of traffic. A couple months ago, we were on 60 Minutes, and the producers told us to expect millions of hits. I did a lot of work, temporarily moving the site to a different server, and we got jack sh_t for traffic. Now, all of a sudden, we get on /. and I get caught with my pants down. But what're ya gonna do?
But how do you get the ball lightning?