On this page
Records make experience reusableA success percentage needs a denominatorRecords support investigation and recoveryUse records for learning and accountabilityFollow the cause and effectSources for this lesson
Sir Airffic Go here. A win count alone does not tell a team what to practice. A fleet also needs records that explain what happened.
Records make experience reusable
In the northeast India study, field staff kept diaries and discussed difficulties after the day’s work. This made experience available for the next day rather than leaving it in individual memory. Events before and after a flight can therefore be as informative as the path the aircraft took.
The same reasoning applies to equipment histories. Linking the aircraft, battery, software version and maintenance date makes changes easier to investigate. A pattern is a starting point for a question, however, not automatic proof of cause. Weather, mission type and other differences may also explain a changed outcome.
A success percentage needs a denominator
When a headline says 99 percent success, ask what was counted. Flights that began, requests that arrived and scheduled missions are different denominators. A serious accident, a repeated landing attempt and an incomplete image set are also different outcomes. Comparisons become misleading when the underlying definitions differ.
Here is an invented example: 99 successes in 100 flown missions does not describe service coverage if another 100 requests were declined beforehand. It answers a narrower question. Keep reliability, readiness and completion of requested work separate, then use each measure for the decision it can legitimately support.
Records alone do not improve performance. Consistent definitions and follow-up checks complete the learning process.
Records support investigation and recovery
A 2019 Swiss Post accident exposed a problem with emergency protection and led to suspension and safety-process changes. Reporting on the 2020 restart described expert examination of procedures and documents. The path from interruption to recovery is part of an operating record, not an inconvenient detail outside it.
These reports cannot establish one company’s general accident rate, much less an industry-wide rate. Their strategic relevance is the need for investigation, corrective action and review. A buyer can assess an explainable improvement process more clearly than a collection of selected successful flights with no account of what changed.
| Record | Useful question | Interpretation safeguard |
|---|---|---|
| Requests, cancellations, completions | How much requested work was served? | Do not count only launched flights |
| Condition and maintenance | What changed, and when? | Check other changing conditions |
| Events and corrective actions | What was learned and changed? | Distinguish severity |
| Public operating records | How was the service used locally? | State the reporting purpose and scope |
Use records for learning and accountability
Skydio’s Dock for X10 and BRINC LiveOps included equipment or post-flight information management in their offers. As a fleet grows, shared knowledge of readiness and previous work becomes more valuable. Collecting data is only the first step; responsible people need to find and use the relevant record.
Yonkers also announced public records describing when, where and why its DFR aircraft fly. Technical investigation and public accountability need different levels of detail. Designing information for each purpose helps people understand the service, while keeping an operational learning record distinct from a public explanation of how it is used.
The advantage is traceable learning across conditions, cancellations and improvements, rather than record volume alone.
Try the idea yourself
Before comparing two high success rates, how would you check their denominators and definitions of failure?
Sources for this lesson
- Implementation of drone based delivery of medical supplies in North-East India: experiences, challenges and adopted strategies ↗Sumit Aggarwal; Prakamya Gupta; Nupur Mahajan; Sivaraman Balaji; Khangembam Jitenkumar Singh; Balram Bhargava; Samiran Panda · 2023-06-02 · operations-p06
- Reliability and Maintenance Analysis of Unmanned Aerial Vehicles ↗Enrico Petritoli; Fabio Leccese; Lorenzo Ciani · 2018-09-19 · operations-p02
- Swiss Post refines safety processes after drone crash ↗SWI swissinfo.ch / Keystone-SDA · 2019-06-28 · operations-n12
- Swiss Post drone deliveries to resume after crashes ↗SWI swissinfo.ch / Keystone-SDA · 2020-01-25 · operations-n11
- Dock for X10: The Future of Scalable, Autonomous Flight and Data Capture ↗Skydio · 2024-09-25 · operations-n07
- BRINC Announces Its Unified Drone Operations Platform: LiveOps ↗BRINC · 2024-03-21 · operations-n17
- Yonkers Police Department Deploys Citywide Drone as First Responder Program ↗City of Yonkers Police Department · 2026-03-13 · operations-n16