Recurring inspections

A single flight tells you what a site looks like. A schedule tells you what is changing. Most Fly customers arrive wanting the first and stay for the second.

Why repetition is the point

A pod does not move. Flown from the same dock on the same route with the same sensor, two missions separated by a month differ only in the thing you care about: the site itself. That is difficult to achieve when every inspection means a different crew, a different day and a different position in the air.

This is what makes progress monitoring, defect tracking and change reporting work as products rather than as a folder of unrelated photographs.

Setting a schedule

A recurring inspection is a mission type, a site, a route and a cadence. Once set, each occurrence enters validation on its own, so a poor weather window delays that occurrence rather than breaking the series.

Cadence is yours to choose. Daily perimeter sweeps and weekly progress surveys are the two most common shapes.

When an occurrence cannot fly

Occurrences that fail validation are held and flown when conditions allow, or skipped if the window closes. The series continues either way, and the mission record shows which occurrences flew and which did not, so a gap in the sequence is always explained rather than silently absent.

Changing a series

Changing the route or the mission type starts a new basis for comparison. Earlier missions remain in the record and remain viewable, but they are no longer directly comparable to what follows. Where continuity matters, run the new series alongside the existing one rather than editing it.