Programme 01
Drone and UAV Operations
- Level
- Intermediate
- Duration
- 4 days
- Cohort
- 8–16 players
- Formats
- In-person, Hybrid
Drone training usually arrives in two unhelpful halves. One is a certification course: the regulation, a syllabus, and enough stick time to pass a test. The other is a software course: which buttons produce an orthomosaic. Neither produces someone who can be handed a site, asked what the volume is, and give an answer with a credible statement of how wrong it might be.
This programme runs the whole chain once, properly. What to fly and what to carry it with. What the rules currently permit, and how to find out rather than assume. How to plan a mission that will actually reconstruct. How to establish control so the output sits where it claims to sit. And how to state accuracy in a form an engineer, an auditor or a contractor's quantity surveyor will accept.
Roughly half the time is spent outside or inside the processing software rather than in front of slides. The day-four deliverable is built from imagery the cohort flew and control the cohort measured, which means the errors in it are their own.
Learning outcomes
What a player can do afterwards.
- 01Select an airframe and sensor combination from the survey requirement rather than from a specification sheet
- 02Plan a mission (altitude, ground sample distance, overlap, flight pattern and battery envelope) that produces imagery which will reconstruct
- 03Establish what the current regulation requires for a given flight, and use Digital Sky and the airspace map to determine where and under what conditions you may fly
- 04Design and measure a ground control and checkpoint network, and explain why badly placed control is worse than none
- 05Process imagery to an orthomosaic, surface model and point cloud, and read the processing report for the evidence that the result is sound
- 06State the accuracy of a deliverable as a measured error against independent checkpoints, and defend it under challenge
- 07Turn a survey into a decision: a volume with an error band, a change larger than the noise, an encroachment with a location attached
Curriculum
4 days, hour by hour.
Platforms, sensors and the rules you fly under
Anchor exercise
Three real briefs (a quarry volume, a transmission corridor and a rooftop solar array) for which players specify platform, sensor and regulatory route, then defend the choices as the facilitator adds constraints: no site access on one side, a yellow zone boundary, a client accuracy clause.
- Starting from the requirement: accuracy, coverage, revisit frequency, and what each one costs in platform terms
- Multirotor, fixed wing and VTOL, endurance, site access, wind tolerance, and where each stops being sensible
- Sensor selection: RGB for geometry, multispectral for condition, thermal for anomaly, lidar where vegetation or canopy defeats photogrammetry
- Mechanical versus rolling shutter, sensor size and focal length. The geometry is decided here, before any software sees it
- The Indian framework: the Drone Rules and the amendments since, what the DGCA administers, categories by take-off weight, registration and the unique identification number, type certification
- Remote pilot certification: who needs it, the exemptions that exist, and where authorised training organisations fit in relation to a programme like this one
- Digital Sky as the operating platform, registration, permissions, and the airspace map as the authoritative source
- Green, yellow and red zones, the altitude ceiling that applies without permission, and the process where permission is required
- What sits outside routine permission (beyond visual line of sight, night operations, payload carriage) and the approvals each needs
- Third-party insurance, operator liability, and what a client will require you to hold before you fly on their site
- Reading the rules as they stand on the day: where the current text and the live map are published, and why no course can be your standing reference
Mission design, control and the accuracy you are promising
Anchor exercise
Control design on a supplied site. Players place control and checkpoints against a stated accuracy requirement, then watch the same block reconstructed three ways (with their network, with a deliberately clustered one, and with none) and read the resulting error against the checkpoints.
- Ground sample distance from sensor geometry and altitude, chosen from the smallest feature that must be resolved
- Forward and side overlap, the surfaces that demand more of both, and what insufficient overlap does to a reconstruction
- Flight patterns: single grid, cross-hatch, corridor, orbit and oblique, and what each is actually for
- Exposure discipline: shutter speed against ground speed, fixed focus, and the motion blur no processing step recovers
- Absolute accuracy against relative precision, which one the deliverable requires, and the cost of confusing them
- GNSS positioning: standalone, network RTK from a reference station, and PPK against a local base, with the accuracy each actually returns
- Datums, projections and the vertical problem: ellipsoidal against orthometric height, geoid models, and the metre-scale error that follows from ignoring the difference
- Ground control design: how many points, where they go, target size against GSD, and why clustering them defeats the purpose
- Checkpoints withheld from the adjustment, because control the solution was fitted to cannot measure your error
- Error expectations: the rules of thumb relating horizontal and vertical error to GSD, and the conditions under which they hold
- Writing the accuracy requirement into a scope of work, so what is being promised is measurable before the aircraft leaves the ground
Field operations
Anchor exercise
A full field day. Crews fly a mapping mission and a corridor mission on a live site, establish and measure the control and checkpoint network, and demobilise only once the data has been checked on site against the plan.
- Site reconnaissance: obstructions, launch and recovery areas, people and livestock, and the things that are never on the map
- The pre-flight sequence run as a checklist and not from memory, airframe, propellers, battery state, compass and IMU, camera settings, storage, home point
- Crew roles: pilot in command, observer, and who on the site is allowed to say stop
- Weather limits that matter, wind at altitude rather than at head height, temperature and battery behaviour, light angle and shadow, precipitation
- Failsafes understood before they trigger: return-to-home altitude, lost link behaviour, low battery response
- Flying the plan: monitoring coverage, image count and reserve as the mission runs, and knowing when to abort a line
- Measuring the control network with a survey-grade receiver, and the observation and log discipline that makes those measurements defensible afterwards
- Verifying data on site (coverage check, image quality check, control sheet reconciled) because the reflight you fly now costs a battery and the one you fly next week costs a day
- Incidents and near misses: what to do, what to record, and what has to be reported
Processing, accuracy assessment and the deliverable
Anchor exercise
Players process their own day-three flight to a complete deliverable set, compute the error against the checkpoints they measured themselves, and present a one-page finding with the accuracy statement attached for cohort critique.
- The structure-from-motion pipeline: feature matching, bundle adjustment, densification, surface and orthomosaic generation
- Reading the processing report, reprojection error, tie points per image, camera calibration, and the residuals on control and checkpoints
- Systematic failures and their signatures: doming on a nadir-only block, water, moving vegetation, repeating pattern surfaces, and the fixes for each
- Surface models: DSM against DTM, ground classification, and what is removed at each step
- Producing the deliverable set, orthomosaic, point cloud, surface, contours, cross sections and volumes
- Accuracy assessment against independent checkpoints, reported as horizontal and vertical RMSE with the checkpoint count and confidence stated
- Change detection across epochs: propagating error over two surveys, and the threshold below which a difference is not a finding
- Volumetrics: base surface selection, bulking and swell assumptions, and why a volume dispute is nearly always about the base rather than the survey
- Writing for the person who has to act, the finding, the number, the error on the number, and the location
- Handover: coordinate systems, file formats and metadata that survive contact with the GIS the client already runs
Assessment
How it is marked.
Assessment is on the work produced during the programme: the mission plan and control design from day two, the conduct of the day-three flight against the pre-flight and log discipline expected of it, and the day-four deliverable with its accuracy statement. Certification requires a processed dataset that meets the accuracy stated for the site and an error statement the faculty can verify against the withheld checkpoints. Sponsoring organisations receive an anonymised cohort profile identifying which parts of the workflow the group can run unsupervised and which still need a second pair of hands.
Questions
The ones we get asked.
Does this programme issue a remote pilot certificate?
No, and any programme that is not an authorised training organisation which tells you otherwise is misleading you. A remote pilot certificate is issued through the DGCA process and the organisations authorised to run it, and it tests flying competence against a defined syllabus. This programme is the other half of the job, what to fly, how to plan it, how to control it, and how to turn the imagery into a measurement you can defend. Organisations commonly run the two in parallel or send people here after certification. If certification is what you need first, we will say so.
The regulation keeps changing. How current is the material?
The framework is stable in shape: categories by weight, registration, pilot certification, an airspace map with permission zones, and additional approval for anything beyond routine flight within visual line of sight. The detail underneath it moves. We teach the structure, teach where the current text and the live airspace map are published, and run each cohort against the rules as they stand that month. What we will not do is hand you a printed threshold to rely on for the next three years.
Do players need to have flown before?
No. Crews are paired so anyone new to the controls flies alongside someone more experienced, and the mapping missions are flown autonomously, which is how survey work is flown in any case. What the programme does assume is comfort with coordinates, elevations and simple arithmetic on error, because that is where the difficult part actually lives.
Can this be delivered virtually?
Days one, two and four can be. Day three cannot, and we will not pretend otherwise, what the programme is really teaching is what a competent crew does on a site before, during and after a flight, and none of that survives a video call. The hybrid format runs the planning, regulatory and processing days remotely and convenes the cohort for the field day.
Can you run it on our own site with our own aircraft?
For closed cohorts that is the better arrangement by some distance. Flying your equipment on your site means the mission plans, the control network and the coordinate system are the ones the team will use afterwards, and the day-four deliverable is a real survey of an asset you own rather than an exercise. We need site access, the relevant permissions and confirmation of the airframe and sensor in advance so the processing is configured before the cohort arrives.
The other programmes
Analytics for Supply Chain Professionals
Five days building working models in Python, forecasting, inventory optimisation, network design and simulation.
Supply Chain Fundamentals
The mental models that make the rest of it comprehensible (variability, flow and trade-offs) and the planning cycle where those trade-offs get settled or deferred.
Enquire
Run Drone Operations for your team.
Tell us the roles, the current level and what the team has to do differently afterwards. We will confirm whether this is the right programme or point you at a better fit.
Or write directly to hello@shyenova.com
