Requesting an inspection

A request describes an outcome. You are not scheduling an aircraft or filing a flight plan, and you are not asked for either.

What a request contains

The site or asset. A registered site, and within it the specific thing you want looked at: a building, an elevation, a stockpile, a perimeter, a stretch of line.

The mission type. What the flight is for. This determines the capture pattern, the sensor used and the form the result arrives in. See Mission types.

When. Either as soon as conditions allow, or within a window you choose. For anything you need repeatedly, set a schedule instead of placing the same request each time. See Recurring inspections.

Anything specific you are looking for. A defect you suspect, an area of concern, a comparison against a previous mission. This does not change the flight, but it changes what the delivered result draws attention to.

What happens after you submit

The request enters validation. SkyyOS checks availability, operating constraints, weather in the flight window and equipment health. One of three things follows:

• Accepted and flown. The mission proceeds to operation and delivery.
• Held. Conditions are not currently suitable, most often weather. The request stays live and flies when the window opens.
• Not possible. The request falls outside what the site is approved or equipped for. You are told why, and where the boundary is.

A held mission is a normal outcome rather than a failure. Persistent deployment means waiting for a better window costs you a delay, not another mobilisation.

What you are not asked to do

You do not obtain permissions, notify an authority, confirm airspace, or nominate a pilot. Those are held at the site level and are part of what you are buying. See Regulatory and airspace.