Complete the post-flight debrief

Post-Flight / Debrief is the last document in the Ops pack. It puts the aircraft away safely, closes the site, and captures what the crew learned while it is still fresh.

Before you start

Land first and record the landing time on the on-site Landing checklist. Like On-Site Planning, this document exists only under PDRA01 — on a job set to another operating authorisation the rail shows it greyed with a reason such as Not required under OPEN.

Steps

1. Open the document

   Open the job, select Forms, and in Ops pack choose Post-Flight / Debrief. It has three rows: Post-flight checklist, Emergencies checklist and Debrief.

2. Work the post-flight checklist

   Eleven items covering the post-flight inspection, powering down the aircraft and controllers, removing and inspecting the battery, storing it in a LiPo-safe bag, inspecting the airframe, propellers and landing gear, and packing the equipment.

3. Confirm the emergencies checklist

   Seven items — stop and assess, approach safely, make the area safe, assess casualties, call for help, provide care, record the incident. Work it only if something happened; leave it untouched if nothing did.

4. Complete the debrief checklist

   Under Completion Checklist, nine items close the operation out: notify air traffic control, disassemble the aircraft, flag maintenance, close the operating site, account for all equipment, complete the remote pilot logbook, debrief the flight crew, and confirm whether the operational objectives and a safe flight were achieved.

5. Write the evaluation

   Post-Flight Evaluation asks four questions: what went well, what improvements could be made, what lessons were learnt, and what action will be taken as a result. Answer all four — this is the part an auditor reads.

6. Sign off and send for review

   Press Sign off in each section header, then Send for review if your organisation reviews debriefs.

Options

Export PDF renders the debrief as a standalone document. It is also included in the job’s Ops Pack archive under the Post-Flight folder.

What happens next

No readiness check reads the debrief — by the time you fill it in, the flight has happened. Its value is the record: the technical log entry for the airframe, the maintenance you flagged, and the lessons the next crew reads.

If anything went wrong, file it properly rather than only noting it here. Use Occurrence / Airprox in the Safety group of the same rail — see Occurrence reports.

Troubleshooting

“No debrief yet.” Nothing has been started on this job. Opening the document creates it.

The rail shows 0/1 reviews approved. The package has been sent for review and the reviewer has not decided yet. It clears to All 1 reviews approved on approval.