First accident with impact on third parties

As strong as it is (>100GPa axial) for scaling - UHMWPE has a consistent melting point.
A tiny wee kite with sewing thread can easy cut through a large competition kite line…
just by running along the stronger line at the one point, the thin thread cuts through the stronger line with the heat of friction.
Melting point is a weakness which needs considered where you have running line.
Pulley sheaves have a lot of energy imparted to them under high tension.
(See kitegen patent on variable capstan groove low friction winch pulleys.)
Any manner of line handling / sharp fault may have happened… Would be good to see the forensics.

This crash is not cultural. It is a reality.
Generally developpers of new technologies take some lessons from failure, above all when it is forseeable. Some of possible risk factors were studied Barnard's predictions. Anthropology has nothing to do with this.
It would be more fruitful to examine if the same power efficiency can be obtained by eliminating some elements of risk when it is possible, concerning both the AWES and its process of realization.

1 Like

As a collorary to my views on not sharing crash statistics before going commercial, those non commercial activities should not risk damage to «civillians». Its a hard thing to ensure fully, but at least such events should be very unlikely.

This probably means testing at a remote location, testing at small scale, more computer simulation work etc.

Any actor not conforming to this philosophy will eventually cause a lot of harm to the industry, probably more than the gains made for that particular project

1 Like
1 Like

Definitely agree - would like to know the forensics.

Indeed. I will try to find out. Was working for Kitepower in the very beginning. One aspect is the question of the security factor (tether braking force divided by max expected tether force).
I always suggested a value of three, but other people said that two might be sufficient.
Other aspects:

  • was the groundstation limiting the force by reeling out faster correctly
  • what was the age of the tether used
  • when was the last time a visual inspection performed
  • was a fail-safe software algorithm in place to steer the kite to a safe landing location in case of a tether rupture

I will ask these questions. Lets see if I get a reply.
Uwe

3 Likes

Thank God no one was hurt! This sort of accident was technically predicted for a long time now, by kPower, in our Forums. In summary, single-line AWES topologies present a single critical failure point, counter to aviation design best practice. Multi-line and Networked Kites are topologically favored.

KiteGen’s original frazzled lines, which I inspected first hand in 2011, confirmed that crude reeling, as KitePower and many others do, quickly ruins kitelines. Since then PR-image analysis of AWES reels shows premature damage again and again. Kitepower was specifically recently critiqued, in detail, for poor line condition, poor fairlead design (not as bad as KPS), and poor level-winding.

In high wind, there is no way just KitePower’s control pod and remnant tether mass was enough to bring this kite back upwind under control. At best a downwind landing in a secure area might have worked. A dragging tether should cutaway at the kite, and/or a kite-killer deploy. These are old issues on the Old Forum. KitePower is now grounded by their apparent lack of adequate fail-safes.

Makani’s M600 is potentially far more destructive and further vulnerable by its high-voltage tether, with many such critical M600 failure modes identified on the Old Forum. It was possible to boldly deduce at least one major crash covered-up crash Makani crash from clues, that was later confirmed. GoogleX can afford to crash, but a single tragic crash has killed many a small aviation company. Many AWE commercial developers willfully and wrongly rely on secrecy about crashes, despite the noble aviation tradition of open crash reporting.

Count on poor aviation safety and insurability to vet the AWE field of many weak players. Energy markets cannot afford the aviation fail-safes that high-complexity AWES designs require. To deliver high performance economically and safely is most practical with low-complexity methods known in professional power kite fields. They don’t have to wait to know that high-velocity high-mass aircraft classes have higher inherent risks, just as FAA/ICAO regulate. AWE R&D workers should not remain silent about safety incidents, out of professional ethics and legal liability.

More than any other venture, kPower has shares safety design and operational solutions to known challenges. We first detailed short-stroke pumping cycles, heavy-duty belt or chain capstan sections, kite killers, many-connected topologies, no com link dependence, passive control, and other strategies. Our business model depends on superior safety.

We must call out anyone’s safety flaws as they are discovered and condemn greed-driven secrecy that hurts us all. Our best model of crash reporting is NASA’s Pathfinder crash report. We will all prosper better and save lives by superior shared AWE safety culture.

http://www.energykitesystems.net/CoopIP/TetheredAviationConOps.html

1 Like

Dyneema start to creep at 50% continuous load. That mean you can’t rely on a 100lbs line to handle 50 lbs continuous but you can handle peak pull up to 100 lbs.
Classic security factor in automotive industry is 3, same for aeronautical.
Wind energy security factor can increase up to 20 for some parts. Due to dependancy between power and wind speed

It’s not likely creep by itself broke the line, but high surface abrasion, based on the frazzled and damaged lines observed on this and multiple other poorly designed reeling prototypes.

Creep itself is a often good thing for kitelines, which come pre-stretched for highest quality. Many fliers fly the same lines for years, claiming they just get better (thinner, less drag, higher unit-cross-sectional strength). While stretched lines are higher performance, they are more prone to harmonic shock failure, a sort of brittle tensile effect.

Line Surface Abrasion gets worse for larger more powerful lines and loads, as higher forces concentrate on the line surface. Nicks and other flaws in the line concentrate forces and localize failure. Longer lines have a greater statistical risk of flaws.

