> For the complete documentation index, see [llms.txt](https://manual.rush.sr/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://manual.rush.sr/readme/break-in-and-initial-setup/engine-break-in.md).

# Engine Break-in

Before you set a new track record… think about that brand new engine. Be kind to it, and it will be kind to you and your wallet!

The engine should be given three break-in sessions of approximately 15-20 minutes:

1. Keeping RPM below 7,500 and moderate throttle.
   1. You should use this opportunity to also [bed your brakes](/readme/break-in-and-initial-setup/bedding-brakes.md).
2. Keeping RPM below 10,500 and full throttle.
3. First half session (\~10min) below 10,500rpm, then allowing full rev out all the way to the limiter.

The engine should be allowed to cool after each session.

This also give you a chance to get broken into the car. Fluids should be checked after each session, and **you must** [**torque-check the wheels**](/maintenance/each-session/torquing-wheels.md) **before every session!**

Following these three sessions, you are good to go. The car is very balanced but will bite back if you horse it around. Find your limits slowly and work into the car. It likes to be balanced in the corners: deep trail braking and yanking your foot off the brake at mid corner, will not give you the results you want. Apply brake pressure quickly, but roll it off smoothly.

Learning to use the shift lights will take some time too. \<ost people are tuned into changing gear by 7,000 rpm. If you short-shift, you are not even in the powerband.

<figure><img src="/files/0iUUiQ6dlUBJMUMVwiNX" alt=""><figcaption></figcaption></figure>


---

# 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://manual.rush.sr/readme/break-in-and-initial-setup/engine-break-in.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.