CoolIP index                                                          Most recent edit: Sunday April 13, 2014              SearchSite

* See legal note below.

Turbine-on-a-Wing Fix

For five years the open Forum has not just critiqued Makani's architecture, but suggested fixes. Our novel ideas and their prototypes, like asymmetric airframes for looping AWES, are presented on the Forum first and then pop up in the Makani design.

The game continues. Will Google compete with open-AWE fairly without adopting its ideas? Will Google rip-off open-AWE ideas or pay for them? M600 engineering does not seem on track by the internal efforts of its small overworked team, so maybe open-AWE with CC licensing can help. We could plow the proceeds back into low-complexity AWE R&D.

Google-Makani's published AWT designs consistently show a hazardous defect. The bridle is so close to the turbine blades that the risk of fouling is clearly excessive. Just a small deviation in pitch downward at common tether angles is enough for catastrophic failure. kPower's design fix for this particular turbine-on-a-wing defect calls for the turbines to all be located along the top wing surface, to separate well both elements. To foul would then require a wild 180-degree flip. For this fix, it would be necessary to relocate flight-balance mass and retune the airframe for the new thrust center, possibly setting the generators in the wing apart from outboard props, slightly tilting the rotors according to flight mode, and like adjustments.

Landing in the cradle would also be facilitated by better locating the turbines. Makani is showing a clearance conflict between Wing7 and M600 docking, with increased fouling potential traded against too-wide of a cradle.

CC BY NC SA

On a side note, the M600 is adding dihedral to the main wing, for more roll stability, and a relatively much larger T-tail empennage, to correct elevator shadowing when the main wing is semi-stalled. Its quite lucky the Wing7 never crashed, unlike the flying-wing debacle no one talks about.

 

CC BY NC SA


Comment and development of this topic will be occurring here also:       
All, send notes, links, drawings, papers, videos, plans, safety-critical findings, and photographs!

  • Terms and aspects:  
  • Related links and concepts:  
    •  
  • Commentary is welcome:
    • "flying-wing debacle" [ ] Research needed here.
    • How does one talk to Google?

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

*Legal Note: coolIP is hereby defined as a Creative-Commons Unported NonCommercial Share-Alike License,
so now we are integrated with the latest standard cooperative IP model, but "coolIP" remains a nice shorthand.