Grand Forks is one of those places where a podcast about drones makes complete sense, right, because with the University of North Dakota's John D. Odegaard School of Aerospace Sciences in town and Grand Sky, the business park built for unmanned aircraft, sitting next to Grand Forks Air Force Base, you end up with a lot of people whose whole working life revolves around flight, and most of them have something to explain that the rest of the world has not caught up with yet.
The shows that come out of a place like that tend to share one quirk, they mix two very different kinds of material, a conversation in a room about airspace, careers, hardware or the rules, and then hours of footage from the air that the host is proud of and wants people to see, and in my experience the whole edit lives or dies on how well those two things get stitched together, which is really what this post is about.
Who in Grand Forks is actually making drone and aviation podcasts?
Mostly three groups, the unmanned aircraft companies explaining what they build, the operators who fly for a living, and the students and instructors around the aerospace school who talk about training and the path into the industry.
Each of them wants something slightly different from an episode. A company working out of a park like Grand Sky usually treats the show as a long, patient sales conversation, where the listeners are program managers, procurement people and other operators, so the episode has to be accurate, calm and look like the company takes itself seriously, which is close to what I wrote in the piece on podcast editing for B2B brands, where the person listening is a buyer and not a fan. An operator's show is more personal, stories from jobs, what went sideways on a survey flight, opinions on gear, and those episodes carry a lot of the host's own footage. The student and instructor shows lean towards explanation, lots of acronyms, and quite often a guest who has never sat in front of a microphone before.
What I notice across all three, right, is that the host knows the subject far better than any editor ever will, so the editor's job is never to have opinions about airspace, it is to make sure the explanation lands for somebody hearing it for the first time.
Do I need an editor based in Grand Forks to cut a drone show?
You do not, because podcast editing happens on files rather than in a room, and a remote team can cut your episode just as well as somebody down the street, as long as the upload is simple and the handoff is predictable.
The hub post on whether an editor has to be close by argues this at length, and what it boils down to is that being local only matters when you need someone physically running cameras on the day. If you record in your office, a hangar or a classroom and the cameras are already there, the editing can sit anywhere in the world. We are in Dubai, we have no office or staff anywhere in North Dakota, and we work with shows in a lot of cities through a shared folder and a clear routine, which is laid out on the remote podcast editing page.
There is one honest exception. If you want somebody to come out, light the room, rig three cameras and run the recording itself, a local production crew is the better hire for that part, and you can still send the files to an editor afterwards, wherever that editor happens to be.
How do flight footage and B-roll fit into a talking episode?
Flight footage belongs in the moments where the conversation describes something the viewer would grasp faster by seeing it, and it should leave the screen as soon as the talk moves on, because footage playing for its own sake pulls attention away from the person explaining.
This is where drone shows are different from almost every other niche we edit. Plenty of hosts we work with have nothing to cut away to except stock clips, whereas a drone operator turns up with whole memory cards of their own aerial work, and with that much material sitting in the folder every shot starts begging for screen time. The catch here is that a gorgeous orbit around a cell tower is only useful in the minute where the guest is walking through how an inspection flight gets planned, and if it shows up anywhere else it turns into wallpaper. So on these episodes we keep a running list of what the guest is describing and match footage to that, and when nothing in the folder matches we stay on the faces, because a person explaining clearly holds attention better than random sky ever will. I go through the general thinking on the podcast B-roll editing page, and there is a related piece on cutaways that earn their place in an episode.
A very practical point, right, is labelling. If you send us flight clips, put them in their own folder and name each one by what it shows, tower inspection, crop survey, night flight and so on, because then the editor finds the right shot in seconds instead of scrubbing through a card full of untitled files.
Flight footage should answer a question the guest just raised, otherwise it is only sky.
Who checks that a regulation explainer gets the rules right?
You do, and the edit is built to make that check easy, because an editor's job is to cut what was said cleanly, never to rewrite or reinterpret a rule on a topic where one wrong detail could mislead someone about what they are allowed to fly.
Regulation episodes are probably the most useful thing a drone show can publish, since people are genuinely confused about what is and is not permitted, and they are also the episodes where a careless cut does the most damage. Say a guest explains that something is allowed and then, after a long pause, adds the condition where it is not, and an edit trims the pause along with the second half, the meaning flips completely. So on these episodes we are stricter than usual about never cutting inside a qualification, we flag any spot where a condition sounds clipped, and the first cut is the moment for you or whoever handles compliance at your company to listen purely for accuracy. The episode is general information for your audience, and that review on your side is what keeps it trustworthy.
On-screen text helps a lot too, right, especially with the acronyms. When a guest names a specific rule or a term, a short lower third with it spelled out stops viewers from mishearing, and captions do the same job for anyone watching with the sound off. The W3C guidance on captions is a sensible reference if you want to see what good captioning looks like.
How does the handoff work between Grand Forks and Dubai?
Grand Forks keeps Central Time, which puts Dubai a full 10 hours ahead through the winter and 9 hours ahead once the clocks spring forward in March, so a recording you upload at 7 pm reaches us at 5 am Dubai time in winter and 4 am in summer, before our day has even started.
In practice that means your recording day ends and ours begins on the same files, and you are asleep for most of the work. You record, you drop the camera files and the separate audio into the shared folder, and the first cut is ready for you inside two days. You sit down with it whenever your flying schedule allows, list your changes in a single batch, and the corrected episode tends to be ready the following business day. If you want to see what time it is on our side before you upload, the Dubai world clock is the quickest check.
Drone episodes sometimes arrive with a huge amount of footage or a lot of on-screen graphics, and when one needs an extra day because of that we tell you at the start of the job, rather than letting a deadline slide quietly.
What do drone and unmanned aircraft shows usually pay for editing?
For the company and operator shows I described, our Studio tier is where I would point you, 299 dollars per episode as long as it runs an hour or less, because it handles two to four cameras, delivers in 4K and includes custom graphics, and flight footage really really deserves the 4K.
If your show is one camera in a classroom and the episodes are mostly conversation, the Starter plan costs less and does the job well, and the full breakdown by length and by pack is in the pricing section. Everything is priced per episode, there is no retainer holding you in, and you can pause whenever a semester ends or a funding cycle shifts, which matters a lot for student shows and for companies whose marketing budgets move around during the year.
When is a cheaper option the better call?
When the show is a student project with no budget and no deadline, editing it yourself or working with a classmate who wants the practice is honestly the smarter choice, because the point of that show is learning, not polish.
The same goes for a host who records once a quarter and only needs the audio tidied. A single freelancer on an hourly rate can handle that, and paying for a team built around fast weekly turnarounds would be wasted money. Where a team like ours earns its fee is the company or operator who publishes on a schedule, has a lot of footage, cares how the brand looks next to competitors and does not want the whole show to depend on one person staying available, so you can see how it splits, right, it comes down to how often you publish and how much the episode has to carry.
Will the show still look like ours after we switch editors?
It will, provided you send us a few recent episodes first, because we rebuild your existing intro, lower thirds, pacing and colour so the audience never notices the change, and only suggest improvements once we have matched what you already have.
For aviation companies this tends to matter more than people expect, since their brand rules are usually strict and their logos and colours are already all over trade events and spec sheets. The project files stay in your name, so if you ever move the edit elsewhere, another editor can open the project and carry on without rebuilding anything. Thumbnails and episode titles can come from ClickTheory, which sits inside the same company as Pixel Samy Podcast, through its thumbnail design for podcasters, so the packaging and the edit are made by people talking to each other.
What should a Grand Forks host send before the first episode?
Send your recent episodes for style, the raw camera files and clean audio from each recording, your flight footage in its own labelled folder, and a short note listing anything the edit must never cut, such as a safety caveat or a sponsor line.
For instance, if your guest is an instructor from the aerospace school and the episode includes a rule explanation, a one-line note saying the caveat at minute 22 has to stay word for word saves everybody a round of revisions. If you are curious how this setup looks for a completely different kind of trade a few hours east, I wrote about Duluth podcast editing for Great Lakes shipping, which runs on the same remote routine with very different footage, and closer to home there is the post on Fargo podcast editing for B2B software and ag tech shows.
What I would want a drone host in Grand Forks to take away is pretty simple, right, the footage is your advantage, the explanation is your product, and an edit that respects both, with the caveats intact and the sky used on purpose, is what turns a recording about flying into a show people in the industry actually learn from. So yeah. That's my way of saying it.