Short answer
Aerospace structural assembly data would pair video of drilling, fastening and sealing on large structures with the records that document each operation. It can support step understanding, sequencing and outcome labeling. It cannot train a robot's hand control, and export-control and customer restrictions may limit what a manufacturer can license. Treat every restriction as a diligence question.
The buyer's problem
Aerospace assembly is attractive to robotics teams for obvious reasons: large structures, repetitive hole patterns, high value per part and a workforce doing physically awkward work. It can also be a difficult domain to buy from. The work is typically done on controlled hardware, to tight tolerances, under documentation practices that record who did what, and often on programs whose designs belong to a customer or are subject to export rules.
A buyer therefore needs to separate three questions. What is the task, physically? What data could represent it? And what is a manufacturer actually in a position to license? This page addresses the first two and frames the third as diligence. It makes no statement about what any regulation requires.
Task anatomy: drilling, fastening and sealing
Structural assembly on a fuselage, wing or sub-assembly commonly involves a repeated cycle:
- Position and clamp: locating panels, stringers or frames against tooling and holding them with temporary fasteners.
- Drill: producing holes at specified locations and sizes, sometimes with a template or a jig, with chip and burr management afterward.
- Inspect and prepare: checking the hole, deburring and cleaning.
- Apply sealant: coating fasteners or faying surfaces with sealing material; see adhesive dispensing and sealing for the shared dispensing issues.
- Install and torque: inserting fasteners and tightening to a requirement; see screw-driving and torque controller data.
- Record: signing off the operation in the plant's documentation.
Work often takes place in confined or awkward positions, such as inside a wing box or under a floor structure, where a person's posture and reach define the method. Failure modes include a misplaced or oversized hole, a missed fastener, damaged sealant, foreign object left in a cavity and an operation signed off without being done. Which of these a plant treats as critical is for the plant to say.
What changes about the data
Scale and viewpoint. Large structures need many camera positions and moving stands, and the working area inside a structure may admit no camera at all. A wide view of an aircraft section shows sequence and team movement; it does not show what is happening at a fastener.
Tolerance. Precision work is judged against measurements that video does not carry. Ask whether hole diameters, positions and torque values are logged and whether they can be joined to recordings.
Fixtures. Large tooling defines how parts are located, and the tooling is itself often proprietary. See fixturing and part orientation.
Documentation. Aerospace plants tend to generate a lot of text around each operation. Two public sources are relevant to understanding that text, though neither covers production assembly in detail. ASD-STE100 is described as a controlled natural language and international standard for writing technical documentation, with Issue 9 dated January 2025 (ASD-STE100); a plant's work instructions may or may not be written in it, so ask. And 14 CFR Part 43 governs maintenance, preventive maintenance, rebuilding and alteration. Its Section 43.9 covers the content of maintenance records, including a description of the work, the completion date, the name of the person performing it if different, and the approver's signature, certificate number and kind of certificate (FAA / eCFR). That is a maintenance record rule; it is not a production-assembly rule, and nothing here states what a manufacturer must record when building a structure.
What data helps each part
| Need | Data that helps | Typical source |
|---|---|---|
| Sequence and team coordination | Wide, multi-view video with step labels | Existing footage or commissioned recording |
| Fastener-level events | Close, stable views where access allows | Commissioned recording |
| Drilling and torque outcomes | Tool logs and measurement records | Plant records |
| Operation text | Work instructions or job cards, with rights cleared | Plant documentation |
| Outcome | Inspection results tied to operation IDs | Quality records |
| Safe alternatives | Mock-up or training-article demonstrations | Commissioned recording |
A mock-up or training article may be easier to record than flight hardware, with fewer restrictions on design information. Whether a plant has them and what they can show is a question for the supplier.
Illustrative package
# Illustrative only - synthetic values, not an available dataset
package: structural_assembly_training_article_v0
site: site_029 (synthetic)
article: training_panel_assembly # synthetic mock-up, not flight hardware
operations: [clamp, drill, deburr, seal, install_fastener, torque]
streams:
wide_views: [fixed_A, fixed_B], 1080p, 30 fps
close_view: tripod or tool-mounted where access allows
tool_logs: drill and torque tool exports, own clock
labels:
step_segments: start/end per operation, operation_id from work card
outcome: accept | rework, per hole or fastener
events: sealant_gap, burr_left, fastener_missed
records_linked: operation sign-off ids (pseudonymous)
metadata: tooling_id tool_T9, operator_id operator_E02 (pseudonymous)
excluded: robot actions, joint states, contact forces, controlled technical data
rights: stated by supplier after review of customer and export restrictions
Limits: what this data cannot support
Footage, work cards and sign-off records describe what people did and when. They contain no robot joint states, commanded motions or contact forces, and a humanoid or other robot needs robot or teleoperation data, or handheld-device capture in its own action space, to learn control. Recognition and pose labels do not substitute. Large aerospace structures add reach, payload and access demands that human demonstrations alone cannot translate. See the human-to-humanoid embodiment gap.
Further limits:
- Access. The hardest-to-reach positions are the least recordable.
- Low volume. Many programs build relatively few units, so repetitions per configuration are limited.
- Documentation is not performance. A signed record shows an operation was recorded as done, not how it was done.
- Aged designs. Program-specific coverage may not carry over to a new structure.
Permissions and provenance
Aerospace programs often involve customer-owned designs and may involve technical data subject to export controls. Whether a given drawing, video frame or work card is affected is a legal and contractual question for the manufacturer, and a buyer should expect to ask how it was determined. This is not legal advice. Redaction or removing identifiers does not settle permissions, and blurring a part number does not change the status of the design visible around it. Operators and inspectors are identifiable by face, badge and signature. See manufacturing data confidentiality and machine safety constraints for recording.
Questions to ask suppliers
- Which operations and structures are covered, and are any recordings of training articles or mock-ups?
- Who has reviewed the material for customer ownership and export-control status, and what did they decide?
- Can measurements (hole size, position, torque) be joined to recordings by operation ID?
- Are work instructions available, and in what writing standard?
- How were people recorded, and what did operators and inspectors agree to?
- Are mistakes, rework and nonconformance dispositions in scope?
- What camera access exists inside structures, and what viewpoints are impossible?
- Which records contain signatures or certificate numbers that must be removed or handled separately?
Discuss your requirements
If large-structure assembly is on your roadmap, describe the operations, restrictions you can accept and permitted uses to SourceX. SourceX reviews the requirement and follows up about potential sources among US businesses, checks the data and the supplier's licensing permissions, and coordinates the license and delivery. If no existing asset fits, SourceX can scope a commissioned collection of new recordings. A request does not guarantee a match. See the humanoid training data guide and the manufacturing hub; for written job sheets see standard work and job breakdown sheets.
Describe the workplace demonstration data your robotics project needs
Sources
- ASD-STE100 Simplified Technical English — controlled language for technical documentation, Issue 9.
- 14 CFR Part 43 - Maintenance, Preventive Maintenance, Rebuilding, and Alteration — maintenance record content under Section 43.9; not a production-assembly rule.