FAQ / PROTOTYPE TO PILOT
Questions Before a Drone Pilot Build
These answers explain the decision logic behind prototype-to-pilot planning. Product, source, schedule, price, facility, and program commitments still require a specific review.
Bring the part, volume, material or process, and deadline. The build desk screens the route before anyone commits capacity or lead time.
Do I need a finished design before starting?
You need a flight-tested aircraft and enough definition to evaluate manufacturing risk. The design does not have to be frozen, but the current baseline, known changes, intended use, and next production milestone must be identifiable. If the architecture is still changing fundamentally, the first output should close engineering gaps rather than promise a build.
Can a working aircraft be the manufacturing reference?
It can communicate design intent, assembly relationships, and expected behavior. It does not replace controlled CAD, drawings, a BOM, software or firmware identification, inspection criteria, and acceptance requirements. The review should identify which missing definitions must be created.
What production volume belongs in a pilot-build discussion?
The relevant signal is repeat-production intent rather than a universal quantity threshold. Fit depends on aircraft complexity, package maturity, material availability, test burden, timing, and forecast confidence. A specific quantity commitment follows a program review.
Can a useful estimate be built from CAD and a BOM?
Those inputs matter, but a useful scope also needs revision state, approved material assumptions, assembly and tooling requirements, inspection, test, records, packaging, responsibility boundaries, and the intended lot profile.
What does DFM mean for a drone aircraft?
Design for manufacturing evaluates whether the aircraft can be sourced, assembled, inspected, tested, serviced, and repeated without losing design intent. The review may examine tolerance interactions, connector access, fastening, wire routing, bonding, tooling, calibration, software loading, test coverage, rework, and component availability as applicable.
Can incumbent sources remain involved?
They can remain in the proposed plan when the scoped review supports that choice. Source status, lead time, alternates, incoming evidence, ownership, and change authority still need to be explicit. A new source or substitute should never be implied without the required approval.
Who owns design and production data?
Ownership, permitted use, confidentiality, access, and derivative production records must be defined in the governing agreements. The initial RFQ email is not the place to transfer proprietary files.
How should changes be handled during the first lot?
Name the approval authority, affected configuration, effectivity, document updates, and treatment of material and work already in process before the change is executed. A useful bench fix should not become an uncontrolled product variant.
What testing is needed before release?
Testing should derive from product requirements and the intended acceptance decision. It may include incoming checks, in-process verification, functional tests, calibration, software or firmware confirmation, ground testing, flight acceptance, and retained records as applicable to the aircraft.
Can a build be transferred from another manufacturer?
A transfer review should identify the controlling package, open deviations, sources, inventory, tooling, work in process, quality history, acceptance evidence, and knowledge that remains with the incumbent. The scope depends on what can be obtained and verified.
Can I send technical files in the first email?
No. Send only high-level, non-sensitive context. Do not include CUI, classified, export-controlled, NDA-protected, proprietary design files, credentials, or other sensitive information in the initial RFQ email. An approved exchange path comes first.