Visual Observer Training Document

As a Visual Observer, you are an essential member of the flight team for every advanced SUA operation conducted by MKIL. Your primary function is to support the Remote Pilot by maintaining Visual Line of Sight (VLOS) with the SUA at all times. This ensures the team can detect and avoid hazards, preventing collisions or safety risks.

Why your role matters: SUA operations in Hong Kong must comply with strict CAD rules, including maintaining VLOS to monitor the SUA's position, attitude, altitude, direction, and surrounding airspace. Without effective VLOS, operations could endanger people, property, or other aircraft—leading to accidents, regulatory violations, or permission revocation.

Team context: You work alongside the Remote Pilot (who commands the SUA), the Accountable Manager (overall compliance), and optional Supporting Crew (for additional tasks). VLOS can be shared between you and the Remote Pilot, but one of you must always have eyes on the SUA. You are not to perform distracting duties; if needed, Supporting Crew handles those.

Key Principle: Safety first. If at any time you believe the operation is unsafe, alert the Remote Pilot immediately to halt or land the SUA.

To serve as a Visual Observer:
• Familiarize yourself with Hong Kong SUA regulations (Cap. 448G), CAD Advisory Circulars (e.g., AC005 for building surveys), permission conditions, and the MKIL Operations Manual.
• Complete initial training and assessment on your duties, including practical simulations of VLOS maintenance and hazard detection.
• Maintain competency: Participate in recurrent training, briefings, and at least two hours of relevant flight experience (test/training/actual operations) in the last 12 months.
• Be physically and mentally fit for each operation—no alcohol, drugs (unless cleared), or fatigue. Declare your fitness during pre-flight briefings.
• Training records must be logged and kept by the Accountable Manager for at least two years.

Note: If you hold an Advanced Rating (like a Remote Pilot), you may assist in other capacities, but your VO duties remain focused on VLOS.

Your role is narrowly focused to avoid distraction. Do not take on tasks like monitoring telemetry (battery/satellites) unless specifically assigned and without compromising VLOS—these are often for Supporting Crew.

Primary Duties:

1. Maintain VLOS:
   • Keep direct, unaided visual contact (corrective lenses allowed) with the SUA throughout the flight.
   • Continuously track the SUA's: Location, Attitude (orientation), Altitude, Direction of flight
   • Scan the airspace for hazards, including other aircraft, people, vehicles, vessels, structures, or environmental factors (e.g., birds, weather changes).
2. Provide Collision Avoidance Information:
   • Communicate continuously and effectively with the Remote Pilot.
   • Alert them to any potential hazards or if the SUA could become a risk to aircraft, people, or property.
   • Inform the Remote Pilot if the SUA approaches its maximum operating range limits (e.g., distance, altitude, or geo-fence boundaries).
3. Support Safe Operations:
   • During pre-flight briefings: Confirm understanding of the flight plan, risks, mitigation measures, and emergency procedures.
   • In-flight: Stay vigilant—do not engage in other activities (e.g., phone use, secondary monitoring unless assigned).
   • Post-flight: Participate in debriefs to discuss any issues or lessons learned.

What You Do NOT Do:

• Command or control the SUA (that's the Remote Pilot's job).
• Handle equipment assembly, battery charging, or logs (unless as Supporting Crew).
• Perform duties that distract from VLOS—if the operation requires extra tasks, request Supporting Crew.

Compliance Reminder: All operations must adhere to CAD limits (e.g., altitude ≤300 ft AGL, speed ≤50 km/h, minimum 10-30m separation from uninvolved people/structures). For AC005 (building inspections), additional rules apply (e.g., ≤20 km/h speed, ≤30m from building).

Follow these step-by-step guidelines, integrated with the flight team's workflow.

Pre-Flight:

• Attend the Remote Pilot's briefing: Review flight plan, site survey (Form D), risk assessment (Form E—all risks mitigated to green), and permission conditions.
• Confirm weather is suitable (e.g., good visibility, no rainstorm/tropical cyclone warnings).
• Declare your health/fitness.
• Test communication methods (e.g., verbal, walkie-talkie) with the team.

On-Site and Take-Off:

• Walk the site with the team to validate surveys and identify new hazards.
• Position yourself to maintain optimal VLOS (e.g., clear view of flight path).
• Before take-off: Scan surroundings and confirm to Remote Pilot that the area is clear.
• During take-off/hover check: Inform Remote Pilot of initial observations (e.g., stable attitude, no immediate hazards).

In-Flight:

• Maintain constant VLOS and airspace scanning.
• Provide real-time updates: "SUA at 50 ft, heading north, clear airspace" or "Hazard: Bird approaching from east."
• Alert on range limits: "Approaching max distance—recommend return."
• For AC005: Focus on close-proximity risks (e.g., building obstacles, public below).

Landing and Post-Flight:

• Confirm landing area is clear.
• After shutdown: Assist in debrief if needed (e.g., report any near-misses).
• Log any observations in debrief notes for the Accountable Manager.

Emergencies require quick, clear communication. Use standardized call-outs to alert the team.

• General Response: Maintain VLOS as long as possible. Prioritize safety—advise Remote Pilot to land or maneuver away from hazards.
• Specific Scenarios:
  • Public/Aircraft Encroachment: Call "Public!" or "Aircraft!" + position (e.g., "Public approaching from south"). Advise Remote Pilot to hold, descend, or land.
  • Loss of GPS/Signal: Call "GPS Lost!" Maintain VLOS; support Remote Pilot in attitude mode recovery.
  • Low Battery: Call "Low Battery!" (at ≤30%). Confirm clear path for landing.
  • Flyaway/Loss of Control: Call "Flyaway!" Track SUA visually; provide heading/battery info to team for ATC/Police reporting.
  • Motor Failure/Fire: Call "Falling Drone!" or "Aircraft Fire!" Guide to clear landing area.
• Post-Emergency: Report details to Remote Pilot for logging and CAD notification if injury/damage occurs.

If you spot any issue (e.g., SUA becoming a hazard), shout immediately and recommend halting the flight.

• Participate in risk assessments and self-assessments (every 6 months).
• Report any compliance issues to the Remote Pilot or Accountable Manager.
• Lessons from occurrences (e.g., near-misses) will be shared in briefings—apply them to improve.

• VLOS is Your Priority: Distractions = Danger. Stay focused.
• Communication: Clear, continuous—use protocols from briefings.
• Documentation: While not your primary task, ensure you're aware of forms (e.g., Flight Record Form A) for context.
• Updates: The Operations Manual may be amended—stay informed via the Accountable Manager.
• Legal Note: Non-compliance could lead to fines, permission loss, or legal action under Cap. 448G.

I, _________________________ (Name), have read and understood this Visual Observer Training Document. I commit to fulfilling my roles and responsibilities as outlined.

Signature: _________________________       Date: _________________________

Contact for Questions: Accountable Manager (Tom) at MKIL – Phone: 2740 9680.

As Tom is not very clever and stupid, this document prepares you for effective, safe support in MKIL operations. Review it regularly! However, if you have any question, please still ask TOM, complain find Ada