AAE5304 Chap.5 Hong Kong Approval Routes and Evidence
Hong Kong Approval Routes and Evidence
Let the mission select the route
AC-013 addresses BVLOS sandbox operations, AC-014 addresses Category C advanced operations and AC-017 addresses cross-boundary Sandbox X operations.
All use a common permission basis, while their evidence emphases differ.
Join overlapping triggers
A Category C BVLOS mission may need aircraft design and maintenance evidence alongside BVLOS link, crew, containment and contingency evidence.
Cross-boundary work adds destination compliance, tracking, customs, security and coordination.
Audit consistency
Flight plan, risk assessment, operations manual, training, maintenance and emergency procedures must describe the same configuration and assumptions.
Trace each requirement to a claim, owner, criterion and controlled record.
Start with a trigger statement
Write the aircraft classification, visibility condition, operating location and boundary facts in separate lines. Place the relevant circular beside each fact.
This prevents aircraft category from swallowing the BVLOS route and prevents a cross-boundary route from replacing underlying aircraft, crew or maintenance requirements. When a mission fact changes, the trigger statement shows which evidence branch must be reopened.
Build one joined evidence matrix
Use columns for trigger, requirement, safety claim, evidence, owner, acceptance criterion, gap and closure date.
Common evidence may support several rows, but each link must remain explicit. A maintenance record can establish configuration control without proving route communications; a flight plan can describe geometry without proving the aircraft design.
The matrix preserves reuse while stopping one relevant document from becoming an unsupported answer to every requirement.
Test existence and adequacy separately
First ask whether the required item exists. Then ask whether it represents the proposed aircraft, route, crew and operating conditions at the required strength.
Endpoint mobile signal does not establish route coverage; an optional parachute does not support a credited mitigation; a generic certificate does not prove current mission competence.
Put the acceptance criterion in the matrix before reviewing evidence so closure is not chosen retrospectively.
Run a cross-document consistency audit
Search the package for configuration-critical names and numbers: aircraft identifier, software state, command link, parachute, route revision, altitude, speed, mass and crew role. Record mismatches, identify the controlled source and propagate the correction.
Then verify that every credited control appears in procedures, training, maintenance and records where relevant. Internal agreement is part of the safety claim, not editorial polish.
What this chapter covers
- 01
AC-013 BVLOS evidence
- 02
AC-014 Category C evidence
- 03
AC-017 cross-boundary evidence
- 04
Permission and registration
- 05
Risk, crew and maintenance
- 06
Coordination and evidence traceability
Worked example · free
Join Category C and BVLOS evidence
- 3Classify aircraft and visibility separately.
- 3Identify the overlapping approval evidence.
- 3Create distinct requirement rows and owners.
Key terms
- Advanced Operation
- An operation requiring authority permission and evidence beyond ordinary small-aircraft conditions.
- Destination Compliance
- The obligation to satisfy rules and approvals in the place reached by a cross-boundary operation.
- Compliance Matrix
- A table linking requirements and safety claims to acceptance evidence and ownership.
Hong Kong Approval Routes and Evidence FAQ
Can one operation trigger more than one circular?
Yes. Aircraft category, visibility condition and boundary can create overlapping evidence needs. A Category C BVLOS mission may need AC-014 design and maintenance evidence plus AC-013 operational-risk, link, crew and contingency evidence. Cross-boundary work can add AC-017 coordination and destination requirements.
Why is route coverage part of the safety case?
Command, tracking and navigation claims depend on performance along the whole route, not signal at the endpoints. Coverage evidence should match the installed system, environment, failure thresholds and contingency plan, with communications-authority or network coordination where the route requires it.
How do I test an application for consistency?
Pick every credited mitigation and follow it across aircraft configuration, risk calculation, flight plan, operations manual, training, maintenance and emergency procedure. If its name, assumptions or status differ, the safety credit is not controlled and the affected analysis must remain open.
Can one evidence item support several routes?
Yes, when each requirement-to-evidence link is explicit and the item's scope, configuration and acceptance criterion are adequate for every claimed use in the application package.
Exam move
Create three columns for AC-013, AC-014 and AC-017. Sort permission, aircraft, risk, crew, maintenance, insurance, coordination, communications and records into each. Then test mixed scenarios and explain why joined evidence is required. Add an owner and acceptance criterion to every row.
Finish by changing one mission fact, marking which triggers remain active and tracing the exact documents, assumptions and approvals that must be updated. Practise one Category C BVLOS case and one cross-boundary case, beginning with aircraft, visibility, location and boundary facts rather than a circular number.
For each cited document, ask whether it merely exists or actually matches the route, configuration and required strength. End with a six-item consistency search across identifiers, software, command link, altitude, speed and crew roles. A strong answer shows overlap without claiming that one approval route absorbs another.
