Drones: The Almond Run
Welcome to Day 1. Today you are a drone pilot.
By the end of the day, you will have flown a real drone, navigated an obstacle course, written your first lines of code, and programmed a drone to survey a simulated almond orchard — the exact same job ag drone pilots do for Merced County growers right now.
No experience required. Five hours from now you will know things you didn't know this morning.
You live in one of the most heavily monitored airspaces in America — and almost none of it is by planes. It's drones.
Merced County has roughly 540 dairies, hundreds of thousands of acres of almonds, and walnut orchards from here to Stevinson. Almost every large grower around Gustine uses drones for at least one of these jobs:
- Canopy imaging — fly an almond orchard with a multispectral camera, find which trees are stressed before you can see it from the ground.
- Irrigation inspection — walk a 200-acre field looking for a leak, or fly it in 12 minutes.
- Herd monitoring — count cattle, check for downed animals at the edges of a pasture.
- Precision spraying — apply fertilizer or pesticide to just the trees that need it, not the whole orchard.
All of this is real. None of it is futuristic. It's what UC Merced researchers, ag service companies in Modesto and Turlock, and individual growers do every week.
- Boot Camp — fly the drone manually
- Flight Challenges — precision landings + obstacle course
- — lunch —
- Code It — write your first drone program in DroneBlocks
- Aerial Crop Survey — program your drone to fly an almond orchard pattern
- Propellers spin fast enough to cut skin. Hands away from the drone whenever the props are spinning.
- Never grab a drone out of the air. Tell it to land. Wait.
- Eyes on your own drone. If you're not the pilot in your pair, you're the spotter — eyes up, calling obstacles.
- When you hear "PROPS DOWN," every drone lands. No exceptions.
Before code, before challenges, before anything — you need to know how the drone moves. By the end of this section, every pilot will have taken off, hovered, moved in all six directions, and landed without a crash.
- 1 Tello drone
- 1 charged battery
- 1 phone
- 📋 Pilot's Log
- Find your partner. Pick a Pilot and a Spotter. You'll swap roles every 5 minutes.
- Find your numbered drones Wifi address in the battery compartment. Memorize the number — you'll need it to connect to the right one.
- Snap a battery in. The drone's lights blink amber when it's ready to pair.
Important: Your phone has to leave the room WiFi to talk to the drone. Your drone has its own WiFi name that looks like TELLO-XXXXXX. You're connecting your phone to that network, not the building's.
- Open your phone's WiFi settings.
- Find the network that starts with
TELLO-. There will be many — pick the one labeled on YOUR drone. - Tap to connect. Ignore any "no internet" warning — that's correct, drones don't need internet.
- Open the Tello app. You should see the live camera view from your drone.
If you don't see a camera feed: forget the WiFi network, reconnect, and reopen the app. Most connection problems fix themselves this way.
Real pilots run a checklist before every takeoff. So do you.
- Props — all four spin freely, no cracks
- Battery — clicked in, drone lights on
- Area clear — nobody within 3 feet of your drone
- Spotter ready — partner has eyes on the drone
- Pilot calls "CLEAR" — out loud, before takeoff
Place the drone on the floor in front of you. Step back. Run your pre-flight check. Call "CLEAR." Then:
- Takeoff — tap the takeoff button in the Tello app. The drone climbs to about 3 feet and hovers. Just watch it. Don't touch anything else for 10 seconds.
- Land — tap the land button. Watch it come down. That's one full flight. Do this 3 times before you touch the joysticks.
- Hover and translate — take off again. Use the left joystick (up/down/rotate) and the right joystick (forward/back/left/right). Move it 1 foot at a time. Small inputs. The drone is more sensitive than you think.
- Swap roles. Spotter becomes pilot. Pilot becomes spotter. Repeat.
What you just did is the entry-level qualification for a commercial drone pilot. The FAA's Part 107 license is open to anyone 16 or older, costs $175, and is the legal ticket to fly drones for money. From there, the work splits into half a dozen different careers — ag surveys, real estate, construction, infrastructure, public safety, cinematography — each with its own pay, schedule, and skill set. Pilots in the Central Valley earn $35–$75 an hour. The hardest part of the test isn't flying — it's reading airspace charts.
Manual flight isn't just keeping the drone up — it's putting it exactly where you want it. Today's two challenges build the muscle memory pros use every day.
Scoring:
- 3 points — landing gear inside the inner circle
- 2 points — landing gear inside the outer circle
- 1 point — drone touched the mat
- 0 points — drone missed the mat entirely
Take off from your home spot. Fly to the target. Hover above the center. Land. Don't rush the landing — the last 6 inches matter most.
The course is set up with hula hoops, pop-up gates, or whatever obstacles your facilitator put down. Walk it on foot first so you know where each gate is.
Rules:
- Clean run — pass through every gate without touching it
- Penalty — +5 seconds for each gate clipped or missed
- Crash — DNF (did not finish). Reset and try again.
- Spotter calls obstacles out loud. The pilot is looking at the screen, not the room.
Walk-it-first rule: before you fly the course, your partner walks it with their hand at drone height, pretending to be the drone. You watch and call the moves. Then you fly it.
First responders use drones in obstacle-heavy environments every week: searching a collapsed building after an earthquake, flying through a burning warehouse to find people, scanning a wildfire perimeter at night. CAL FIRE, the Merced County Sheriff's Office, and the California Highway Patrol all run drone programs. Search-and-rescue drone pilots are full-time public-safety employees with pensions, training, and stable salaries — and the work matters.
How might you use drones for search and rescue or a wildfire mission?
Lunch break. Drones go down on the table, props facing up. Batteries on the charging hub.
So far you've flown manually. That's how a hobby pilot or a real-estate photographer flies. But the drones flying almond orchards this week aren't being joysticked through every row. They're flying autonomously — running a program a human wrote, all by themselves.
That's what you're about to do. Write code. Run it. Watch your drone follow your instructions, exactly.
Watch the projector. Your instructor will demo DroneBlocks live — how blocks snap together, where the parameters go, and where the Run button lives. Pay attention to the order of blocks; that order is your program.
- Reconnect to the room WiFi (just for this step).
- App Store / Play Store → search DroneBlocks. The logo is a yellow drone on a blue square.
- Install. It's free.
- Open it. When it asks what drone type, pick Tello.
- Switch your phone back to your
TELLO-XXXXXXWiFi.
You're going to make the drone fly a square. Four sides, four turns, back to where it started.
Drag these blocks onto the canvas in this order:
Don't run it yet. Part III first.
The walk-it rule: before any code runs on a real drone, one teammate walks the path. Stand where the drone will start. Walk forward 50 cm (roughly 2 big steps). Turn 90° right. Walk forward. Turn right. Walk forward. Turn right. Walk forward. You should be back where you started.
If you walked it and ended up somewhere weird, your code is wrong. Fix it in DroneBlocks before you run it. Two ways to be wrong:
- Turn direction backward (left instead of right)
- Wrong number of forwards or turns
Walk it as many times as you need until it's right. Code that's been walked is code that flies.
Flight zone rules: Watch out for others. Be Careful.
- When it's your pair's turn, place your drone at the starting mark.
- Run your pre-flight check. Call "CLEAR."
- Hit Run Mission in DroneBlocks. Hands off the phone.
- Watch. The drone should fly a square and land near where it started.
What you just learned — drag-and-drop block coding — is the gateway to software engineering. Scratch, Snap, Blockly, DroneBlocks — they all teach the same thing: logic, sequence, repetition, conditionals. Real software engineers write in Python, JavaScript, or C++, but every one of them started with these same concepts. Bay Area software engineers — at companies like Skydio (autonomous drones, San Mateo), Joby Aviation (electric aircraft, Santa Cruz), or any one of dozens of ag-tech startups in Salinas and Davis — start at $120k+ out of college. Many of them got hooked on coding in a workshop like this one.
This is the part where everything you did today pays off.
An almond orchard in Gustine is laid out in rows. Trees in a row, spaced about 22 feet apart. Rows spaced about 22 feet apart. To check the health of every tree, an ag drone flies back and forth in a snake pattern over the orchard — fly down a row, turn, fly down the next row, turn, fly down the next. It's called a boustrophedon scan — Greek for "as the ox plows."
You're going to fly one.
Before you open DroneBlocks, sketch the path on your Pilot's Log. The drone starts at the bottom of Row 1. It needs to:
- Fly the length of Row 1
- Turn left, scoot over to Row 2
- Fly the length of Row 2 (now going the other direction)
- Turn right, scoot over to Row 3
- Fly the length of Row 3
- Land
Measure (in steps, then convert to cm — 1 big step ≈ 50 cm) and write the distances on your log.
Translate your sketch into DroneBlocks. Use the same blocks you used for the square — take off, fly forward, yaw left/right, land. You'll need:
- 3 long forward flights (the rows)
- 2 short forward flights (the row-to-row scoots)
- 4 turns (alternating directions)
Then walk it. Out loud. Step by step. If the walked path doesn't cover all 3 rows, fix the code.
One pair at a time in the flight zone. Pre-flight check. Facilitator thumbs-up. Run.
Scoring (out of 5):
- 1 point — drone took off and ran the program
- 1 point — drone flew over Row 1 in its full length
- 1 point — drone flew over Row 2
- 1 point — drone flew over Row 3
- 1 point — clean landing, no crash
The boustrophedon scan you just flew is the same flight pattern precision agriculture specialists fly every day at orchards from here to Bakersfield. The pattern feeds into multispectral analysis software that detects stressed trees from canopy color before a human can see the difference. UC Merced runs ag drone research — there are agronomists, software engineers, and field technicians on staff doing exactly this work. Two-year ag-tech certificates at Merced College, Modesto Junior College, and West Hills College get you in the door at companies like Aerobotics, PrecisionHawk, and Skycatch.
Five hours ago, none of you had flown a drone. Now all of you have — and most of you have written code that flew one autonomously over a simulated almond orchard. That's a real skill jump.
Before you leave, share one word that describes today. Just one.
On your 📋 Pilot's Log, finish these three:
- What part of today surprised you most?
- If you could fly any drone mission in the world tomorrow, what would it be?
- One thing you can do now that you couldn't this morning:
Great Day 1. You flew, you crashed, you coded, you debugged, and your drone surveyed an orchard. That's more than most adults can say. See you next week for Physics & Engineering Challenges.
