> For the complete documentation index, see [llms.txt](https://docs.openbrim.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openbrim.org/templates/openbrimfea/loads-fea/wind-loads-fea.md).

# Wind Loads \[FEA]

Wind Loads holds the **Wind Load Case**, which applies wind pressure to the projected area of the nominated components and sweeps a range of attack angles.

This is a **static** treatment: pressure on projected area. It does not model aerodynamic instability - flutter, galloping or vortex shedding - nor gust dynamics, so slender and cable-supported bridges need a separate aerodynamic assessment.

The two things that most often go wrong are the exposed area (parapets and barriers contribute disproportionately and are easy to omit) and the FE group that receives the computed forces (if it does not cover the loaded region, the force is silently lost).


---

# 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.openbrim.org/templates/openbrimfea/loads-fea/wind-loads-fea.md?ask=<question>&goal=<endgoal>
```

`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.