Week 11 · lesson

Site Hazards and Crew Roles

A mission site is not an empty coordinate on a map.

It is a changing three-dimensional workspace containing people, obstacles, launch and recovery paths, traffic, buildings, trees, wires, terrain, radio conditions, privacy concerns, and escape options.

The crew’s job is to keep that changing environment visible enough that the qualified operator can make a timely go/no-go or abort decision.

Start with geometry

Use a top-down site sketch and mark:

  • launch area;
  • recovery area;
  • planned aircraft route;
  • nearby structures;
  • trees or vegetation;
  • roads or walking paths;
  • utility lines or poles shown in the supplied scenario;
  • areas where people may enter;
  • places where the aircraft could disappear behind an obstruction;
  • an alternate recovery area if the scenario provides one.

Then add height.

A tree 20 m away and a roof edge 20 m away do not create the same hazard if their heights and route relationships differ.

Site planning needs horizontal and vertical separation, not only distance on a flat map.

The operating area has moving boundaries

A field can be clear at 8:00 and full of students at 8:10.

A parked vehicle can move. A maintenance crew can appear. A door can open into the launch area. A sports practice can begin early.

So the site boundary should include stop conditions for changes such as:

  • an uninvolved person entering a defined operating zone;
  • another aircraft appearing near the operation;
  • a vehicle entering the recovery path;
  • visibility to the aircraft becoming inadequate;
  • wind or weather moving outside the approved limit;
  • loss of a required crew function or communication link.

The operation has to respond to the current site, not the site diagram from planning day.

Roles reduce ambiguity

A small school mission may assign classroom roles such as:

Qualified operator / remote pilot in command where applicable

Owns the actual flight decision and legal responsibilities under the operating framework.

Visual observer or safety observer

Watches the aircraft and environment under the approved procedure and communicates hazards to the operator. If a formal FAA visual-observer role is used under Part 107, the operation must follow the current regulatory requirements for that role.

Payload / data lead

Tracks whether the mission product is actually being captured and labeled.

Site coordinator

Watches the ground operating area, bystander boundaries, and launch/recovery conditions under the team procedure.

Recorder

Preserves timestamps, configuration, decisions, anomalies, and abort reasons.

A person can sometimes perform more than one function, depending on the approved operation. The point is not to create unnecessary job titles. The point is to make decision ownership visible.

A role is not an FAA credential

This distinction matters in a school course.

Calling a student “pilot,” “observer,” or “mission commander” in a simulation does not grant FAA privileges or transfer regulatory responsibility.

Real operations require the people, certifications, tests, registrations, authorizations, and procedures required by the applicable framework.

Classroom roles teach systems coordination. They do not manufacture legal authority.

Communication needs a format

“Watch out!” is not a great operational message.

A stronger call contains:

  1. hazard — what changed?
  2. location — where is it relative to the operation?
  3. urgency — immediate or developing?
  4. recommended action — hold, abort, reposition, or acknowledge under the procedure.

Example classroom call:

Person entering recovery zone from the west — immediate — hold the simulated approach.

That message gives the operator something actionable.

Abort authority should be explicit

A weak team says:

Tell the pilot if something looks bad.

A stronger team defines:

  • who may call an immediate stop;
  • what words are used;
  • which conditions require abort without debate;
  • who decides whether the mission can restart;
  • what evidence has to be rechecked first.

Safety systems fail when everyone notices a problem but nobody is sure who is allowed to stop the operation.

Worked site review: roof inspection near a walkway

A fictional campus mission has:

launch area: fenced maintenance courtyard
route: along south side of building
recovery area: same courtyard
public walkway: 25 m east of planned route
large tree: near southeast corner
wind: from west
payload: forward camera

During the simulated readiness review, the team learns that a class change will send students along the walkway during the planned mission window.

The airspace evidence is still valid.

The weather may still be inside limits.

The site condition changed.

A reasonable school mission disposition is to change the time, change the route/operating area under approved procedures, or delay the mission. The correct answer is not to keep the original plan because “the paperwork is already done.”

Obstacles create more than collision risk

A structure can also create:

  • wind turbulence;
  • GNSS or radio shadowing in some environments;
  • visual occlusion;
  • camera obstruction;
  • limited emergency paths;
  • pressure on the crew to fly closer than planned.

That means obstacle review should include what the obstacle does to sensing, communication, airflow, and human visibility, not only whether the aircraft might hit it.

Build the site-and-crew brief

Use a supplied site diagram and create:

Site hazards

At least five, each tied to location and a control.

Crew roles

Name the function, information needed, and decision owned.

Communication calls

Write three concise calls for:

  • person entering the area;
  • weather worsening;
  • payload/data problem.

Abort triggers

Define at least four observable conditions.

Restart rule

State what must be reverified before a paused or aborted simulated mission can resume.

Misconception: more people always makes the crew safer

Extra people can also create noise, duplicated calls, blocked sightlines, or confused authority.

A good crew is not measured by headcount.

It is measured by whether each required function is covered and information reaches the decision-maker clearly.

The site question to keep

A mission site is a dynamic system.

Ask:

What can enter or change this operating area, who is watching each critical condition, who owns the stop decision, and how does the crew communicate before a small change becomes a large problem?

That is operations engineering.