Reporting an Incident

1.1 Drone Operations Center – Overview

Incident reporting in AirHub allows your organisation to document and track operational events such as incidents, accidents, or hazards.
Reports can be created directly from the Incidents Overview or linked directly from a Flight Log, ensuring that every event is properly recorded and tied to its corresponding operation.

1.2 Method 1: Reporting from the Incidents Overview

Use this method to create a new report manually from the Incidents section.

1. Go to Manage in the sidebar and expand it.

2. Click on Incidents.

3. In the header, click + New.

4. A form will appear. Fill in the following information:
   • Type of incident: Select from Incident, Accident, or Hazard.
   • Title (Required): Provide a brief, clear title for the report.
   • Description (Optional): Add a detailed description of what happened.
   • Flight (Required): Search for and select the flight on which the event occurred.
   • Flight Phase (Optional): Select when the event occurred, e.g. Take-off or Cruise.
   • Investigator (Optional): Assign a person responsible for investigating the report.
   • Status (Required): Choose the current status, e.g. Open, Under Investigation, or Closed.
   • Documents (Optional): Attach files such as photos, witness statements, or maintenance records.

5. Click Save to submit your report.

Your incident will now appear in the Incidents Overview and will automatically link to the corresponding logbook entry for the selected flight.

1.3 Method 2: Reporting Directly from a Flight Log

Use this method when you want to create an incident directly from a specific mission or flight record.

1. Navigate to Missions from the sidebar.

2. Click on the mission name to open its details.

3. Within the flight log view, open the Info tab.

4. Locate the Incidents section and click Report Incident.

5. The incident report form will appear. Fill in the following details:
   • Type of incident: Select from the dropdown.
   • Title (Required): Add a brief, descriptive title.
   • Description (Optional): Provide any additional context.
   • Flight (Required): This will be pre-filled with the flight you are reporting on.
   • Flight Phase (Optional): Select the relevant phase, such as Landing or Hover.
   • Investigator (Optional): Assign an investigator.
   • Status (Required): Indicate the current state of the report.
   • Documents (Optional): Attach supporting files if available.

6. Click Save to finalise the report.

The incident is now successfully created and automatically linked to the selected flight.
It will also appear in the Incidents Overview, where it can be edited, followed up, or exported as needed.

1.4 Summary

AirHub provides two simple methods for reporting incidents: directly from the Incidents Overview for general reporting, or from a Flight Log for quick, contextual entries.
Both methods ensure full traceability and compliance, linking all relevant information and documents to your flight operations.