Drones: Operations and Applications

Understand the four forces and the parts so faults make sense. You will explain how lift, weight, thrust and drag act on a multirotor, so you can reason about a fault instead of guessing at it.

• Lift, weight, thrust and drag; four or more rotors give control by changing speed.
• Parts: frame, motors, battery, flight controller, sensors, radio link, camera.
• Positioning by satellite signal; what happens when the signal is lost.
• Return-to-home and failsafe settings must be checked before every flight.
• Learn the four forces of lift, weight, thrust and drag, and note that a multirotor holds position only because its controller adjusts motor speeds many times each second.
• Check battery health before every flight. Retire a battery that is swollen or loses charge fast under load. Follow the maker's limits, because power loss is a leading cause of crashes.
• Learn the sound and feel of each motor; unusual vibration is the earliest warning of a fault.
• Keep spare propellers and a screwdriver in the kit.

Activity. Label a drone diagram and write what each part does.

Standard to meet. Label all main parts and explain failsafe behaviour in your own words.

Common mistake. Thinking the drone is a toy and skipping the failsafe check.

Check yourself. Name the parts that fail most often and how you check each.

Rules protect people and decide whether you may fly at all. You will check current rules, airspace limits and your paperwork before each new site, so you know in advance whether a flight is allowed.

• Find your authority's registration, pilot knowledge and no-fly rules.
• Keep away from crowds, airports, prisons, power sites and emergencies.
• Get written permission from land owners and respect privacy.
• Check insurance: who pays if something goes wrong?
• Before a new site, read the current national rules and airspace map, note the current height limit for that place, and save a screenshot of what you checked with the date.
• Keep a folder with your registration details, pilot proof, insurance document and any site permission, so you can show them quickly if someone asks.
• Write the emergency contact and the nearest landing site on the checklist.
• Check whether schools, hospitals or prisons nearby have their own no-fly rules.

Activity. Write a one-page rules note for your place and get the mentor to check it.

Standard to meet. Name the authority, limits and permissions required in the rules note.

Common mistake. Assuming rules are the same as in another country.

Check yourself. What are the height and distance limits in your place?

Risk is chance times harm. Write it down and reduce it before launch. You will score hazards for likelihood and harm, write controls and set go or no-go limits, so decisions are made calmly before launch.

• List hazards: people, wind, trees, wires, signal loss, battery failure.
• Score chance and harm 1 to 5; multiply for a risk score.
• Add a control for every score of 10 or more.
• Name who stops the flight and when.
• List hazards by category such as people, property, wildlife, weather and radio interference, then give each a likelihood and severity score from 1 to 5 and a control.
• Set go and no-go limits in advance. For example, do not fly if wind gusts exceed 10 metres per second or visibility is under 1 kilometre. Then the decision is made before pressure builds.
• Re-score the risks when weather changes; a plan is not fixed for the day.
• Brief every helper in two minutes: what to watch, who can say stop.

Activity. Complete a risk assessment for your mission.

Standard to meet. Give every high risk a control and an owner.

Common mistake. Writing "low risk" without a score.

Check yourself. Which hazard has your highest score, and what is the control?

Checks come before skill. Then practise slow, smooth control. You will follow a written pre-flight checklist and fly basic patterns smoothly, building the control habits that keep people and equipment safe.

