Start with a specific mission
“Infrastructure inspection” is a category, not a complete requirement. Describe the asset, the useful output, the working distance, access constraints, expected operating conditions, and how the result will be reviewed. Ask the team to distinguish necessary capabilities from features that would be convenient.
For example, an inspection team may need images that let a reviewer identify a defined defect from a safe position. That is a more useful acceptance question than asking which aircraft has the longest advertised flight time. Confirm that the proposed camera, lens, stabilization, workflow, and training support the actual inspection.
Resolve the operating path early
FAA guidance describes different operating paths for public agencies, including Part 107 and qualifying public aircraft operations. The appropriate path depends on the operation; buying an aircraft does not provide flight authorization. The agency’s flight-program lead should review the current FAA requirements, pilot qualifications, airspace, and any needed authorizations before deployment. [1]
For commercial buyers, use the FAA’s getting-started guidance to identify the applicable requirements. Avoid treating a supplier’s product description or a general training course as evidence that a particular mission is authorized. [2]
Request a complete equipment and support package
Ask the quote to identify the aircraft, payload, controller, software, storage, communications, batteries, charging equipment, transport cases, spares, and subscriptions. Have the supplier label included and optional items clearly. Confirm the conditions behind endurance and range figures rather than planning from headline specifications.
- Who provides repairs and what happens while an aircraft is unavailable?
- Which batteries, chargers, and accessories are compatible with the proposed configuration?
- What training is included, for how many people, and what does completion establish?
- Can the team export usable data without an unexpected additional subscription?
- What site or device access is needed during setup and support?
Check sourcing and data requirements against the exact configuration
Give the supplier the actual agency, contract, grant, or internal sourcing requirements. Request documentation for the proposed model, components, software, and services. Do not substitute a general “compliant” label for the review of a specific requirement.
Decide who may view, export, and retain mission data. Identify cloud accounts, external processing, remote support, and offline requirements. Include the person responsible for security and records decisions in the review before the system enters service.
Agree on acceptance before ordering
Write a short test plan with the flight-program lead and supplier. Include a representative mission, the required output, the people who will assess it, and the conditions under which the test will run. Record what would require a configuration change or a decision to stop.
For a regional deployment, gather the PA, NY, NJ, or DE operating sites and their access requirements. Chris can coordinate product and integration questions through Superior Access Solutions; the customer remains responsible for its operating authority and policies.
Sources & further reading
- [1] FAA — Public Safety and starting a drone program
- [2] FAA — Getting Started with Unmanned Aircraft Systems
Published by Chris Wright Enterprises, LLC. Chris is Director of Sales at Superior Access Solutions, which provides the technology products and services discussed on this site. See the partner disclosure. Confirm current requirements with the responsible agency, provider, or adviser before acting.
Discuss your project
Chris can help turn these questions into a scoped conversation.