> For the complete documentation index, see [llms.txt](https://avss.gitbook.io/prs-m30-for-dji-m30-and-m30t/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://avss.gitbook.io/prs-m30-for-dji-m30-and-m30t/prs-m30-for-dji-m30-series/safety-instructions.md).

# Safety Instructions

<table data-header-hidden><thead><tr><th width="219"></th><th></th></tr></thead><tbody><tr><td>Eye Protection</td><td>As with any system designed to launch a mass at high velocity, precautions shall be taken to prevent potential injury. Users should wear eye protection.</td></tr><tr><td>Never point the Parachute Pod™ towards anyone or anything</td><td>While the PRS-M30 includes features to prevent unintentional deployments, users shall be aware that the Parachute Pod™ is launched vertically. It is recommended that the operator maintains a clear area of at least five (5) meters (16 feet) after the system has been powered.</td></tr><tr><td>Approaching the Drone After Landing</td><td>Verify that the PSDK text window displays the "DISARMED" message before approaching the drone. Then hide the PSDK menu to avoid inadvertently pressing the MTD button before approaching the Drone after a landing or in the event of an aborted takeoff.</td></tr><tr><td>Ensure PRS-M30 is OFF before moving it</td><td>Do not pick up the PRS-M30 when it is powered on and connected to the drone as the sensors may interpret the movements as an in-flight failure. Power off the drone and PRS before moving the drone. See the "<a href="/prs-m30-for-dji-m30-and-m30t/prs-m30-for-dji-m30-series/calibration-processes.md">Calibration Processes</a>" section for instructions on handling the drone for calibration.</td></tr><tr><td>Error Status</td><td>The system should not be used unless it is indicated that no errors are present. The system will not arm itself nor deploy in a failure scenario unless it has initialized successfully.</td></tr><tr><td>Parachute Repacking</td><td>Only parachutes packed by AVSS are compliant. The Parachute shall be repacked or replaced every twelve (12) months only by AVSS.  You will no longer be compliant and will void the warranty if you attempt to repack the Parachute.</td></tr><tr><td>Flight Mode Changes</td><td>The ATS is designed to automatically detect abnormal flight behaviors. Flying in a controlled manner and avoiding erratic maneuvers ensures that the PRS-M30 can more accurately distinguish between pilot commands and loss of control. It is not recommended to change the flight mode mid-flight, as the drone may execute an abrupt maneuver that can exceed the maximum allowable "35°-degree pitch angle”, as per the manufacturer.</td></tr><tr><td>Rules and Regulations</td><td>Pilots shall follow the rules and regulations put in place by civil aviation or government bodies in their operating regions.</td></tr><tr><td>Energetic Charge Warning</td><td>The PRS-M30 utilizes an automotive pyrotechnic as the means of deployment. These charges are similar to that in automobile airbag and seat belt systems. Caution should always be observed around the system. Ensure the System is never pointing towards someone. Note, throughout this document, the pyrotechnic charge is referenced as an "Energetic Charge".</td></tr></tbody></table>


---

# 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://avss.gitbook.io/prs-m30-for-dji-m30-and-m30t/prs-m30-for-dji-m30-series/safety-instructions.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.
