This article explains in which cases a report is required, until when it needs to be written, what content is required and who should review the report.
We should write the report in case the drone crashed to provide detailed insight into what happened and what we are doing to prevent incidents from happening in the future.
The warranty assessment report presents the facts that led to the crash in simple terms understandable to the customer. Include all important points but keep it as short as possible.
The report should be written, reviewed and sent to the customer in 5 working days from the date when we have all necessary information (flight logs, damage photos, flight plans, other info if needed)
Before sending the report to the customer, it should be reviewed by a peer.
Copy and adjust this template: 0000_template_Warranty_assessment
All reports are stored in this folder: Warranty assessment reports
Structure of the report
Title of the report
The title should have the date, “Warranty assessment”, name of the company and WingtraOne ID connected with the underscore (_).
Details
This section has info about the customer company, Wingtra company info, responsible person, WingtraOne ID, reference ticket, date of the incident and date of writing the report.
Incident description
Combine customer reports, dev notes, flight logs and flight plans to reconstruct the incident flight. You can use screenshots of the trajectory plot and the graphs from the flight logs, but don’t forget to describe in detail what each variable means. Also, be careful not to disclose any sensitive technical information about the system.
You can use WingtraFlightReview to obtain nice 3D visualizations of the flight.
Check the customer story with information available on the internet, such as for example local weather data, elevation model, height of buildings, etc.
Also, describe the damages and what has to be replaced and which parts can be reused. It is important to use simple language, which is understandable also for non technical customers.
Warranty assessment
In this paragraph explain if the incident is covered under warranty and if not, why not. It is important to describe safety procedures that are already implemented (e.g. safety parameters, preflight checks etc.) and what the operator can do to prevent similar incidents in the future.
It is also important to explain that we are working on improving the system to prevent similar incidents in the future.
Conclusion
Write a short summary of the findings above. Mention what parts need to be replaced and how much they cost. You can mention in this section if the drone or its parts need to be returned for further investigation.
Signature
Add your signature and the date.
Appendix - Damage Assessment
Write a short paragraph summarizing the main damages and damages that are not visible on the images. Add the photos of the damage and write a short description below each photo that describes the visible damages.