An FPV label, a past visual-observer summary or a product weight claim does not decide a particular event. Keep the actual site, people, exact equipment, viewing or support roles, event scope and current responsible-route answers together before the session.
What should a team establish before planning an FPV session in Canada?
Decision layer
Evidence to retain
What it can establish
What it cannot establish
Site and people
Exact site, event organiser, participants, spectators, staff, access and a ground alternative
What the proposed session involves
That an FPV label settles the whole site plan
Exact system
Aircraft, goggles, controller, batteries, accessories, version, serial and condition record
What equipment is actually proposed
That a product name determines every requirement
Roles and visibility
Named responsible people, communication plan, viewing or support roles and boundaries
Who is accountable for the session
That a generic role description approves an event
Current route
Current responsible route for the actual site, people and activity
What needs confirmation
A fixed certificate, fee, fine or observer conclusion
Stop condition
A written reason to pause when site, people, equipment or current answers conflict
When the session should stop
That a previous event guarantees a current result
Why should an FPV session plan name the actual people and site?
The practical question is not whether a label applies in the abstract. The team needs a visible site and people plan, documented equipment and a current route for the specific session. That is more useful than a copied fine, certificate or product-weight claim.
How should a team turn the review into an action plan?
Action
What to retain
1. Define the site and event
Record the exact location, organiser, participants, spectators, staff and ground alternative.
2. Document the exact system
Keep aircraft, goggles, controller, batteries, accessories, version, serial and condition evidence.
3. Name responsible roles
Write who coordinates the session and how people communicate and remain within boundaries.
4. Use a current route
Confirm the current route for the actual site, people and activity.
5. Keep a stop rule
Pause when site, people, equipment or written answers do not support the session.
