Dayton is one of those places where the history is not in a book somewhere, right, it is down the street, because the Wright brothers ran their bicycle shop here, the Dayton Aviation Heritage National Historical Park still preserves the sites connected to them, and out at Wright-Patterson Air Force Base you have the National Museum of the United States Air Force, which is the largest military aviation museum in the world. So when someone in Dayton starts a podcast about flight, they are usually not a casual fan, they are a historian, a retired engineer, a museum volunteer, a defense contractor or someone who spent a career around the base, and they care a great deal about getting the details right. Pixel Samy Podcast is how I put my Dubai editors to work on shows like these, podcast video editing where a human editor, never a program, decides each cut after hearing the whole interview, and a typical aviation history episode of 60 minutes with archival images on screen sits on our Studio plan at 299 dollars.
What makes these shows different from a general interview podcast is not the cameras or the microphones, it is the weight of the material, the photos, the scanned documents, the old film, the model designations and the dates, and the fact that the audience includes people who will notice if a single one is wrong.
Who is making aviation and aerospace podcasts in Dayton?
The aviation and aerospace podcasts that come out of Dayton are mostly made by people with a working connection to flight, so aviation historians and museum educators, aerospace and propulsion engineers, retired service members and the wider defense community around Wright-Patterson, and their shows tend to mix oral history interviews, technical explanation and archival material rather than chat and opinion.
That is one group, the historians, and they usually come with a deep archive and a strong view about how a story should be told. Secondly, the engineers, who want to explain how a thing actually worked, the airflow, the materials, the testing, and who get frustrated when a show smooths that into a slogan. And then there is the community around the base, people who served, people who worked alongside them, families, and that last group overlaps a lot with veterans shows, which have their own needs that I cover in editing veterans and military life podcasts.
The common thread, right, is that these hosts are rarely trying to go viral. They want a record, a well made episode that a museum visitor or a young engineer can find in five years and trust.
Why does an aviation history podcast need a more careful edit than a talk show?
An aviation history podcast needs a more careful edit than a talk show because every cut can change a fact, so removing a pause might join two dates that belonged to different aircraft, and a tidy lower third with the wrong designation or rank can sit on screen in front of an audience of people who flew, built or restored that exact machine.
I'm pretty sure most general editors do not think about this, and they do not have to, because on a business show a slightly wrong caption is embarrassing and nothing more. On a history show it undoes the reason the episode exists. So when our editors work on a Dayton aviation episode they treat names, aircraft types, units, places and years as things to be checked against what the host actually said, not against what the editor assumes.
On a history show, the edit is part of the record, so we cut it as if someone will cite it.
The other thing is pacing, and it matters more than people expect. An older guest telling a story about a test flight in the 1960s will pause, go back, correct themselves and then land a detail that nobody else alive remembers, and an editor who is trained to cut every hesitation will cut the correction along with the stumble. Our editors leave a correction in when it changes the fact, and take out the false start when it only changes the rhythm, and that judgment is exactly why we do not let software decide where the cuts go. There is more on why history storytelling needs this kind of patience in what a history podcast needs from its editor.
How do you handle archival photos, film and documents in a podcast edit?
Archival photos, film and documents go into a podcast edit as cutaways placed exactly where the guest refers to them, labelled with whatever caption, date and credit the host supplies, kept at their real proportions instead of stretched to fill the frame, and only used when the host has permission, because an archive image with a wrong label is worse than no image at all.
The way we like to receive archival material is simple, right, a folder of images or clips, each file named so we can tell what it is, and a short note or spreadsheet with the caption and credit for each one. If you send us fifty photos of different aircraft with names like scan 004, we can still place them, but we will be guessing which hangar is which, and guessing is exactly what a history show cannot afford.
Permission matters too. Material held by a museum, a library or an archive often comes with terms about how it can be used and credited, and we follow whatever usage note you give us, but we cannot clear rights on your behalf. For the general craft of putting cutaways into a conversation without distracting from it, how we use B-roll and cutaways in podcast episodes goes further.
What should a defense or base-connected guest know before their episode is edited?
A defense or base-connected guest should know that our editors work only with what the host sends, that we are not a security review step, and that anything not already cleared for public release should be left out of the recording or removed by the guest's own review process before the files ever reach Dubai, because editing cannot make sensitive material appropriate to publish.
This is a simple rule, right, but it is the one I am most firm about. If a guest is current or former military, a contractor or a civilian employee at the base, their employer or public affairs office may have its own process for interviews, and that process belongs to them, not to us. What we can do is make the review easy, so we deliver a first cut they can watch with time codes, and if a section needs to come out after their review, it comes out, and we confirm it is gone from the episode, the clips and the audio master.
Is it a problem that the editor is in Dubai and the show is in Dayton?
It is not a problem for a Dayton show to be edited in Dubai, because editing happens on uploaded files rather than in a shared room, and the only things that truly need a person in Dayton are the recording itself and any filming at a museum, a hangar or a heritage site, which you or a local camera operator handle before the files come to us.
Plenty of hosts assume, right, that a history show should be edited by someone who knows the city, and I understand the instinct, but the knowledge that matters sits with you and your guests, and what you need from an editor is care, consistency and turnaround. If you are weighing that question more broadly, I have written about whether a nearby editor actually matters, and the same answer holds here. One thing that does help is if you tell us which Dayton names and places come up often, so our editors can spell them right in lower thirds and captions from the first episode.
How the handoff between Dayton and Dubai actually runs
Picture a Dayton host who stops recording at 9 pm in January and uploads straight away, the files reach us at 6 am Dubai time, since we sit nine hours ahead of Eastern Time through the US winter, and in July, with daylight saving shrinking the gap to eight hours, that same upload lands at 5 am. In practical terms, right, your evening becomes our morning and the work is moving while you sleep.
The first cut is ready within 48 hours of the upload. When an episode carries dozens of placed photographs and scanned pages, or the oral history simply runs long, give it one more day, and we will mention that the moment we open the folder. You send a single round of notes, we turn those around the following day, and you get exports for YouTube and Spotify plus the audio master for your podcast host. If you want every stage of that relay spelled out, read our remote editing workflow for hosts in any time zone.
Chapters are something I push on every aviation interview we put on YouTube, since a researcher hunting for the four minutes about one airframe should not have to scrub through an hour of oral history, and a list of timestamps pasted into the description is all YouTube needs to split a long video into chapters. Captions help too, especially for older viewers and anyone watching in a museum lobby with the sound off, and the W3C guidance on captions is worth a read if accessibility matters to your audience. Our editors check names against your list rather than trusting automatic transcripts, which is a habit I explain in why I do not trust AI transcription on its own.
What should a Dayton aviation show expect to pay per episode?
A Dayton aviation or aerospace show with archival images, lower thirds and two or more cameras should expect 299 dollars per 60 minute episode on the Studio plan, or 255 dollars per episode when you book a 4-episode pack, and a simpler single camera interview without custom graphics fits the Starter plan at 199 dollars, all in US dollars and fixed per episode.
Most of the history hosts I talk to record in seasons, so the 4-episode pack is often the natural fit, a run of four interviews recorded over a few weeks and edited to the same standard. If your guest stories run long, a 90 minute Studio episode is 390 dollars, and there is no retainer, so you can stop between seasons without paying for months you did not use. Show notes and chapters are 35 dollars an episode if you want us to write them, and the rest of the menu is in what each plan costs by episode length.
So tell me, honestly, how many interviews are sitting on a hard drive right now that you recorded with somebody who will not be around to record again? That question is usually what gets a history show finished.
Where we are not the right team for a Dayton show
There are Dayton shows we are not built for, and it is better to know that early. If your project is a full documentary with narration recorded separately, original score, reconstructed sound effects of engines and aircraft and a script that is rewritten during the edit, then you need a documentary producer or a sound designer, not a podcast editing team. If your organisation requires every editor to work inside its own secure systems, then an in-house editor is the only real option.
And if your show is really about the Cincinnati consumer world down the road rather than aviation, the needs change completely, which is why editing branded shows for Cincinnati marketers is a different conversation, with brand books instead of archive boxes.
Keeping the record straight
The reason I like working with Dayton hosts is that they take the material seriously, the bicycle shop, the test pilots, the engineers who did their best work without anyone filming it, and the job of Pixel Samy Podcast on a show like that is not to make it flashy, it is to make it clear, accurate and easy to watch, so that the person who finds your episode years from now gets the story the way your guest actually told it. Send us one recording and your caption list, and let the first cut show you how carefully it can be handled. So yeah. That's my way of saying it.