> For the complete documentation index, see [llms.txt](https://docs.enercalc.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enercalc.com/sel-faq/using-the-software/calculation-modules/beams2/steel-beam/treatment-of-unbraced-lengths.md). # Treatment of Unbraced Lengths How the ENERCALC Steel Beam module determines unbraced lengths and treats points of inflection when computing Lb and Cb. ## How does the Steel Beam module determine the unbraced length of a beam? Going from "most general" to "most specific"... Spans: "Spans" are defined by supports. Unbraced Lengths: A Span may be subdivided into one or more Unbraced Lengths based on the locations of brace points. **Cb values apply to Unbraced Lengths.** Design Segments: An Unbraced Length may be subdivided into one or more Design Segments, based on the locations of points of inflection. **Each Design Segment will only have compression in the top or in the bottom.** ## AISC clearly states that points of inflection are not considered brace points. At the same time lateral torsional buckling is a compression-type failure, so it's unclear as to whether the value of Lb should also include some portion of the beam where the flange is no longer in compression. How does the Steel Beam module handle this? This is a real ambiguity that the profession has argued about for decades, not a code bug. The AISC F1 rule is deliberately conservative. Yura's work in the 1990s showed that at an inflection point, the beam cross-section isn't physically restrained. It can translate and twist. The full brace-to-brace segment can buckle as a single S-shaped wave crossing zero moment, so Lb should be the full physical brace-to-brace distance. That's the letter of AISC. But instinct suggests that LTB is fundamentally about the compression flange going unstable. If the top flange is compressed on one side of the inflection point and the bottom flange on the other, neither flange sees a continuous compressed length equal to the full unbraced span. The two "half-buckles" are somewhat coupled through the web and through warping continuity at the inflection, but they're not identical to a single-curvature buckle of the full length. The middle-ground position, which is roughly what ENERCALC does, is: * Use the shorter design-segment length for Lb (recognizing the compression flange discontinuity) * Use Cb computed over the physical unbraced length (so the moment-gradient benefit reflects the real reversal) That's a hybrid. It's non-conservative versus strict AISC F2, and conservative versus treating the inflection as a true brace (which ENERCALC doesn't do, it doesn't credit Cb = 1.0 per segment either, it uses the full-span quarter-point moments). The AISC Commentary to F1 acknowledges the debate; the current rule sides with Yura because reverse-curvature LTB tests showed the single-wave mode does control in some geometries, particularly with unequal end restraints. Practically: for a symmetric double-curvature beam with roughly equal positive and negative moment regions, ENERCALC's approach and strict AISC will give similar answers because Cb is large. For asymmetric cases, one small negative region near a support, ENERCALC will be materially less conservative than AISC F1. Worth being aware of when reviewing capacity ratios near 1.0. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.enercalc.com/sel-faq/using-the-software/calculation-modules/beams2/steel-beam/treatment-of-unbraced-lengths.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.