Tether wear for UHWMPE tether is indeed not a simple issue to tackle. We must expect learning to happen in each company and the industry as a whole. Sharing such experience would gain each player for sure, so personally I could only recommend sharing.

That bein said: it you are in a testing operation, crashing within the planned envelope of testing, there is no need to report outside the company. This would probably apply to a possible Makani incident.

There is no shame in sharing crash details, and we can only hope many players will do this, but it is not wrong to not do it.

The offshore crane industry (oil industry) and I’m sure many others have lots knowledge avout tether wear and monitoring. I think part of the problem is in AWE companies ability to digest this knowledge, in terms of manpower, getting in touch with the correct people and also the crane industries inability to share such knowledge at a reasonable price (pure speculation on my behalf)

Commercial fishing and tug-boat operations are the most intensive industrial users of UHMWPE. That’s why I embedded ten years with the legendary fishing fleet of Ilwaco, on the US NW Coast, to master their unsurpassed domain knowledge, from kW to MW scales. Power kiting and yachting are also cultures of UHMWPE excellence. Don’t count on the average AWES venture for much vital art. UHMWPE is an amazing technology that takes amazing skill to get the most from it.

The AWE field is now big enough for the set of safety outcomes to cover all major possibilities. There is “good, bad, and ugly”. Our first AWE field fatality is probably only a matter of time, and there will likely be a scandal to the backstory. It will then be clear to all parties that crash-report-optional culture is dangerous, both internally and externally.

Venture capitalists lack the public-minded objectivity to self-censor crash statistics, because of commercial conflict-of-interest. They can only partly get away with covering-up risks and crashing from investors, regulators, and the rest of us. If they persistently hide fatal flaws in operations, eventually the worst happens. Safety data must not be private IP.

Investors are advised to divest from the more dangerous ventures and architectures, as measured by standard flight-risk criteria like mass, velocity, and complexity.

http://www.infinitysnews.com/nacogdoches/first-ever-energy-kite-crash-texas-hits-close-home-oklahoma

1 Like

Why, that’s Fort Felker hanging in the air! That crazy cat has nine lives, I tell you.

When Makani crashes in Texas, they are forced to produce a report with any random redneck. Told you the electrical tether was a particular concern. Good try, but this document is just not up the NASA crash report standard. Kite Power’s report should fall somewhere between Makani-in-Texas and NASA here-

1 Like

Thanks for the Helios report link.
Well worth reading

1 Like

Yep, impressive images

The Makani story is satire btw, If there are others who could not make complete sense of it…

There is more room in Norway than in Netherlands.

Being forced to test remotely due to safety concerns indicates an inherently hazardous AWES architecture.

Text of initial Mishap Report messages to TUDelft, Kite Power, Makani, Ampyx, etc.

Hi All,

Best practice AWES Mishap Analysis and Reporting is presumed to be an open documentation process by many domain experts, by aviation safety culture tradition. The entire AWE community are stakeholders. KiteLab Ilwaco and kPower Austin’s circles share JoeF’s KiteLab, Los Angeles documentation request.

As Roland is familiar, Open AWE circles have long publicly identified single-line AWES with com-link and control-pod dependencies as a high risk architecture above about 10kW class. Part of the mishap analysis is how Kite Power, Amypx, Makani, and so on, down selected to the high-risk architecture in terms of research due-diligence. Mass and velocity metrics also figure. The Kite Power mishap was at the lower end of such risk, bit could still have killed someone, as the breech of the commercial roof shows.

Please refer to TACO1.0 as Open AWE’s early effort to put aviation safety first. It was developed with help from veteran FAA, commercial aviation, and general aviation help. Dr. Mark Moore, former NASA LaRC and now Director of Engineering for Uber’s Flying Taxi program, stated TACO1.0 was a document “to bring us together”. TACO2.0 is due, and the Kite Power Mishap should be a model case study. Please review TACO if you are not familiar with it-

Tethered Aviation ConOps (TACO) v0.8

Looking forward to a productive process. There is a feeling that TUDelft sort of lost its way when Wubbo died, and went to far toward a venture-capital model of R&D that put Kite Power PR ahead of safety-culture. As the infant industry moves forward, there is a need for broader global collaboration that TUDelft has not fostered, especially by monopolizing conferences and EU public funding. Future rounds of R&D funding will be far greater, and Mishap reporting and statistics are critical factors. Makani is known to have suppressed mishap information and Ampyx is regarded as an accident waiting to happen. These are far faster more massive platforms with single line and com link dependencies, and too many other critical failure points to list here.

This the general context, with lots of complexity to work out. NASA’s Helios Mishap Report is a model standard. Kite Power’s Mishap is far less complex but historically momentous. Looking forward to an interesting process that better informs us all, and advances AWE safety culture to aviation norms. Its hoped Kite Power will emerge from this event a better and stronger player.

Sincerely,

dave santos

kPower CTO

TACO lead-author

On ‎Friday‎, ‎July‎ ‎12‎, ‎2019‎ ‎12‎:‎46‎:‎08‎ ‎PM‎ ‎CDT, Joe Faust joefaust333@gmail.com wrote:

Joep,

Please include KiteLab, Los Angeles, for reception of safety notice details concerning the May 30, 2019, incident.

Thank you,

Joe Faust

KiteLab, Los Angeles