> For the complete documentation index, see [llms.txt](https://docs.flylogs.com/fcom/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flylogs.com/fcom/sms/safety-reports.md).
# Safety Reports
Flylogs SMS, is an integrated Safety Management System based on the [ICAO recommendations](https://www.unitingaviation.com/publications/safetymanagementimplementation/content/#/) fully compliant with the [ICAO Doc 9859](https://www.icao.int/safety/safetymanagement/pages/guidancematerial.aspx). It allows to receive safety events directly in your Flylogs account linked with all the relevant information like flight crew, aircraft, maintenance, flight crew, trainings, duty times, etc.
**Any member** of your organization **has the ability to** access the Safety Reporting System and **create a new report.**
These reports can be specifically related to a flight, or not, allowing any of your users to inform about more other types of risks.
The safety manager and other company managers can see the whole list of events and access to the statistics.\
They can also request third parties to complete a report on an existing event, giving you more information of the a single event.
Related events will appear grouped together and will share some common details like date, location, type of event, etc.
***
### Flight safety reports
Each report can be associated to a flight. If it is, the flight information will be displayed on the top part of the report, along with the crew names and user types.
All other report information is displayed below and only the safety manager or other, higher level managers can edit or delete the stored information.
Additionally, the person writing the report or any manager can comment on the report and upload files as needed that will be attached to the existing report.
### Report status
A report has 5 possible status in which can be.
* **New.** Default status when the report is created.
* Reviewed. Initial review performed, waiting for more details or further processing.
* **Closed.** Report is closed and no further actions are expected.
* Deleted. Useful for test reports.
* **Published.** The report is closed and published to all members in the organization.
#### Published Reports
Published SMS reports are public to all members of your organization. This enables that every body learns from the findings of a report, which is the final goal of the Safety System.
All members can see all published reports, and a summary of them are also available on the aircraft page. Each aicraft, has a summary of SMS reports in which it has been involved.
***
### Departments
Reports can be assigned to a **department** within your organisation (e.g. Flight Operations, Maintenance, Cabin Crew). This allows safety managers to filter and group events by area of responsibility.
Departments are configured at company level. Once configured, a department selector appears at the top of the report creation and editing forms, and the selected department is shown in the report list, the report detail view, and the printed PDF.
The **Analytics** page includes a dedicated **Reports by Department** chart and a department filter so you can focus the statistics on a specific area.
### Filtering reports
The report list supports filters to help you find specific events quickly. Available filters depend on your role.
**All users**
* **Date range** — from / to
**Managers and Safety Officers** (`user_group_id < 150`) **only**
* **Status** — Open, Reviewed, Closed, Published
* **Category** — event classification category
* **Severity** — Information, Incident, Accident, Hazard
* **Department** — filter by organisational department
Filters can be combined freely. The date range is the only filter available to standard crew members, who already see only their own reports plus any published ones.
---
# 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:
```
GET https://docs.flylogs.com/fcom/sms/safety-reports.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.