METHOD / PROTOTYPE TO PILOT
From Prototype to Controlled Pilot Build
The transition is not a larger version of prototype work. It is the creation of a production basis that lets another qualified person build, inspect, test, and release the same intended aircraft.
Bring the part, volume, material or process, and deadline. The build desk screens the route before anyone commits capacity or lead time.
PILOT-BUILD ANSWER
What changes after the prototype flies?
The product definition becomes a controlled baseline, sourcing decisions become approved inputs, build knowledge becomes documented work, and test becomes an acceptance decision supported by records.
FOUR GATES
The pilot-build method
- 01
Establish the current baseline
Name the controlling CAD, drawings, BOM, software or firmware, physical reference, and known changes. Conflicts are recorded instead of resolved informally at the bench.
Decision: what product is actually being planned? - 02
Expose production risk
Review component availability, alternates, tolerances, assembly access, tooling, workmanship, inspection, test, packaging, and retained records.
Decision: which gaps must close before commitment? - 03
Plan the controlled lot
Assign owners, sequence the work, define inputs and checks, identify hold points, and establish deviation and acceptance authority.
Decision: what releases the build to begin? - 04
Capture and release learning
Record actual material, work, defects, rework, deviations, test, and approved changes. Update the package before treating the next lot as repeat work.
Decision: what evidence supports another lot?
CONTROL TABLE
Prototype artifact vs pilot-build control
| Area | Prototype condition | Pilot-build control |
|---|---|---|
| Product definition | Latest files understood by the core team | Identified controlling configuration and change authority |
| Material | Parts that made the prototype work | Approved sources, alternates, ownership, and incoming basis |
| Assembly | Engineer judgment and hands-on adjustment | Sequence, instructions, tooling, workmanship, and hold points |
| Test | Demonstrated function or flight | Requirement-linked method, record, disposition, and acceptance |
| Learning | Informal fixes | Deviation, root issue, owner, approval, and package update |
Do not freeze uncertainty into the lot.
If the package is still moving, make the change path explicit. The purpose of the gate is not to pretend engineering is finished. It is to prevent unowned changes from becoming uncontrolled variants.