Case Studies of Fatigue Life Improvement Using Low Plasticity Burnishing in Gas Turbine Engine Applications

Surface enhancement technologies such as shot peening, laser shock peening (LSP), and low plasticity burnishing (LPB) can provide substantial fatigue life improvement. However, to be effective, the compressive residual stresses that increase fatigue strength must be retained in service. For successful integration into turbine design, the process must be affordable and compatible with the manufacturing environment. LPB provides thermally stable compression of comparable magnitude and even greater depth than other methods, and can be performed in conventional machine shop environments on CNC machine tools. LPB provides a means to extend the fatigue lives of both new and legacy aircraft engines and ground-based turbines. Improving fatigue performance by introducing deep stable layers of compressive residual stress avoids the generally cost prohibitive alternative of modifying either material or design. The X-ray diffraction based background studies of thermal and mechanical stability of surface enhancement techniques are briefly reviewed, demonstrating the importance of minimizing cold work. The LPB process, tooling, and control systems are described. An overview of current research programs conducted for engine OEMs and the military to apply LPB to a variety of engine and aging aircraft components are presented. Fatigue performance and residual stress data developed to date for several case studies are presented including: * The effect of LPB on the fatigue performance of the nickel based super alloy IN718, showing fatigue benefit of thermal stability at engine temperatures. * An order of magnitude improvement in damage tolerance of LPB processed Ti-6-4 fan blade leading edges. * Elimination of the fretting fatigue debit for Ti-6-4 with prior LPB. * Corrosion fatigue mitigation with LPB in Carpenter 450 steel. *Damage tolerance improvement in 17-4PH steel. Where appropriate, the performance of LPB is compared to conventional shot peening after exposure to engine operating temperatures

Plant traits poorly predict winner and loser shrub species in a warming tundra biome

Peer reviewe

Tundra Trait Team:a database of plant traits spanning the tundra biome

Abstract Motivation: The Tundra Trait Team (TTT) database includes field‐based measurements of key traits related to plant form and function at multiple sites across the tundra biome. This dataset can be used to address theoretical questions about plant strategy and trade‐offs, trait–environment relationships and environmental filtering, and trait variation across spatial scales, to validate satellite data, and to inform Earth system model parameters. Main types of variable contained: The database contains 91,970 measurements of 18 plant traits. The most frequently measured traits (> 1,000 observations each) include plant height, leaf area, specific leaf area, leaf fresh and dry mass, leaf dry matter content, leaf nitrogen, carbon and phosphorus content, leaf C:N and N:P, seed mass, and stem specific density. Spatial location and grain: Measurements were collected in tundra habitats in both the Northern and Southern Hemispheres, including Arctic sites in Alaska, Canada, Greenland, Fennoscandia and Siberia, alpine sites in the European Alps, Colorado Rockies, Caucasus, Ural Mountains, Pyrenees, Australian Alps, and Central Otago Mountains (New Zealand), and sub‐Antarctic Marion Island. More than 99% of observations are georeferenced. Time period and grain: All data were collected between 1964 and 2018. A small number of sites have repeated trait measurements at two or more time periods. Major taxa and level of measurement: Trait measurements were made on 978 terrestrial vascular plant species growing in tundra habitats. Most observations are on individuals (86%), while the remainder represent plot or site means or maximums per species. Software format: csv file and GitHub repository with data cleaning scripts in R; contribution to TRY plant trait database (www.try-db.org) to be included in the next version release