A construction request, an Avata 2 FPV kit and an older statement about a licence are separate inputs. Begin with the project deliverable, exact kit, responsible construction-site contact and the current DGAC and location route for the proposed activity; do not turn an article into a fixed certificate, observer, insurance, fee or penalty answer.
What should a Chile construction team establish before proposing an Avata 2 FPV project?
Decision layer
Evidence to retain
What it can establish
What it cannot establish
Construction brief
Required scenes, project stage, people context, responsible site contact and grounded alternate
What the construction project needs
That aerial capture is assured
Exact Avata 2 kit
Aircraft, controller, batteries, accessories, serial, condition and included-items record
Which individual system is proposed
A result for another configuration
Site route
Current construction-site boundaries, responsible contact and written response
Which site questions need confirmation
Access based on a generic construction example
Current DGAC route
Current official and location information relevant to the actual proposed activity
Which operating questions need current confirmation
A fixed licence, observer, insurance, fee or penalty result
Decision record
Brief, kit evidence, current responses and alternate plan
What the team evaluated
Permission for another site or date
Why should a construction deliverable and current DGAC confirmation stay separate?
A construction contact can clarify the project stage, site access, people context and requested delivery. The proposed activity has a separate current official and location route. Keeping both records with the exact Avata 2 kit lets a team avoid treating a model label or older regulatory summary as a conclusion for the actual site.
How should a team turn the review into an action plan?
Action
What to retain
1. Define the construction deliverable
Record required scenes, project stage, people context, responsible contact and grounded alternate.
