A crop-monitoring request, an Air 3S listing and an older statement about a permit are separate inputs. Start with the farm question, exact kit, responsible site contact and the current DGAC and location route for the proposed activity; do not turn a generic article into a fixed certificate, cost, insurance or height answer.
What should a Peru farm team establish before proposing an Air 3S crop-monitoring project?
Decision layer
Evidence to retain
What it can establish
What it cannot establish
Farm brief
Crop question, required evidence, field context, responsible contact and grounded alternate
What the monitoring project needs
That aerial capture is assured
Exact Air 3S kit
Aircraft, controller, camera, batteries, accessories, serial, condition and included-items record
Which individual system is proposed
A result for another configuration
Output review
Representative capture plan, sample-output criteria and stated limitations
What the proposed workflow will be tested to provide
A universal crop-monitoring capability
Farm-site route
Responsible farm contact, site boundaries and current written response
Which site questions need confirmation
Access based on a broad farming example
Current DGAC route
Current official and location information for the proposed activity
Which operating questions need current confirmation
A fixed permit, certificate, cost, insurance or altitude result
Why should a crop question be tested against outputs rather than a broad model claim?
A useful farm project begins with the decision the team needs to make from the proposed evidence. A documented sample review can show what the exact kit and planned capture provide for that question. It does not replace the responsible farm-site process or the current official route for the actual location and activity.
How should a team turn the review into an action plan?
Action
What to retain
1. Define the farm question
Record the crop question, evidence required, field context, responsible contact and grounded alternate.
