Drone Requirements Check
Compare caller-supplied expected and observed records for drone requirements check.
Description
Drone-assignment requirements can be tracked against recorded preparations.
Drone-assignment requirements can be tracked against recorded preparations. This audit compares caller-defined requirement labels.1
Compare caller-supplied expected and observed records for drone requirements check.
When to use Drone Requirements Check
Use this tool to compare caller-supplied expected and observed records for drone requirements check.
Prepare the text, recorded observations, aligned figures or editorial criteria requested. Confirm what each label, count, timestamp or supplied flag represents before interpreting the result.
How to use Drone Requirements Check and understand its results
- Prepare the text, recorded observations, aligned figures or editorial criteria requested. Confirm what each label, count, timestamp or supplied flag represents before interpreting the result.
- Enter requiredApprovals, obtainedApprovals using the field table and calculation rules, then run the tool.
- Read coveragePercent, matched, missing, unexpected. The explanation below defines the units, signs, ordering and any flags or placeholder values.
- If the tool reports an input issue, correct the values and run it again. Apply the stated assumptions when interpreting a successfully returned result.
| Input field | Meaning | Value type; see rules below | Requirement |
|---|---|---|---|
| requiredApprovals | Required flight approvals | list of string | Required |
| obtainedApprovals | Obtained approvals | list of string | Required |
Supply required and completed requirement labels. Enter a nonempty required list and an observed list, which may be empty. Trim and lowercase entries for comparison; blank entries are errors. Deduplicate by normalized key. Return matched/missing required labels, unexpected observed labels, and coverage. Required order is preserved; the last trimmed spelling wins for duplicate keys.
coverage%=100×matchedUnique/requiredUnique Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| coveragePercent | Coverage (%) | number; minimum: 0; maximum: 100 |
| matched | Matched items | list of string |
| missing | Missing items | list of string |
| unexpected | Unexpected items | list of string |
{
"input": {
"requiredApprovals": [
"pilot credential",
"airspace authorization",
"location permission"
],
"obtainedApprovals": [
"pilot credential",
"location permission"
]
},
"output": {
"coveragePercent": 66.66666666666666,
"matched": [
"pilot credential",
"location permission"
],
"missing": [
"airspace authorization"
],
"unexpected": []
}
}Limitations and assumptions
No airspace, weather, aircraft, operator credentials or jurisdictional flight permission is checked.
Numeric inputs must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Lists are limited to 100,000 entries; the rules above may require smaller limits. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors.
Alternative or Complementary methods
Use Live-Shot Checklist: Audit pre-air live-shot checklist completion. For a complementary task, use HEFAT Coverage: Audit hostile-environment and first-aid training module completion.
References
-
Drone Requirements Check — tool.io
Similar or alternative tools
- Live-Shot Checklist
Audit pre-air live-shot checklist completion.
- HEFAT Coverage
Audit hostile-environment and first-aid training module completion.