<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>KTA on MechCalc how-to Guide</title>
    <link>https://mechcalc.net/blog/en/tags/kta/</link>
    <description>Recent content in KTA on MechCalc how-to Guide</description>
    <image>
      <title>MechCalc how-to Guide</title>
      <url>https://mechcalc.net/blog/og-default.png</url>
      <link>https://mechcalc.net/blog/og-default.png</link>
    </image>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sat, 21 Feb 2026 12:00:00 +0100</lastBuildDate>
    <atom:link href="https://mechcalc.net/blog/en/tags/kta/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Fatigue Crack Growth and Environmental Effects (KTA 3206)</title>
      <link>https://mechcalc.net/blog/en/posts/08-fatigue-crack-growth/</link>
      <pubDate>Sat, 21 Feb 2026 12:00:00 +0100</pubDate>
      <guid>https://mechcalc.net/blog/en/posts/08-fatigue-crack-growth/</guid>
      <description>&lt;blockquote&gt;
&lt;p&gt;🧮 &lt;strong&gt;Go straight to the calculator&lt;/strong&gt;: to skip the derivation and use the online tool with a built-in verification flow, open the &lt;a href=&#34;https://mechcalc.net/blog/calculators&#34;&gt;fatigue crack growth calculator&lt;/a&gt;
 from the large category cards on the calculators home page.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id=&#34;1-where-fatigue-crack-growth-sits-in-an-lbb-analysis&#34;&gt;1. Where fatigue crack growth sits in an LBB analysis&lt;/h2&gt;
&lt;p&gt;At the core of a Leak-Before-Break (LBB) argument: you must show that, over the service life, the time for an initial non-penetrating surface flaw to grow by &lt;strong&gt;subcritical crack growth&lt;/strong&gt; through the wall and cause a leak — and the time from leak to growth to the critical fracture size — is long enough for the monitoring system to detect it and act.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
