> For the complete documentation index, see [llms.txt](https://enercalc.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://enercalc.com/docs/sel-user-manual/calculation-modules/earth-retention/sw-segmental-walls/block-geogrid-data-tab-for-ge-2/stability-tab-5.md).

# Internal Stability Tab (for Geogrid Reinforced Walls)

How to review internal stability results including tension, pullout, connection, and sliding factors for geogrid reinforced segmental walls.

![](https://3283832020-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiBJmBoewuy4ZcBC7RF3m%2Fuploads%2Fgit-blob-28107139b50e924aa9d5b7f70910f93bba087924%2FClip61.jpg?alt=media)

Displays internal stability table:

**Layer**: Displays geogrid layer numbers.

**Height, ft**: Displays the height from the base to the elevation of each geogrid layer.

**Trib Height**: Displays the tributary height of each geogrid layer.

**Depth to Midpoint**: Displays the distance from the top of the wall to each geogrid layer.

**Tension from Soil**: Displays the tension in each layer of geogrid due to lateral earth pressure from the soil.

**Tension from DL Surcharge**: Displays the tension in each layer of geogrid due to lateral earth pressure from a dead load surcharge.

**Tension from LL Surcharge**: Displays the tension in each layer of geogrid due to lateral earth pressure from a live load surcharge.

**Static Total Tension, Fg**: The sum of Tension from Soil plus Tension from DL Surcharge plus Tension from LL Surcharge.

**LTDS**: Echoes the Long Term Design Strength of the selected geogrid.

**LTDS\*\*\*\*seismic**: Echoes the Long Term Design Strength for seismic design of the selected geogrid.

**Total Tension (w/ Seismic), Fi**: Total tension in the geogrid when subjected to the load condition that includes seismic loading.

**FS Tensile Overstress (static)**: LTDS / Static Total Tension

**FS Tensile Overstress (w/ seismic)**: LTDSseismic / Total Tension (w/ seismic), Fi

**Pullout Strength**: Ability of the geogrid to resist pullout failure.

**FS Pullout (static)**: Pullout Strength / Static Total Tension, Fg

**FS Pullout (w/ seismic)**: Pullout Strength / Total Tension (w/ seismic), Fi

**Connection Strength**: Connection strength of the selected block/geogrid combination.

**FS Connection (static)**: Connection capcacity / Static Total Tension, Fg

**FS Connection (w/ seismic)**: Connection capcacity / Total Tension (w/ seismic), Fi

**Internal Sliding Force (static)**: The driving force at each layer of geogrid from static loading tending to cause the soil mass above to slide sideways.

**FS Internal Sliding (static)**: Internal sliding resistance / Static internal sliding force

**Internal Sliding Force (w/ seismic)**:The driving force at each layer of geogrid from loading including seismic tending to cause the soil mass above to slide sideways.

**FS Internal Sliding (w/ seismic)**: Internal sliding resistance / Internal sliding force (w/ seismic)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://enercalc.com/docs/sel-user-manual/calculation-modules/earth-retention/sw-segmental-walls/block-geogrid-data-tab-for-ge-2/stability-tab-5.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