• Checklist: weather, battery, propellers, firmware (the drone's built-in software), memory card, radio, return point.
• Practise take-off, hover, square, figure of eight and landing.
• Keep line of sight unless your rules allow otherwise.
• Log every flight: date, place, time, battery, faults.
• Practise a square, a circle and a slow figure of eight at 10 metres height until each is smooth, then repeat with the nose pointing toward you.
• Use a printed pre-flight checklist covering props, battery seating, memory card, compass, home point and a short hover at 1 metre before climbing.
• Practise a manual landing from 10 m in a simulator first. Then practise in an empty field with a safety observer.
• Never fly with a swollen or damaged battery; store batteries in a fire-safe bag.

Activity. Fly or simulate five practice drills and log them.

Standard to meet. Log five drills and use the checklist each time.

Common mistake. Flying until the battery warning and landing in panic.

Check yourself. What is your land-by time for the mission?

A good plan sets height, overlap and speed to match the question. You will pick height, overlap and speed to match a client's question, so the pictures you collect can actually answer it.

• Choose height: lower gives more detail, covers less.
• Plan overlap of about 75% front and 65% side for mapping.
• Plan batteries and landing spots; fly at steady light.
• Take a few ground reference points for accuracy checks.
• For mapping missions choose about 75 percent forward overlap and 65 percent side overlap, and fly at a steady height so the pixel size stays the same across the site.
• Time flights for even light, ideally midday for mapping or the golden hours for visuals, and avoid shifting cloud that creates patchy exposure across the images.
• Fly slower for sharper images; blur is a common cause of failed maps.
• Plan the mission so the sun is behind you where possible, to reduce glare.

Activity. Write the mission plan with a map and battery table.

Standard to meet. Plan has height, overlap, passes, batteries and a stop rule.

Common mistake. Planning one huge flight instead of safe, short ones.

Check yourself. How many batteries does your plan need and why?

Raw pictures are not an answer. Process, check, then explain. You will process images, check results against known ground points and judge accuracy, so your numbers can be trusted before anyone sees them.

• Build a map or model with a free tool; check gaps and blur.
• Compare a measured distance on the ground with the map to find error.
• Remove people and plates before sharing.
• Store files with dates and a backup.
• After processing, check three ground points of known position and compare; an error over twice the pixel size (the ground width of one image dot) means the control or the settings need another look.
• Back up the raw images to two places before you start processing, and name folders by date, site and flight number so you can trace any result.
• Keep a copy of raw pictures separate from processed maps.
• Mark any area with gaps so the client knows what is missing.

Activity. Process your pictures and calculate one error figure.

Standard to meet. Calculate the error figure and list gaps with causes.

Common mistake. Trusting the map without a ground check.

Check yourself. What is the error figure for your map?

The report answers the client's question in plain words with numbers. You will write a short client report with a direct answer, a map and honest limits, so the reader can act without needing the raw files.

• Start with the answer, then three supporting findings.
• Add a map or picture for each finding, with scale and date.
• State limits: weather, accuracy, areas missed.
• Give next actions and costs in your own currency.
• Open with a one-paragraph answer to the client's question, then add a map, two key images, the method in five lines and a note on the accuracy found.
• State plainly what the data cannot show, such as ground under dense trees, and offer a follow-up flight rather than stretching the claims.
• Use the same scale bar and north arrow on every map in the report.
• Add a one-line cost per hectare so the client can compare with other methods.

Activity. Write a two-page report for your mission.

Standard to meet. Answer first; every claim has a picture or number.

Common mistake. Burying the answer on page two.

Check yourself. Does your first line answer the client question?

Reflect on what went wrong and right and plan your growth. You will review your flight log for repeated slips and set measurable goals, turning each flight into practice for the next.

• Hold a short debrief: what happened, why, what to change.
• Give two peers written feedback.
• Share a checklist or template to help the next learner.
• Plan next 90 days: hours to log, skills to add.
• After every five flights, review the log for patterns such as the same checklist item missed or a battery that sags, and write one improvement for the next five.
• Set three goals for 90 days, for example one new mission type, a documented accuracy check and one client report, and review progress monthly.
• Share a near-miss report even if nothing went wrong; patterns show up early.
• Set a flight-hours target for the next 90 days and log each hour.

Activity. Hold the debrief and write the plan.

Standard to meet. Write a debrief with at least three changes and dates.

Common mistake. Skipping the debrief after a good flight.

Check yourself. What one change will you make to your checklist?

A client asks for a sunset shot over a street fair.

Question: What is your answer?

Model answer: Decline over the crowd. Offer a shot from a permitted position that keeps people away, after checking rules and getting permission.

Forecast gusts rise from 6 to 11 m/s during your slot. Stop limit is 10 m/s.

Question: What do you do?

Model answer: Postpone or fly earlier within the limit; log the decision and the forecast.

On the slide: L1 Basic · Basics of flight

Notes: Explain how a drone flies: lift, thrust, weight and drag, and the parts that control them. Notes: watch a flight and name the parts and forces. Standard: a labelled sketch with four forces and four parts.

On the slide: L2 Awareness · Awareness of rules

Notes: Describe registration, no-fly zones, height limits and privacy rules for your place. Notes: read your authority's public page together and note the rule numbers. Standard: five rules listed with their source and date.

On the slide: L3 Foundation · Safe operator basics

Notes: Run a pre-flight check, practise take-off, hover and landing drills, and plan a simple mission. Notes: a simulator is acceptable. Standard: checklist completed before every flight and three clean landings in a row.

On the slide: L4 Practitioner · Practitioner

Notes: Fly or simulate a short mission with a map, a battery plan and a written risk assessment. Notes: record battery use and wind at start and end. Standard: mission flown inside the plan, landing with at least 25% battery, risks and controls listed.

On the slide: L5 Specialist · Specialist mapping or inspection

Notes: Plan, fly (or simulate) and report one drone mission for a real client need, with a written risk assessment. Notes: choose mapping, inspection or film; the client report states what was done, what was found and the limits. Standard: permission obtained, risk assessment signed, report delivered with images and limits.

On the slide: L6 Advanced · Advanced operations lead

Notes: Plan multi-drone work with a safety system: roles, a flight log, an incident process and a maintenance schedule. Notes: add a briefing script and a check for each pilot's currency. Standard: every flight logged, incidents reviewed within a week and maintenance on schedule.

On the slide: L7 Super expert · Super expert

Notes: Set safety method and teach teachers. Notes: review incidents yearly and publish lessons.