Enhance research documentation for UAV frame materials and reliability assessment. Update SKILL.md with new guidelines for internet search depth and multi-perspective analysis. Revise quality checklists to include comprehensive search criteria. Improve source tiering with emphasis on broad and cross-domain searches. Refine solution draft and reasoning chain to focus on reliability comparisons between VTOL and catapult+parachute systems.

This commit is contained in:
Oleksandr Bezdieniezhnykh
2026-03-21 18:40:58 +02:00
parent f70d701979
commit 27febff23c
14 changed files with 2125 additions and 666 deletions
BIN
View File
Binary file not shown.
+129 -26
View File
@@ -26,6 +26,9 @@ Transform vague topics raised by users into high-quality, deliverable research r
- **Prioritize authoritative sources: L1 > L2 > L3 > L4** - **Prioritize authoritative sources: L1 > L2 > L3 > L4**
- **Intermediate results must be saved for traceability and reuse** - **Intermediate results must be saved for traceability and reuse**
- **Ask, don't assume** — when any aspect of the problem, criteria, or restrictions is unclear, STOP and ask the user before proceeding - **Ask, don't assume** — when any aspect of the problem, criteria, or restrictions is unclear, STOP and ask the user before proceeding
- **Internet-first investigation** — do not rely on training data for factual claims; search the web extensively for every sub-question, rephrase queries when results are thin, and keep searching until you have converging evidence from multiple independent sources
- **Multi-perspective analysis** — examine every problem from at least 3 different viewpoints (e.g., end-user, implementer, business decision-maker, contrarian, domain expert, field practitioner); each perspective should generate its own search queries
- **Question multiplication** — for each sub-question, generate multiple reformulated search queries (synonyms, related terms, negations, "what can go wrong" variants, practitioner-focused variants) to maximize coverage and uncover blind spots
## Context Resolution ## Context Resolution
@@ -152,18 +155,20 @@ A focused preliminary research pass **before** the main solution research. The g
- Ambiguous acceptance criteria values → ask - Ambiguous acceptance criteria values → ask
- Missing context (no `security_approach.md`, no `input_data/`) → ask what they have - Missing context (no `security_approach.md`, no `input_data/`) → ask what they have
- Conflicting restrictions → ask which takes priority - Conflicting restrictions → ask which takes priority
3. Research in internet: 3. Research in internet **extensively** — use multiple search queries per question, rephrase, and search from different angles:
- How realistic are the acceptance criteria for this specific domain? - How realistic are the acceptance criteria for this specific domain? Search for industry benchmarks, standards, and typical values
- How critical is each criterion? - How critical is each criterion? Search for case studies where criteria were relaxed or tightened
- What domain-specific acceptance criteria are we missing? - What domain-specific acceptance criteria are we missing? Search for industry standards, regulatory requirements, and best practices in the specific domain
- Impact of each criterion value on the whole system quality - Impact of each criterion value on the whole system quality — search for research papers and engineering reports
- Cost/budget implications of each criterion - Cost/budget implications of each criterion — search for pricing, total cost of ownership analyses, and comparable project budgets
- Timeline implications — how long would it take to meet each criterion - Timeline implications — search for project timelines, development velocity reports, and comparable implementations
4. Research restrictions: - What do practitioners in this domain consider the most important criteria? Search forums, conference talks, and experience reports
- Are the restrictions realistic? 4. Research restrictions from multiple perspectives:
- Should any be tightened or relaxed? - Are the restrictions realistic? Search for comparable projects that operated under similar constraints
- Are there additional restrictions we should add? - Should any be tightened or relaxed? Search for what constraints similar projects actually ended up with
5. Verify findings with authoritative sources (official docs, papers, benchmarks) - Are there additional restrictions we should add? Search for regulatory, compliance, and safety requirements in this domain
- What restrictions do practitioners wish they had defined earlier? Search for post-mortem reports and lessons learned
5. Verify findings with authoritative sources (official docs, papers, benchmarks) — each key finding must have at least 2 independent sources
**Uses Steps 0-3 of the 8-step engine** (question classification, decomposition, source tiering, fact extraction) scoped to AC and restrictions assessment. **Uses Steps 0-3 of the 8-step engine** (question classification, decomposition, source tiering, fact extraction) scoped to AC and restrictions assessment.
@@ -204,12 +209,14 @@ Full 8-step research methodology. Produces the first solution draft.
**Input**: All files from INPUT_DIR (possibly updated after Phase 1) + Phase 1 artifacts **Input**: All files from INPUT_DIR (possibly updated after Phase 1) + Phase 1 artifacts
**Task** (drives the 8-step engine): **Task** (drives the 8-step engine):
1. Research existing/competitor solutions for similar problems 1. Research existing/competitor solutions for similar problems — search broadly across industries and adjacent domains, not just the obvious competitors
2. Research the problem thoroughly — all possible ways to solve it, split into components 2. Research the problem thoroughly — all possible ways to solve it, split into components; search for how different fields approach analogous problems
3. For each component, research all possible solutions and find the most efficient state-of-the-art approaches 3. For each component, research all possible solutions and find the most efficient state-of-the-art approaches — use multiple query variants and perspectives from Step 1
4. Verify that suggested tools/libraries actually exist and work as described 4. For each promising approach, search for real-world deployment experience: success stories, failure reports, lessons learned, and practitioner opinions
5. Include security considerations in each component analysis 5. Search for contrarian viewpoints — who argues against the common approaches and why? What failure modes exist?
6. Provide rough cost estimates for proposed solutions 6. Verify that suggested tools/libraries actually exist and work as described — check official repos, latest releases, and community health (stars, recent commits, open issues)
7. Include security considerations in each component analysis
8. Provide rough cost estimates for proposed solutions
Be concise in formulating. The fewer words, the better, but do not miss any important details. Be concise in formulating. The fewer words, the better, but do not miss any important details.
@@ -271,11 +278,17 @@ Full 8-step research methodology applied to assessing and improving an existing
**Task** (drives the 8-step engine): **Task** (drives the 8-step engine):
1. Read the existing solution draft thoroughly 1. Read the existing solution draft thoroughly
2. Research in internet — identify all potential weak points and problems 2. Research in internet extensively — for each component/decision in the draft, search for:
3. Identify security weak points and vulnerabilities - Known problems and limitations of the chosen approach
4. Identify performance bottlenecks - What practitioners say about using it in production
5. Address these problems and find ways to solve them - Better alternatives that may have emerged recently
6. Based on findings, form a new solution draft in the same format - Common failure modes and edge cases
- How competitors/similar projects solve the same problem differently
3. Search specifically for contrarian views: "why not [chosen approach]", "[chosen approach] criticism", "[chosen approach] failure"
4. Identify security weak points and vulnerabilities — search for CVEs, security advisories, and known attack vectors for each technology in the draft
5. Identify performance bottlenecks — search for benchmarks, load test results, and scalability reports
6. For each identified weak point, search for multiple solution approaches and compare them
7. Based on findings, form a new solution draft in the same format
**📁 Save action**: Write `OUTPUT_DIR/solution_draft##.md` (incremented) using template: `templates/solution_draft_mode_b.md` **📁 Save action**: Write `OUTPUT_DIR/solution_draft##.md` (incremented) using template: `templates/solution_draft_mode_b.md`
@@ -374,6 +387,35 @@ Key principle: Critical-sensitivity topics (AI/LLMs, blockchain) require sources
- **Sub-question C**: "In what scenarios is X applicable/inapplicable?" (Boundary conditions) - **Sub-question C**: "In what scenarios is X applicable/inapplicable?" (Boundary conditions)
- **Sub-question D**: "What are X's development trends/best practices?" (Extended analysis) - **Sub-question D**: "What are X's development trends/best practices?" (Extended analysis)
#### Perspective Rotation (MANDATORY)
For each research problem, examine it from **at least 3 different perspectives**. Each perspective generates its own sub-questions and search queries.
| Perspective | What it asks | Example queries |
|-------------|-------------|-----------------|
| **End-user / Consumer** | What problems do real users encounter? What do they wish were different? | "X problems", "X frustrations reddit", "X user complaints" |
| **Implementer / Engineer** | What are the technical challenges, gotchas, hidden complexities? | "X implementation challenges", "X pitfalls", "X lessons learned" |
| **Business / Decision-maker** | What are the costs, ROI, strategic implications? | "X total cost of ownership", "X ROI case study", "X vs Y business comparison" |
| **Contrarian / Devil's advocate** | What could go wrong? Why might this fail? What are critics saying? | "X criticism", "why not X", "X failures", "X disadvantages real world" |
| **Domain expert / Academic** | What does peer-reviewed research say? What are theoretical limits? | "X research paper", "X systematic review", "X benchmarks academic" |
| **Practitioner / Field** | What do people who actually use this daily say? What works in practice vs theory? | "X in production", "X experience report", "X after 1 year" |
Select at least 3 perspectives relevant to the problem. Document the chosen perspectives in `00_question_decomposition.md`.
#### Question Explosion (MANDATORY)
For **each sub-question**, generate **at least 3-5 search query variants** before searching. This ensures broad coverage and avoids missing relevant information due to terminology differences.
**Query variant strategies**:
- **Specificity ladder**: broad ("indoor navigation systems") → narrow ("UWB-based indoor drone navigation accuracy")
- **Negation/failure**: "X limitations", "X failure modes", "when X doesn't work"
- **Comparison framing**: "X vs Y for Z", "X alternative for Z", "X or Y which is better for Z"
- **Practitioner voice**: "X in production experience", "X real-world results", "X lessons learned"
- **Temporal**: "X 2025", "X latest developments", "X roadmap"
- **Geographic/domain**: "X in Europe", "X for defense applications", "X in agriculture"
Record all planned queries in `00_question_decomposition.md` alongside each sub-question.
**⚠️ Research Subject Boundary Definition (BLOCKING - must be explicit)**: **⚠️ Research Subject Boundary Definition (BLOCKING - must be explicit)**:
When decomposing questions, you must explicitly define the **boundaries of the research subject**: When decomposing questions, you must explicitly define the **boundaries of the research subject**:
@@ -397,9 +439,11 @@ When decomposing questions, you must explicitly define the **boundaries of the r
- Classified question type and rationale - Classified question type and rationale
- **Research subject boundary definition** (population, geography, timeframe, level) - **Research subject boundary definition** (population, geography, timeframe, level)
- List of decomposed sub-questions - List of decomposed sub-questions
- **Chosen perspectives** (at least 3 from the Perspective Rotation table) with rationale
- **Search query variants** for each sub-question (at least 3-5 per sub-question)
4. Write TodoWrite to track progress 4. Write TodoWrite to track progress
### Step 2: Source Tiering & Authority Anchoring ### Step 2: Source Tiering & Exhaustive Web Investigation
Tier sources by authority, **prioritize primary sources** (L1 > L2 > L3 > L4). Conclusions must be traceable to L1/L2; L3/L4 serve as supplementary and validation. Tier sources by authority, **prioritize primary sources** (L1 > L2 > L3 > L4). Conclusions must be traceable to L1/L2; L3/L4 serve as supplementary and validation.
@@ -411,6 +455,24 @@ Tier sources by authority, **prioritize primary sources** (L1 > L2 > L3 > L4). C
- Always cross-verify training data claims against live sources for facts that may have changed (versions, APIs, deprecations, security advisories) - Always cross-verify training data claims against live sources for facts that may have changed (versions, APIs, deprecations, security advisories)
- When citing web sources, include the URL and date accessed - When citing web sources, include the URL and date accessed
#### Exhaustive Search Requirements (MANDATORY)
Do not stop at the first few results. The goal is to build a comprehensive evidence base.
**Minimum search effort per sub-question**:
- Execute **all** query variants generated in Step 1's Question Explosion (at least 3-5 per sub-question)
- Consult at least **2 different source tiers** per sub-question (e.g., L1 official docs + L4 community discussion)
- If initial searches yield fewer than 3 relevant sources for a sub-question, **broaden the search** with alternative terms, related domains, or analogous problems
**Search broadening strategies** (use when results are thin):
- Try adjacent fields: if researching "drone indoor navigation", also search "robot indoor navigation", "warehouse AGV navigation"
- Try different communities: academic papers, industry whitepapers, military/defense publications, hobbyist forums
- Try different geographies: search in English + search for European/Asian approaches if relevant
- Try historical evolution: "history of X", "evolution of X approaches", "X state of the art 2024 2025"
- Try failure analysis: "X project failure", "X post-mortem", "X recall", "X incident report"
**Search saturation rule**: Continue searching until new queries stop producing substantially new information. If the last 3 searches only repeat previously found facts, the sub-question is saturated.
**📁 Save action**: **📁 Save action**:
For each source consulted, **immediately** append to `01_source_registry.md` using the entry template from `references/source-tiering.md`. For each source consulted, **immediately** append to `01_source_registry.md` using the entry template from `references/source-tiering.md`.
@@ -456,6 +518,40 @@ For each extracted fact, **immediately** append to `02_fact_cards.md`:
- Wrong: "The Ministry of Education banned phones in classrooms" (doesn't specify who) - Wrong: "The Ministry of Education banned phones in classrooms" (doesn't specify who)
- Correct: "The Ministry of Education banned K-12 students from bringing phones into classrooms (does not apply to university students)" - Correct: "The Ministry of Education banned K-12 students from bringing phones into classrooms (does not apply to university students)"
### Step 3.5: Iterative Deepening — Follow-Up Investigation
After initial fact extraction, review what you have found and identify **knowledge gaps and new questions** that emerged from the initial research. This step ensures the research doesn't stop at surface-level findings.
**Process**:
1. **Gap analysis**: Review fact cards and identify:
- Sub-questions with fewer than 3 high-confidence facts → need more searching
- Contradictions between sources → need tie-breaking evidence
- Perspectives (from Step 1) that have no or weak coverage → need targeted search
- Claims that rely only on L3/L4 sources → need L1/L2 verification
2. **Follow-up question generation**: Based on initial findings, generate new questions:
- "Source X claims [fact] — is this consistent with other evidence?"
- "If [approach A] has [limitation], how do practitioners work around it?"
- "What are the second-order effects of [finding]?"
- "Who disagrees with [common finding] and why?"
- "What happened when [solution] was deployed at scale?"
3. **Targeted deep-dive searches**: Execute follow-up searches focusing on:
- Specific claims that need verification
- Alternative viewpoints not yet represented
- Real-world case studies and experience reports
- Failure cases and edge conditions
- Recent developments that may change the picture
4. **Update artifacts**: Append new sources to `01_source_registry.md`, new facts to `02_fact_cards.md`
**Exit criteria**: Proceed to Step 4 when:
- Every sub-question has at least 3 facts with at least one from L1/L2
- At least 3 perspectives from Step 1 have supporting evidence
- No unresolved contradictions remain (or they are explicitly documented as open questions)
- Follow-up searches are no longer producing new substantive information
### Step 4: Build Comparison/Analysis Framework ### Step 4: Build Comparison/Analysis Framework
Based on the question type, select fixed analysis dimensions. **For dimension lists** (General, Concept Comparison, Decision Support): Read `references/comparison-frameworks.md` Based on the question type, select fixed analysis dimensions. **For dimension lists** (General, Concept Comparison, Decision Support): Read `references/comparison-frameworks.md`
@@ -657,9 +753,15 @@ Default intermediate artifacts location: `RESEARCH_DIR/`
│ │ │ │
│ 8-STEP ENGINE: │ │ 8-STEP ENGINE: │
│ 0. Classify question type → Select framework template │ │ 0. Classify question type → Select framework template │
1. Decompose question → mode-specific sub-questions 0.5 Novelty sensitivity → Time windows for sources
2. Tier sources → L1 Official > L2 Blog > L3 Media > L4 1. Decompose question → sub-questions + perspectives + queries
│ → Perspective Rotation (3+ viewpoints, MANDATORY) │
│ → Question Explosion (3-5 query variants per sub-Q) │
│ 2. Exhaustive web search → L1 > L2 > L3 > L4, broad coverage │
│ → Execute ALL query variants, search until saturation │
│ 3. Extract facts → Each with source, confidence level │ │ 3. Extract facts → Each with source, confidence level │
│ 3.5 Iterative deepening → gaps, contradictions, follow-ups │
│ → Keep searching until exit criteria met │
│ 4. Build framework → Fixed dimensions, structured compare │ │ 4. Build framework → Fixed dimensions, structured compare │
│ 5. Align references → Ensure unified definitions │ │ 5. Align references → Ensure unified definitions │
│ 6. Reasoning chain → Fact→Compare→Conclude, explicit │ │ 6. Reasoning chain → Fact→Compare→Conclude, explicit │
@@ -668,6 +770,7 @@ Default intermediate artifacts location: `RESEARCH_DIR/`
├──────────────────────────────────────────────────────────────────┤ ├──────────────────────────────────────────────────────────────────┤
│ Key discipline: Ask don't assume · Facts before reasoning │ │ Key discipline: Ask don't assume · Facts before reasoning │
│ Conclusions from mechanism, not gut feelings │ │ Conclusions from mechanism, not gut feelings │
│ Search broadly, from multiple perspectives, until saturation │
└──────────────────────────────────────────────────────────────────┘ └──────────────────────────────────────────────────────────────────┘
``` ```
@@ -10,6 +10,17 @@
- [ ] Every citation can be directly verified by the user (source verifiability) - [ ] Every citation can be directly verified by the user (source verifiability)
- [ ] Structure hierarchy is clear; executives can quickly locate information - [ ] Structure hierarchy is clear; executives can quickly locate information
## Internet Search Depth
- [ ] Every sub-question was searched with at least 3-5 different query variants
- [ ] At least 3 perspectives from the Perspective Rotation were applied and searched
- [ ] Search saturation reached: last searches stopped producing new substantive information
- [ ] Adjacent fields and analogous problems were searched, not just direct matches
- [ ] Contrarian viewpoints were actively sought ("why not X", "X criticism", "X failure")
- [ ] Practitioner experience was searched (production use, real-world results, lessons learned)
- [ ] Iterative deepening completed: follow-up questions from initial findings were searched
- [ ] No sub-question relies solely on training data without web verification
## Mode A Specific ## Mode A Specific
- [ ] Phase 1 completed: AC assessment was presented to and confirmed by user - [ ] Phase 1 completed: AC assessment was presented to and confirmed by user
@@ -25,6 +25,9 @@
- L3/L4 serve only as supplementary and validation - L3/L4 serve only as supplementary and validation
- L4 community discussions are used to discover "what users truly care about" - L4 community discussions are used to discover "what users truly care about"
- Record all information sources - Record all information sources
- **Search broadly before searching deeply** — cast a wide net with multiple query variants before diving deep into any single source
- **Cross-domain search** — when direct results are sparse, search adjacent fields, analogous problems, and related industries
- **Never rely on a single search** — each sub-question requires multiple searches from different angles (synonyms, negations, practitioner language, academic language)
## Timeliness Filtering Rules (execute based on Step 0.5 sensitivity level) ## Timeliness Filtering Rules (execute based on Step 0.5 sensitivity level)
+83 -29
View File
@@ -2,8 +2,9 @@
## Assessment Findings ## Assessment Findings
| Old Component Solution | Weak Point (functional/security/performance) | New Solution | | Old Component Solution | Weak Point (functional/security/performance) | New Solution |
|------------------------|----------------------------------------------|-------------| | ------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| ESKF described as "16-state vector, ~10MB" with no mathematical specification | **Functional**: No state vector, no process model (F,Q), no measurement models (H for VO, H for satellite), no noise parameters, no scale observability analysis. Impossible to implement or validate accuracy claims. | **Define complete ESKF specification**: 15-state error vector, IMU-driven prediction, dual measurement models (VO relative pose, satellite absolute position), initial Q/R values, scale constraint via altitude + satellite corrections. | | ESKF described as "16-state vector, ~10MB" with no mathematical specification | **Functional**: No state vector, no process model (F,Q), no measurement models (H for VO, H for satellite), no noise parameters, no scale observability analysis. Impossible to implement or validate accuracy claims. | **Define complete ESKF specification**: 15-state error vector, IMU-driven prediction, dual measurement models (VO relative pose, satellite absolute position), initial Q/R values, scale constraint via altitude + satellite corrections. |
| GPS_INPUT at 5-10Hz via pymavlink — no field mapping | **Functional**: GPS_INPUT requires 15+ fields (velocity, accuracy, hdop, fix_type, GPS time). No specification of how ESKF state maps to these fields. ArduPilot requires minimum 5Hz. | **Define GPS_INPUT population spec**: velocity from ESKF, accuracy from covariance, fix_type from confidence tier, GPS time from system clock conversion, synthesized hdop/vdop. | | GPS_INPUT at 5-10Hz via pymavlink — no field mapping | **Functional**: GPS_INPUT requires 15+ fields (velocity, accuracy, hdop, fix_type, GPS time). No specification of how ESKF state maps to these fields. ArduPilot requires minimum 5Hz. | **Define GPS_INPUT population spec**: velocity from ESKF, accuracy from covariance, fix_type from confidence tier, GPS time from system clock conversion, synthesized hdop/vdop. |
| Confidence scoring "unchanged from draft03" — not in draft05 | **Functional**: Draft05 is supposed to be self-contained. Confidence scoring determines GPS_INPUT accuracy fields and fix_type — directly affects how ArduPilot EKF weights the position data. | **Define confidence scoring inline**: 3 tiers (satellite-anchored, VO-tracked, IMU-only) mapping to fix_type + accuracy values. | | Confidence scoring "unchanged from draft03" — not in draft05 | **Functional**: Draft05 is supposed to be self-contained. Confidence scoring determines GPS_INPUT accuracy fields and fix_type — directly affects how ArduPilot EKF weights the position data. | **Define confidence scoring inline**: 3 tiers (satellite-anchored, VO-tracked, IMU-only) mapping to fix_type + accuracy values. |
@@ -14,15 +15,17 @@
| 3-consecutive-failure re-localization request undefined | **Functional**: AC requires ground station re-localization request. No message format, no operator workflow, no system behavior while waiting. | **Define re-localization protocol**: detect 3 failures → send custom MAVLink message with last known position + uncertainty → operator provides approximate coordinates → system uses as ESKF measurement with high covariance. | | 3-consecutive-failure re-localization request undefined | **Functional**: AC requires ground station re-localization request. No message format, no operator workflow, no system behavior while waiting. | **Define re-localization protocol**: detect 3 failures → send custom MAVLink message with last known position + uncertainty → operator provides approximate coordinates → system uses as ESKF measurement with high covariance. |
| Object localization — "trigonometric calculation" with no details | **Functional**: No math, no API, no Viewpro gimbal integration, no accuracy propagation. Other onboard systems cannot use this component as specified. | **Define object localization**: pixel→ray using Viewpro intrinsics + gimbal angles → body frame → NED → ray-ground intersection → WGS84. FastAPI endpoint: POST /objects/locate. Accuracy propagated from UAV position + gimbal uncertainty. | | Object localization — "trigonometric calculation" with no details | **Functional**: No math, no API, no Viewpro gimbal integration, no accuracy propagation. Other onboard systems cannot use this component as specified. | **Define object localization**: pixel→ray using Viewpro intrinsics + gimbal angles → body frame → NED → ray-ground intersection → WGS84. FastAPI endpoint: POST /objects/locate. Accuracy propagated from UAV position + gimbal uncertainty. |
| Satellite matching — GSD normalization and tile selection unspecified | **Functional**: Camera GSD ~15.9 cm/px at 600m vs satellite ~0.3 m/px at zoom 19. The "pre-resize" step is mentioned but not specified. Tile selection radius based on ESKF uncertainty not defined. | **Define GSD handling**: downsample camera frame to match satellite GSD. Define tile selection: ESKF position ± 3σ_horizontal → select tiles covering that area. Assemble tile mosaic for matching. | | Satellite matching — GSD normalization and tile selection unspecified | **Functional**: Camera GSD ~15.9 cm/px at 600m vs satellite ~0.3 m/px at zoom 19. The "pre-resize" step is mentioned but not specified. Tile selection radius based on ESKF uncertainty not defined. | **Define GSD handling**: downsample camera frame to match satellite GSD. Define tile selection: ESKF position ± 3σ_horizontal → select tiles covering that area. Assemble tile mosaic for matching. |
| Satellite tile storage requirements not calculated | **Functional**: "±2km" preload mentioned but no storage estimate. At zoom 19: a 200km path with ±2km buffer requires ~130K tiles (~2.5GB). | **Calculate tile storage**: specify zoom level (18 preferred — 0.6m/px, 4× fewer tiles), estimate storage per mission profile, define maximum mission area by storage limit. | | Satellite tile storage requirements not calculated | **Functional**: "±2km" preload mentioned but no storage estimate. At zoom 19: a 200km path with ±2km buffer requires ~~130K tiles (~~2.5GB). | **Calculate tile storage**: specify zoom level (18 preferred — 0.6m/px, 4× fewer tiles), estimate storage per mission profile, define maximum mission area by storage limit. |
| FastAPI endpoints not in solution draft | **Functional**: Endpoints only in security_analysis.md. No request/response schemas. No SSE event format. No object localization endpoint. | **Consolidate API spec in solution**: define all endpoints, SSE event schema, object localization endpoint. Reference security_analysis.md for auth. | | FastAPI endpoints not in solution draft | **Functional**: Endpoints only in security_analysis.md. No request/response schemas. No SSE event format. No object localization endpoint. | **Consolidate API spec in solution**: define all endpoints, SSE event schema, object localization endpoint. Reference security_analysis.md for auth. |
| cuVSLAM configuration missing (calibration, IMU params, mode) | **Functional**: No camera calibration procedure, no IMU noise parameters, no T_imu_rig extrinsic, no mode selection (Mono vs Inertial). | **Define cuVSLAM configuration**: use Inertial mode, specify required calibration data (camera intrinsics, distortion, IMU noise params from datasheet, T_imu_rig from physical measurement), define calibration procedure. | | cuVSLAM configuration missing (calibration, IMU params, mode) | **Functional**: No camera calibration procedure, no IMU noise parameters, no T_imu_rig extrinsic, no mode selection (Mono vs Inertial). | **Define cuVSLAM configuration**: use Inertial mode, specify required calibration data (camera intrinsics, distortion, IMU noise params from datasheet, T_imu_rig from physical measurement), define calibration procedure. |
| tech_stack.md inconsistent with draft05 | **Functional**: tech_stack.md says 3fps (should be 0.7fps), LiteSAM at 480px (should be 1280px), missing EfficientLoFTR. | **Flag for update**: tech_stack.md must be synchronized with draft05 corrections. Not addressed in this draft — separate task. | | tech_stack.md inconsistent with draft05 | **Functional**: tech_stack.md says 3fps (should be 0.7fps), LiteSAM at 480px (should be 1280px), missing EfficientLoFTR. | **Flag for update**: tech_stack.md must be synchronized with draft05 corrections. Not addressed in this draft — separate task. |
## Overall Maturity Assessment ## Overall Maturity Assessment
| Category | Maturity (1-5) | Assessment | | Category | Maturity (1-5) | Assessment |
|----------|---------------|------------| | ----------------------------- | -------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
| Hardware & Platform Selection | 3.5 | UAV airframe, cameras, Jetson, batteries — well-researched with specs, weight budget, endurance calculations. Ready for procurement. | | Hardware & Platform Selection | 3.5 | UAV airframe, cameras, Jetson, batteries — well-researched with specs, weight budget, endurance calculations. Ready for procurement. |
| Core Algorithm Selection | 3.0 | cuVSLAM, LiteSAM/XFeat, ESKF — components selected with comparison tables, fallback chains, decision trees. Day-one benchmarks defined. | | Core Algorithm Selection | 3.0 | cuVSLAM, LiteSAM/XFeat, ESKF — components selected with comparison tables, fallback chains, decision trees. Day-one benchmarks defined. |
| AI Inference Runtime | 3.5 | TRT Engine migration thoroughly analyzed. Conversion workflows, memory savings, performance estimates. Code wrapper provided. | | AI Inference Runtime | 3.5 | TRT Engine migration thoroughly analyzed. Conversion workflows, memory savings, performance estimates. Code wrapper provided. |
@@ -33,6 +36,7 @@
| Security | 3.0 | Comprehensive threat model, OP-TEE analysis, LUKS, secure boot. Well-researched. | | Security | 3.0 | Comprehensive threat model, OP-TEE analysis, LUKS, secure boot. Well-researched. |
| **Overall TRL** | **~2.5** | **Technology concept formulated + some component validation. Not implementation-ready.** | | **Overall TRL** | **~2.5** | **Technology concept formulated + some component validation. Not implementation-ready.** |
The solution is at approximately **TRL 3** (proof of concept) for hardware/algorithm selection and **TRL 1-2** (basic concept) for system integration, ESKF, and operational procedures. The solution is at approximately **TRL 3** (proof of concept) for hardware/algorithm selection and **TRL 1-2** (basic concept) for system integration, ESKF, and operational procedures.
## Product Solution Description ## Product Solution Description
@@ -42,6 +46,7 @@ A real-time GPS-denied visual navigation system for fixed-wing UAVs, running on
Position is determined by fusing: (1) CUDA-accelerated visual odometry (cuVSLAM in Inertial mode) from ADTI 20L V1 at 0.7 fps sustained, (2) absolute position corrections from satellite image matching (LiteSAM or XFeat — TRT Engine FP16) using keyframes from the same ADTI image stream, and (3) IMU data from the flight controller via ESKF. Viewpro A40 Pro is reserved for AI object detection only. Position is determined by fusing: (1) CUDA-accelerated visual odometry (cuVSLAM in Inertial mode) from ADTI 20L V1 at 0.7 fps sustained, (2) absolute position corrections from satellite image matching (LiteSAM or XFeat — TRT Engine FP16) using keyframes from the same ADTI image stream, and (3) IMU data from the flight controller via ESKF. Viewpro A40 Pro is reserved for AI object detection only.
The ESKF is the central state estimator with 15-state error vector. It fuses: The ESKF is the central state estimator with 15-state error vector. It fuses:
- **IMU prediction** at 5-10Hz (high-frequency pose propagation) - **IMU prediction** at 5-10Hz (high-frequency pose propagation)
- **cuVSLAM VO measurement** at 0.7Hz (relative pose correction) - **cuVSLAM VO measurement** at 0.7Hz (relative pose correction)
- **Satellite matching measurement** at ~0.07-0.14Hz (absolute position correction) - **Satellite matching measurement** at ~0.07-0.14Hz (absolute position correction)
@@ -125,18 +130,21 @@ GPS_INPUT messages carry position, velocity, and accuracy derived from the ESKF
**Nominal state vector** (propagated by IMU): **Nominal state vector** (propagated by IMU):
| State | Symbol | Size | Description | | State | Symbol | Size | Description |
|-------|--------|------|-------------| | ---------- | ------ | ---- | ------------------------------------------------ |
| Position | p | 3 | NED position relative to mission origin (meters) | | Position | p | 3 | NED position relative to mission origin (meters) |
| Velocity | v | 3 | NED velocity (m/s) | | Velocity | v | 3 | NED velocity (m/s) |
| Attitude | q | 4 | Unit quaternion (body-to-NED rotation) | | Attitude | q | 4 | Unit quaternion (body-to-NED rotation) |
| Accel bias | b_a | 3 | Accelerometer bias (m/s²) | | Accel bias | b_a | 3 | Accelerometer bias (m/s²) |
| Gyro bias | b_g | 3 | Gyroscope bias (rad/s) | | Gyro bias | b_g | 3 | Gyroscope bias (rad/s) |
**Error-state vector** (estimated by ESKF): δx = [δp, δv, δθ, δb_a, δb_g]ᵀ ∈ ℝ¹⁵ **Error-state vector** (estimated by ESKF): δx = [δp, δv, δθ, δb_a, δb_g]ᵀ ∈ ℝ¹⁵
where δθ ∈ so(3) is the 3D rotation error. where δθ ∈ so(3) is the 3D rotation error.
**Prediction step** (IMU at 5-10Hz from flight controller): **Prediction step** (IMU at 5-10Hz from flight controller):
- Input: accelerometer a_m, gyroscope ω_m, dt - Input: accelerometer a_m, gyroscope ω_m, dt
- Propagate nominal state: p += v·dt, v += (R(q)·(a_m - b_a) - g)·dt, q ⊗= Exp(ω_m - b_g)·dt - Propagate nominal state: p += v·dt, v += (R(q)·(a_m - b_a) - g)·dt, q ⊗= Exp(ω_m - b_g)·dt
- Propagate error covariance: P = F·P·Fᵀ + Q - Propagate error covariance: P = F·P·Fᵀ + Q
@@ -144,6 +152,7 @@ where δθ ∈ so(3) is the 3D rotation error.
- Q: process noise diagonal, initial values from IMU datasheet noise densities - Q: process noise diagonal, initial values from IMU datasheet noise densities
**VO measurement update** (0.7Hz from cuVSLAM): **VO measurement update** (0.7Hz from cuVSLAM):
- cuVSLAM outputs relative pose: ΔR, Δt (camera frame) - cuVSLAM outputs relative pose: ΔR, Δt (camera frame)
- Transform to NED: Δp_ned = R_body_ned · T_cam_body · Δt - Transform to NED: Δp_ned = R_body_ned · T_cam_body · Δt
- Innovation: z = Δp_ned_measured - Δp_ned_predicted - Innovation: z = Δp_ned_measured - Δp_ned_predicted
@@ -152,6 +161,7 @@ where δθ ∈ so(3) is the 3D rotation error.
- Kalman update: K = P·Hᵀ·(H·P·Hᵀ + R)⁻¹, δx = K·z, P = (I - K·H)·P - Kalman update: K = P·Hᵀ·(H·P·Hᵀ + R)⁻¹, δx = K·z, P = (I - K·H)·P
**Satellite measurement update** (0.07-0.14Hz, async): **Satellite measurement update** (0.07-0.14Hz, async):
- Satellite matching outputs absolute position: lat_sat, lon_sat in WGS84 - Satellite matching outputs absolute position: lat_sat, lon_sat in WGS84
- Convert to NED relative to mission origin - Convert to NED relative to mission origin
- Innovation: z = p_satellite - p_predicted - Innovation: z = p_satellite - p_predicted
@@ -160,20 +170,24 @@ where δθ ∈ so(3) is the 3D rotation error.
- Provides absolute position correction — bounds drift accumulation - Provides absolute position correction — bounds drift accumulation
**Scale observability**: **Scale observability**:
- Monocular cuVSLAM has scale ambiguity during constant-velocity flight - Monocular cuVSLAM has scale ambiguity during constant-velocity flight
- Scale is constrained by: (1) satellite matching absolute positions (primary), (2) known flight altitude from barometer + predefined mission altitude, (3) IMU accelerometer during maneuvers - Scale is constrained by: (1) satellite matching absolute positions (primary), (2) known flight altitude from barometer + predefined mission altitude, (3) IMU accelerometer during maneuvers
- During long straight segments without satellite correction, scale drift is possible. Satellite corrections every ~7-14s re-anchor scale. - During long straight segments without satellite correction, scale drift is possible. Satellite corrections every ~7-14s re-anchor scale.
**Tuning approach**: Start with IMU datasheet noise values for Q. Start with conservative R values (high measurement noise). Tune on flight test data by comparing ESKF output to known GPS ground truth. **Tuning approach**: Start with IMU datasheet noise values for Q. Start with conservative R values (high measurement noise). Tune on flight test data by comparing ESKF output to known GPS ground truth.
| Solution | Tools | Advantages | Limitations | Performance | Fit | | Solution | Tools | Advantages | Limitations | Performance | Fit |
|----------|-------|-----------|-------------|------------|-----| | -------------------------- | --------------- | ------------------------------------------------------------- | -------------------------------------- | ------------- | ----------- |
| Custom ESKF (Python/NumPy) | NumPy, SciPy | Full control, minimal dependencies, well-understood algorithm | Implementation effort, tuning required | <1ms per step | ✅ Selected | | Custom ESKF (Python/NumPy) | NumPy, SciPy | Full control, minimal dependencies, well-understood algorithm | Implementation effort, tuning required | <1ms per step | ✅ Selected |
| FilterPy ESKF | FilterPy v1.4.5 | Reference implementation, less code | Less flexible for multi-rate fusion | <1ms per step | ⚠️ Fallback | | FilterPy ESKF | FilterPy v1.4.5 | Reference implementation, less code | Less flexible for multi-rate fusion | <1ms per step | ⚠️ Fallback |
### Component: Coordinate System & Transformations (NEW — previously undefined) ### Component: Coordinate System & Transformations (NEW — previously undefined)
**Reference frames**: **Reference frames**:
- **Camera frame (C)**: origin at camera optical center, Z forward, X right, Y down (OpenCV convention) - **Camera frame (C)**: origin at camera optical center, Z forward, X right, Y down (OpenCV convention)
- **Body frame (B)**: origin at UAV CG, X forward (nose), Y right (starboard), Z down - **Body frame (B)**: origin at UAV CG, X forward (nose), Y right (starboard), Z down
- **NED frame (N)**: North-East-Down, origin at mission start point - **NED frame (N)**: North-East-Down, origin at mission start point
@@ -187,17 +201,20 @@ where δθ ∈ so(3) is the 3D rotation error.
4. **NED → WGS84**: lat = lat_origin + p_north / R_earth, lon = lon_origin + p_east / (R_earth · cos(lat_origin)) where (lat_origin, lon_origin) is the mission start GPS position 4. **NED → WGS84**: lat = lat_origin + p_north / R_earth, lon = lon_origin + p_east / (R_earth · cos(lat_origin)) where (lat_origin, lon_origin) is the mission start GPS position
**Camera intrinsic matrix K** (ADTI 20L V1 + 16mm lens): **Camera intrinsic matrix K** (ADTI 20L V1 + 16mm lens):
- Sensor: 23.2 × 15.4 mm, Resolution: 5456 × 3632 - Sensor: 23.2 × 15.4 mm, Resolution: 5456 × 3632
- fx = fy = focal_mm × width_px / sensor_width_mm = 16 × 5456 / 23.2 = 3763 pixels - fx = fy = focal_mm × width_px / sensor_width_mm = 16 × 5456 / 23.2 = 3763 pixels
- cx = 2728, cy = 1816 (sensor center) - cx = 2728, cy = 1816 (sensor center)
- Distortion: Brown model (k1, k2, p1, p2 from calibration) - Distortion: Brown model (k1, k2, p1, p2 from calibration)
**T_cam_body** (camera mount): **T_cam_body** (camera mount):
- Navigation camera is fixed, pointing nadir (downward), not autostabilized - Navigation camera is fixed, pointing nadir (downward), not autostabilized
- R_cam_body = R_x(180°) · R_z(0°) (camera Z-axis aligned with body -Z, camera X with body X) - R_cam_body = R_x(180°) · R_z(0°) (camera Z-axis aligned with body -Z, camera X with body X)
- Translation: offset from CG to camera mount (measured during assembly, typically <0.3m) - Translation: offset from CG to camera mount (measured during assembly, typically <0.3m)
**Satellite match → WGS84**: **Satellite match → WGS84**:
- Feature correspondences between camera frame and geo-referenced satellite tile - Feature correspondences between camera frame and geo-referenced satellite tile
- Homography H maps camera pixels to satellite tile pixels - Homography H maps camera pixels to satellite tile pixels
- Satellite tile pixel → WGS84 via tile's known georeference (zoom level + tile x,y → lat,lon) - Satellite tile pixel → WGS84 via tile's known georeference (zoom level + tile x,y → lat,lon)
@@ -206,8 +223,9 @@ where δθ ∈ so(3) is the 3D rotation error.
### Component: GPS_INPUT Message Population (NEW — previously undefined) ### Component: GPS_INPUT Message Population (NEW — previously undefined)
| GPS_INPUT Field | Source | Computation | | GPS_INPUT Field | Source | Computation |
|-----------------|--------|-------------| | ----------------------- | ---------------------------------------------- | ------------------------------------------------------------------------------------------------------- |
| lat, lon | ESKF position (NED) | NED → WGS84 conversion using mission origin | | lat, lon | ESKF position (NED) | NED → WGS84 conversion using mission origin |
| alt | ESKF position (Down) + mission origin altitude | alt = alt_origin - p_down | | alt | ESKF position (Down) + mission origin altitude | alt = alt_origin - p_down |
| vn, ve, vd | ESKF velocity state | Direct from ESKF v[0], v[1], v[2] | | vn, ve, vd | ESKF velocity state | Direct from ESKF v[0], v[1], v[2] |
@@ -222,15 +240,18 @@ where δθ ∈ so(3) is the 3D rotation error.
| gps_id | Constant | 0 | | gps_id | Constant | 0 |
| ignore_flags | Constant | 0 (provide all fields) | | ignore_flags | Constant | 0 (provide all fields) |
**Confidence tiers** mapping to GPS_INPUT: **Confidence tiers** mapping to GPS_INPUT:
| Tier | Condition | fix_type | horiz_accuracy | Rationale | | Tier | Condition | fix_type | horiz_accuracy | Rationale |
|------|-----------|----------|----------------|-----------| | ------ | ------------------------------------------------- | ---------- | ------------------------------- | -------------------------------------- |
| HIGH | Satellite match <30s ago, ESKF covariance < 400m² | 3 (3D fix) | From ESKF P (typically 5-20m) | Absolute position anchor recent | | HIGH | Satellite match <30s ago, ESKF covariance < 400m² | 3 (3D fix) | From ESKF P (typically 5-20m) | Absolute position anchor recent |
| MEDIUM | cuVSLAM tracking OK, no recent satellite match | 3 (3D fix) | From ESKF P (typically 20-50m) | Relative tracking valid, drift growing | | MEDIUM | cuVSLAM tracking OK, no recent satellite match | 3 (3D fix) | From ESKF P (typically 20-50m) | Relative tracking valid, drift growing |
| LOW | cuVSLAM lost, IMU-only | 2 (2D fix) | From ESKF P (50-200m+, growing) | Only IMU dead reckoning, rapid drift | | LOW | cuVSLAM lost, IMU-only | 2 (2D fix) | From ESKF P (50-200m+, growing) | Only IMU dead reckoning, rapid drift |
| FAILED | 3+ consecutive total failures | 0 (no fix) | 999.0 | System cannot determine position | | FAILED | 3+ consecutive total failures | 0 (no fix) | 999.0 | System cannot determine position |
### Component: Disconnected Route Segment Handling (NEW — previously undefined) ### Component: Disconnected Route Segment Handling (NEW — previously undefined)
**Trigger**: cuVSLAM reports tracking_lost OR tracking confidence drops below threshold **Trigger**: cuVSLAM reports tracking_lost OR tracking confidence drops below threshold
@@ -278,6 +299,7 @@ STATE: SEGMENT_DISCONNECT
### Component: Satellite Image Matching Pipeline (UPDATED — added GSD + tile selection details) ### Component: Satellite Image Matching Pipeline (UPDATED — added GSD + tile selection details)
**GSD normalization**: **GSD normalization**:
- Camera GSD at 600m: ~15.9 cm/pixel (ADTI 20L V1 + 16mm) - Camera GSD at 600m: ~15.9 cm/pixel (ADTI 20L V1 + 16mm)
- Satellite tile GSD at zoom 18: ~0.6 m/pixel - Satellite tile GSD at zoom 18: ~0.6 m/pixel
- Scale ratio: ~3.8:1 - Scale ratio: ~3.8:1
@@ -285,6 +307,7 @@ STATE: SEGMENT_DISCONNECT
- This is close to LiteSAM's 1280px input — use 1280px with minor GSD mismatch acceptable for matching - This is close to LiteSAM's 1280px input — use 1280px with minor GSD mismatch acceptable for matching
**Tile selection**: **Tile selection**:
- Input: ESKF position estimate (lat, lon) + horizontal covariance σ_h - Input: ESKF position estimate (lat, lon) + horizontal covariance σ_h
- Search radius: max(3·σ_h, 500m) — at least 500m to handle initial uncertainty - Search radius: max(3·σ_h, 500m) — at least 500m to handle initial uncertainty
- Compute geohash for center position → load tiles covering the search area - Compute geohash for center position → load tiles covering the search area
@@ -292,6 +315,7 @@ STATE: SEGMENT_DISCONNECT
- If ESKF uncertainty > 2km: tile selection unreliable, fall back to wider search or request operator input - If ESKF uncertainty > 2km: tile selection unreliable, fall back to wider search or request operator input
**Tile storage calculation** (zoom 18 — 0.6 m/pixel): **Tile storage calculation** (zoom 18 — 0.6 m/pixel):
- Each 256×256 tile covers ~153m × 153m - Each 256×256 tile covers ~153m × 153m
- Flight path 200km with ±2km buffer: area ≈ 200km × 4km = 800 km² - Flight path 200km with ±2km buffer: area ≈ 200km × 4km = 800 km²
- Tiles needed: 800,000,000 / (153 × 153) ≈ 34,200 tiles - Tiles needed: 800,000,000 / (153 × 153) ≈ 34,200 tiles
@@ -299,17 +323,20 @@ STATE: SEGMENT_DISCONNECT
- With zoom 19 overlap tiles for higher precision: ×4 = ~1.4-2.0 GB - With zoom 19 overlap tiles for higher precision: ×4 = ~1.4-2.0 GB
- Recommended: zoom 18 primary + zoom 19 for ±500m along flight path → ~500-800 MB total - Recommended: zoom 18 primary + zoom 19 for ±500m along flight path → ~500-800 MB total
| Solution | Tools | Advantages | Limitations | Performance (est. Orin Nano Super TRT FP16) | Params | Fit | | Solution | Tools | Advantages | Limitations | Performance (est. Orin Nano Super TRT FP16) | Params | Fit |
|----------|-------|-----------|-------------|----------------------------------------------|--------|-----| | -------------------------------------- | ------------------------- | ------------------------------------------------------------------------ | ------------------------------------------------------ | ------------------------------------------- | ------ | ------------------------------- |
| LiteSAM (opt) TRT Engine FP16 @ 1280px | trtexec + tensorrt Python | Best satellite-aerial accuracy (RMSE@30=17.86m UAV-VisLoc), 6.31M params | MinGRU TRT export needs verification (LOW-MEDIUM risk) | Est. ~165-330ms | 6.31M | ✅ Primary | | LiteSAM (opt) TRT Engine FP16 @ 1280px | trtexec + tensorrt Python | Best satellite-aerial accuracy (RMSE@30=17.86m UAV-VisLoc), 6.31M params | MinGRU TRT export needs verification (LOW-MEDIUM risk) | Est. ~165-330ms | 6.31M | ✅ Primary |
| EfficientLoFTR TRT Engine FP16 | trtexec + tensorrt Python | Proven TRT path (Coarse_LoFTR_TRT). Semi-dense. CVPR 2024. | 2.4x more params than LiteSAM. | Est. ~200-400ms | 15.05M | ✅ Fallback if LiteSAM TRT fails | | EfficientLoFTR TRT Engine FP16 | trtexec + tensorrt Python | Proven TRT path (Coarse_LoFTR_TRT). Semi-dense. CVPR 2024. | 2.4x more params than LiteSAM. | Est. ~200-400ms | 15.05M | ✅ Fallback if LiteSAM TRT fails |
| XFeat TRT Engine FP16 | trtexec + tensorrt Python | Fastest. Proven TRT implementation. | General-purpose, not designed for cross-view gap. | Est. ~50-100ms | <5M | ✅ Speed fallback | | XFeat TRT Engine FP16 | trtexec + tensorrt Python | Fastest. Proven TRT implementation. | General-purpose, not designed for cross-view gap. | Est. ~50-100ms | <5M | ✅ Speed fallback |
### Component: cuVSLAM Configuration (NEW — previously undefined) ### Component: cuVSLAM Configuration (NEW — previously undefined)
**Mode**: Inertial (mono camera + IMU) **Mode**: Inertial (mono camera + IMU)
**Camera configuration** (ADTI 20L V1 + 16mm lens): **Camera configuration** (ADTI 20L V1 + 16mm lens):
- Model: Brown distortion - Model: Brown distortion
- fx = fy = 3763 px (16mm on 23.2mm sensor at 5456px width) - fx = fy = 3763 px (16mm on 23.2mm sensor at 5456px width)
- cx = 2728 px, cy = 1816 px - cx = 2728 px, cy = 1816 px
@@ -317,6 +344,7 @@ STATE: SEGMENT_DISCONNECT
- Border: 50px (ignore lens edge distortion) - Border: 50px (ignore lens edge distortion)
**IMU configuration** (Pixhawk 6x IMU — ICM-42688-P): **IMU configuration** (Pixhawk 6x IMU — ICM-42688-P):
- Gyroscope noise density: 3.0 × 10⁻³ °/s/√Hz - Gyroscope noise density: 3.0 × 10⁻³ °/s/√Hz
- Gyroscope random walk: 5.0 × 10⁻⁵ °/s²/√Hz - Gyroscope random walk: 5.0 × 10⁻⁵ °/s²/√Hz
- Accelerometer noise density: 70 µg/√Hz - Accelerometer noise density: 70 µg/√Hz
@@ -325,17 +353,20 @@ STATE: SEGMENT_DISCONNECT
- T_imu_rig: measured transformation from Pixhawk IMU to camera center (translation + rotation) - T_imu_rig: measured transformation from Pixhawk IMU to camera center (translation + rotation)
**cuVSLAM settings**: **cuVSLAM settings**:
- OdometryMode: INERTIAL - OdometryMode: INERTIAL
- MulticameraMode: PRECISION (favor accuracy over speed — we have 1430ms budget) - MulticameraMode: PRECISION (favor accuracy over speed — we have 1430ms budget)
- Input resolution: downsample to 1280×852 (or 720p) for processing speed - Input resolution: downsample to 1280×852 (or 720p) for processing speed
- async_bundle_adjustment: True - async_bundle_adjustment: True
**Initialization**: **Initialization**:
- cuVSLAM initializes automatically when it receives the first camera frame + IMU data - cuVSLAM initializes automatically when it receives the first camera frame + IMU data
- First few frames used for feature initialization and scale estimation - First few frames used for feature initialization and scale estimation
- First satellite match validates and corrects the initial position - First satellite match validates and corrects the initial position
**Calibration procedure** (one-time per hardware unit): **Calibration procedure** (one-time per hardware unit):
1. Camera intrinsics: checkerboard calibration with OpenCV (or use manufacturer data if available) 1. Camera intrinsics: checkerboard calibration with OpenCV (or use manufacturer data if available)
2. Camera-IMU extrinsic (T_imu_rig): Kalibr tool with checkerboard + IMU data 2. Camera-IMU extrinsic (T_imu_rig): Kalibr tool with checkerboard + IMU data
3. IMU noise parameters: Allan variance analysis or use datasheet values 3. IMU noise parameters: Allan variance analysis or use datasheet values
@@ -354,6 +385,7 @@ cuVSLAM in Inertial mode, fed by ADTI 20L V1 at 0.7 fps sustained. See draft05 f
pymavlink over UART at 5-10Hz. GPS_INPUT field population defined above. pymavlink over UART at 5-10Hz. GPS_INPUT field population defined above.
ArduPilot configuration: ArduPilot configuration:
- GPS1_TYPE = 14 (MAVLink) - GPS1_TYPE = 14 (MAVLink)
- GPS_RATE = 5 (minimum, matching our 5-10Hz output) - GPS_RATE = 5 (minimum, matching our 5-10Hz output)
- EK3_SRC1_POSXY = 1 (GPS), EK3_SRC1_VELXY = 1 (GPS) — EKF uses GPS_INPUT as position/velocity source - EK3_SRC1_POSXY = 1 (GPS), EK3_SRC1_VELXY = 1 (GPS) — EKF uses GPS_INPUT as position/velocity source
@@ -363,6 +395,7 @@ ArduPilot configuration:
**Input**: pixel coordinates (u, v) in Viewpro A40 Pro image, current gimbal angles (pan_deg, tilt_deg), zoom factor, UAV position from GPS-denied system, UAV altitude **Input**: pixel coordinates (u, v) in Viewpro A40 Pro image, current gimbal angles (pan_deg, tilt_deg), zoom factor, UAV position from GPS-denied system, UAV altitude
**Process**: **Process**:
1. Pixel → camera ray: ray_cam = K_viewpro⁻¹(zoom) · [u, v, 1]ᵀ 1. Pixel → camera ray: ray_cam = K_viewpro⁻¹(zoom) · [u, v, 1]ᵀ
2. Camera → gimbal frame: ray_gimbal = R_gimbal(pan, tilt) · ray_cam 2. Camera → gimbal frame: ray_gimbal = R_gimbal(pan, tilt) · ray_cam
3. Gimbal → body: ray_body = T_gimbal_body · ray_gimbal 3. Gimbal → body: ray_body = T_gimbal_body · ray_gimbal
@@ -371,15 +404,18 @@ ArduPilot configuration:
6. NED → WGS84: convert to lat, lon 6. NED → WGS84: convert to lat, lon
**Output**: { lat, lon, accuracy_m, confidence } **Output**: { lat, lon, accuracy_m, confidence }
- accuracy_m propagated from: UAV position accuracy (from ESKF) + gimbal angle uncertainty + altitude uncertainty - accuracy_m propagated from: UAV position accuracy (from ESKF) + gimbal angle uncertainty + altitude uncertainty
**API endpoint**: POST /objects/locate **API endpoint**: POST /objects/locate
- Request: { pixel_x, pixel_y, gimbal_pan_deg, gimbal_tilt_deg, zoom_factor } - Request: { pixel_x, pixel_y, gimbal_pan_deg, gimbal_tilt_deg, zoom_factor }
- Response: { lat, lon, alt, accuracy_m, confidence, uav_position: {lat, lon, alt}, timestamp } - Response: { lat, lon, alt, accuracy_m, confidence, uav_position: {lat, lon, alt}, timestamp }
### Component: Startup, Handoff & Failsafe (UPDATED — added handoff + reboot + re-localization) ### Component: Startup, Handoff & Failsafe (UPDATED — added handoff + reboot + re-localization)
**GPS-denied handoff protocol**: **GPS-denied handoff protocol**:
- GPS-denied system runs continuously from companion computer boot - GPS-denied system runs continuously from companion computer boot
- Reads initial position from FC (GLOBAL_POSITION_INT) — this may be real GPS or last known - Reads initial position from FC (GLOBAL_POSITION_INT) — this may be real GPS or last known
- First satellite match validates the initial position - First satellite match validates the initial position
@@ -387,6 +423,7 @@ ArduPilot configuration:
- No explicit "switch" — the GPS-denied system is a secondary GPS source - No explicit "switch" — the GPS-denied system is a secondary GPS source
**Startup sequence** (expanded from draft05): **Startup sequence** (expanded from draft05):
1. Boot Jetson → start GPS-Denied service (systemd) 1. Boot Jetson → start GPS-Denied service (systemd)
2. Connect to flight controller via pymavlink on UART 2. Connect to flight controller via pymavlink on UART
3. Wait for heartbeat 3. Wait for heartbeat
@@ -403,6 +440,7 @@ ArduPilot configuration:
14. System ready 14. System ready
**Mid-flight reboot recovery**: **Mid-flight reboot recovery**:
1. Jetson boots (~30-60s) 1. Jetson boots (~30-60s)
2. GPS-Denied service starts, connects to FC 2. GPS-Denied service starts, connects to FC
3. Read GLOBAL_POSITION_INT (FC's current IMU-extrapolated position) 3. Read GLOBAL_POSITION_INT (FC's current IMU-extrapolated position)
@@ -416,6 +454,7 @@ ArduPilot configuration:
11. **Known limitation**: recovery time is dominated by Jetson boot time 11. **Known limitation**: recovery time is dominated by Jetson boot time
**3-consecutive-failure re-localization**: **3-consecutive-failure re-localization**:
- Trigger: VO lost + satellite match failed × 3 consecutive camera frames - Trigger: VO lost + satellite match failed × 3 consecutive camera frames
- Action: send re-localization request via MAVLink STATUSTEXT or custom message - Action: send re-localization request via MAVLink STATUSTEXT or custom message
- Message content: "RELOC_REQ: last_lat={lat} last_lon={lon} uncertainty={σ}m" - Message content: "RELOC_REQ: last_lat={lat} last_lon={lon} uncertainty={σ}m"
@@ -428,23 +467,27 @@ ArduPilot configuration:
MAVLink messages to ground station: MAVLink messages to ground station:
| Message | Rate | Content | | Message | Rate | Content |
|---------|------|---------| | ----------------------------- | -------- | --------------------------------------------------- |
| NAMED_VALUE_FLOAT "gps_conf" | 1Hz | Confidence score (0.0-1.0) | | NAMED_VALUE_FLOAT "gps_conf" | 1Hz | Confidence score (0.0-1.0) |
| NAMED_VALUE_FLOAT "gps_drift" | 1Hz | Estimated drift from last satellite anchor (meters) | | NAMED_VALUE_FLOAT "gps_drift" | 1Hz | Estimated drift from last satellite anchor (meters) |
| NAMED_VALUE_FLOAT "gps_hacc" | 1Hz | Horizontal accuracy (meters, from ESKF) | | NAMED_VALUE_FLOAT "gps_hacc" | 1Hz | Horizontal accuracy (meters, from ESKF) |
| STATUSTEXT | On event | "RELOC_REQ: ..." for re-localization request | | STATUSTEXT | On event | "RELOC_REQ: ..." for re-localization request |
| STATUSTEXT | On event | Tracking loss / recovery notifications | | STATUSTEXT | On event | Tracking loss / recovery notifications |
### Component: Thermal Management (UNCHANGED) ### Component: Thermal Management (UNCHANGED)
Same adaptive pipeline from draft05. Active cooling required at 25W. Throttling at 80°C SoC junction. Same adaptive pipeline from draft05. Active cooling required at 25W. Throttling at 80°C SoC junction.
### Component: API & Inter-System Communication (NEW — consolidated) ### Component: API & Inter-System Communication (NEW — consolidated)
FastAPI (Uvicorn) running locally on Jetson for inter-process communication with other onboard systems. FastAPI (Uvicorn) running locally on Jetson for inter-process communication with other onboard systems.
| Endpoint | Method | Purpose | Auth | | Endpoint | Method | Purpose | Auth |
|----------|--------|---------|------| | --------------------- | --------- | -------------------------------------- | ---- |
| /sessions | POST | Start GPS-denied session | JWT | | /sessions | POST | Start GPS-denied session | JWT |
| /sessions/{id}/stream | GET (SSE) | Real-time position + confidence stream | JWT | | /sessions/{id}/stream | GET (SSE) | Real-time position + confidence stream | JWT |
| /sessions/{id}/anchor | POST | Operator re-localization hint | JWT | | /sessions/{id}/anchor | POST | Operator re-localization hint | JWT |
@@ -452,7 +495,9 @@ FastAPI (Uvicorn) running locally on Jetson for inter-process communication with
| /objects/locate | POST | Object GPS from pixel coordinates | JWT | | /objects/locate | POST | Object GPS from pixel coordinates | JWT |
| /health | GET | System health + memory + thermal | None | | /health | GET | System health + memory + thermal | None |
**SSE event schema** (1Hz): **SSE event schema** (1Hz):
```json ```json
{ {
"type": "position", "type": "position",
@@ -483,8 +528,9 @@ Unchanged from draft05. VO frame: ~17-22ms. Satellite matching: ≤210ms async.
## Memory Budget (Jetson Orin Nano Super, 8GB shared) ## Memory Budget (Jetson Orin Nano Super, 8GB shared)
| Component | Memory | Notes | | Component | Memory | Notes |
|-----------|--------|-------| | ------------------------- | -------------- | ------------------------------------------- |
| OS + runtime | ~1.5GB | JetPack 6.2 + Python | | OS + runtime | ~1.5GB | JetPack 6.2 + Python |
| cuVSLAM | ~200-500MB | CUDA library + map | | cuVSLAM | ~200-500MB | CUDA library + map |
| LiteSAM TRT engine | ~50-80MB | If LiteSAM fails: EfficientLoFTR ~100-150MB | | LiteSAM TRT engine | ~50-80MB | If LiteSAM fails: EfficientLoFTR ~100-150MB |
@@ -495,10 +541,12 @@ Unchanged from draft05. VO frame: ~17-22ms. Satellite matching: ≤210ms async.
| ESKF + buffers | ~10MB | | | ESKF + buffers | ~10MB | |
| **Total** | **~2.1-2.9GB** | **26-36% of 8GB** | | **Total** | **~2.1-2.9GB** | **26-36% of 8GB** |
## Key Risks and Mitigations ## Key Risks and Mitigations
| Risk | Likelihood | Impact | Mitigation | | Risk | Likelihood | Impact | Mitigation |
|------|-----------|--------|------------| | ------------------------------------------------------- | ---------- | ----------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| LiteSAM MinGRU ops unsupported in TRT 10.3 | LOW-MEDIUM | LiteSAM TRT export fails | Day-one verification. Fallback: EfficientLoFTR TRT → XFeat TRT. | | LiteSAM MinGRU ops unsupported in TRT 10.3 | LOW-MEDIUM | LiteSAM TRT export fails | Day-one verification. Fallback: EfficientLoFTR TRT → XFeat TRT. |
| cuVSLAM fails on low-texture terrain at 0.7fps | HIGH | Frequent tracking loss | Satellite matching corrections bound drift. Re-localization pipeline handles tracking loss. IMU bridges short gaps. | | cuVSLAM fails on low-texture terrain at 0.7fps | HIGH | Frequent tracking loss | Satellite matching corrections bound drift. Re-localization pipeline handles tracking loss. IMU bridges short gaps. |
| Google Maps satellite quality in conflict zone | HIGH | Satellite matching fails, outdated imagery | Pre-flight tile validation. Consider alternative providers (Bing, Mapbox). Robust to seasonal appearance changes via feature-based matching. | | Google Maps satellite quality in conflict zone | HIGH | Satellite matching fails, outdated imagery | Pre-flight tile validation. Consider alternative providers (Bing, Mapbox). Robust to seasonal appearance changes via feature-based matching. |
@@ -511,9 +559,11 @@ Unchanged from draft05. VO frame: ~17-22ms. Satellite matching: ≤210ms async.
| Engine incompatibility after JetPack update | MEDIUM | Must rebuild engines | Include engine rebuild in update procedure. | | Engine incompatibility after JetPack update | MEDIUM | Must rebuild engines | Include engine rebuild in update procedure. |
| TRT engine build OOM on 8GB | LOW | Cannot build on target | Models small (6.31M, <5M). Reduce --memPoolSize if needed. | | TRT engine build OOM on 8GB | LOW | Cannot build on target | Models small (6.31M, <5M). Reduce --memPoolSize if needed. |
## Testing Strategy ## Testing Strategy
### Integration / Functional Tests ### Integration / Functional Tests
- **ESKF correctness**: Feed recorded IMU + synthetic VO/satellite data → verify output matches reference ESKF implementation - **ESKF correctness**: Feed recorded IMU + synthetic VO/satellite data → verify output matches reference ESKF implementation
- **GPS_INPUT field validation**: Send GPS_INPUT to SITL ArduPilot → verify EKF accepts and uses the data correctly - **GPS_INPUT field validation**: Send GPS_INPUT to SITL ArduPilot → verify EKF accepts and uses the data correctly
- **Coordinate transform chain**: Known GPS → NED → pixel → back to GPS — verify round-trip error <0.1m - **Coordinate transform chain**: Known GPS → NED → pixel → back to GPS — verify round-trip error <0.1m
@@ -528,6 +578,7 @@ Unchanged from draft05. VO frame: ~17-22ms. Satellite matching: ≤210ms async.
- **Confidence tier transitions**: Verify fix_type and accuracy change correctly across HIGH → MEDIUM → LOW → FAILED transitions - **Confidence tier transitions**: Verify fix_type and accuracy change correctly across HIGH → MEDIUM → LOW → FAILED transitions
### Non-Functional Tests ### Non-Functional Tests
- **End-to-end accuracy** (primary validation): Fly with real GPS recording → run GPS-denied system in parallel → compare estimated vs real positions → verify 80% within 50m, 60% within 20m - **End-to-end accuracy** (primary validation): Fly with real GPS recording → run GPS-denied system in parallel → compare estimated vs real positions → verify 80% within 50m, 60% within 20m
- **VO drift rate**: Measure cuVSLAM drift over 1km straight segment without satellite correction - **VO drift rate**: Measure cuVSLAM drift over 1km straight segment without satellite correction
- **Satellite matching accuracy**: Compare satellite-matched position vs real GPS at known locations - **Satellite matching accuracy**: Compare satellite-matched position vs real GPS at known locations
@@ -540,29 +591,32 @@ Unchanged from draft05. VO frame: ~17-22ms. Satellite matching: ≤210ms async.
- **Flight endurance**: Ground-test full system power draw against 267W estimate - **Flight endurance**: Ground-test full system power draw against 267W estimate
## References ## References
- ArduPilot GPS_RATE parameter: https://github.com/ArduPilot/ardupilot/pull/15980
- MAVLink GPS_INPUT message: https://ardupilot.org/mavproxy/docs/modules/GPSInput.html - ArduPilot GPS_RATE parameter: [https://github.com/ArduPilot/ardupilot/pull/15980](https://github.com/ArduPilot/ardupilot/pull/15980)
- pymavlink GPS_INPUT example: https://webperso.ensta.fr/lebars/Share/GPS_INPUT_pymavlink.py - MAVLink GPS_INPUT message: [https://ardupilot.org/mavproxy/docs/modules/GPSInput.html](https://ardupilot.org/mavproxy/docs/modules/GPSInput.html)
- ESKF reference (fixed-wing UAV): https://github.com/ludvigls/ESKF - pymavlink GPS_INPUT example: [https://webperso.ensta.fr/lebars/Share/GPS_INPUT_pymavlink.py](https://webperso.ensta.fr/lebars/Share/GPS_INPUT_pymavlink.py)
- ROS ESKF multi-sensor: https://github.com/EliaTarasov/ESKF - ESKF reference (fixed-wing UAV): [https://github.com/ludvigls/ESKF](https://github.com/ludvigls/ESKF)
- Range-VIO scale observability: https://arxiv.org/abs/2103.15215 - ROS ESKF multi-sensor: [https://github.com/EliaTarasov/ESKF](https://github.com/EliaTarasov/ESKF)
- NaviLoc trajectory-level localization: https://www.mdpi.com/2504-446X/10/2/97 - Range-VIO scale observability: [https://arxiv.org/abs/2103.15215](https://arxiv.org/abs/2103.15215)
- SatLoc-Fusion hierarchical framework: https://www.scilit.com/publications/e5cafaf875a49297a62b298a89d5572f - NaviLoc trajectory-level localization: [https://www.mdpi.com/2504-446X/10/2/97](https://www.mdpi.com/2504-446X/10/2/97)
- Auterion GPS-denied workflow: https://docs.auterion.com/vehicle-operation/auterion-mission-control/useful-resources/operations/gps-denied-workflow - SatLoc-Fusion hierarchical framework: [https://www.scilit.com/publications/e5cafaf875a49297a62b298a89d5572f](https://www.scilit.com/publications/e5cafaf875a49297a62b298a89d5572f)
- PX4 GNSS-denied flight: https://docs.px4.io/main/en/advanced_config/gnss_degraded_or_denied_flight.html - Auterion GPS-denied workflow: [https://docs.auterion.com/vehicle-operation/auterion-mission-control/useful-resources/operations/gps-denied-workflow](https://docs.auterion.com/vehicle-operation/auterion-mission-control/useful-resources/operations/gps-denied-workflow)
- ArduPilot GPS_INPUT advanced usage: https://discuss.ardupilot.org/t/advanced-usage-of-gps-type-mav-14/99406 - PX4 GNSS-denied flight: [https://docs.px4.io/main/en/advanced_config/gnss_degraded_or_denied_flight.html](https://docs.px4.io/main/en/advanced_config/gnss_degraded_or_denied_flight.html)
- Google Maps Ukraine imagery: https://newsukraine.rbc.ua/news/google-maps-has-surprise-for-satellite-imagery-1727182380.html - ArduPilot GPS_INPUT advanced usage: [https://discuss.ardupilot.org/t/advanced-usage-of-gps-type-mav-14/99406](https://discuss.ardupilot.org/t/advanced-usage-of-gps-type-mav-14/99406)
- Jetson Orin Nano Super thermal: https://edgeaistack.app/blog/jetson-orin-nano-power-consumption/ - Google Maps Ukraine imagery: [https://newsukraine.rbc.ua/news/google-maps-has-surprise-for-satellite-imagery-1727182380.html](https://newsukraine.rbc.ua/news/google-maps-has-surprise-for-satellite-imagery-1727182380.html)
- GSD matching research: https://www.kjrs.org/journal/view.html?pn=related&uid=756&vmd=Full - Jetson Orin Nano Super thermal: [https://edgeaistack.app/blog/jetson-orin-nano-power-consumption/](https://edgeaistack.app/blog/jetson-orin-nano-power-consumption/)
- VO+satellite matching pipeline: https://polen.itu.edu.tr/items/1fe1e872-7cea-44d8-a8de-339e4587bee6 - GSD matching research: [https://www.kjrs.org/journal/view.html?pn=related&uid=756&vmd=Full](https://www.kjrs.org/journal/view.html?pn=related&uid=756&vmd=Full)
- PyCuVSLAM docs: https://wiki.seeedstudio.com/pycuvslam_recomputer_robotics/ - VO+satellite matching pipeline: [https://polen.itu.edu.tr/items/1fe1e872-7cea-44d8-a8de-339e4587bee6](https://polen.itu.edu.tr/items/1fe1e872-7cea-44d8-a8de-339e4587bee6)
- Pixhawk 6x IMU (ICM-42688-P) datasheet: https://invensense.tdk.com/products/motion-tracking/6-axis/icm-42688-p/ - PyCuVSLAM docs: [https://wiki.seeedstudio.com/pycuvslam_recomputer_robotics/](https://wiki.seeedstudio.com/pycuvslam_recomputer_robotics/)
- Pixhawk 6x IMU (ICM-42688-P) datasheet: [https://invensense.tdk.com/products/motion-tracking/6-axis/icm-42688-p/](https://invensense.tdk.com/products/motion-tracking/6-axis/icm-42688-p/)
- All references from solution_draft05.md - All references from solution_draft05.md
## Related Artifacts ## Related Artifacts
- AC Assessment: `_docs/00_research/gps_denied_nav/00_ac_assessment.md` - AC Assessment: `_docs/00_research/gps_denied_nav/00_ac_assessment.md`
- Completeness assessment research: `_docs/00_research/solution_completeness_assessment/` - Completeness assessment research: `_docs/00_research/solution_completeness_assessment/`
- Previous research: `_docs/00_research/trt_engine_migration/` - Previous research: `_docs/00_research/trt_engine_migration/`
- Tech stack evaluation: `_docs/01_solution/tech_stack.md` (needs sync with draft05 corrections) - Tech stack evaluation: `_docs/01_solution/tech_stack.md` (needs sync with draft05 corrections)
- Security analysis: `_docs/01_solution/security_analysis.md` - Security analysis: `_docs/01_solution/security_analysis.md`
- Previous draft: `_docs/01_solution/solution_draft05.md` - Previous draft: `_docs/01_solution/solution_draft05.md`
@@ -1,50 +1,65 @@
# Question Decomposition # Question Decomposition — Draft 05
## Original Question ## Original Question
"I want to build a UAV plane for reconnaissance missions maximizing flight duration. Investigate what is the best frame material for that purpose." How durable and reliable would be using catapult+parachute instead of VTOL? Assess reliability of both options — VTOL motor failure during takeoff/landing, parachute landing damage to UAV and camera on gimbal.
## Active Mode ## Active Mode
Mode A (Initial Research) — no existing solution drafts found. Standalone mode. Mode B: Solution Assessment — assessing Draft 04 (VTOL vs Catapult+Parachute variants) with deep focus on reliability and durability comparison.
## Problem Context Summary
- Fixed-wing UAV for reconnaissance missions
- Primary objective: maximize flight duration
- Payload: ~1.47 kg (ADTI 20L V1 camera 0.22 kg + Viewpro A40 Pro gimbal 0.85 kg + Jetson Orin Nano Super 0.30 kg + Pixhawk 6x + GPS 0.10 kg)
- Battery: to be investigated, including semi-solid state options
- Budget: ~$100k first iteration
- No specific manufacturing method access yet
- Standard fixed-wing UAV operating environment
- No specific regulatory constraints stated
## Classified Question Type ## Classified Question Type
**Decision Support** — the user needs to select the optimal frame material (and battery technology) to maximize a specific metric (flight duration) under budget and payload constraints. **Problem Diagnosis + Decision Support** — diagnosing specific failure modes (motor failure, landing damage) and weighing reliability trade-offs between two launch/recovery approaches.
## Summary of Relevant Problem Context
- Platform: 18-22 kg MTOW, 3.8m wingspan, S2 fiberglass sandwich
- Variant A: Quad VTOL (4+1), 21-22 kg MTOW, 6.5-7.5h endurance
- Variant B: Catapult + Parachute, 18 kg MTOW, 7.5-8.5h endurance
- Payload: Viewpro Z40K gimbal camera (595g, 3-axis, belly-mounted) + ADTI 26S V1 nav camera
- Operational context: reconnaissance in eastern Ukraine, field deployment from pickup trucks
- Aircraft value: $15,000-17,000 per unit
- Fleet: 5 UAVs
- VTOL hover phase: ~75-120 seconds per sortie at 4,000-4,500W
- Parachute descent: 4.6 m/s, 950g system weight
## Research Subject Boundary Definition ## Research Subject Boundary Definition
| Dimension | Boundary | - **Population**: Fixed-wing UAVs in 15-25 kg MTOW class with VTOL or catapult+parachute launch/recovery
|-----------|----------| - **Geography**: Global technology, operational theater in Ukraine
| Population | Electric fixed-wing UAVs in the 5-15 kg MTOW class | - **Timeframe**: Current (2024-2026) production and field-proven systems
| Geography | Global — no regional restriction | - **Level**: Component-level failure analysis (motors, ESCs, parachutes, gimbals)
| Timeframe | Current state-of-the-art (2024-2026) |
| Level | Commercial/prosumer reconnaissance UAVs, not military large-scale platforms |
## Decomposed Sub-Questions ## Decomposed Sub-Questions
1. What frame materials are used in long-endurance fixed-wing UAVs and what are their properties (weight, strength, stiffness, cost, manufacturability)?
2. How does frame material choice impact flight endurance for a ~1.5 kg payload fixed-wing UAV? ### Sub-question A: VTOL Motor/ESC Failure Rates
3. What construction methods (monocoque, sandwich composite, foam-core) offer the best weight-to-strength for this class? What are the failure rates and MTBF data for brushless motors and ESCs in VTOL UAV applications? What are the dominant failure modes?
4. What battery technologies (LiPo, Li-Ion, semi-solid state) are available for fixed-wing UAVs and what are their energy densities?
5. What is the optimal airframe weight budget to maximize endurance given ~1.47 kg payload? ### Sub-question B: VTOL Motor Failure Consequences During Hover
6. What existing platforms in this class serve as benchmarks? What happens when a single motor or ESC fails during takeoff/landing hover at low altitude (0-30m)? Can a quad (4+1) configuration survive single motor out?
7. What are realistic acceptance criteria for flight duration, MTOW, and cost?
### Sub-question C: Parachute Landing Impact Forces
What impact forces does an 18 kg UAV experience at 4.6 m/s parachute descent rate? What is the landing attitude? What components are at risk?
### Sub-question D: Camera/Gimbal Vulnerability During Parachute Landing
How vulnerable is a belly-mounted gimbal camera (Viewpro Z40K) to parachute landing impact? What design solutions exist to protect it?
### Sub-question E: Parachute Deployment Reliability
What is the reliability of parachute deployment systems for fixed-wing UAVs? What are the failure modes?
### Sub-question F: Catapult Reliability
What is the reliability of pneumatic catapult systems? What are the maintenance requirements and failure modes?
### Sub-question G: Overall System Reliability Comparison
Considering all failure modes, which system (VTOL vs catapult+parachute) has higher operational reliability for the specific mission profile?
## Timeliness Sensitivity Assessment ## Timeliness Sensitivity Assessment
- **Research Topic**: UAV frame materials and semi-solid state batteries
- **Sensitivity Level**: 🟠 High — battery technology (semi-solid state) is evolving rapidly; frame materials are more stable (🟡 Medium) but current commercial offerings matter - **Research Topic**: UAV VTOL motor reliability, parachute recovery system durability, gimbal camera impact resistance
- **Rationale**: Semi-solid state batteries are a fast-moving market with new products launching in 2025-2026. Frame materials are more established but new composite techniques are emerging. - **Sensitivity Level**: Medium
- **Source Time Window**: 12 months for battery tech, 2 years for frame materials - **Rationale**: Motor/ESC technology, parachute recovery systems, and gimbal camera designs are mature and evolving moderately. Fundamental failure mechanisms are well-understood.
- **Source Time Window**: 2 years
- **Priority official sources to consult**: - **Priority official sources to consult**:
1. Grepow, Tattu, Herewin official product pages (semi-solid batteries) 1. ArduPilot quadplane reliability documentation
2. Applied Aeronautics, UAVMODEL product specs (benchmark platforms) 2. DeltaQuad maintenance schedules and procedures
3. Academic papers on composite UAV structures (2023-2025) 3. Fruity Chutes deployment guides and specifications
4. Motor/ESC manufacturer reliability data
- **Key version information to verify**: - **Key version information to verify**:
- Semi-solid battery energy density: currently 300-350 Wh/kg - ArduPilot quadplane motor failure handling (current firmware)
- Tattu/Grepow product availability: confirmed commercial products in 2025-2026 - Viewpro Z40K environmental specifications
@@ -1,221 +1,179 @@
# Source Registry # Source Registry — Draft 05
## Source #1 ## Sources 1-31: See Draft 04 source registry (all still applicable)
- **Title**: Why Carbon Fiber Fixed Wing Drones Are the Future of Industrial UAVs — UAVMODEL
- **Link**: https://www.uavmodel.com/blogs/news/skyeye-sr260-fixed-wing-drone-2600mm-long-endurance-mapping-amp-inspection
- **Tier**: L2
- **Publication Date**: 2025
- **Timeliness Status**: ✅ Currently valid
- **Target Audience**: Industrial/commercial UAV operators
- **Research Boundary Match**: ✅ Full match
- **Summary**: CFRP density 1.55-1.60 g/cm³ vs aluminum 2.7 g/cm³. Carbon fiber provides 40-50% weight reduction, superior vibration damping, thermal stability, and corrosion resistance for long-endurance fixed-wing drones.
- **Related Sub-question**: 1, 2
## Source #2 ## Source #32
- **Title**: SUX61 UAV Frame — Carbon Fiber, 8KG Payload, 91min Endurance - **Title**: Tips for Improving QuadPlane Safe Operation — ArduPilot Plane documentation
- **Link**: https://aerojetparts.com/product/sux61-uav-frame-carbon-fiber-8kg-payload-91min-endurance/ - **Link**: https://ardupilot.org/plane/docs/quadplane-reliability.html
- **Tier**: L1
- **Publication Date**: 2025 (latest)
- **Timeliness Status**: Currently valid
- **Target Audience**: Full match — quadplane VTOL operators
- **Research Boundary Match**: Full match
- **Summary**: Official ArduPilot guide for improving quadplane safety. Recommends redundant IMUs, sensors, airspeeds, compasses, GPS. Covers Q_TRANS_FAIL timer for transition failures. Does NOT include built-in motor failure detection/compensation for individual VTOL motors. Emphasizes proper battery voltage config and landing approach planning.
- **Related Sub-question**: A, B
## Source #33
- **Title**: DeltaQuad Evo TAC Preventative Maintenance schedule
- **Link**: https://docs.deltaquad.com/tac/maintenance/preventative-maintenance
- **Tier**: L1
- **Publication Date**: 2025 (latest)
- **Timeliness Status**: Currently valid
- **Target Audience**: Full match — VTOL fixed-wing operators
- **Research Boundary Match**: Full match
- **Summary**: DeltaQuad Evo maintenance schedule: post-flight propeller cleaning/inspection + fuselage cleaning after every flight. Full maintenance kit replacement every 12 months (4 VTOL arms with propellers, pusher motor pod with propeller, 2 wingtips). VTOL arms have moving parts requiring lubricant.
- **Related Sub-question**: A, F
## Source #34
- **Title**: How Long Do Brushless Drone Motors Last? — Mepsking
- **Link**: https://www.mepsking.shop/blog/how-long-do-brushless-drone-motors-last.html
- **Tier**: L3 - **Tier**: L3
- **Publication Date**: 2025
- **Timeliness Status**: ✅ Currently valid
- **Target Audience**: UAV builders/operators
- **Research Boundary Match**: ✅ Full match
- **Summary**: SUX61 carbon fiber frame: 3.4 kg airframe weight, 91-minute endurance, 8 kg payload. Uses 0.7mm thin-shell monocoque 3K carbon fiber via internal pressure molding.
- **Related Sub-question**: 1, 6
## Source #3
- **Title**: Vanilla UAV 192-hour flight duration record — FAI
- **Link**: https://www.fai.org/vanilla-uav-flight-duration-record
- **Tier**: L1
- **Publication Date**: 2021 (record event)
- **Timeliness Status**: ✅ Currently valid (record still stands)
- **Target Audience**: Aviation community
- **Research Boundary Match**: ⚠️ Partial overlap — fuel-powered, much larger class, but demonstrates endurance design principles
- **Summary**: Vanilla UAV set 192-hour 50-minute record. Demonstrates importance of systematic optimization across propulsion, avionics, and structural subsystems.
- **Related Sub-question**: 6
## Source #4
- **Title**: Fluid Coupled Structural Analysis of EPS-Fiber-Reinforced Composite Wing — Springer
- **Link**: https://link.springer.com/10.1007/s11029-024-10185-3
- **Tier**: L1
- **Publication Date**: 2024 - **Publication Date**: 2024
- **Timeliness Status**: Currently valid - **Timeliness Status**: Currently valid
- **Target Audience**: Aerospace engineers - **Target Audience**: Full match — drone motor reliability
- **Research Boundary Match**: Full match - **Research Boundary Match**: Full match
- **Summary**: EPS foam core + carbon/glass fiber composites achieved 30.5% wing weight reduction through topology optimization for MALE UAVs. - **Summary**: High-quality brushless motors: 10,000-20,000 hours under ideal conditions. Real-world drone use: FPV 500-2,000h, long-range/cruising 1,500-3,000h. Key failure points: bearing wear, overheating (degrades insulation/magnets/bearings), shaft play.
- **Related Sub-question**: 3 - **Related Sub-question**: A
## Source #5 ## Source #35
- **Title**: Grepow Semi-Solid State Battery Product Page - **Title**: ESC Desync and Common ESC Faults — Oscar Liang / Mepsking
- **Link**: https://www.grepow.com/semi-solid-state-battery/300wh-kg-series-high-energy-density-battery-pack.html - **Link**: https://oscarliang.com/fix-esc-desync/ and https://www.mepsking.com/blog/esc-faults-and-fixes-for-fpv-drones.html
- **Tier**: L2 - **Tier**: L3
- **Publication Date**: 2025
- **Timeliness Status**: ✅ Currently valid
- **Target Audience**: UAV manufacturers/integrators
- **Research Boundary Match**: ✅ Full match
- **Summary**: 300 Wh/kg series semi-solid state battery. NMC cathode, silicon-carbon anode, 2C charge, 3C continuous / 10C peak discharge, 1200+ cycles, -40°C to 60°C. 4S to 18S configurations.
- **Related Sub-question**: 4
## Source #6
- **Title**: Tattu Semi-Solid State Battery for UAVs
- **Link**: https://tattuworld.com/semi-solid-state-battery/
- **Tier**: L2
- **Publication Date**: 2025
- **Timeliness Status**: ✅ Currently valid
- **Target Audience**: Commercial drone operators
- **Research Boundary Match**: ✅ Full match
- **Summary**: 330-350 Wh/kg semi-solid batteries. Configurations from 1,550 mAh to 76,000 mAh, 11.4V to 68.4V. 500+ cycles at 90% retention. 30% flight endurance increase over LiPo.
- **Related Sub-question**: 4
## Source #7
- **Title**: Herewin Semi-Solid State Battery Guide (2026 Update)
- **Link**: https://www.herewinpower.com/blog/solid-state-drone-batteries-ultimate-guide/
- **Tier**: L2
- **Publication Date**: 2026
- **Timeliness Status**: ✅ Currently valid
- **Target Audience**: UAV manufacturers
- **Research Boundary Match**: ✅ Full match
- **Summary**: 300-400 Wh/kg at cell level, 303-313 Wh/kg at pack level. Silicon-carbon anodes (5-10% Si), high-Ni NCM cathode, 1000-3000 cycles. -20°C to 60°C operation.
- **Related Sub-question**: 4
## Source #8
- **Title**: Applied Aeronautics Albatross UAV Specifications
- **Link**: https://www.appliedaeronautics.com/albatross-uav
- **Tier**: L2
- **Publication Date**: 2024-2025 - **Publication Date**: 2024-2025
- **Timeliness Status**: Currently valid - **Timeliness Status**: Currently valid
- **Target Audience**: Commercial UAV operators - **Target Audience**: Full match — drone ESC reliability
- **Research Boundary Match**: Full match - **Research Boundary Match**: Full match
- **Summary**: Fiberglass+carbon fiber composite airframe. 3.35 kg bare airframe, 10 kg MTOW, up to 4 hours flight time, 4.5 kg payload capacity, 250+ km range. - **Summary**: ESC desync = motor stall mid-flight when ESC loses commutation timing. "Most common issue faced by drone pilots." Causes: sudden throttle changes, high RPM, electrical noise, voltage sag. ESC burnout is "most common issue" — rarely fixable without micro-soldering. Fixes: low-ESR caps, DShot protocol, proper BLHeli settings.
- **Related Sub-question**: 6, 1 - **Related Sub-question**: A, B
## Source #9 ## Source #36
- **Title**: Drone Frames: Carbon Fiber vs Aluminum — KingRaysCarbon - **Title**: Integrating a Drone Parachute / Understanding UAS Recovery — Fruity Chutes
- **Link**: https://kingrayscarbon.com/carbon-fiber-vs-aluminum-for-drone-frames-which-performs-better/ - **Link**: https://fruitychutes.com/uav_rpv_drone_recovery_parachutes/integrating-a-drone-parachute and https://fruitychutes.com/uav_rpv_drone_recovery_parachutes/uas-parachute-recovery-tutorial
- **Tier**: L3
- **Publication Date**: 2024
- **Timeliness Status**: ✅ Currently valid
- **Target Audience**: UAV hobbyists and professionals
- **Research Boundary Match**: ✅ Full match
- **Summary**: Carbon fiber: tensile strength up to 3000 MPa, specific stiffness 113 vs aluminum 26. Carbon fiber is 40% lighter than aluminum. Fiberglass cheaper but heavier (2.46-2.58 g/cm³).
- **Related Sub-question**: 1
## Source #10
- **Title**: Kevlar vs Carbon Fiber comparison — Dronecarbon
- **Link**: https://www.dronecarbon.com/kevlar-vs-carbon-fiber_a9075.html
- **Tier**: L3
- **Publication Date**: 2024
- **Timeliness Status**: ✅ Currently valid
- **Target Audience**: UAV builders
- **Research Boundary Match**: ✅ Full match
- **Summary**: Kevlar: 5x stronger than steel by weight, superior impact absorption, lower cost than CF. But heavier than CF, poor compressive strength, UV/moisture sensitive, difficult to machine.
- **Related Sub-question**: 1
## Source #11
- **Title**: LFP vs LiPo vs Semi-Solid Industrial Drone Batteries 2026 — Herewin
- **Link**: https://www.herewinpower.com/blog/lfp-vs-lipo-vs-semi-solid-industrial-drone-batteries-2026-roi-safety-and-performance/
- **Tier**: L2 - **Tier**: L2
- **Publication Date**: 2026 - **Publication Date**: 2024
- **Timeliness Status**: Currently valid - **Timeliness Status**: Currently valid
- **Target Audience**: UAV manufacturers/operators - **Target Audience**: Full match — UAV parachute recovery
- **Research Boundary Match**: Full match - **Research Boundary Match**: Full match
- **Summary**: Comparison of LFP, LiPo, and semi-solid batteries for industrial drones. Semi-solid achieves highest energy density and best long-term ROI. - **Summary**: Industry standard descent rate: 15 fps (4.6 m/s). Too small parachute = impact damage; too large = dragging after landing causing abrasion to cameras, gimbals. Y-harness attachment at CG. Parachute sizing by MTOW.
- **Related Sub-question**: 4 - **Related Sub-question**: C, D, E
## Source #12 ## Source #37
- **Title**: ASTM F3563-22 — Standard Specification for Large Fixed-Wing UAS - **Title**: DRS-25 Drone Parachute Recovery System — Harris Aerial
- **Link**: https://www.astm.org/f3563-22.html - **Link**: https://harrisaerial.com/drs-25-drone-parachute-recovery-system-15-25-kg-uav/
- **Tier**: L1
- **Publication Date**: 2022
- **Timeliness Status**: ✅ Currently valid
- **Target Audience**: UAV manufacturers, CAAs
- **Research Boundary Match**: ⚠️ Partial overlap — covers larger UAS but defines industry consensus standards
- **Summary**: Industry consensus standard for design and construction of large fixed-wing UAS. Accepted by CAAs as Means of Compliance.
- **Related Sub-question**: 7
## Source #13
- **Title**: DeltaQuad Evo Government Edition Specifications
- **Link**: https://docs.deltaquad.com/gov/vehicle-specifications
- **Tier**: L1 - **Tier**: L1
- **Publication Date**: 2025 - **Publication Date**: 2025
- **Timeliness Status**: Currently valid - **Timeliness Status**: Currently valid
- **Target Audience**: UAV operators/integrators - **Target Audience**: Full match — 15-25 kg UAV recovery
- **Research Boundary Match**: Full match - **Research Boundary Match**: Full match
- **Summary**: Empty weight 4.8 kg, MTOW 10 kg, wingspan 269 cm. Uses semi-solid state Li-ion batteries (6S, 22 Ah). Airframe: fiberglass, carbon, Kevlar, composite. 4h32m endurance (dual battery), 8h55m record with solid-state batteries. - **Summary**: Non-pyrotechnic electric deployment, ~600g, descent 2-3.6 m/s, impact energy tolerance 30-162 J. Operational even if all electronics fail. Patented design.
- **Related Sub-question**: 6, 1, 4 - **Related Sub-question**: C, E
## Source #14 ## Source #38
- **Title**: T700 vs T800 Carbon Fiber — Practical Selection Guide - **Title**: Boeing-Insitu ScanEagle operational data (150,000 hours, 1,500 recoveries)
- **Link**: https://www.carbonfibermaterial.com/t700-vs-t800-carbon-fiber-a-practical-guide-for-material-selection/ - **Link**: https://boeing.mediaroom.com/2009-04-13-Boeing-Insitu-ScanEagle-Logs-150-000-Service-Hours-in-Iraq-and-Afghanistan and http://www.globalsecurity.org/intell/library/news/2009/intell-090107-boeing01.htm
- **Tier**: L3 - **Tier**: L2
- **Publication Date**: 2009
- **Timeliness Status**: Currently valid — historical operational data remains factual
- **Target Audience**: Partial overlap — ScanEagle is smaller (18-22 kg) but uses similar catapult+recovery concept
- **Research Boundary Match**: Partial overlap (reference for operational reliability patterns)
- **Summary**: ScanEagle achieved 1,500 safe shipboard recoveries with U.S. Navy. 150,000+ service hours in Iraq/Afghanistan by 2009. Uses pneumatic SuperWedge catapult + SkyHook rope recovery. Described as "mature ISR asset that is safe, dependable."
- **Related Sub-question**: E, F, G
## Source #39
- **Title**: Assessing transferred energy in drone impacts — PMC
- **Link**: https://pmc.ncbi.nlm.nih.gov/articles/PMC12900295/
- **Tier**: L2
- **Publication Date**: 2025
- **Timeliness Status**: Currently valid
- **Target Audience**: Full match — UAV impact analysis
- **Research Boundary Match**: Reference only (studies human impact, but energy transfer physics apply)
- **Summary**: Drone impact energy transfer is NOT linear. Tested 5-180 J range. DJI Phantom at 280 J theoretical KE → only ~20% actual transmitted energy due to airframe deformation. Deformable structures significantly reduce impact transmission.
- **Related Sub-question**: C, D
## Source #40
- **Title**: Aludra SR-10 parachute recovery performance study
- **Link**: https://files.core.ac.uk/download/478919988.pdf
- **Tier**: L2
- **Publication Date**: 2018
- **Timeliness Status**: Currently valid — physics data
- **Target Audience**: Full match — fixed-wing UAV parachute recovery
- **Research Boundary Match**: Partial overlap (5 kg UAV, smaller than our 18 kg)
- **Summary**: Pilot-chute deployed and fully inflated main parachute in < 3 seconds. Terminal descent velocity ~4 m/s. Parachute reduced impact forces by 4× compared to belly landing (139.77 N to 30.81 N at 5 kg).
- **Related Sub-question**: C, E
## Source #41
- **Title**: Runway-Free Recovery Methods for Fixed-Wing UAVs: A Comprehensive Review — MDPI Drones
- **Link**: https://www.mdpi.com/2504-446X/8/9/463
- **Tier**: L2
- **Publication Date**: 2024 - **Publication Date**: 2024
- **Timeliness Status**: Currently valid - **Timeliness Status**: Currently valid
- **Target Audience**: Composite engineers - **Target Audience**: Full match
- **Research Boundary Match**: Full match - **Research Boundary Match**: Full match
- **Summary**: T700: 4900 MPa tensile, 230 GPa modulus, ~$18/m². T800: 5880 MPa, 294 GPa, ~$26/m². T700 recommended for UAVs — better impact resistance, lower cost, nearly same density. - **Summary**: Comprehensive review of recovery methods including parachute, net, deep stall, belly landing. Multiple recovery approaches can provide broader coverage than single-system solutions. Parachute recovery is mature and widely used for military fixed-wing UAVs.
- **Related Sub-question**: 1 - **Related Sub-question**: C, E, G
## Source #15 ## Source #42
- **Title**: CFRP Manufacturing Methods Comparison (VI vs VB vs HLU) - **Title**: ViewPro Z40K User Manual and specs
- **Link**: https://ejournal.brin.go.id/ijoa/article/view/286 - **Link**: https://www.manualslib.com/manual/2385515/Viewpro-Z40k.html and https://rcdrone.top/products/viewpro-z40k-4k-gimbal-camera
- **Tier**: L1 - **Tier**: L1
- **Publication Date**: 2024 - **Publication Date**: 2024-2025
- **Timeliness Status**: Currently valid - **Timeliness Status**: Currently valid
- **Target Audience**: Aerospace composite engineers - **Target Audience**: Full match
- **Research Boundary Match**: Full match - **Research Boundary Match**: Full match
- **Summary**: Vacuum infusion: 71% higher compressive/shear strength than hand layup, 53% higher than vacuum bagging. Prepreg achieves <0.5% void content vs 2-5% wet layup. - **Summary**: 3-axis stabilization, ±0.02° vibration, CNC aluminum housing, -20°C to +60°C operating temp. 5-axis OIS. Weight 595g. No published shock/impact G-force rating.
- **Related Sub-question**: 3 - **Related Sub-question**: D
## Source #16 ## Source #43
- **Title**: Rohacell vs Honeycomb, Balsa & PVC Foam — Chem-Craft - **Title**: Basic Design of a Repositioning Event — Airborne Systems
- **Link**: https://chem-craft.com/blog/comparative-analysis-rohacell-vs-traditional-materials-in-composite-engineering/ - **Link**: https://airborne-sys.com/wp-content/uploads/2016/10/aiaa-2009-2911_basic_design_of_a_reposit.pdf
- **Tier**: L3
- **Publication Date**: 2024
- **Timeliness Status**: ✅ Currently valid
- **Target Audience**: Composite engineers
- **Research Boundary Match**: ✅ Full match
- **Summary**: Rohacell PMI: highest stiffness-to-weight, closed-cell, withstands autoclave temps. XPS: good cost/performance middle ground. EPS: cheapest but lowest strength. PVC: moderate cost/performance.
- **Related Sub-question**: 3
## Source #17
- **Title**: LFP vs LiPo vs Semi-Solid Industrial Drone Batteries 2026 — Herewin
- **Link**: https://www.herewinpower.com/blog/lfp-vs-lipo-vs-semi-solid-industrial-drone-batteries-2026-roi-safety-and-performance/
- **Tier**: L2 - **Tier**: L2
- **Publication Date**: 2026 - **Publication Date**: 2009
- **Timeliness Status**: Currently valid - **Timeliness Status**: Currently valid — engineering principles
- **Target Audience**: UAV manufacturers/operators - **Target Audience**: Full match — UAV parachute recovery orientation
- **Research Boundary Match**: Full match - **Research Boundary Match**: Full match
- **Summary**: Semi-solid 300-400 Wh/kg, 800-1200 cycles. LiPo 100-200 Wh/kg, 200-500 cycles. Li-ion 200-250 Wh/kg, 500-800 cycles. Semi-solid reduces internal temp rise by 60% vs LiPo. - **Summary**: UAV typically hangs nose-down under parachute. Repositioning event can reorient to ~95° (5° nose up) for belly-first landing. Attachment point relative to CG determines hanging attitude.
- **Related Sub-question**: 4 - **Related Sub-question**: C, D
## Source #18 ## Source #44
- **Title**: Carbon-Kevlar Hybrid Fabric Properties — Impact Materials - **Title**: UAV payload retraction mechanism — AeroVironment patent
- **Link**: https://ictmaterial.com/what-is-carbon-kevlar-hybrid-fabric-properties-and-use-cases/ - **Link**: https://patents.justia.com/patent/11975867
- **Tier**: L3
- **Publication Date**: 2025
- **Timeliness Status**: ✅ Currently valid
- **Target Audience**: Composite engineers
- **Research Boundary Match**: ✅ Full match
- **Summary**: Carbon-Kevlar hybrid: 800-1200 MPa tensile, 70-90 GPa modulus, 25-40% lighter than aluminum. Superior crash survivability via Kevlar's energy absorption.
- **Related Sub-question**: 1
## Source #19
- **Title**: Scabro Innovations — UAV Composite Prototyping
- **Link**: https://scabroinnovations.com/diensten/composite-airframe-prototyping/
- **Tier**: L3
- **Publication Date**: 2025
- **Timeliness Status**: ✅ Currently valid
- **Target Audience**: UAV developers
- **Research Boundary Match**: ✅ Full match
- **Summary**: Full-service composite airframe prototyping. Flexible tooling from single prototype to production. Semi-assembled airframes, wings, full systems with wiring/sensor integration.
- **Related Sub-question**: 3
## Source #20
- **Title**: Tattu 330Wh/Kg Semi-Solid 33000mAh 22.2V 6S Product Page
- **Link**: https://www.tattuworld.com/semi-solid-state-battery/semi-solid-330wh-kg-33000mah-22-2v-10c-6s-battery.html
- **Tier**: L2 - **Tier**: L2
- **Publication Date**: 2024
- **Timeliness Status**: Currently valid
- **Target Audience**: Full match
- **Research Boundary Match**: Full match
- **Summary**: Patented retractable gimbal mechanism: payload pivotally attached to housing with biasing member pushing outward, winch retracts payload into housing for protection during landing. ArduPilot supports automatic landing gear/camera retraction via servo.
- **Related Sub-question**: D
## Source #45
- **Title**: Catapult launch reliability factors — Alibaba industry guide
- **Link**: https://www.alibaba.com/product-insights/how-to-choose-the-best-drone-catapult-for-reliable-launches.html
- **Tier**: L4
- **Publication Date**: 2025 - **Publication Date**: 2025
- **Timeliness Status**: Currently valid - **Timeliness Status**: Currently valid
- **Target Audience**: UAV operators - **Target Audience**: Full match
- **Research Boundary Match**: Full match - **Research Boundary Match**: Full match
- **Summary**: 330 Wh/kg, 33000 mAh, 22.2V (6S), 10C peak discharge, weight 2324g, 732.6 Wh energy per pack. Dimensions: 210x93x60.5mm. - **Summary**: Systems with < 5% velocity variance reduce pre-flight recalibration by 68%, cut mid-flight stabilization corrections by >50%. Critical reliability factors: IP65 minimum sealing, ±0.05mm precision rails, vibration damping, adjustable energy profiles.
- **Related Sub-question**: 4 - **Related Sub-question**: F
## Source #46
- **Title**: Reliability Analysis of Multi-rotor UAV Based on Fault Tree — Springer
- **Link**: https://link.springer.com/chapter/10.1007/978-981-10-6553-8_100
- **Tier**: L2
- **Publication Date**: 2018
- **Timeliness Status**: Currently valid — reliability engineering principles
- **Target Audience**: Reference only — multirotor, not fixed-wing VTOL
- **Research Boundary Match**: Reference only
- **Summary**: Fault tree analysis + Monte Carlo simulation for multirotor reliability. Identifies motors, ESCs, and batteries as critical components. Proposes redundancy at component and system levels to meet reliability targets.
- **Related Sub-question**: A, G
## Source #47
- **Title**: Post-ESC-Failure Performance of UAM-Scale Hexacopter — VFS
- **Link**: https://proceedings.vtol.org/80/evtol/post-esc-failure-performance-of-a-uam-scale-hexacopter-with-dual-three-phase-motors
- **Tier**: L2
- **Publication Date**: 2024
- **Timeliness Status**: Currently valid
- **Target Audience**: Partial overlap — larger scale eVTOL
- **Research Boundary Match**: Reference only (larger scale, but failure physics apply)
- **Summary**: Dual three-phase motor systems with independent ESCs can tolerate single ESC failure while maintaining control. Power electronics identified as "weak links" for propulsion reliability.
- **Related Sub-question**: A, B
@@ -1,161 +1,113 @@
# Fact Cards # Fact Cards — Draft 05 Research (Reliability: VTOL vs Catapult+Parachute)
## Fact #1 ## Fact #36
- **Statement**: Carbon fiber reinforced polymer (CFRP) has a density of 1.55-1.60 g/cm³, compared to aluminum at 2.7 g/cm³ and fiberglass at 2.46-2.58 g/cm³, resulting in 40-50% lighter frames for equivalent stiffness. - **Statement**: High-quality brushless motors last 10,000-20,000 hours under ideal conditions. Real-world drone usage: FPV/racing 500-2,000h, long-range/cruising 1,500-3,000h. Key failure modes: bearing wear (correlates with rotations), overheating (degrades insulation, magnets, bearings), shaft play. No manufacturer publishes formal MTBF data for drone motors.
- **Source**: Source #1, #9 - **Source**: Source #34
- **Phase**: Phase 1 - **Phase**: Assessment
- **Target Audience**: All fixed-wing UAV classes - **Confidence**: ⚠️ Medium — general guidance from industry blog, no formal testing data
- **Confidence**: ✅ High - **Related Dimension**: VTOL motor reliability
- **Related Dimension**: Weight / material density
## Fact #2 ## Fact #37
- **Statement**: CFRP tensile strength reaches up to 3000 MPa with specific stiffness of 113, compared to aluminum at 26 and titanium at 25. - **Statement**: ESC desync (motor stall mid-flight when ESC loses commutation timing) is described as "the most common issue faced by drone pilots." ESC burnout is "the most common issue experienced with ESCs" — rarely fixable. Causes: sudden throttle changes (hover transitions), high RPM, electrical noise, voltage sag from weak batteries, damaged MOSFETs. Mitigation: low-ESR capacitors, DShot protocol, proper BLHeli settings, rampup power tuning.
- **Source**: Source #9 - **Source**: Source #35
- **Phase**: Phase 1 - **Phase**: Assessment
- **Target Audience**: All UAV classes - **Confidence**: ✅ High — well-documented in multiple expert sources
- **Confidence**: ✅ High - **Related Dimension**: VTOL ESC reliability
- **Related Dimension**: Structural strength
## Fact #3 ## Fact #38
- **Statement**: The Albatross UAV (fiberglass + carbon fiber composite) weighs 3.35 kg bare airframe, achieves 10 kg MTOW, and flies up to 4 hours with payload capacity of 4.5 kg. - **Statement**: ArduPilot quadplane firmware does NOT have built-in individual VTOL motor failure detection or automatic compensation. Q_TRANS_FAIL timer exists for transition failure (e.g., cruise motor failure during transition) but not for individual hover motor loss. Official safety tips recommend redundant IMUs, sensors, airspeeds, compasses, GPS — but do not address motor-level redundancy. Motor failure during VTOL hover must be handled by the inherent physics of quad configuration.
- **Source**: Source #8 - **Source**: Source #32
- **Phase**: Phase 1 - **Phase**: Assessment
- **Target Audience**: Commercial fixed-wing UAVs in our target class - **Confidence**: ✅ High — official ArduPilot documentation
- **Confidence**: ✅ High - **Related Dimension**: VTOL failure recovery
- **Related Dimension**: Benchmark platform
## Fact #4 ## Fact #39
- **Statement**: EPS foam core reinforced with carbon/glass fiber composites achieved 30.5% wing weight reduction through topology optimization for MALE UAVs. - **Statement**: ArduPilot Copter CAN detect thrust loss when motors saturate at 100% throttle and issue warnings. However, this is detection/warning only — not automatic motor-out compensation for quadplane VTOL. In copter mode (not quadplane), some single-motor-out survival has been demonstrated at altitude by sacrificing yaw control, but this is not officially supported for quadplane VTOL phase.
- **Source**: Source #4 - **Source**: Source #32, ArduPilot Copter docs
- **Phase**: Phase 1 - **Phase**: Assessment
- **Target Audience**: Fixed-wing UAV designers - **Confidence**: ⚠️ Medium — copter mode data extrapolated to quadplane context
- **Confidence**: ✅ High (peer-reviewed) - **Related Dimension**: VTOL failure recovery
- **Related Dimension**: Construction method
## Fact #5 ## Fact #40
- **Statement**: Semi-solid state batteries currently achieve 300-350 Wh/kg at cell level, with pack-level targets of 303-313 Wh/kg. This is 30-50% higher than traditional LiPo (150-250 Wh/kg). - **Statement**: DeltaQuad Evo TAC maintenance schedule: propeller cleaning/inspection + fuselage cleaning after EVERY flight. Full maintenance kit replacement every 12 months: 4 VTOL arms with propellers, pusher motor pod with propeller, 2 wingtips. VTOL arms described as having "moving parts requiring lubricants." This implies motor/arm assemblies are considered wear items with ~12 month service life under operational use.
- **Source**: Source #5, #6, #7 - **Source**: Source #33
- **Phase**: Phase 1 - **Phase**: Assessment
- **Target Audience**: UAV battery selection - **Confidence**: ✅ High — official manufacturer maintenance schedule
- **Confidence**: ✅ High (multiple manufacturer confirmations) - **Related Dimension**: VTOL maintenance burden, component wear
- **Related Dimension**: Battery energy density
## Fact #6 ## Fact #41
- **Statement**: Tattu semi-solid batteries: 330-350 Wh/kg, capacities from 1,550-76,000 mAh, voltages 11.4-68.4V, 500+ cycles at 90% retention, 10C peak discharge. - **Statement**: DeltaQuad Evo TAC max hover time: 90 seconds before forced landing. VTOL hover phase per sortie: ~75-120 seconds (takeoff climb 30-45s + transition 10-15s + return transition 15-20s + descent 20-30s). At 4,000-4,500W hover power for 20 kg aircraft, each motor runs at ~1,000-1,125W — near its operational limit for 15" prop class motors rated at 1,200-1,500W max.
- **Source**: Source #6 - **Source**: Source #22 (DeltaQuad), Fact #25, #26 from Draft 04
- **Phase**: Phase 1 - **Phase**: Assessment
- **Target Audience**: Commercial UAV operators - **Confidence**: ✅ High — manufacturer data + physics calculation
- **Confidence**: ✅ High (manufacturer spec) - **Related Dimension**: VTOL stress during hover
- **Related Dimension**: Battery specifications
## Fact #7 ## Fact #42
- **Statement**: Grepow semi-solid batteries: 300 Wh/kg series, 2C charge, 3C continuous / 10C peak discharge, 1200+ cycles, -40°C to 60°C, multiple S configurations (4S-18S). - **Statement**: Quad VTOL configuration provides partial single-motor-out redundancy. If one of 4 VTOL motors fails, the remaining 3 can theoretically maintain controlled descent — but yaw control is degraded (must sacrifice yaw to maintain thrust/attitude) and available thrust drops to 75%. At 20 kg with 260% thrust margin (Y37 reference), 3 motors provide ~195% margin — sufficient for controlled descent but not extended hover. At low altitude (< 10m during takeoff/landing), reaction time is < 2 seconds before ground contact.
- **Source**: Source #5 - **Source**: Derived from Fact #21 (Y37 thrust margin), ArduPilot community discussions
- **Phase**: Phase 1 - **Phase**: Assessment
- **Target Audience**: Commercial UAV operators - **Confidence**: ⚠️ Medium — theoretical analysis, not flight-tested on our platform
- **Confidence**: ✅ High (manufacturer spec) - **Related Dimension**: VTOL motor redundancy
- **Related Dimension**: Battery specifications
## Fact #8 ## Fact #43
- **Statement**: Semi-solid state batteries deliver 800-1200+ cycle life vs 200-300 for traditional LiPo, retaining >80% capacity after 1000+ cycles. - **Statement**: Parachute landing at 4.6 m/s for 18 kg UAV: kinetic energy = 0.5 × 18 × 4.6² = 190 J. This equals a drop from 1.08m height. Research on drone impact energy transfer shows only ~20% of theoretical KE is actually transmitted due to airframe deformation and energy absorption. Effective transmitted energy: ~38 J. For comparison, DRS-25 system tolerates 30-162 J impact energy at 2-3.6 m/s descent.
- **Source**: Source #5, #7 - **Source**: Source #39, #37
- **Phase**: Phase 1 - **Phase**: Assessment
- **Target Audience**: UAV operators - **Confidence**: ⚠️ Medium — energy transmission ratio from different UAV type (DJI Phantom), our S2 FG may differ
- **Confidence**: ✅ High - **Related Dimension**: Parachute landing impact
- **Related Dimension**: Battery longevity / cost of ownership
## Fact #9 ## Fact #44
- **Statement**: Kevlar is heavier than carbon fiber, has poor compressive strength, is UV/moisture sensitive, and difficult to machine — making it inferior to CFRP for UAV primary structure despite superior impact absorption. - **Statement**: Fixed-wing UAV typically hangs nose-down under parachute descent when Y-harness is attached at CG. A repositioning event (mid-air reorientation) can change attitude to ~95° from vertical (5° nose up) for belly-first landing. Without repositioning, the nose and any belly-mounted payload will be the first contact point. With repositioning to belly-first, a belly-mounted gimbal is still vulnerable.
- **Source**: Source #10 - **Source**: Source #43, #36
- **Phase**: Phase 1 - **Phase**: Assessment
- **Target Audience**: UAV frame material selection - **Confidence**: ✅ High — engineering documentation from Airborne Systems (parachute manufacturer)
- **Confidence**: ✅ High - **Related Dimension**: Camera vulnerability during parachute landing
- **Related Dimension**: Material comparison
## Fact #10 ## Fact #45
- **Statement**: Carbon fiber-balsa sandwich structures provide excellent mechanical properties. Balsa core is ultra-lightweight but susceptible to moisture absorption. Modern approach favors EPS/Rohacell foam cores for moisture immunity. - **Statement**: Viewpro Z40K: 3-axis stabilization, ±0.02° vibration, CNC aluminum housing, -20°C to +60°C. Weight 595g. No published shock/impact G-force rating or MIL-STD compliance. The gimbal is designed for aerial operation vibration, NOT for landing impact loads. Typical drone gimbal cameras are consumer/commercial grade and do not have explicit impact survival ratings.
- **Source**: Source #4, Springer comparative analysis - **Source**: Source #42
- **Phase**: Phase 1 - **Phase**: Assessment
- **Target Audience**: UAV wing designers - **Confidence**: ✅ High — manufacturer specifications
- **Confidence**: ✅ High - **Related Dimension**: Camera vulnerability
- **Related Dimension**: Construction method
## Fact #11 ## Fact #46
- **Statement**: SUX61 carbon fiber frame achieves 91-minute endurance with 3.4 kg airframe weight and 8 kg payload using 0.7mm thin-shell monocoque 3K carbon fiber. - **Statement**: Camera/gimbal protection during parachute landing depends on: (1) gimbal position — belly-mounted is most vulnerable, side-mounted or top-mounted is safer; (2) harness attachment point and resulting landing attitude; (3) retractable gimbal mechanisms exist (AeroVironment patent, ArduPilot landing gear retraction via LGR_OPTIONS); (4) terrain softness; (5) parachute size — too large causes dragging after landing, abrading exposed components.
- **Source**: Source #2 - **Source**: Source #36, #43, #44
- **Phase**: Phase 1 - **Phase**: Assessment
- **Target Audience**: Fixed-wing UAV builders in our class - **Confidence**: ✅ High — multiple engineering sources
- **Confidence**: ⚠️ Medium (single manufacturer claim) - **Related Dimension**: Camera protection design solutions
- **Related Dimension**: Benchmark platform
## Fact #12 ## Fact #47
- **Statement**: For electric propeller-driven aircraft, maximum endurance occurs at minimum power required speed (~76% of best-range speed). Endurance is directly proportional to battery energy and L/D ratio, inversely proportional to weight. - **Statement**: Parachute deployment from fixed-wing in forward flight: pilot chute catches airflow → drags main chute → full inflation in < 3 seconds (Aludra SR-10 test data). Dual deployment triggers (autopilot + RC manual) significantly reduce deployment failure risk. Spring-loaded hatch mechanism is simple and reliable. Fruity Chutes systems use proven Iris Ultra dome chutes with Spectra shroud lines — mature, field-proven technology.
- **Source**: FIRGELLI endurance calculator, general aerospace engineering - **Source**: Source #40, #36
- **Phase**: Phase 1 - **Phase**: Assessment
- **Target Audience**: All electric fixed-wing UAVs - **Confidence**: ✅ High — flight test data + commercial product track record
- **Confidence**: ✅ High (established physics) - **Related Dimension**: Parachute deployment reliability
- **Related Dimension**: Endurance optimization
## Fact #13 ## Fact #48
- **Statement**: Custom carbon fiber UAV airframes range from $20-50 for small CNC-cut frames to ~$3000 for large industrial frames. Full custom composite airframe development with tooling would be significantly more. - **Statement**: ScanEagle (18-22 kg fixed-wing) achieved 1,500 safe shipboard recoveries and 150,000+ service hours in Iraq/Afghanistan using catapult launch + SkyHook recovery. Described as "mature ISR asset that is safe, dependable." Catapult launch is the standard for military tactical fixed-wing UAVs. However, ScanEagle uses SkyHook (rope catch), not parachute — different recovery method.
- **Source**: Multiple manufacturer listings - **Source**: Source #38
- **Phase**: Phase 1 - **Phase**: Assessment
- **Target Audience**: UAV builders - **Confidence**: ✅ High — official Boeing/Insitu press releases with specific numbers
- **Confidence**: ⚠️ Medium (prices vary widely by specification) - **Related Dimension**: Catapult system reliability
- **Related Dimension**: Cost
## Fact #14 ## Fact #49
- **Statement**: T700 carbon fiber: 4900 MPa tensile, 230 GPa modulus, ~$18/m². T800: 5880 MPa, 294 GPa, ~$26/m² (44% premium). T700 has better impact tolerance due to higher elongation at break. Density is nearly identical (1.80 vs 1.81 g/cm³). - **Statement**: Pneumatic catapult reliability factors: systems with < 5% velocity variance reduce pre-flight recalibration by 68%. Critical: IP65 minimum sealing, ±0.05mm precision rails, vibration damping. ELI PL-60 uses Makita 18V battery — simple, field-serviceable power source. Failure modes: seal degradation, pressure loss, carriage jamming. All are mechanical and inspectable pre-flight. Robonic: annual maintenance ~4-5% of acquisition cost.
- **Source**: Source #14 - **Source**: Source #45, #26 (Robonic), #24 (ELI)
- **Phase**: Phase 2 - **Phase**: Assessment
- **Target Audience**: UAV composite designers - **Confidence**: ⚠️ Medium — catapult reliability data from industry guide (L4) + manufacturer claims
- **Confidence**: ✅ High - **Related Dimension**: Catapult system reliability
- **Related Dimension**: Material grade selection
## Fact #15 ## Fact #50
- **Statement**: Vacuum infusion produces 71% higher compressive strength and 71% higher shear strength than hand layup; 53% higher than vacuum bagging. Prepreg achieves <0.5% void content vs 2-5% for wet layup. - **Statement**: Parachute reduced impact forces by 4× compared to belly landing in Aludra SR-10 tests (139.77 N to 30.81 N at 5 kg). Scaling to 18 kg: belly landing at 15 m/s = 2,025 J kinetic energy vs parachute at 4.6 m/s = 190 J. Parachute reduces landing energy by >90% compared to belly landing.
- **Source**: Source #15 - **Source**: Source #40
- **Phase**: Phase 2 - **Phase**: Assessment
- **Target Audience**: Composite manufacturers - **Confidence**: ✅ High — flight test data (though at smaller 5 kg scale)
- **Confidence**: ✅ High (peer-reviewed) - **Related Dimension**: Landing damage comparison
- **Related Dimension**: Manufacturing method
## Fact #16 ## Fact #51
- **Statement**: DeltaQuad Evo: 4.8 kg empty, 10 kg MTOW, 269 cm wingspan. Uses fiberglass + carbon + Kevlar composite. Semi-solid state 6S 22Ah batteries. Achieved 8h55m endurance record with solid-state batteries. Standard endurance 4h32m with dual semi-solid batteries. - **Statement**: VTOL motor/ESC failure probability: no public quantitative data exists for small UAV brushless motor failure rates per flight hour. NASA research identifies power electronics (ESCs) and electric motors as "weak links" raising predicted catastrophic failure rates in eVTOL vehicles. Fault tree + Monte Carlo analyses identify motors, ESCs, and batteries as critical components requiring redundancy. Industry consensus: motor reliability is high (1000s of hours) but ESC desync/burnout is the dominant propulsion failure mode.
- **Source**: Source #13 - **Source**: Source #46, #47, NASA NTRS 20240005899
- **Phase**: Phase 2 - **Phase**: Assessment
- **Target Audience**: Fixed-wing UAV designers in our target class - **Confidence**: ⚠️ Medium — qualitative assessment, no specific failure rate numbers
- **Confidence**: ✅ High (manufacturer + FAI-type record) - **Related Dimension**: VTOL failure probability
- **Related Dimension**: Benchmark validation
## Fact #17
- **Statement**: Carbon-Kevlar hybrid fabric: 800-1200 MPa tensile, 70-90 GPa modulus, 25-40% lighter than aluminum. Superior crash survivability via Kevlar energy absorption. But Kevlar is UV-sensitive, moisture-absorbing, and very difficult to machine.
- **Source**: Source #18
- **Phase**: Phase 2
- **Target Audience**: UAV structural designers
- **Confidence**: ✅ High
- **Related Dimension**: Hybrid material approach
## Fact #18
- **Statement**: PVC foam (Divinycell H-series): closed-cell, density 40-250 kg/m³, moisture-immune, handles 80°C cure. Rohacell PMI: highest stiffness/weight, 180°C+, but 3-5x more expensive. XPS: cheapest closed-cell option but limited to 75°C.
- **Source**: Source #16
- **Phase**: Phase 2
- **Target Audience**: Composite wing designers
- **Confidence**: ✅ High
- **Related Dimension**: Foam core selection
## Fact #19
- **Statement**: For electric fixed-wing UAV, endurance = usable battery energy / total system power. Payload electronics (Jetson Orin Nano ~15-25W, camera+gimbal ~10-15W) add ~30W to cruise power, reducing endurance by ~15-20% compared to calculations ignoring payload power.
- **Source**: General aerospace engineering + manufacturer specs
- **Phase**: Phase 2
- **Target Audience**: UAV system designers
- **Confidence**: ✅ High
- **Related Dimension**: Endurance calculation
## Fact #20
- **Statement**: Tattu 330Wh/kg 6S 33000mAh: weight 2324g, energy 732.6 Wh, dimensions 210×93×60.5mm. At pack level: 732.6/2.324 = 315 Wh/kg actual. 10C peak discharge, XT90-S connector.
- **Source**: Source #20
- **Phase**: Phase 2
- **Target Audience**: UAV battery integration
- **Confidence**: ✅ High (manufacturer spec)
- **Related Dimension**: Battery sizing
@@ -1,69 +1,40 @@
# Comparison Framework # Comparison Framework — Draft 05 (Reliability Focus)
## Selected Framework Type ## Selected Framework Type
Decision Support — selecting optimal frame material and battery to maximize flight endurance under budget/payload constraints. Decision Support — reliability and durability comparison of VTOL vs Catapult+Parachute for 18-22 kg S2 FG reconnaissance UAV.
## Selected Dimensions ## Candidates
1. Weight (density, specific weight) 1. **Quad VTOL (4+1)** — 4 hover motors + 1 pusher, precision takeoff/landing
2. Structural performance (stiffness, strength, fatigue) 2. **Catapult + Parachute** — pneumatic catapult launch + parachute recovery
3. Impact resistance / crash survivability
4. Manufacturing complexity / accessibility
5. Cost (material + manufacturing + tooling)
6. Environmental durability (temperature, moisture, UV)
7. Repairability in field conditions
8. Endurance impact (calculated flight time contribution)
## Component 1: Frame Material ## Selected Dimensions (Reliability-Focused)
| Dimension | CFRP (T700) | Fiberglass (E-glass) | Carbon-Kevlar Hybrid | Aluminum 6061-T6 | 1. Propulsion system failure probability (per sortie)
|-----------|-------------|---------------------|----------------------|-------------------| 2. Failure consequence severity (single component failure)
| Density (g/cm³) | 1.55-1.60 | 2.46-2.58 | ~1.45 | 2.70 | 3. Low-altitude failure survivability
| Tensile strength (MPa) | 3000-4900 | 800-1500 | 800-1200 | 310 | 4. Payload/camera damage risk per landing
| Specific stiffness | 113 | ~28 | 48-62 | 26 | 5. Landing damage to airframe per landing
| Impact resistance | Low (brittle) | Medium | High (Kevlar absorption) | High (ductile) | 6. System complexity (number of failure points)
| Cost (relative) | High ($18/m² T700) | Low (~$5/m²) | Very High (~$30/m²) | Low | 7. Maintenance burden and component wear
| Manufacturability | Medium (requires curing) | Easy (room-temp cure) | Difficult (Kevlar hard to machine) | Easy (CNC) | 8. Environmental sensitivity (wind, terrain, temperature)
| Moisture resistance | Excellent | Good | Good (Kevlar absorbs) | Excellent | 9. Single point of failure analysis
| UV resistance | Good (with coating) | Good | Poor (Kevlar degrades) | Excellent | 10. Operational availability (% of sorties successfully completed)
| Repairability | Difficult | Easy | Very difficult | Easy | 11. Cumulative airframe fatigue (over 100+ landings)
| Weight savings vs Al | 40-50% | 5-10% | 45-55% | Baseline |
| Factual Basis | Fact #1, #2, #9 | Fact #1, #3 | Source #18 | Fact #1 |
## Component 2: Construction Method ## Initial Population
| Dimension | Sandwich (foam core + CF skin) | Monocoque (solid CF shell) | Spar + Rib + Skin (traditional) | | Dimension | Quad VTOL | Catapult + Parachute |
|-----------|-------------------------------|---------------------------|-------------------------------| |-----------|-----------|---------------------|
| Weight efficiency | Excellent (30% lighter) | Good | Moderate | | 1. Motor/ESC failure probability | 8 electronic components (4 motors + 4 ESCs) active during high-stress hover | 0 electronic components during recovery; 1 motor during launch (cruise motor) |
| Stiffness per weight | Highest | High | Moderate | | 2. Single component failure consequence | Motor/ESC fail during hover → degraded control, possible crash at low altitude | Parachute non-deploy → aircraft loss; catapult fail → cannot launch (no aircraft loss) |
| Manufacturing complexity | Medium (requires core + layup) | Medium (requires mold) | Higher (many parts) | | 3. Low-altitude survivability | Quad has partial redundancy; < 10m altitude = < 2s reaction time | N/A — no powered hover phase |
| Tooling cost | Medium | High (precise molds) | Low-Medium | | 4. Camera damage per landing | Near-zero (precision landing on gear or flat surface) | Medium-high if gimbal protrudes below fuselage; low if properly protected |
| Repairability | Moderate | Difficult | Good (replace parts) | | 5. Airframe damage per landing | Near-zero (VTOL landing on gear) | Low (190 J at 4.6 m/s, S2 FG absorbs well) + risk of wind drag |
| Best for | Wings, fuselage panels | Fuselage, nacelles | Prototype/custom builds | | 6. System complexity | +8 electronic components, VTOL battery, boom attachments | Parachute (passive fabric), hatch servo, catapult (mechanical) |
| Factual Basis | Fact #4, #10 | Fact #11 | General aerospace | | 7. Maintenance | VTOL arms/motors replaced every 12 months (DeltaQuad); per-flight prop inspection | Parachute repack every landing (5-10 min); catapult maintenance 4-5%/year |
| 8. Environmental sensitivity | Wind limits hover (typically < 12 m/s); temperature affects batteries | Wind causes drift (100-200m); terrain must be suitable for landing |
| 9. Single point of failure | Cruise motor (shared); VTOL battery; individual motor/ESC (partial redundancy) | Catapult (if broken, cannot launch); parachute (if non-deploy, aircraft loss) |
| 10. Operational availability | High — works from any 5×5m flat area | Medium — requires catapult + recovery area |
| 11. Cumulative fatigue | Motor/ESC wear from repeated hover cycles; boom attachment fatigue | Parachute landing shock absorbed by airframe; minimal fatigue |
## Component 3: Battery Technology Factual basis: Facts #36-51
| Dimension | Semi-Solid State | Li-Ion (21700/18650) | LiPo |
|-----------|-----------------|---------------------|------|
| Energy density (Wh/kg) | 300-350 (pack: 310) | 200-250 | 150-200 |
| Cycle life | 800-1200 | 500-800 | 200-500 |
| Peak discharge (C) | 10C | 3-5C | 25-50C |
| Continuous discharge (C) | 3-5C | 1-3C | 5-10C |
| Operating temp | -20°C to 60°C | -20°C to 60°C | 0°C to 50°C |
| Safety (thermal runaway) | Very low risk | Low risk | Medium risk |
| Cost per Wh | ~$0.50-0.80 | ~$0.20-0.35 | ~$0.15-0.25 |
| Availability | Commercial (Tattu, Grepow) | Widely available | Widely available |
| Endurance impact (same weight) | Baseline (best) | -20 to -30% | -40 to -50% |
| Factual Basis | Fact #5-8, Source #17, #20 | Source #17 | Source #17 |
## Component 4: Foam Core Selection (for sandwich construction)
| Dimension | Rohacell (PMI) | XPS | PVC (Divinycell) | EPS |
|-----------|---------------|-----|-------------------|-----|
| Density (kg/m³) | 32-110 | 25-45 | 40-250 | 15-30 |
| Compressive strength | Highest | Moderate (200-500 kPa) | High | Lowest |
| Temp resistance | High (180°C+) | Low (75°C) | Moderate (80°C) | Low (70°C) |
| Moisture absorption | Very low | Low | Low | Medium |
| Cost | Very high | Low | Medium | Very low |
| Best for | High-performance wings | Budget wings | General-purpose | Prototypes only |
| Factual Basis | Source #16 | Source #16 | Source #16 | Fact #4 |
@@ -1,115 +1,305 @@
# Reasoning Chain # Reasoning Chain — Draft 05 (Reliability: VTOL vs Catapult+Parachute)
## Dimension 1: Frame Material Selection ## Dimension 1: VTOL Motor/ESC Failure During Hover
### Fact Confirmation ### Fact Confirmation
CFRP (T700) has density 1.55-1.60 g/cm³ with specific stiffness of 113 (Fact #1, #2). This is 40-50% lighter than aluminum for equivalent stiffness. Fiberglass at 2.46-2.58 g/cm³ offers only 5-10% weight savings over aluminum. The DeltaQuad Evo (Source #13) uses a hybrid of fiberglass, carbon, and Kevlar — achieving 4.8 kg empty weight at 269 cm wingspan. - Quad VTOL has 8 active electronic components during hover: 4 motors + 4 ESCs (Fact #37, #38)
- ESC desync is "the most common issue faced by drone pilots" (Fact #37)
- Causes relevant to VTOL hover: sudden throttle changes (transition in/out of hover), high current draw (~25-30A per motor at hover), voltage sag from high-draw VTOL battery
- Each motor runs at ~1,000-1,125W during hover of 20 kg aircraft — near operational limits (Fact #41)
- Brushless motors themselves: 10,000-20,000 hours ideal, 1,500-3,000h real (Fact #36)
- No formal MTBF data published by any drone motor manufacturer (Fact #36)
### Reference Comparison ### Analysis
The Albatross UAV uses fiberglass + carbon fiber hybrid and achieves 3.35 kg bare airframe at similar wingspan (~3m). The DeltaQuad uses a tri-material hybrid at 4.8 kg empty (but includes VTOL motors and mounting). Pure CFRP frames like the SUX61 achieve 3.4 kg (Fact #11) at larger scale. VTOL hover is the highest-stress phase for the propulsion system:
- High current draw per motor (near max continuous rating)
- Rapid throttle changes during transition (trigger for ESC desync)
- All 4 motors must work simultaneously — failure of any one degrades control
- Hover phase is short (~75-120s per sortie) but failure during this window is catastrophic
Probability estimation (qualitative):
- Motor bearing failure during single sortie hover (~100s): Very Low — bearings fail over 1000s of hours, not seconds
- ESC desync during hover: Low but non-negligible — desync is triggered by sudden throttle changes and voltage sag, both present during VTOL transitions
- ESC burnout during hover: Very Low per sortie — burnout is cumulative
- Overall motor/ESC failure during single hover phase: **Low** (estimated 1 in 500-2,000 sorties for a well-maintained system)
Over the lifetime of 5 UAVs doing ~300 sorties each (1,500 total sorties):
- Expected motor/ESC incidents: 1-3 over fleet lifetime
- Each incident during hover = potential aircraft loss ($15-17k)
### Conclusion ### Conclusion
**Primary CFRP (T700) with selective Kevlar reinforcement at impact zones** is optimal. The weight savings from CFRP directly translate to larger battery budget. T700 is preferred over T800 due to better impact tolerance and 44% lower cost at nearly identical density (Source #14). Kevlar layers at landing gear mounts and belly add crash protection without significant weight penalty (~100-200g). VTOL motor/ESC failure during hover is a **low-probability but high-consequence** event. The dominant risk is ESC desync during VTOL-to-cruise or cruise-to-VTOL transitions, not steady-state motor failure. Over a fleet lifetime of 1,500 sorties, 1-3 motor/ESC-related incidents are plausible. Each incident during low-altitude hover is likely fatal for the aircraft.
### Confidence ### Confidence
✅ High — supported by multiple L1/L2 sources and confirmed by benchmark platforms. ⚠️ Medium — no quantitative failure rate data exists; estimate derived from qualitative industry assessment
--- ---
## Dimension 2: Construction Method ## Dimension 2: Quad Single-Motor-Out Survivability
### Fact Confirmation ### Fact Confirmation
Foam-core sandwich construction with CFRP skins achieves 30.5% wing weight reduction vs solid composite (Fact #4). Vacuum infusion produces 71% higher compressive strength than hand layup and 53% higher than vacuum bagging (Source #15). Prepreg achieves <0.5% void content but at higher cost. - Quad (4+1) provides 260% thrust margin in hover (Y37 reference) (Fact #21)
- 3 remaining motors provide ~195% thrust margin — sufficient for controlled descent (Fact #42)
- ArduPilot does NOT have built-in single VTOL motor failure compensation for quadplane (Fact #38)
- In copter mode, single motor loss survival demonstrated at altitude by sacrificing yaw control (Fact #39)
- During takeoff/landing at < 10m altitude, reaction time is < 2 seconds (Fact #42)
- DeltaQuad max hover time: 90 seconds (Fact #41)
### Reference Comparison ### Analysis
Industry benchmark platforms (Albatross, DeltaQuad) use composite sandwich construction. Academic research confirms sandwich panels with foam cores provide the highest stiffness-to-weight ratio for wing structures. Monocoque is preferred for fuselage sections where torsional loads dominate. At altitude (> 30m): single motor out on quad VTOL is survivable in theory. Three motors have enough thrust (195% margin), and the aircraft can sacrifice yaw control to maintain attitude and perform controlled descent.
At low altitude (< 10m, i.e., during takeoff or final landing approach):
- Time to react and compensate: < 2 seconds
- Autopilot has no built-in motor-out detection for VTOL phase
- Even with sufficient thrust, the transient — loss of one motor's torque contribution — causes immediate yaw rotation and attitude disturbance
- At 5m altitude with 2 seconds to impact: recovery requires instant thrust redistribution that ArduPilot quadplane firmware does not currently implement
Critical window analysis:
- Takeoff: 0-30m, ~30-45 seconds — HIGH RISK zone for first 10m (~10-15 seconds)
- Landing: 30-0m, ~20-30 seconds — HIGH RISK zone for last 10m (~10-15 seconds)
- Total high-risk time per sortie: ~20-30 seconds (out of ~100s total hover)
### Conclusion ### Conclusion
**Sandwich construction (foam core + CFRP skin) for wings; monocoque for fuselage** is the optimal hybrid approach. Vacuum infusion is the recommended manufacturing process — best quality-to-cost ratio. Prepreg with autoclave cure would deliver superior results but requires expensive tooling; not justified for prototype phase. Quad VTOL single-motor-out is **theoretically survivable at altitude** (> 30m) due to 195% thrust margin on 3 motors. However, it is **likely fatal below 10m altitude** due to insufficient reaction time and lack of firmware support. Approximately 20-30% of total hover time is in this high-risk low-altitude zone. The quad configuration improves survival odds significantly over Y-3 (which has zero motor redundancy), but does not eliminate the risk.
### Confidence ### Confidence
✅ High — well-established in aerospace, confirmed by peer-reviewed research. ⚠️ Medium — physics-based analysis with firmware limitation confirmed, but no flight test validation on this specific platform
--- ---
## Dimension 3: Foam Core Selection ## Dimension 3: Parachute Landing Impact on Airframe
### Fact Confirmation ### Fact Confirmation
Rohacell PMI has highest stiffness-to-weight and withstands autoclave temps (180°C+). XPS offers good closed-cell structure at low cost. PVC (Divinycell) is the industry standard middle ground. EPS is cheapest but has lowest strength and absorbs moisture (Source #16). - Parachute descent: 4.6 m/s, 18 kg → KE = 190 J (Fact #43)
- Equivalent to 1.08m drop height (Fact #43)
- Energy transfer is ~20% of theoretical KE due to airframe deformation → ~38 J effective (Fact #43)
- Parachute reduced impact by 4× vs belly landing in Aludra tests (Fact #50)
- S2 FG sandwich construction has good impact tolerance (Fact #31 from Draft 04)
- Fixed-wing hangs nose-down under parachute; belly-first with repositioning (Fact #44)
### Reference Comparison ### Analysis
For a UAV operating in -10°C to 45°C, thermal resistance beyond 80°C is sufficient (no autoclave required if using vacuum infusion). XPS and PVC both meet this requirement. Rohacell's premium is justified only for mass-produced military/aerospace where grams matter at scale. Impact severity at 4.6 m/s, 18 kg:
- 190 J total KE — moderate for a foam-core fiberglass sandwich airframe
- S2 FG sandwich absorbs impact through foam core compression and skin flexing
- Effective transmitted energy ~38 J (after deformation absorption) — well within S2 FG survivable range
- For comparison: static load test target is 3g (Draft 03) = 529 N static vs ~190 J dynamic
Landing attitude matters:
- Nose-down (default parachute hanging): nose, propeller housing absorb impact first. Belly-mounted gimbal may be protected if fuselage absorbs first contact.
- Belly-first (with repositioning harness): belly contacts first. Good for airframe but belly-mounted gimbal takes direct impact.
- Horizontal/random attitude possible with wind gusts
Cumulative damage over 100+ parachute landings:
- S2 FG belly skin will develop micro-cracks and compression damage in foam core
- Replaceable belly panel or sacrificial belly skid plate mitigates this
- Wing attachment points stressed by parachute deceleration — Y-harness distributes load
Post-landing parachute drag:
- In wind, parachute continues pulling after touchdown → drags UAV across ground
- This can cause more damage than the initial impact (abrasion to skin, snapping of protruding components)
- Mitigation: parachute release mechanism or wind-side landing approach
### Conclusion ### Conclusion
**PVC (Divinycell H-series) for wing cores** — best balance of stiffness, moisture resistance, and cost for prototype phase. XPS as budget alternative if cost optimization needed. Rohacell only justified if transitioning to production where marginal weight savings compound. Parachute landing at 4.6 m/s is **low-risk for the S2 FG airframe**. The 190 J impact energy is well within the structural capability of fiberglass sandwich construction. The main risks are: (1) post-landing drag in wind causing abrasion, (2) cumulative micro-damage over many landings, and (3) damage to protruding components (gimbal, antennas). A replaceable belly panel and automatic parachute release can mitigate most risks.
### Confidence ### Confidence
✅ High — PVC foam cores are industry standard for composite UAV wings. ✅ High — physics well-understood, S2 FG impact tolerance established in Draft 03
--- ---
## Dimension 4: Battery Technology ## Dimension 4: Camera/Gimbal Vulnerability During Parachute Landing
### Fact Confirmation ### Fact Confirmation
Semi-solid state batteries achieve 300-350 Wh/kg at cell level, ~310 Wh/kg at pack level (Fact #5, Source #20). Tattu 330Wh/kg 6S 33000mAh pack: 2324g weight, 732.6 Wh energy (Source #20). LiPo: 150-200 Wh/kg. Li-Ion: 200-250 Wh/kg. Semi-solid cycle life 800-1200 vs LiPo 200-500 (Fact #8, Source #17). - Viewpro Z40K: CNC aluminum housing, ±0.02° vibration, no shock/impact G-force rating (Fact #45)
- Gimbal designed for aerial vibration, NOT landing impacts (Fact #45)
- If belly-mounted and protruding below fuselage: FIRST contact point during belly-first landing (Fact #44)
- If nose-down landing attitude: fuselage nose absorbs first contact; belly gimbal somewhat protected
- Retractable gimbal mechanisms exist (AeroVironment patent, ArduPilot landing gear retraction) (Fact #46)
- Too-large parachute causes post-landing dragging, abrading cameras/gimbals (Fact #36 source)
### Endurance Estimate ### Analysis
Reference: Albatross at 10 kg MTOW, ~3 kg LiPo (~180 Wh/kg = 540 Wh), gets 4 hours → cruise power ~135W.
With semi-solid (same 3 kg at 310 Wh/kg = 930 Wh): **Scenario A — Belly-mounted gimbal, belly-first landing attitude:**
Endurance = 930 Wh / 135 W ≈ 6.9 hours - Gimbal is the lowest point of the aircraft → direct ground contact
- Even at 38 J effective impact energy, concentrated on the gimbal's CNC aluminum housing = risk of lens damage, gimbal arm bending, sensor misalignment
- Repeated parachute landings will progressively damage the gimbal
- **Risk: HIGH** — this configuration is incompatible with parachute recovery without protection
With optimized lighter airframe (saving 0.5 kg → extra battery weight): **Scenario B — Belly-mounted gimbal, nose-down landing attitude:**
3.5 kg semi-solid at 310 Wh/kg = 1085 Wh - Fuselage nose contacts ground first; gimbal is behind/below and may not touch ground
Endurance = 1085 / 135 ≈ 8.0 hours - Depends on exact attitude angle and terrain unevenness
- If aircraft tips after nose impact, gimbal may still contact ground
- **Risk: MEDIUM** — depends on terrain and exact dynamics
The DeltaQuad Evo achieved 8h55m with solid-state batteries at 10 kg MTOW — validating the 6-8 hour range estimate for semi-solid + optimized airframe. **Scenario C — Belly-mounted gimbal with retractable mount:**
- Gimbal retracts into fuselage cavity before parachute deployment
- ArduPilot triggers retraction automatically on landing sequence
- Adds ~100-200g mechanism weight and mechanical complexity
- **Risk: LOW** — gimbal protected inside fuselage during landing
**Scenario D — Side-mounted or top-mounted gimbal:**
- Gimbal not on belly → not a contact point during belly or nose landing
- But: field of view may be restricted; typical reconnaissance gimbals are belly-mounted
- **Risk: LOW** — but may compromise camera field of view
**Scenario E — Internal turret with protective window:**
- Gimbal inside fuselage, views through transparent window/dome in belly
- Adds window (glass/sapphire), reduces optical quality slightly
- Fully protected during landing
- **Risk: VERY LOW** — but adds cost and weight
### Key Insight
The user is correct — **the risk depends entirely on the actual camera design and position**. A belly-mounted protruding gimbal like the Viewpro Z40K is highly vulnerable to parachute landing. But this is a solvable engineering problem with multiple design options.
### Conclusion ### Conclusion
**Semi-solid state batteries are the clear choice** for maximizing endurance. The Tattu 330 Wh/kg 6S or 12S packs are the most accessible commercial option. Expected endurance: 5-8 hours depending on airframe optimization and battery configuration. Cost premium (~2-3x LiPo per Wh) is offset by 4-6x cycle life and 30-50% more energy per kg. Belly-mounted protruding gimbal + parachute recovery is a **problematic combination** without mitigation. The recommended solutions (in order of preference):
1. **Retractable gimbal mount** — retracts before parachute deployment (adds ~150g, $100-200)
2. **Nose-down parachute attitude** — default Y-harness at CG provides this naturally
3. **Sacrificial bumper/guard** around gimbal — absorbs impact if ground contact occurs
4. **Internal turret** — best protection but limits camera selection
For VTOL variant: camera damage risk per landing is **near-zero** because VTOL provides precision soft landing with no ground contact forces.
### Confidence ### Confidence
✅ High — validated by DeltaQuad Evo real-world results and multiple manufacturer specifications. ✅ High — engineering analysis with multiple validated design solutions
--- ---
## Dimension 5: Cost Analysis ## Dimension 5: Parachute Deployment Reliability
### Fact Confirmation ### Fact Confirmation
Carbon fiber T700: ~$18/m². Custom composite airframe prototyping services available globally (Source #19). Tattu semi-solid batteries: ~$500-1500 per pack (estimated from capacity/chemistry). Total system costs for this class: $30-60k for first prototype. - Pilot chute → main chute deployment in < 3 seconds (Aludra SR-10 test) (Fact #47)
- Dual triggers: autopilot + RC manual (Fact #47)
- Spring-loaded hatch is simple mechanical mechanism (Fact #47)
- Iris Ultra dome chutes with Spectra shroud lines — mature technology (Fact #47)
- DRS-25 system works even if all electronics fail (Fact #37 source)
- No quantitative failure rate data for UAV parachute deployment (research gap)
### Budget Breakdown (estimated for $100k) ### Analysis
Parachute deployment failure modes:
1. **Hatch fails to open**: spring-loaded hatch with servo release. Mitigation: redundant release (servo + mechanical). Probability: Very Low.
2. **Pilot chute fails to catch airflow**: requires sufficient forward airspeed. If deployed during stall or vertical descent, risk increases. Mitigation: deploy in forward flight before deceleration. Probability: Very Low in forward flight.
3. **Main chute tangled or fails to inflate**: most common parachute failure mode. Mitigation: proper packing, deployment bag, pilot chute extraction. Fruity Chutes Iris Ultra has proven track record. Probability: Very Low with proper maintenance.
4. **Lines tangled with aircraft structure**: protruding components can snag lines. Mitigation: clean exterior, dedicated deployment channel. Probability: Low.
5. **Parachute too small for actual weight**: sizing error. Mitigation: verify against MTOW. Probability: Negligible.
| Item | Estimated Cost | Overall deployment reliability: estimated **>99%** (1 failure per 100+ deployments) with proper packing and maintenance. Skydiving parachutes achieve >99.9% reliability; UAV parachutes are simpler (no human maneuvers) but also have less rigorous packing/inspection standards.
|------|---------------|
| Airframe design + engineering | $10,000-15,000 | Parachute repack between sorties: 5-10 minutes by trained operator. Operator error in repacking is the dominant failure mode.
| Composite tooling + molds | $5,000-10,000 |
| Materials (CF, foam, resin) | $3,000-5,000 |
| Airframe manufacturing (outsourced) | $5,000-10,000 |
| Motor, ESC, propeller | $1,000-2,000 |
| Semi-solid batteries (2-3 packs) | $2,000-4,000 |
| Avionics (Pixhawk 6x, GPS, telemetry) | Already owned |
| Payload (camera, gimbal, Jetson) | Already owned |
| Ground station + data link | $5,000-10,000 |
| Integration + testing | $10,000-15,000 |
| Contingency (~20%) | $10,000-15,000 |
| **Total** | **$51,000-86,000** |
### Conclusion ### Conclusion
$100k budget is sufficient with margin. CFRP airframe outsourcing is the most cost-effective path — avoids $50-100k investment in autoclave/clean-room equipment. Parachute deployment reliability is **very high** (>99%) when properly maintained and packed. The dominant risk factor is operator error during repacking, not the parachute system itself. Dual trigger mechanisms (autopilot + manual RC) provide redundancy against electronic trigger failure. The system's passive nature (no electronics needed for the fabric + lines) is a fundamental reliability advantage over VTOL.
### Confidence ### Confidence
⚠️ Medium — cost estimates based on industry ranges; actual quotes needed from manufacturers. ⚠️ Medium — no quantitative UAV parachute failure data available; estimate based on parachute engineering principles and skydiving industry data
--- ---
## Dimension 6: Carbon Fiber Grade Selection ## Dimension 6: Catapult System Reliability
### Fact Confirmation ### Fact Confirmation
T700: tensile 4900 MPa, modulus 230 GPa, ~$18/m², better impact tolerance. T800: tensile 5880 MPa, modulus 294 GPa, ~$26/m², 44% cost premium, more brittle (Source #14). Density is nearly identical (~1.80 vs ~1.81 g/cm³). - ScanEagle: 1,500 safe recoveries, 150,000+ service hours — catapult system proven (Fact #48)
- ELI PL-60: simple pneumatic system, Makita 18V battery powered (Fact #28 from Draft 04)
- < 5% velocity variance for well-maintained catapults (Fact #49)
- IP65 sealing, precision rails, vibration damping critical (Fact #49)
- Robonic: annual maintenance 4-5% of acquisition cost (Fact #49)
- Failure modes: seal degradation, pressure loss, carriage jamming — all mechanical, all inspectable (Fact #49)
### Analysis
Catapult failure modes:
1. **Seal degradation → pressure loss**: gradual, detectable in pre-flight check. Probability per sortie: Very Low.
2. **Carriage jamming**: mechanical, detectable in pre-launch test. Probability: Very Low.
3. **Battery depletion**: Makita 18V battery — carry spares. Probability: Negligible.
4. **Rail misalignment**: caused by transport damage. Pre-launch alignment check. Probability: Very Low.
5. **Complete catapult failure**: if catapult is inoperable, ENTIRE FLEET IS GROUNDED. This is the key SPOF.
ScanEagle's 150,000+ hours on catapult+recovery provides strong evidence that pneumatic catapult systems are reliable in field conditions. The ELI PL-60 is simpler (no SkyHook, no rocket assist) — fewer failure modes.
Key difference from VTOL: catapult failure prevents launch (no aircraft loss), while VTOL motor failure during hover can cause aircraft loss. Catapult failure is a **mission failure**, VTOL motor failure is a **vehicle loss**.
### Conclusion ### Conclusion
**T700 for all primary structure.** The 44% cost premium of T800 buys 15-20% more strength and 28% more stiffness, but T700 already exceeds structural requirements for this MTOW class. T800's brittleness is a liability for a UAV that may experience hard landings. T800 only justified for specific high-load areas (wing root spar caps) if FEA shows need. Pneumatic catapult systems have **very high reliability** (proven by ScanEagle's 150,000+ hours). Failure modes are mechanical, inspectable, and repairable in the field. The critical weakness is single-point-of-failure: if the catapult breaks, no aircraft can launch until it's repaired. This is mitigated by carrying spare seals and having a backup launch method (hand launch for lighter config, or carrying a second catapult for critical operations).
### Confidence ### Confidence
✅ High — standard industry recommendation for UAV class. ✅ High — ScanEagle provides strong L2 evidence for catapult reliability in military operations
---
## Dimension 7: Cumulative Wear and Fatigue
### Fact Confirmation
- DeltaQuad: full VTOL arm/motor replacement every 12 months (Fact #40)
- VTOL motors run at ~1,000W per hover cycle (100s) — high thermal stress (Fact #41)
- Motor bearing wear correlates with total rotations (Fact #36)
- Parachute landing: 190 J per landing on S2 FG airframe (Fact #43)
- Parachute dragging risk after landing in wind (Fact #36 source)
### Analysis
**VTOL cumulative wear (over 300 sorties/year/aircraft):**
- Total hover time: ~300 × 100s = 30,000 seconds = 8.3 hours of high-power hover per year per aircraft
- At ~8,000 RPM, each motor completes: 8,000 × 500 min = 4,000,000 revolutions/year (rough estimate)
- Motor bearings: well within 10,000-hour lifespan for this duty cycle
- ESC thermal cycling: 300 high-current cycles/year — modest but non-trivial
- Boom attachment points: 300 thrust cycles → fatigue risk if not properly designed
- DeltaQuad replaces VTOL assemblies annually — conservative but appropriate schedule
**Parachute landing cumulative wear (over 300 sorties/year/aircraft):**
- Total impact energy absorbed: 300 × 190 J = 57,000 J/year
- S2 FG belly: repeated 1m-equivalent drops → progressive foam core compression, micro-cracking
- Parachute harness attachment points: 300 × shock load → fatigue in mounting hardware
- Belly-mounted components: cumulative abrasion from occasional ground contact or dragging
- Mitigation: replaceable belly panel (swap every 50-100 landings), inspect harness mounts
### Conclusion
Both systems accumulate wear, but in different ways. VTOL wear is in **electronics and mechanical joints** (motors, ESCs, boom attachments) — hard to inspect, failure can be sudden and catastrophic. Parachute landing wear is in **airframe structure** (belly skin, foam core, harness mounts) — visible, inspectable, and repairable. VTOL requires **annual component replacement** (DeltaQuad model). Parachute recovery requires **periodic belly panel replacement** and harness mount inspection.
### Confidence
⚠️ Medium — DeltaQuad maintenance data provides VTOL baseline; parachute landing fatigue estimate is engineering judgment
---
## Dimension 8: Overall Reliability Comparison
### Fact Confirmation
All facts from Dimensions 1-7.
### Analysis
**Failure mode comparison matrix:**
| Failure Mode | VTOL | Catapult+Parachute | Consequence |
|--------------|------|-------------------|-------------|
| Motor/ESC failure during hover | Low prob, HIGH impact | N/A | Aircraft loss ($17k) |
| Motor/ESC failure during cruise | Same for both (cruise motor) | Same for both | Emergency landing / parachute deploy |
| Parachute non-deployment | N/A | Very Low prob, HIGH impact | Aircraft loss ($17k) |
| Catapult failure | N/A | Very Low prob, LOW impact | Mission abort (no aircraft loss) |
| Camera damage per landing | Near-zero | Medium (design-dependent) | $3,000-5,000 repair |
| Airframe damage per landing | Near-zero | Low | $200-500 belly panel |
| Post-landing drag damage | N/A | Low-Medium (wind) | $500-3,000 |
| Landing in hazardous terrain | Near-zero (precision) | Medium (50-200m drift) | Aircraft recovery difficulty |
**Risk scoring (5 UAVs, 1,500 sorties fleet lifetime):**
VTOL:
- Expected motor/ESC incidents: 1-3 (at $17k each = $17k-51k)
- Expected camera damage: ~0
- Expected airframe damage: ~0
- **Total expected loss: $17k-51k** over fleet lifetime
Catapult+Parachute:
- Expected parachute non-deploy: 0-1 (at $17k = $0-17k)
- Expected camera damage incidents: 5-15 (depends on protection design; at $500-3,000 each = $2,500-45,000)
- Expected belly panel replacements: 15-30 (at $200-500 each = $3,000-15,000)
- **Total expected loss: $5,500-77,000** (wide range due to camera protection design dependency)
With proper camera protection (retractable gimbal):
- Camera damage incidents drop to 0-2 → expected loss: $3,000-21,000
### Conclusion
**Without camera protection**, catapult+parachute has comparable or worse total cost of damage than VTOL due to camera/gimbal damage. **With camera protection** (retractable gimbal or internal turret), catapult+parachute has **better overall reliability** — lower probability of catastrophic aircraft loss, with manageable minor damage. The critical differentiator: VTOL failure during hover can destroy the aircraft, while parachute failure modes mostly cause repairable damage (except the rare non-deployment scenario).
The user's concern about VTOL motor failure is **well-founded** — it's the dominant risk in the VTOL variant. The concern about parachute landing camera damage is also **well-founded** but is **solvable** through design (retractable gimbal, landing attitude control, sacrificial bumpers).
### Confidence
⚠️ Medium — risk quantification is estimated, not based on actuarial data
@@ -1,43 +1,106 @@
# Validation Log # Validation Log — Draft 05 (Reliability)
## Validation Scenario ## Validation Scenario 1: VTOL Motor Failure During Landing — 300th Sortie
A fixed-wing reconnaissance UAV with 1.47 kg payload, targeting maximum endurance within 10 kg MTOW and $100k budget.
Design: CFRP (T700) sandwich construction with PVC foam cores, powered by semi-solid state batteries (Tattu 330 Wh/kg). ### Scenario
UAV #3 is on its 300th mission (1 year of operations). Returning from 7-hour recon sortie. Begins VTOL transition at 80m AGL. During final descent at 8m altitude, rear-left ESC desyncs due to voltage sag from partially degraded VTOL battery.
## Expected Based on Conclusions ### Expected Based on Conclusions
- ESC desync causes rear-left motor to stall instantly
- Aircraft experiences sudden yaw rotation and loss of ~25% thrust
- At 8m altitude: ~1.6 seconds to ground impact
- ArduPilot has no automatic motor-out compensation for quadplane VTOL
- 3 remaining motors have 195% thrust margin — sufficient thrust exists but no firmware to redistribute
- Aircraft will enter uncontrolled descent with yaw spin
- Ground impact at ~3-5 m/s descent + lateral velocity from yaw spin
- **Likely outcome: aircraft damaged or destroyed**
- Gimbal camera destroyed on impact: $3,000-5,000 loss
- Total loss: ~$17,000 (aircraft) + crew time + mission data at risk
**Airframe weight**: 3.0-3.5 kg bare (based on Albatross benchmark at 3.35 kg with fiberglass+CF; pure CFRP should be lighter) ### Actual Validation
DeltaQuad's maintenance schedule (annual motor/arm replacement) suggests this is a recognized wear pattern. The 12-month replacement interval implies components approach end-of-life reliability around 300-500 sorties. No published incident data from DeltaQuad to validate specific motor-out scenarios.
**Battery allocation**: 3.0-4.0 kg (target 3.5 kg semi-solid at ~310 Wh/kg pack = ~1085 Wh) ArduPilot community forums report ESC desync incidents during VTOL operations, particularly during transitions. The Q_TRANS_FAIL timer was added specifically to handle transition failures, confirming this is a real operational concern.
**Total weight**: 3.2 (airframe+avionics+motor) + 1.47 (payload) + 3.5 (battery) = 8.17 kg — under 10 kg MTOW with margin ### Issues Found
- No firmware-level motor failure compensation for quadplane VTOL phase is a significant gap
- VTOL battery degradation over ~300 charge cycles increases voltage sag → increases ESC desync risk
- The 12-month maintenance interval (DeltaQuad) is probably conservative, but in a conflict zone with high sortie rates, components may wear faster
**Cruise power**: ~120-140 W (based on Albatross reference at ~135W for similar MTOW/speed) ---
**Endurance**: 1085 Wh / 135 W ≈ 8.0 hours ## Validation Scenario 2: Parachute Landing Damages Camera — Wind Day
**Cost**: $50-85k total (within $100k budget) ### Scenario
UAV #2 returns from 8-hour mission. Deploys parachute at 100m AGL. Wind is 8 m/s (moderate). Descent takes 22 seconds. Horizontal drift: 176m from intended landing point. UAV lands belly-first in plowed field with Viewpro Z40K gimbal protruding 8cm below fuselage.
## Actual Validation Results ### Expected Based on Conclusions
Cross-checked against DeltaQuad Evo: 4.8 kg empty, 10 kg MTOW, 22 Ah × 22.2V × 2 = ~978 Wh, achieved 4h32m (standard) and 8h55m (solid-state record). Our lighter payload (1.47 kg vs 3 kg) and similar battery energy put us in the 6-8 hour range — consistent with DeltaQuad data. - Descent velocity: 4.6 m/s vertical + 8 m/s horizontal = 9.2 m/s resultant
- Impact energy: 0.5 × 18 × 9.2² = 762 J (significantly more than calm-wind 190 J)
- Horizontal velocity component means aircraft slides/tumbles after touchdown
- Belly-mounted gimbal contacts ground: concentrated impact on CNC aluminum housing
- **Likely outcome: gimbal lens cracked, gimbal arm bent, possible sensor misalignment**
- Camera repair/replacement: $3,000-5,000
- Airframe: belly skin abraded from sliding, minor foam core compression
- Airframe repair: $200-500 (belly panel replacement)
Albatross validation: 3.35 kg airframe, 10 kg MTOW, 4 hours with LiPo. Semi-solid upgrade alone (same airframe) would yield ~6.9 hours. With optimized CFRP airframe saving ~0.5 kg → additional battery weight → ~8 hours. ### With Retractable Gimbal Protection
- Gimbal retracted into fuselage cavity before parachute deployment
- Fuselage belly absorbs impact — S2 FG handles 762 J via skin+foam deformation
- Belly skin damage: moderate (sliding abrasion in field)
- Camera: **undamaged** — protected inside fuselage
- **Outcome: belly panel replacement only ($200-500)**
## Counterexamples ### Actual Validation
1. **Wind/turbulence**: Real-world endurance is typically 70-80% of theoretical due to wind, maneuvers, and non-optimal cruise segments. Realistic expectation: 5-6 hours practical endurance. Fruity Chutes documentation explicitly warns that too-large parachutes cause "abrasion damage to cameras, gimbals, and other components from dirt, rocks, and debris" during post-landing drag. This confirms that exposed gimbal cameras ARE at risk during parachute recovery. The warning specifically mentions gimbals.
2. **Battery degradation**: Semi-solid batteries lose capacity over cycles; after 500 cycles at 90% retention, endurance drops to ~5.4 hours.
3. **Payload power draw**: Jetson Orin Nano Super draws ~15-25W, camera/gimbal ~10-15W. Total payload power: ~25-40W. This must be added to cruise power → total system power ~160-175W, reducing endurance to ~6.2-6.8 hours theoretical, ~5-5.5 hours practical. Wind-induced horizontal velocity during parachute descent is a well-understood problem in military operations. ScanEagle's SkyHook system was developed specifically to avoid this problem (precision catch instead of uncontrolled parachute landing).
### Issues Found
- Wind significantly increases impact energy (190 J calm → 762 J at 8 m/s wind)
- Horizontal velocity component causes sliding/tumbling — much more damaging than vertical drop alone
- Post-landing drag is potentially MORE damaging than initial impact (continuous abrasion)
- The user's concern about camera damage is STRONGLY validated by both physics and manufacturer warnings
- Retractable gimbal solves the camera problem but belly skin damage remains
---
## Validation Scenario 3: Catapult Malfunction — Second Day of Operations
### Scenario
Day 2 of deployment. Catapult was transported 200km on rough roads. Pressure seal on pneumatic cylinder has developed a slow leak.
### Expected Based on Conclusions
- Pre-launch pressure check reveals low pressure (fails to reach 10 bar target)
- **No aircraft risk** — malfunction detected before launch
- Mission delayed while crew replaces seal (15-30 min with spare parts kit)
- If no spare seal available: mission aborted until repair
- **Fleet grounded** if catapult is the only launch method
### Actual Validation
ELI PL-60 is battery-operated (Makita 18V) with simple pneumatic system. Seal replacement is a standard field maintenance task for pneumatic systems. Carrying spare seals and O-rings (< 100g, $20) eliminates this single point of failure.
ScanEagle operations carry field repair kits for their SuperWedge catapult. This is standard operating procedure for catapult-based military UAV systems.
### Issues Found
- Catapult SPOF is real but mitigatable with spare parts
- Transport vibration can accelerate seal wear — important for rough-terrain deployment
- Unlike VTOL motor failure (which risks aircraft loss), catapult failure only delays missions
---
## Review Checklist ## Review Checklist
- [x] Draft conclusions consistent with fact cards - [x] Draft conclusions consistent with fact cards
- [x] No important dimensions missed - [x] No important dimensions missed
- [x] No over-extrapolation - [x] No over-extrapolation
- [x] Conclusions actionable/verifiable - [x] Conclusions actionable/verifiable
- [x] Payload power consumption accounted for (see counterexample #3) - [x] Wind scenario reveals significantly higher parachute landing damage than calm-air analysis
- [x] User concerns about VTOL motor failure validated
- [x] User concerns about parachute camera damage validated
- [x] Camera protection solutions identified and practical
- [ ] ⚠️ No quantitative motor/ESC failure rate data — all probability estimates are qualitative
## Conclusions Requiring Revision ## Conclusions Requiring Revision
Endurance estimate revised downward from 8 hours theoretical to **5-6 hours practical** after accounting for: - Draft 04's risk assessment listed VTOL motor failure as "Low probability" — this needs more nuance: low per sortie but significant over fleet lifetime
- Payload power draw (~30W) - Draft 04 did not address wind-induced horizontal velocity during parachute landing — this significantly increases damage risk (190 J → 762 J at 8 m/s wind)
- Real-world flight efficiency (75%) - Camera protection was not addressed in Draft 04 — must be included as a design requirement for the catapult+parachute variant
- Battery reserve requirements (typically 20% reserve)
@@ -0,0 +1,489 @@
# Solution Draft (Rev 03) — 8+ Hour Endurance
## Assessment Findings
| Old Component Solution | Weak Point | New Solution |
|------------------------|------------|-------------|
| Single 6S 33Ah battery (1001 Wh) | Only 3.5-4.7h endurance — insufficient for 8h target | 4× 6S 33Ah 350 Wh/kg packs (2930 Wh) or 2× 12S 33Ah (2930 Wh) |
| 10 kg MTOW | Cannot carry enough battery for 8h at current energy densities | Increase to 18 kg MTOW |
| 3.0m wingspan | L/D ≈ 15 at AR≈10; higher wing loading increases cruise power | Scale to 3.8-4.0m wingspan (AR≈14, L/D≈17) |
| S2 FG airframe (3m) | Good but limited battery capacity due to MTOW constraint | S2 FG airframe scaled to 4m; same material, radio transparency preserved |
| Motor + ESC (500W class) | Undersized for 18 kg platform | Scale to 700-800W motor + 60-80A ESC |
| ADTI 20L V1 nav camera (20MP APS-C) | 34 cm/px GSD at 2 km — too coarse for feature matching | ADTI 26S V1 (26MP APS-C, mech. shutter) + 35mm lens → 21.6 cm/px at 2 km |
| Viewpro A40 Pro AI camera (1080p, 40×) | 1080p limits FoV to 65×37m at max zoom from 2 km | Viewpro Z40K (4K, 20×) → 2.7 cm/px GSD, 103×58m FoV, 479g lighter |
## Product Solution Description
A scaled-up modular, radio-transparent electric fixed-wing reconnaissance UAV built with **S2 fiberglass/foam-core sandwich construction** and internal carbon fiber spar reinforcement. Wingspan increased to **3.8-4.0m** for better aerodynamic efficiency (L/D ≈ 17). MTOW raised to **18 kg** to accommodate **4× semi-solid battery packs** totaling ~2930 Wh. Disassembles into modular sections for pickup truck transport; 2 complete aircraft fit in a standard 6.5ft bed.
**Target performance**: 8-9 hours practical flight endurance, 18 kg MTOW, 3.8-4.0m wingspan. Camera payload: ADTI 26S V1 (26MP, mech. shutter, 21.6 cm/px at 2 km) for GPS-denied navigation + Viewpro Z40K (4K, 20× zoom, 2.7 cm/px at 2 km) for AI reconnaissance. Total payload 892g — 578g lighter than Draft 02.
```
┌──────────────────────────────────────────────────────────────────┐
│ SCALED-UP MODULAR AIRFRAME LAYOUT │
│ │
│ LEFT WING PANEL FUSELAGE RIGHT WING PANEL │
│ (~1.9m span) (~1.1m) (~1.9m span) │
│ ┌──────────────┐ ┌──────────────────┐ ┌──────────────┐ │
│ │ S2 FG skin │ │ S2 FG skin │ │ S2 FG skin │ │
│ │ PVC foam core│◄─►│ Battery bay ×4 │◄─►│ PVC foam core│ │
│ │ CF spar cap │ │ Payload bay │ │ CF spar cap │ │
│ │ (internal) │ │ Motor (700W) │ │ (internal) │ │
│ └──────────────┘ └──────────────────┘ └──────────────┘ │
│ │
│ Wing-fuselage joint: aluminum spar joiner + 2 pin locks │
│ Assembly time target: < 10 minutes │
│ Material: S2 fiberglass = RF transparent (GPS/telemetry OK) │
│ Internal CF spar: minimal RF impact (narrow linear element) │
│ │
│ BATTERY BAY (4 packs, 2S2P wiring for 12S 66Ah): │
│ ┌──────┐ ┌──────┐ │
│ │ 6S │ │ 6S │ Series pair A → 12S 33Ah │
│ │ 33Ah │ │ 33Ah │ │
│ └──────┘ └──────┘ │
│ ┌──────┐ ┌──────┐ │
│ │ 6S │ │ 6S │ Series pair B → 12S 33Ah │
│ │ 33Ah │ │ 33Ah │ Pairs A+B in parallel → 12S 66Ah │
│ └──────┘ └──────┘ │
│ Total: 44.4V × 66Ah = 2930 Wh │
└──────────────────────────────────────────────────────────────────┘
TRANSPORT CONFIGURATION (standard pickup truck, 6.5ft bed):
┌───────────────────────────────────────────────┐
│ Truck bed: 198cm × 130cm (between wells) │
│ ┌────────────────────┐ ┌──────────────────┐ │
│ │ Plane 1 wings │ │ Plane 2 wings │ │
│ │ (2 × 190cm long) │ │ (2 × 190cm) │ │
│ │ stacked ~25cm │ │ stacked ~25cm │ │
│ ├────────────────────┤ ├──────────────────┤ │
│ │ Plane 1 fuselage │ │ Plane 2 fuse. │ │
│ │ (~110cm) │ │ (~110cm) │ │
│ └────────────────────┘ └──────────────────┘ │
│ Width per plane: ~35cm × 2 = 70cm │
│ Total width: 70cm × 2 = 140cm > 130cm ⚠️ │
│ → Stack all 4 wings in one pile + 2 fuselages │
│ alongside: 190cm × 70cm + 110cm × 40cm │
│ Total width: ~110cm < 130cm ✓ │
│ Total length: 190cm < 198cm ✓ │
└───────────────────────────────────────────────┘
```
## Existing/Competitor Solutions Analysis
| Platform | MTOW | Endurance | Battery | Wingspan | Material | RF Transparent | Transport | Price |
|----------|------|-----------|---------|----------|----------|---------------|-----------|-------|
| DeltaQuad Evo (standard) | 10 kg | 4h32m | 2× 22Ah semi-solid | 2.69m | CF+Kevlar+FG | Partial | Wing removable | $25,000+ |
| DeltaQuad Evo (record) | ~9 kg | **8h55m** | 2× Tulip Tech 450 Wh/kg | 2.69m | CF+Kevlar+FG | Partial | Wing removable | N/A (prototype batteries) |
| **YUAV Y37** | 17-20 kg | **8.5h** (1 kg payload) | 12S 60Ah semi-solid (~2700 Wh) | 3.7m | Full carbon | ❌ No | 138×55×45 cm | ~$15,000+ est. |
| NOCTUA (H2) | 20-25 kg | **10h** | Hydrogen fuel cell | 5.10m | CFRP | ❌ No | Field-portable | Academic |
| CW-80E (JOUAV) | >25 kg | 10-11h | Large electric | >4m | Composite | Unknown | Vehicle-mounted | $50,000+ |
| Albatross | 10 kg | 4h | LiPo | 3.0m | FG+CF | Partial | Removable wings | $4,800 RTF |
| **Our Draft 03** | **18 kg** | **8-9h target** | **4× 6S 33Ah 330+ Wh/kg** | **3.8-4.0m** | **S2 FG** | **✅ Yes** | **2 in pickup** | **$5,500-7,500** |
**Key insight**: YUAV Y37 proves that 8.5h at 17-20 kg MTOW with 3.7m wingspan and semi-solid batteries is achievable in production. Our design targets similar performance with S2 FG (heavier but radio transparent) offset by slightly longer wingspan for better L/D.
## Architecture
### Component: Frame Material
| Solution | Advantages | Limitations | Cost (per unit) | Fit |
|----------|-----------|-------------|----------------|-----|
| **S2 fiberglass skin + PVC foam core + internal CF spar (recommended)** | RF transparent, good impact tolerance, field repairable, proven at 3m scale | ~25-30% heavier than carbon at 4m scale; requires careful weight management | $600-1,200 materials | ✅ Only option that preserves RF transparency |
| Full carbon fiber (YUAV Y37 approach) | Lightest possible (~4-5 kg bare at 4m), best L/D | Blocks RF — GPS/telemetry degraded | $1,500-3,000 | ❌ Fails radio transparency |
| Carbon-Kevlar hybrid | Good crash survivability, lighter than FG | Partially blocks RF, expensive, hard to machine | $1,200-2,500 | ❌ RF compromise |
| S2 FG with Dyneema (UHMWPE) reinforcement | RF transparent, excellent impact resistance | Dyneema has poor compression strength, complex bonding | $800-1,500 | ⚠️ Complex but possible |
### Component: Wingspan & Aerodynamics
| Solution | L/D | Platform Weight | Endurance Impact | Transport | Fit |
|----------|-----|----------------|-----------------|-----------|-----|
| **3.8m wingspan (recommended for 2-in-pickup)** | ~17 | 6.5-7.5 kg | Baseline | 190cm half-wings fit 198cm bed ✓ | ✅ Best balance |
| 4.0m wingspan | ~17.5 | 7.0-8.0 kg | +3-5% | 200cm > 198cm; needs 3-section wing | ⚠️ Good but transport harder |
| 4.5m wingspan (single UAV transport) | ~18.5 | 8.0-9.5 kg | +8-12% | 225cm half-wings; 1 UAV per pickup | ⚠️ Maximum endurance, 1 plane only |
| 3.0m wingspan (Draft 02) | ~15 | 5.3 kg | Reference (3.5-4.7h) | 150cm easily fits | ❌ Insufficient for 8h |
**Recommendation**: 3.8m wingspan as primary design. Half-wings at 190cm fit within 198cm pickup bed length. AR ≈ 13.6, L/D ≈ 17. Optional detachable wingtips (+20cm per side = 4.2m total) for maximum endurance missions where single-UAV transport is acceptable.
### Component: Battery Configuration
| Solution | Total Energy | Weight | Wiring | Cost | Endurance (18 kg) | Fit |
|----------|-------------|--------|--------|------|-------------------|-----|
| **4× Tattu 6S 33Ah 350 Wh/kg (recommended)** | 2930 Wh | 8.86 kg | 2S2P → 12S 66Ah | ~$2,930 | **8-8.5h** | ✅ Best modularity, off-the-shelf |
| 2× Tattu 12S 33Ah 350 Wh/kg | 2930 Wh | 8.89 kg | 2P → 12S 66Ah | ~$3,800 | **8-8.5h** | ✅ Simpler wiring, same endurance |
| 1× Tattu 12S 76Ah 330 Wh/kg | 3374 Wh | 10.88 kg | Direct 12S | ~$4,300 | **8.5-9h** (needs 20 kg MTOW) | ⚠️ Best energy but requires 20 kg MTOW |
| 4× Xingto 6S 30Ah 370 Wh/kg | ~3280 Wh (est.) | ~8.9 kg (est.) | 2S2P → 12S 60Ah | ~$3,000-4,000 | **9-9.5h** | ⚠️ Higher density but less verified |
| Future: 4× 450 Wh/kg packs | ~4000 Wh | ~8.9 kg | 2S2P → 12S | $5,000-8,000 est. | **10-11h** | ⚠️ Not yet available at volume |
**4-Battery Configuration Detail (2S2P)**:
- 2 series pairs: each pair = 2× 6S in series = 12S 33Ah (44.4V, 1465 Wh)
- 2 parallel pairs: both 12S pairs in parallel = 12S 66Ah (44.4V, 2930 Wh)
- Requires: 2× series adapters, 1× parallel bus bar, battery management for each pair
- Advantage: individual pack replacement if one degrades; modular packing for transport
- Disadvantage: more wiring complexity, more connectors (failure points)
**2-Battery Configuration (2P)**:
- 2× 12S 33Ah in parallel = 12S 66Ah (44.4V, 2930 Wh)
- Simpler wiring, fewer connectors
- Each pack heavier individually (4.4 kg) but fewer handling steps
### Component: Motor & Propulsion (scaled for 18 kg)
| Solution | Power | Weight | Efficiency | Cost | Fit |
|----------|-------|--------|-----------|------|-----|
| **T-Motor U8 Lite (recommended)** | 700W max, 200-300W cruise | ~250g | η ≈ 0.92 at cruise | ~$150 | ✅ Proven for this MTOW class |
| Dualsky XM6350EA | 800W max | ~280g | η ≈ 0.90 | ~$120 | ✅ Good budget option |
| SunnySky V4014 | 600W max | ~210g | η ≈ 0.91 | ~$90 | ⚠️ Borderline power margin |
Propeller: 16×10 or 17×10 folding (vs 13×8 in Draft 02). Larger prop = higher propulsive efficiency at lower RPM, critical for endurance.
ESC: 60-80A continuous rating (vs 40-60A in Draft 02).
### Component: Foam Core
Same as Draft 02 — PVC Divinycell H60 recommended. No change.
### Component: Wing-Fuselage Joint
Same aluminum spar joiner + pin lock concept as Draft 02, but scaled for larger wing loads:
- Spar tube: 25mm OD (vs 20mm) to handle higher bending moments
- Joiner: machined 7075-T6 aluminum (stronger than 6061-T6)
- Weight: ~0.35 kg per joint set (vs 0.2-0.3 in Draft 02)
### Component: Camera Payload (Upgraded for 2 km Altitude)
**GSD = (Sensor Width × Altitude) / (Focal Length × Image Width)**
#### Navigation Camera (GPS-Denied System)
| Solution | Sensor | Resolution | Weight (body+lens) | GSD at 2 km | FoV at 2 km | Cost | Fit |
|----------|--------|-----------|-------------------|-------------|-------------|------|-----|
| ADTI 20L V1 (Draft 02) | APS-C 23.2mm | 20MP (5456×3632) | ~271g (121g+150g) | 34 cm/px (25mm) | 1855×1235m | $480+lens | ❌ Too coarse at 2 km |
| **ADTI 26S V1 + 35mm (recommended)** | APS-C 23.4mm | 26MP (6192×4128) | **~172g** (122g+50g) | **21.6 cm/px** (35mm) | 1337×892m | **$1,890** | ✅ Best value: mech. shutter, light, good GSD |
| ADTI 61PRO + 50mm | FF 35.7mm | 61MP (9504×6336) | ~426g (276g+150g) | **15 cm/px** (50mm) | 1426×950m | $2,830 | ✅ Best GSD but +$940 over 26S |
| Sony ILX-LR1 + 50mm | FF 35.7mm | 61MP (9504×6336) | ~393g (243g+150g) | **15 cm/px** (50mm) | 1426×950m | $3,100 | ⚠️ Lightest 61MP, drone-native, most expensive |
| ADTI 36S + 50mm | FF 35.9mm | 36MP (7360×4912) | ~390g (240g+150g) | 19.5 cm/px (50mm) | 1434×957m | $1,600 | ❌ No mechanical shutter — rolling shutter distortion |
**Recommendation**: ADTI 26S V1 with 35mm fixed lens. Mechanical shutter eliminates rolling shutter distortion (critical for GPS-denied feature matching at speed). 21.6 cm/pixel GSD at 2 km is sufficient for terrain feature matching, road/building identification, and satellite image correlation. IMX571 back-illuminated sensor delivers excellent dynamic range. Lightest option at 172g. Upgrade to ADTI 61PRO (+$940, 15 cm/px) if finer GSD is needed.
#### AI Camera (Reconnaissance — "Nice Shots" from 2 km)
| Solution | Sensor | Resolution | Zoom | Weight | GSD at 2 km (max zoom) | FoV at max zoom | Thermal | Cost | Fit |
|----------|--------|-----------|------|--------|----------------------|----------------|---------|------|-----|
| Viewpro A40 Pro (Draft 02) | 1/2.8" | 1080p (1920×1080) | 40× optical | 1074g | 3.4 cm/px | 65×37m | 640×512 | $2,999 | ⚠️ Good zoom but 1080p limits FoV |
| **Viewpro Z40K (recommended)** | 1/2.3" | **4K** (3840×2160) | 20× optical + 25× IA (4K) | **595g** | **2.7 cm/px** | **103×58m** | No | $2,999-4,879 | ✅ Better GSD, 2.5× wider FoV, 479g lighter |
| Viewpro Z40TIR | 1/2.3" | **4K** (3840×2160) | 20× optical + 40× IA (1080p) | ~700g est. | **2.7 cm/px** (4K) | 103×58m | 640×480 | ~$5,000 est. | ✅ Best of both: 4K + thermal |
| Viewpro A40T Pro | 1/2.8" | 1080p | 40× optical | ~1200g | 3.4 cm/px | 65×37m | 640×512 | $5,999 | ⚠️ Thermal + zoom but 1080p, heavy |
**Recommendation**: Viewpro Z40K. At 4K resolution with 20× optical zoom, it delivers **better GSD (2.7 vs 3.4 cm/px)** and **2.5× wider field of view** at max zoom than the A40 Pro at 1080p/40×. And it's **479g lighter** — weight that can go to battery or margin. If thermal is needed, step up to Z40TIR.
At 2.7 cm/pixel: vehicles clearly identifiable, human figures detectable, building details visible. At 20× wide end (53 cm/px): wide-area situational awareness covering ~2 km × 1.2 km.
#### Payload Weight Summary (Upgraded)
| Component | Draft 02/03 | Upgraded | Delta |
|-----------|-------------|---------|-------|
| Navigation camera (body+lens) | ADTI 20L + 25mm = 271g | ADTI 26S + 35mm = 172g | **-99g** |
| AI camera + gimbal | Viewpro A40 Pro = 1074g | Viewpro Z40K = 595g | **-479g** |
| Jetson Orin Nano Super | 60g | 60g | — |
| Pixhawk 6x + GPS | 65g | 65g | — |
| **Payload total** | **1470g** | **892g** | **-578g** |
**Net effect: 578g saved.** This frees ~191 Wh of battery capacity at 331 Wh/kg (~42 min extra endurance) or provides comfortable MTOW margin.
### Component: Alternative Power Sources Assessment
| Solution | Endurance | System Weight | Cost | Logistics | RF Compat. | Fit |
|----------|-----------|---------------|------|-----------|-----------|-----|
| **Semi-solid battery (primary)** | 8-9h | 8.9 kg | $2,930-3,800 | ✅ Charge from any outlet | ✅ S2 FG | ✅ Recommended |
| Solid-state 450 Wh/kg (upgrade path) | 10-11h | 8.9 kg (or lighter) | $5,000-8,000 est. | ✅ Same as above | ✅ S2 FG | ⚠️ Future upgrade |
| Hydrogen fuel cell | 15-17h | 9.8 kg (FC + tank) | $25,000-40,000 | ❌ H2 supply in field | ❌ Needs CFRP | ❌ Impractical |
| Solar + battery hybrid | +1h over battery alone | +0.5-1.0 kg panels | +$500-1,500 | ⚠️ Weather dependent | ⚠️ Panels on wing | ❌ Marginal gain |
## Weight Budget (18 kg MTOW, 3.8m Wingspan)
| Component | Weight (kg) | Notes |
|-----------|-------------|-------|
| Airframe (S2 FG sandwich + CF spar, 3.8m) | 5.5-6.5 | Scaled from 3m (3.8-4.5 kg) proportional to area |
| Wing joints (aluminum 7075) | 0.35 | Larger joiner for higher loads |
| Motor (700W) + ESC (80A) + folding prop 16" | 0.6 | Scaled up from Draft 02 |
| Wiring, connectors, battery bus | 0.45 | More wiring for 4-battery config |
| **Platform subtotal** | **6.9-7.9** | |
| Payload (ADTI 26S + Z40K + Jetson + Pixhawk + GPS) | 0.89 | Upgraded cameras — 578g lighter than Draft 02 payload |
| Battery (4× Tattu 6S 33Ah) | 8.86 | 4 × 2.216 kg |
| **Total** | **16.7-17.7** | |
Conservative: 7.9 + 0.89 + 8.86 = **17.65 kg** (well under 18 kg MTOW ✓).
Optimistic: 6.9 + 0.89 + 8.86 = **16.65 kg** (1.35 kg margin for accessories or extra battery).
## Endurance Estimates
### Flight Physics Parameters
- Cruise speed: 17 m/s (optimized for endurance at this wing loading)
- L/D at cruise: 17 (conservative; L/D_max ≈ 19-20 for AR=13.6)
- Overall propulsive efficiency: η = 0.72 (motor 0.92 × prop 0.82 × ESC 0.95)
### Cruise Power Calculation
P_cruise = (W × g × V) / (L/D × η)
= (18 × 9.81 × 17) / (17 × 0.72)
= 3001.9 / 12.24 = **245W**
P_total = 245 + 30 (payload) = **275W**
### Endurance by Battery Configuration
| Config | Energy (Wh) | Usable 80% (Wh) | Theoretical (h) | Practical (h) | Conservative (h) |
|--------|------------|------------------|-----------------|---------------|------------------|
| 4× 6S 33Ah 330 Wh/kg | 2930 | 2344 | 10.7 | **8.5** | **7.5-8.0** |
| 2× 12S 33Ah 350 Wh/kg | 2930 | 2344 | 10.7 | **8.5** | **7.5-8.0** |
| 4× Xingto 370 Wh/kg (est.) | ~3280 | ~2624 | 11.9 | **9.5** | **8.5-9.0** |
| 1× 12S 76Ah 330 Wh/kg (20 kg MTOW) | 3374 | 2699 | 10.5* | **8.4** | **7.5-8.0** |
| Future 450 Wh/kg (est.) | ~4000 | ~3200 | 14.5 | **11.6** | **10-10.5** |
*Higher MTOW (20 kg) → higher cruise power (~300W) partially offsets larger battery.
**Practical** = with 80% DoD. **Conservative** = with additional 10% real-world margin (wind, maneuvers, non-optimal cruise).
### Cross-Validation Against Reference Platforms
| Reference | MTOW | Energy | Endurance | Wh/min | Our scaled |
|-----------|------|--------|-----------|--------|------------|
| DeltaQuad Evo (standard) | 10 kg | 976 Wh | 4.5h | 3.62 | — |
| DeltaQuad Evo (record) | ~9 kg | ~1800 Wh | 8.9h | 3.37 | — |
| YUAV Y37 | ~17 kg | 2700 Wh | 8.5h | 5.29 | Our 18 kg @ 2930 Wh: extrapolated **8.0-8.7h** |
The YUAV Y37 cross-check (full carbon, 3.7m) extrapolates to 8.0-8.7h for our S2 FG design at 18 kg with 2930 Wh, accounting for the ~10% aerodynamic penalty of fiberglass vs carbon. This confirms our calculated range.
### Comparison to Draft 02
| Parameter | Draft 02 | Draft 03 | Change |
|-----------|----------|----------|--------|
| MTOW | 10 kg | 18 kg | +80% |
| Wingspan | 3.0m | 3.8m | +27% |
| Battery weight | 3.2 kg | 8.86 kg | +177% |
| Battery energy | 1001 Wh | 2930 Wh | +193% |
| Cruise power | ~170W | ~275W | +62% |
| Practical endurance | 3.5-4.7h | **8-8.5h** | +80-140% |
| BOM cost | $2,800-4,500 | $5,500-7,500 | +67% |
## BOM Cost Estimate (Per Unit, 8h Config)
| Component | Low Est. | High Est. | Notes |
|-----------|----------|-----------|-------|
| S2 fiberglass fabric | $250 | $500 | ~14 m² at $15-30/m² (40% more than 3m) |
| PVC foam core (Divinycell H60) | $160 | $300 | Wing + fuselage + tail |
| Epoxy resin + hardener | $120 | $230 | ~3.5-4 kg resin |
| CF spar material (tube + UD tape) | $80 | $150 | Longer spars for 3.8m |
| Aluminum spar joiners 7075-T6 | $50 | $100 | Larger, machined |
| Vacuum bagging consumables | $40 | $80 | |
| Motor (T-Motor U8 Lite or equiv.) | $120 | $200 | 700W class |
| ESC (60-80A) | $60 | $120 | |
| Folding propeller (16×10) | $20 | $40 | |
| Servos (6× for larger surfaces) | $80 | $160 | |
| Wiring, connectors, battery bus | $80 | $150 | More complex 4-battery wiring |
| **Batteries (4× Tattu 6S 33Ah 350)** | **$2,930** | **$2,930** | Retail price |
| RC receiver | $30 | $80 | |
| Telemetry radio | $100 | $300 | |
| Transport case / padded bag | $80 | $200 | Larger for 190cm wings |
| **Subtotal (airframe + propulsion + battery)** | **$4,200** | **$5,540** | |
| Nav camera: ADTI 26S V1 + 35mm lens | $1,890 | $1,890 | 26MP APS-C, mech. shutter, 21.6 cm/px at 2 km |
| AI camera: Viewpro Z40K 4K gimbal | $2,999 | $4,879 | 4K 20× zoom, 2.7 cm/px at 2 km |
| Pixhawk 6x + GPS | $300 | $500 | |
| **Total BOM (complete unit)** | **$9,389** | **$12,809** | |
With 2× 12S 33Ah instead of 4× 6S: battery cost rises to ~$3,800 (+$870).
With Xingto 370 Wh/kg: battery cost est. ~$3,000-4,000 but better endurance.
**Per-unit cost at batch of 5+**: **$10,500-14,500** (including cameras, tooling amortization)
**Per-unit cost first prototype**: **$13,500-17,000** (includes tooling)
Optional upgrade: swap ADTI 26S → ADTI 61PRO (+$940/unit) for 15 cm/px GSD if finer nav resolution needed.
## Battery Upgrade Roadmap
| Timeline | Battery Technology | Energy Density (pack) | Endurance (18 kg platform) | Availability |
|----------|-------------------|----------------------|---------------------------|-------------|
| **Now (2025-2026)** | Tattu/Grepow semi-solid 350 Wh/kg | ~331 Wh/kg | **8-8.5h** | ✅ Off-the-shelf |
| **Now (2025-2026)** | Xingto semi-solid 370 Wh/kg | ~350 Wh/kg | **9-9.5h** | ✅ Available (limited) |
| **Near-term (2026-2027)** | Tulip Tech Ampera solid-state | ~430 Wh/kg | **10-11h** | ⚠️ Shipping to select partners |
| **Near-term (2026-2027)** | Amprius SA102 silicon-nanowire | ~430 Wh/kg | **10-11h** | ⚠️ Pilot production |
| **Future (2027-2028)** | Tulip Tech Enerza / Amprius 500 | ~475 Wh/kg | **11-12h** | ❓ Announced, not volume |
### Solid-State 450 Wh/kg Cost Impact
Solid-state batteries (Tulip Tech, Amprius) are not yet priced publicly — both sell on custom quotes to defense/aerospace customers. Industry estimates for 2025-2026 production cost: $800-1,000/kWh. With small-volume aerospace/defense retail markup (1.5-3×), estimated retail: $1,500-2,500/kWh.
| Battery | Pack Wh/kg | Total Energy | Endurance | Battery Cost | Total UAV BOM | Delta vs Baseline |
|---------|-----------|-------------|-----------|-------------|--------------|------------------|
| Tattu semi-solid (baseline) | ~331 | 2930 Wh | 8-8.5h | **$2,930** | ~$6,500 | — |
| Solid-state 450 (low est.) | ~430 | 3810 Wh | 10-11h | **$5,700** | ~$9,300 | **+$2,800 (+43%)** |
| Solid-state 450 (mid est.) | ~430 | 3810 Wh | 10-11h | **$7,600** | ~$11,200 | **+$4,700 (+72%)** |
| Solid-state 450 (defense premium) | ~430 | 3810 Wh | 10-11h | **$9,500** | ~$13,100 | **+$6,600 (+100%)** |
Prices should converge toward production cost ($800-1,000/kWh → low estimate above) as Amprius scales 1.8 GWh contract manufacturing capacity and Tulip Tech ramps with Dutch MoD backing through 2026-2027.
**Design for upgradability**: The battery bay should accommodate the same physical volume regardless of chemistry. Start with Tattu semi-solid at 8-8.5h for $2,930. When solid-state packs become available in compatible form factor, drop them in for 10-11h — no airframe changes needed, just a battery swap.
## Modular Transport Specifications
| Dimension | Value (3.8m) | Value (4.0m, 3-section) |
|-----------|-------------|------------------------|
| Wing panel length | 190 cm (half-span) | 170 cm outer + 60 cm center |
| Wing panel chord | 28-30 cm | 28-30 cm |
| Wing panel thickness | 4-5 cm | 4-5 cm |
| Fuselage length | 110 cm | 110 cm |
| Fuselage width/height | 18-22 cm | 18-22 cm |
| Assembly time | < 12 minutes | < 15 minutes |
| Disassembly time | < 7 minutes | < 10 minutes |
**Pickup truck (2 planes, 3.8m design)**: All wing panels stack in one pile (190×30×20 cm = 4 panels × 5cm). Fuselages alongside (110×22 cm × 2). Total footprint: 190×110 cm < 198×130 cm. ✅
**Car trunk (1 plane, 3.8m)**: Tight but possible in larger sedans/SUVs. Two wing panels (190cm) require fold-down rear seats or diagonal placement. Fuselage fits easily. ⚠️ Borderline for sedans; SUV or wagon preferred.
## Hydrogen Fuel Cell — Assessment (Not Recommended)
Investigated as requested. While hydrogen offers dramatically higher endurance (15-17h), it is **not recommended** for this application:
| Factor | Assessment |
|--------|-----------|
| Endurance | ✅ 15-17h theoretical with IE-SOAR 2.4 + 10.8L tank |
| System weight | ⚠️ ~9.8 kg (FC 4.8 + tank 4.2 + regulator 0.3 + buffer 0.5) — similar to 4-battery pack but higher complexity |
| Cost | ❌ $25,000-40,000 per unit (FC module alone est. $15-25k) |
| H2 logistics | ❌ Compressed hydrogen (350 bar) supply chain in eastern Ukraine = extremely difficult. Requires specialized transport, hazmat protocols, compressor equipment |
| Radio transparency | ❌ H2 platforms (NOCTUA, Doosan) use CFRP to save weight, conflicting with RF requirement |
| Reliability | ⚠️ Fuel cells have 1000h life but are sensitive to contaminants and temperature extremes |
| Practical recommendation | Revisit only if (1) hydrogen infrastructure develops in theater, (2) RF transparency requirement is relaxed, or (3) endurance requirement exceeds 12h |
## Solar Augmentation — Assessment (Not Recommended)
| Factor | Assessment |
|--------|-----------|
| Available wing area | ~0.7 m² usable upper surface |
| Solar power at altitude | ~35-40W average (Ukrainian latitude, 22% efficient flexible panels) |
| Endurance gain | +1.0-1.5h theoretical, but -0.5h from panel weight → net +0.5-1.0h |
| Cost | +$500-1,500 per unit for flexible panels |
| Complexity | Adds MPPT controller, fragile surface, weather dependency |
| Recommendation | Not worth the cost/complexity for ~1h marginal gain |
## Testing Strategy
### Integration / Functional Tests
- Static wing load test: 3× max flight load at spar joiner (verify no failure at 3g with 18 kg MTOW)
- Wing joint cycling: 100× assembly/disassembly, verify no wear (critical at higher loads)
- RF transparency test: measure GPS signal through airframe skin (target: < 3 dB attenuation)
- Assembly time test: verify < 12 minutes from transport case to flight-ready
- Battery wiring test: verify 2S2P balancing, measure voltage sag under load, test fail-safe (single pack disconnect)
- Range/endurance test: fly at cruise until 20% reserve, measure actual vs predicted
- Payload integration: electronics function under vibration at 18 kg flight loads
### Non-Functional Tests
- Transport test: load 2 planes in pickup, drive 100 km on mixed roads, verify no damage
- Hard landing test: belly landing at 2.5 m/s descent (higher than Draft 02 due to heavier aircraft)
- Field repair test: wing skin puncture → FG patch + epoxy → airworthy in < 30 minutes
- Temperature test: battery + avionics at -10°C and +45°C
- Battery endurance test: 50 charge/discharge cycles on 4-battery 2S2P config, verify balanced degradation
- CG test: verify stable CG across all battery configurations (4-battery, 3-battery partial, 2-battery emergency)
- Emergency flight test: verify aircraft can fly safely on 2 batteries (reduced endurance) if 1 series pair fails
## Production BOM: 5 UAVs From Scratch (8h Config)
### A. One-Time Equipment & Tooling
Same as Draft 02 base equipment: $3,335. Add:
| Item | Qty | Unit Price | Total | Notes |
|------|-----|-----------|-------|-------|
| Larger mold materials (4m wing + fuselage) | 1 set | $900 | $900 | MDF plugs + tooling epoxy for 3.8m molds |
| Aluminum spar joiner machining (7075, 12 sets) | 1 | $600 | $600 | Larger joiners, CNC outsourced |
| Battery parallel bus bar / wiring jig | 1 | $100 | $100 | For consistent 2S2P assembly |
| **Equipment & Tooling TOTAL** | | | **$4,935** | |
### B. Raw Materials (5 UAVs + 20% waste)
| Item | Qty (5 UAVs + margin) | Unit Price | Total |
|------|----------------------|-----------|-------|
| S2 fiberglass fabric 6oz | 100 yards | $12.50/yard | $1,250 |
| PVC foam Divinycell H60 10mm | 24 sheets | $40/sheet | $960 |
| Laminating epoxy resin | 6 gallons | $125/gal | $750 |
| Epoxy hardener | 3 gallons | $80/gal | $240 |
| Carbon fiber tube (spar, 25mm OD, 2.0m) | 12 | $35 each | $420 |
| Carbon fiber UD tape 25mm | 50 m | $5/m | $250 |
| Vacuum bagging consumables | — | — | $400 |
| Misc hardware | — | — | $250 |
| **Materials TOTAL (5 UAVs)** | | | **$4,520** |
| **Per UAV materials** | | | **~$904** |
### C. Electronics & Propulsion (per UAV × 5)
| Item | Per UAV | ×5 Total |
|------|---------|----------|
| Motor (T-Motor U8 Lite or equiv.) | $150 | $750 |
| ESC (80A) | $80 | $400 |
| Folding propeller 16×10 (2 per UAV) | $40 | $200 |
| Servos (6× digital metal gear) | $150 | $750 |
| Nav camera: ADTI 26S V1 + 35mm lens | $1,890 | $9,450 |
| AI camera: Viewpro Z40K 4K gimbal | $3,500 | $17,500 |
| Pixhawk 6X Mini + GPS | $380 | $1,900 |
| RC receiver (TBS Crossfire) | $60 | $300 |
| RFD900x telemetry | $170 air × 5 + $350 GCS | $1,200 |
| Power distribution + BEC | $30 | $150 |
| Wiring, connectors, battery bus | $80 | $400 |
| **Batteries: 4× Tattu 6S 33Ah 350 (per UAV)** | **$2,930** | **$14,650** |
| **Electronics TOTAL (5 UAVs)** | | **$47,650** |
| **Per UAV electronics** | | **~$9,530** |
### D. Summary
| Category | Total | Per UAV |
|----------|-------|---------|
| A. Equipment & Tooling | $4,935 | $987 |
| B. Raw Materials | $4,520 | $904 |
| C. Electronics & Propulsion | $47,650 | $9,530 |
| D. Consumables & Misc | $1,200 | $240 |
| E. Labor (est. same structure as Draft 02, +20%) | $19,176 | $3,835 |
| **GRAND TOTAL (5 UAVs)** | **$77,481** | |
| **Per UAV (all-in, with labor)** | | **$15,496** |
| **Per UAV (materials + electronics, no labor)** | | **$11,661** |
The cost increase vs Draft 02 ($6,502/unit) is driven by cameras (+$2,391/unit: ADTI 26S replaces ADTI 20L, Z40K replaces A40 Pro), batteries (+$2,200/unit), and larger airframe (+$250/unit). Optional: swap to ADTI 61PRO (+$940/unit) for 15 cm/px nav GSD.
## Risk Assessment
| Risk | Impact | Probability | Mitigation |
|------|--------|------------|-----------|
| S2 FG airframe heavier than estimated → MTOW exceeded | Reduced endurance | Medium | Build weight tracking into construction; accept 18.5 kg MTOW if needed |
| 4-battery wiring complexity → connector failure | Loss of power pair | Low | Redundant connectors; test fail-safe on 2 batteries; parallel bus bar design |
| Semi-solid battery supply disruption | Cannot build | Low | Multiple suppliers (Tattu, Grepow, Xingto) |
| L/D lower than 17 in practice | Endurance drops to 7-7.5h | Medium | Use Xingto 370 Wh/kg for margin; optimize airfoil selection (SD7037 or AG series) |
| Wing flutter at 3.8m span | Structural failure | Low | Ground vibration test; CF spar sized for 1.5× flutter speed margin |
| CG shift with 4 battery packs | Controllability | Low | Fixed battery bay positions; CG calculated for all configurations |
## References
1-34: See Draft 01 and Draft 02 references (all still applicable)
Additional sources:
35. DeltaQuad Evo 8h55m record: https://uasweekly.com/2025/06/27/deltaquad-evo-sets-record-with-8-hour-flight-endurance-for-electric-vtol-uas-milestone/
36. Tulip Tech batteries: https://tulip.tech/batteries/
37. DeltaQuad Evo specs: https://docs.deltaquad.com/tac/vehicle-specifications
38. DeltaQuad Evo performance calculator: https://evo.deltaquad.com/calc/
39. YUAV Y37 specs: https://www.airmobi.com/yuav-y37-a-new-standard-in-long-endurance-vtol-fixed-wing-uavs/
40. YUAV Y37 product page: https://www.airmobi.com/product/yuav-y37-3700mm-vtol-fixed-wing-uav-pnp/
41. Tattu 350 Wh/kg 6S 33Ah: https://tattuworld.com/semi-solid-state-battery/semi-solid-350wh-kg-33000mah-22-2v-10c-6s-battery.html
42. Tattu 350 Wh/kg 12S 33Ah: https://tattuworld.com/semi-solid-state-battery/semi-solid-350wh-kg-33000mah-44-4v-10c-12s-battery.html
43. Tattu 330 Wh/kg 12S 76Ah: https://tattuworld.com/semi-solid-state-battery/semi-solid-330wh-kg-76000mah-44-4v-10c-12s-battery.html
44. Xingto 370 Wh/kg battery: https://www.xtbattery.com/370wh/kg-42v-high-energy-density-6s-12s-14s-18s-30ah-semi-solid-state-drone-battery/
45. Amprius SA102 450 Wh/kg: https://amprius.com/the-all-new-amprius-500-wh-kg-battery-platform-is-here/
46. Amprius UAV selection: https://amprius.com/amprius-high-power-silicon-batteries-selected-by-esaero-to-power-next-generation-uavs/
47. NOCTUA hydrogen UAV: https://noctua.ethz.ch/technology
48. IE-SOAR 2.4 fuel cell: https://www.intelligent-energy.com/our-products/ie-soar-fuel-cells-for-uavs/ie-soar-2-4/
49. IE-SOAR specs (retail): https://shop.thebioniceye.co.uk/products/ie-soar-2-4kw-hydrogen-fuel-cell
50. Doosan DS30W specs: https://www.doosanmobility.com/en/products/drone-ds30
51. Cellen hydrogen refueling: https://cellenh2.com/reinventing-hydrogen-refueling-for-drones/
52. Tattu battery catalog (pricing): https://rcdrone.top/collections/tattu-semi-solid-state-battery
53. Tattu 76Ah pricing (FlexRC): https://flexrc.com/product/tattu-semi-solid-state-330wh-kg-76000mah-10c-44-4v-12s1p-lipo-battery-pack-with-qs12-s-plug/
54. JOUAV CW-80E: https://www.jouav.com/products/cw-80e.html
55. Discus 2b 4m glider: https://icare-rc.com/discus2b_4m.htm
56. Pickup bed dimensions: https://kevinsautos.com/faq/what-are-the-dimensions-of-a-65-foot-truck-bed.html
57. Tulip Tech Dutch MoD partnership: https://www.tulip.tech/news/
## Related Artifacts
- Previous drafts: `solution_draft01.md` (CFRP), `solution_draft02.md` (S2 FG, 3m, 10 kg)
- Research artifacts: `_standalone/UAV_frame_material/00_research/UAV_frame_material/`
@@ -0,0 +1,296 @@
# Solution Draft (Rev 04) — Launch & Recovery Assessment
## Assessment Findings
| Old Component Solution | Weak Point | New Solution |
|------------------------|------------|-------------|
| No launch/recovery method specified | Aircraft cannot operate without a defined takeoff/landing approach | Two viable options analyzed: Quad VTOL (recommended for field ops) or Catapult + Parachute (recommended for maximum endurance) |
| Y-3 tricopter VTOL (user proposed) | Zero motor redundancy, tilt servo failure risk, no production platforms use Y-3 | Quad (4+1) VTOL — industry standard used by DeltaQuad, YUAV Y37, WingtraOne |
| YUAV Y37 listed as 17-20 kg MTOW | Product page confirms TOW 22-26 kg; 10 kg empty weight with VTOL system | Corrected Y37 specs: TOW 22-26 kg, empty 10 kg (with VTOL), 4+1 config, $16,900 PNP |
| 18 kg MTOW design (Draft 03) | Cannot accommodate VTOL within 18 kg — VTOL system adds 2.5-3.2 kg | Option A: raise MTOW to 21-22 kg for VTOL variant; Option B: keep 18 kg for catapult variant |
## Product Solution Description
Two platform variants from the same S2 FG airframe, optimized for different operational needs:
**Variant A — Quad VTOL** (recommended for forward/mobile operations):
Scaled-up modular S2 FG fixed-wing with 4+1 quadplane VTOL. Wingspan 3.8m, MTOW 21-22 kg. 4 dedicated VTOL motors on carbon fiber tube booms + 1 pusher for cruise. Separate VTOL battery (12S 5500 mAh). Endurance 6.5-7.5 hours. Launches and recovers from any 5m × 5m flat area. No ground equipment needed.
**Variant B — Catapult + Parachute** (recommended for maximum endurance from established bases):
Same S2 FG fixed-wing, no VTOL hardware. Wingspan 3.8m, MTOW 18 kg. Pneumatic catapult launch (ELI PL-60 class). Parachute recovery (Fruity Chutes 20 kg bundle). Endurance 8-8.5 hours. Requires 108 kg catapult system and 8m launch space.
```
VARIANT A — QUAD VTOL (4+1)
┌───────────────────────────────────────────────────────────┐
│ │
│ VTOL Motor 1 VTOL Motor 2 │
│ (front-left) (front-right) │
│ ⟐ 15" prop ⟐ 15" prop │
│ \ / │
│ \ CF tube boom / │
│ \ / │
│ ┌────────────────────────────┐ │
│ │ LEFT FUSELAGE RIGHT│ │
│ │ WING [VTOL bat] WING │ │
│ │ 1.9m [Cruise 1.9m │ │
│ │ batteries] │ Pusher motor │
│ │ [Payload] ─────┤────── ⊕ (cruise) │
│ └────────────────────────────┘ │
│ / \ │
│ / CF tube boom \ │
│ / \ │
│ ⟐ 15" prop ⟐ 15" prop │
│ VTOL Motor 3 VTOL Motor 4 │
│ (rear-left) (rear-right) │
│ │
│ Motor booms: CF tubes (narrow, minimal RF impact) │
│ Boom-wing joints: aluminum brackets with S2 FG layup │
└───────────────────────────────────────────────────────────┘
VARIANT B — CATAPULT + PARACHUTE
┌───────────────────────────────────────────────────────────┐
│ │
│ ┌────────────────────────────┐ │
│ │ LEFT FUSELAGE RIGHT│ │
│ │ WING [Parachute WING │ │
│ │ 1.9m bay + hatch] │ Pusher motor │
│ │ [Cruise 1.9m │ │
│ │ batteries] │ ⊕ (cruise) │
│ │ [Payload] ─────┤─────── │
│ └────────────────────────────┘ │
│ │
│ No motor booms = cleaner aerodynamics │
│ Parachute bay with spring-loaded hatch (top/bottom) │
│ Catapult carriage mounting rails on belly │
└───────────────────────────────────────────────────────────┘
```
## Why Not Y-3 (Tricopter)?
The user asked specifically about Y-3 (3-motor) VTOL. After research, Y-3 is **not recommended** for this application:
| Factor | Y-3 (Tricopter) | Quad (4+1) |
|--------|-----------------|------------|
| Weight saving vs quad | ~400g less | Baseline |
| Motor redundancy | **Zero** — any motor failure = crash | Partial — single motor loss survivable |
| Yaw control | Tilt servo on rear motor (mechanical failure point) | Differential thrust (no moving parts) |
| Production platforms using this | None found in 15-25 kg class | DeltaQuad, YUAV Y37, WingtraOne |
| ArduPilot support | Supported but less tested | Well-tested, widely deployed |
| Hover stability | Lower (3-point, asymmetric) | Higher (4-point, symmetric) |
The 400g weight saving (~2% of MTOW) does not justify the reliability and redundancy loss. For a $15,000-17,000 aircraft in a conflict zone, motor redundancy is critical.
## Architecture
### Component: Launch & Recovery System
| Solution | Weight on Aircraft | Ground Equipment | Endurance | Landing Precision | Cost (airborne) | Cost (ground) | Deployment Speed | Fit |
|----------|-------------------|-----------------|-----------|------------------|----------------|---------------|-----------------|-----|
| **Quad VTOL (recommended for field ops)** | +3.0-3.2 kg | None | 6.5-7.5h | 1-2m | $1,000-1,500 | $0 | < 2 min | ✅ Best for mobile ops |
| **Catapult + Parachute (recommended for max endurance)** | +0.95 kg | 108 kg catapult | 7.5-8.2h | 50-200m drift | $925 | $15,000-25,000 | 5-10 min | ✅ Best for endurance |
| Catapult + Belly landing | 0 kg | 108 kg catapult + 200m strip | 8-8.5h | On strip | $0 | $15,000-25,000 | 5-10 min + strip | ⚠️ Needs flat terrain |
| Y-3 VTOL | +2.5-2.7 kg | None | 7-7.5h | 1-2m | $800-1,200 | $0 | < 2 min | ❌ Reliability risk |
### Component: VTOL System (Variant A — Quad)
| Component | Specification | Weight | Cost |
|-----------|--------------|--------|------|
| VTOL motors (×4) | T-Motor MN505-S or equiv., ~5-6 kg thrust each on 15" prop | 880g total | $400-600 |
| VTOL ESCs (×4) | 40A BLHeli_32 or equiv. | 320g total | $120-200 |
| VTOL propellers (×4) | 15" folding (fold for cruise to reduce drag) | 200g total | $60-100 |
| Motor booms (×4) | Carbon fiber tubes 20mm OD, 400mm length + aluminum brackets | 700g total | $150-250 |
| VTOL battery | 12S 5500 mAh LiPo (dedicated) | 700g | $120-180 |
| Wiring + connectors | 12AWG silicone, XT60 connectors | 180g | $30-50 |
| **VTOL system total** | | **2,980g** | **$880-1,380** |
### Component: Catapult System (Variant B)
| Component | Specification | Weight/Size | Cost |
|-----------|--------------|-------------|------|
| Pneumatic catapult | ELI PL-60 or equivalent | 108 kg (2 cases) | $15,000-25,000 est. |
| Catapult carriage | Custom for UAV fuselage, quick-release | ~2 kg (stays on ground) | Included or $500 custom |
| Belly mounting rails | Aluminum rails on fuselage for carriage attachment | ~150g on aircraft | $50 |
### Component: Parachute System (Variant B)
| Component | Specification | Weight | Cost |
|-----------|--------------|--------|------|
| Fruity Chutes FW bundle 20 kg | IFC-120-S Iris Ultra + pilot chute + deployment bag + Y-harness | 950g | $925 |
| Servo-actuated hatch | Spring-loaded door on fuselage top/bottom, triggered by autopilot | 80g | $30 |
| **Recovery system total** | | **1,030g** | **$955** |
## Updated Weight Budgets
### Variant A — Quad VTOL (21 kg MTOW)
| Component | Weight (kg) | Notes |
|-----------|-------------|-------|
| Airframe (S2 FG, 3.8m, reinforced for VTOL loads) | 6.0-7.0 | +0.5 kg structural reinforcement at boom attach points |
| Wing joints (aluminum 7075) | 0.35 | Same as Draft 03 |
| Motor (800W cruise) + ESC + prop | 0.65 | Slightly larger to handle higher MTOW |
| Wiring, connectors (cruise) | 0.45 | Same as Draft 03 |
| **VTOL system** | **2.98** | **4 motors, 4 ESCs, 4 props, booms, VTOL battery, wiring** |
| **Platform subtotal** | **10.4-11.4** | |
| Payload (cameras + compute) | 0.89 | Same as Draft 03 |
| Cruise battery (4× Tattu 6S 33Ah) | 8.86 | Same as Draft 03 |
| **Total** | **20.2-21.2** | |
Conservative: 11.4 + 0.89 + 8.86 = **21.15 kg** (at 21 kg MTOW — tight)
Optimistic: 10.4 + 0.89 + 8.86 = **20.15 kg** (0.85 kg margin)
**To fit 21 kg MTOW**: reduce to 3× cruise battery packs (6.65 kg, 2198 Wh) → total 18.9-19.9 kg → endurance ~5.5-6.5h. Or accept 22 kg MTOW → endurance ~6.5-7h with 4 packs.
### Variant B — Catapult + Parachute (18 kg MTOW)
| Component | Weight (kg) | Notes |
|-----------|-------------|-------|
| Airframe (S2 FG, 3.8m) | 5.5-6.5 | Same as Draft 03 |
| Wing joints (aluminum 7075) | 0.35 | Same |
| Motor (700W cruise) + ESC + prop | 0.6 | Same as Draft 03 |
| Wiring, connectors | 0.45 | Same |
| Catapult belly rails | 0.15 | Aluminum mounting interface |
| Parachute system | 1.03 | Chute + hatch mechanism |
| **Platform subtotal** | **8.1-9.1** | |
| Payload (cameras + compute) | 0.89 | Same |
| Cruise battery (4× Tattu 6S 33Ah) | 8.86 | Same |
| **Total** | **17.9-18.9** | |
Conservative: 9.1 + 0.89 + 8.86 = **18.85 kg** (slightly over 18 kg; accept 19 kg MTOW or trim airframe)
Optimistic: 8.1 + 0.89 + 8.86 = **17.85 kg** (fits within 18 kg ✓)
## Endurance Comparison
### Variant A — Quad VTOL
| MTOW | Battery Config | Usable Energy | Cruise Power | Endurance (practical) |
|------|---------------|--------------|-------------|----------------------|
| 21 kg | 4× 6S 33Ah (2930 Wh) | 2344 Wh | ~310W | **7.0-7.5h** |
| 22 kg | 4× 6S 33Ah (2930 Wh) | 2344 Wh | ~330W | **6.5-7.0h** |
| 20 kg | 3× 6S 33Ah (2198 Wh) | 1758 Wh | ~295W | **5.5-6.0h** |
Cruise power increase vs Draft 03: higher MTOW (21-22 vs 18 kg) + ~3-5% additional drag from VTOL booms.
P_cruise (21 kg) = (21 × 9.81 × 17) / (17 × 0.72) × 1.04 = ~310W (including boom drag penalty)
### Variant B — Catapult + Parachute
| MTOW | Battery Config | Usable Energy | Cruise Power | Endurance (practical) |
|------|---------------|--------------|-------------|----------------------|
| 18 kg | 4× 6S 33Ah (2930 Wh) | 2344 Wh | ~275W | **8.0-8.5h** |
| 19 kg | 4× 6S 33Ah (2930 Wh) | 2344 Wh | ~285W | **7.5-8.0h** |
Parachute adds ~1 kg but no aerodynamic penalty (stowed internally).
### Summary
| Variant | MTOW | Endurance | vs Draft 03 (8-8.5h) |
|---------|------|-----------|---------------------|
| A: Quad VTOL (4 packs) | 21-22 kg | **6.5-7.5h** | -12-20% |
| A: Quad VTOL (3 packs) | 20 kg | **5.5-6.0h** | -30-35% |
| B: Catapult + Parachute | 18-19 kg | **7.5-8.5h** | -0-6% |
| B: Catapult + Belly | 18 kg | **8-8.5h** | 0% |
## Cross-Validation Against YUAV Y37
The Y37 is the closest production reference for our VTOL variant:
| Parameter | YUAV Y37 | Our Variant A (Quad VTOL) | Delta |
|-----------|----------|--------------------------|-------|
| Wingspan | 3.7m | 3.8m | +3% |
| Empty weight (with VTOL) | 10 kg | 10.4-11.4 kg | +4-14% (S2 FG heavier than carbon) |
| MTOW | 22-26 kg | 21-22 kg | Similar |
| Battery energy | 2700 Wh | 2930 Wh | +9% |
| Endurance (1 kg payload) | 8.5h | ~7h (est. at 0.89 kg payload) | -18% (S2 FG weight penalty) |
| Material | Full carbon | S2 FG + CF spar | S2 FG is ~2-3 kg heavier |
| RF transparent | No | Yes | Our advantage |
| Price (PNP) | $16,900 | ~$11,000-14,000 (DIY) | 18-35% cheaper |
The 18% endurance gap between Y37 and our Variant A is primarily due to the S2 FG weight penalty (~2-3 kg heavier airframe). If RF transparency is not required, a carbon airframe would close this gap.
## BOM Cost Impact (5 UAVs)
### Variant A — Quad VTOL
| Category | Total (5 UAVs) | Per UAV | vs Draft 03 |
|----------|----------------|---------|-------------|
| Draft 03 baseline | $77,481 | $15,496 | — |
| VTOL system hardware | $5,000-7,000 | $1,000-1,400 | +$1,000-1,400/unit |
| Structural reinforcement | $750 | $150 | +$150/unit |
| Larger cruise motor/ESC | $250 | $50 | +$50/unit |
| **Variant A total** | **$83,481-85,481** | **$16,696-17,096** | **+$1,200-1,600/unit** |
### Variant B — Catapult + Parachute
| Category | Total (5 UAVs) | Per UAV | vs Draft 03 |
|----------|----------------|---------|-------------|
| Draft 03 baseline | $77,481 | $15,496 | — |
| Parachute systems (×5) | $4,775 | $955 | +$955/unit |
| Catapult (ELI PL-60, ×1) | $15,000-25,000 | $3,000-5,000 (amortized) | +$3,000-5,000/unit |
| Belly rails + hatch mech. | $500 | $100 | +$100/unit |
| **Variant B total** | **$97,756-107,756** | **$19,551-21,551** | **+$4,055-6,055/unit** |
**Key insight**: VTOL is cheaper per fleet. The catapult is expensive one-time equipment that only amortizes well over large fleets (20+ UAVs).
## Recommendation Matrix
| Operational Scenario | Recommended Variant | Rationale |
|---------------------|--------------------|-----------|
| **Mobile forward operations** (changing locations, no established base) | **A: Quad VTOL** | No ground equipment, instant deploy from any flat area, precision recovery |
| **Fixed base operations** (airfield or prepared area available) | **B: Catapult + Parachute** | Maximum endurance, no VTOL dead weight, lower per-unit complexity |
| **Mixed operations** (both scenarios) | **A: Quad VTOL** | VTOL works everywhere; endurance trade-off (6.5-7.5h vs 8h) is acceptable for operational flexibility |
| **Maximum endurance priority** (>8h critical) | **B: Catapult + Belly** | Zero weight penalty; but needs 200m landing strip |
| **Budget-constrained fleet** (5 units) | **A: Quad VTOL** | $83-85k total vs $98-108k for catapult variant |
## Risk Assessment (New Items for Draft 04)
| Risk | Impact | Probability | Mitigation |
|------|--------|------------|-----------|
| VTOL motor failure during hover landing | Aircraft loss ($17k) | Low | Quad config allows single-motor-out survival; redundant ESC power feeds |
| VTOL boom attachment failure on S2 FG | Boom separation → crash | Low | Aluminum through-bolt brackets; static load test to 5× hover thrust |
| Catapult malfunction | No launch capability | Low | Carry spare seals and Makita batteries; ELI PL-60 is simple design |
| Parachute deployment failure | Aircraft loss + ground damage | Very Low | Dual deployment triggers (autopilot + RC manual); pre-flight chute check |
| Wind drift on parachute recovery | UAV lands in inaccessible area | Medium | Select recovery area with margin; GPS tracking; contingency recovery team |
| VTOL adds drag → endurance less than calculated | Endurance only 6h instead of 7h | Medium | Folding VTOL props reduce cruise drag; boom fairing; accept margin |
| S2 FG structure insufficient for 21-22 kg VTOL loads | Structural failure | Low | Full FEA analysis; static wing load test at 3.5g; boom attachment cycling test |
## Testing Strategy (Additions for Draft 04)
### VTOL-Specific Tests (Variant A)
- Hover stability test: 60-second hover at 21 kg, measure motor temps and vibration
- Transition test: full transition from hover to cruise and back, measure altitude loss and energy
- Single-motor-out test: kill one VTOL motor at 30m altitude, verify safe emergency landing
- Boom attachment cycling: 200× VTOL power-on/off cycles, inspect boom joints for fatigue
- VTOL battery endurance: verify 2+ full VTOL cycles (takeoff + landing) on single charge
- Drag measurement: compare cruise power with VTOL booms vs clean airframe
### Catapult-Specific Tests (Variant B)
- Catapult launch: 10 consecutive launches, verify consistent exit speed and UAV integrity
- Launch acceleration: measure g-forces on airframe and payload during catapult stroke
- Parachute deployment: 5 test deployments at various speeds and altitudes (min 50m AGL)
- Parachute reliability: 20 pack-deploy cycles, verify consistent opening
- Landing impact: verify payload cameras survive 4.6 m/s descent impact
## References
1-57: See Draft 03 references (all still applicable)
Additional sources:
58. YUAV Y37 product page (updated specs): https://www.airmobi.com/product/yuav-y37-3700mm-vtol-fixed-wing-uav-pnp/
59. YUAV Y37 engineering blog: https://www.airmobi.com/yuav-y37-a-new-standard-in-long-endurance-vtol-fixed-wing-uavs/
60. DeltaQuad Evo TAC specs: https://docs.deltaquad.com/tac/vehicle-specifications
61. DeltaQuad Evo VTOL takeoff: https://docs.deltaquad.com/tac/flight/quick-takeoff/vtol-takeoff
62. ELI PL-60 pneumatic catapult: https://eli.ee/products/catapults/pl60/
63. Fruity Chutes FW bundle 20 kg: https://shop.fruitychutes.com/products/fixed-wing-recovery-bundle-44lbs-20kg-15fps
64. Robonic pneumatic launcher advantages: https://www.robonic.fi/advantages-of-pneumatic-launch/
65. Starlino power-to-thrust analysis: http://www.starlino.com/power2thrust.html
66. T-Motor U13II specs: https://store.tmotor.com/product/U13-v2-KV130-Power-Type-UAV-Motor.html
67. Belly landing research: https://www.scientific.net/AMM.842.178
68. Aeromao Talon belly landing: https://aeromao.com/2018/10/18/talon-fully-autonomous-belly-landing/
69. SCL bungee launcher specs: https://uascomponents.com/launch-and-landing-systems/bungee-catapult-scl2
70. UkrSpecSystems SCL-1A: https://ukrspecsystems.com/uascomponents/bungee-uav-launching-system-scl-1a
71. VTOL weight penalty research: https://hal.science/hal-03832115v1/document
72. VTOL configuration endurance comparison: https://mediatum.ub.tum.de/1462822
## Related Artifacts
- Previous drafts: `solution_draft01.md` through `solution_draft03.md`
- Research artifacts: `_standalone/UAV_frame_material/00_research/UAV_frame_material/`
@@ -0,0 +1,354 @@
# Solution Draft (Rev 05) — Reliability & Durability Assessment
## Assessment Findings
| Old Component Solution | Weak Point (functional/security/performance) | New Solution |
|------------------------|----------------------------------------------|-------------|
| Quad VTOL (Draft 04 Variant A) — reliability listed as "Low probability" motor failure | Motor/ESC failure during low-altitude hover (< 10m) is survivable at altitude but likely fatal below 10m; ArduPilot has no motor-out compensation for quadplane VTOL; ESC desync is dominant propulsion failure mode; 1-3 incidents expected per fleet lifetime | Risk reclassified: LOW per sortie but SIGNIFICANT over fleet lifetime; add ESC desync mitigation (low-ESR caps, DShot protocol); add VTOL battery health monitoring; consider redundant ESC feeds |
| Catapult+Parachute (Draft 04 Variant B) — camera damage risk not addressed | Belly-mounted Viewpro Z40K gimbal protruding 8-10cm below fuselage is directly vulnerable to parachute landing impact; wind increases impact energy 4× (190 J calm → 762 J at 8 m/s wind); post-landing drag abrades exposed components | **Semi-recessed gimbal mount** (recommended): mount Z40K in a 120mm-deep belly cavity with only ~40mm lens protrusion; fuselage structure acts as natural bumper. No retractable mechanism needed. Saves 150g and $100-200 vs retractable approach. Add replaceable belly panel + foam bumper around cavity opening |
| Draft 04 parachute landing analysis — calm-air only | Did not account for horizontal wind velocity during parachute descent; at 8 m/s wind, resultant velocity is 9.2 m/s (not 4.6 m/s), impact energy increases 4× | Revised landing energy analysis including wind scenarios; belly panel design must handle 762 J at moderate wind |
| Draft 04 risk matrix — qualitative only | No quantitative risk estimation over fleet lifetime | Added fleet-lifetime risk analysis: expected incidents, costs, and comparison for 5 UAVs × 300 sorties each |
## Product Solution Description
Two platform variants from the same S2 FG airframe with updated reliability assessment and camera protection requirements:
**Variant A — Quad VTOL**: Higher-risk takeoff/landing phase (8 active electronic components during hover, ESC desync possible) but near-zero landing damage to aircraft and payload. Dominant risk: motor/ESC failure below 10m altitude. Estimated 1-3 propulsion incidents per 1,500 fleet sorties.
**Variant B — Catapult + Parachute**: No powered hover risk. Passive parachute recovery is inherently reliable (>99% deployment success). Landing impact (190-762 J depending on wind) is manageable for S2 FG airframe. Camera protection achieved via **semi-recessed gimbal mount** — the same Viewpro Z40K mounted inside a belly cavity with only the lens ball protruding ~40mm, shielded by the fuselage structure.
**Key reliability finding**: Both variants have comparable overall reliability when proper mitigations are applied. VTOL risks are **electronic/catastrophic** (rare but expensive). Catapult+parachute risks are **mechanical/incremental** (more frequent but cheaper and repairable).
## Architecture
### Component: VTOL Reliability System (Variant A)
| Failure Mode | Probability (per sortie) | Consequence | Mitigation | Residual Risk |
|--------------|-------------------------|-------------|-----------|---------------|
| ESC desync during VTOL transition | 1 in 500-2,000 | Aircraft loss at low altitude | Low-ESR capacitors on each ESC; DShot protocol; rampup power tuning; fresh VTOL battery per sortie | Medium — hardware mitigation reduces but doesn't eliminate |
| Motor bearing failure during hover | 1 in 5,000+ | Aircraft loss at low altitude | Replace VTOL motors every 6 months (not 12); pre-flight motor spin test | Low |
| VTOL battery voltage sag | 1 in 200-500 (partial) | ESC desync trigger → motor stall | Dedicated VTOL battery; replace after 200 cycles; monitor internal resistance | Low-Medium |
| VTOL boom attachment fatigue | 1 in 2,000+ | Boom separation → crash | Aluminum through-bolt brackets; inspect every 50 sorties; cycling test per Draft 04 | Low |
| Single motor out at altitude (> 30m) | N/A | Degraded landing, likely survivable | 195% thrust on 3 motors; controlled descent possible with yaw sacrifice | Low — survivable |
| Single motor out at low altitude (< 10m) | N/A | Likely crash — < 2s reaction time | No firmware solution exists; this is an accepted residual risk of VTOL | **HIGH** — inherent to VTOL |
**VTOL Reliability Enhancements (recommended additions to Draft 04):**
| Enhancement | Weight | Cost | Benefit |
|-------------|--------|------|---------|
| Low-ESR capacitors (4×, on each ESC) | 40g | $20 | Reduces voltage noise → fewer ESC desyncs |
| DShot protocol (firmware config) | 0g | $0 | Digital ESC communication → no signal noise |
| Redundant ESC power feeds (dual BEC) | 30g | $40 | Prevents ESC brownout from single feed failure |
| VTOL battery health monitor (voltage + IR) | 10g | $15 | Alerts to degraded battery before failure |
| 6-month VTOL motor replacement (vs 12) | 0g | +$200-300/year per UAV | Halves motor wear risk |
| Pre-flight VTOL motor spin test (procedure) | 0g | $0 | Detects bearing wear, ESC issues before flight |
| **Total** | **80g** | **$75 initial + $200-300/year** | **~50% reduction in ESC desync risk** |
### Component: Camera Mounting & Parachute Landing Protection (Variant B)
#### Camera Mounting Options Comparison
| Mounting Approach | Protrusion Below Belly | Camera Protection | Weight Impact | Cost | FoV | Complexity | Fit |
|-------------------|----------------------|-------------------|-------------|------|-----|-----------|-----|
| **Protruding gimbal (Draft 04)** | 8-10 cm | None — first ground contact point | 0g (baseline) | $0 | 360° pan, full tilt | Lowest | ❌ Incompatible with parachute recovery |
| **Retractable gimbal** | 0-8 cm (retracted/deployed) | Full when retracted | +150g (servo + rail) | +$100-200 | Same as protruding when deployed | Medium — moving parts, timing sequence | ⚠️ Works but adds complexity and failure mode |
| **Semi-recessed mount (recommended)** | ~4 cm (lens ball only) | High — fuselage structure is natural bumper | +50-80g (cavity reinforcing frame) | +$30-60 | ±60-70° pan, ±60° tilt | Lowest — no moving parts | ✅ Best balance of protection, simplicity, weight |
| **Fully recessed / internal turret** | 0 cm | Maximum | +100-200g (window + deeper cavity) | +$100-300 | Most restricted (±45° pan) | Low — but needs optical window | ⚠️ Best protection, but FoV too restricted |
#### Semi-Recessed Gimbal Mount (Recommended)
The same Viewpro Z40K (153 × 95.3 × 166mm, 595g) mounted inside a belly cavity rather than hanging below. The damping board attaches at the top of the cavity — same mounting hardware, same damping balls, no modifications to the camera itself.
```
SEMI-RECESSED Z40K — CROSS SECTION
┌──────────────────────────────────────────────┐
│ FUSELAGE (18-22cm deep) │
│ │
│ ═══════ Damping board + balls ════════ │ ← Same Z40K mounting hardware
│ │ │ │
│ │ Z40K gimbal body │ │
│ │ (153mm tall) │ │ ← Entire gimbal mechanism
│ │ 3-axis motors │ │ inside fuselage
│ │ CNC aluminum housing │ │
│ │ │ │
│ ══════╧══════════════════════════╧═══════ │ ← Belly skin with opening
│ reinforcing ┌──────────┐ reinforcing │ (~170×125mm cutout)
│ frame (FG) │ Lens ball │ frame (FG) │
│ │ (~40mm │ │
└────────────────│protrusion)│───────────────────┘
└──────────┘
Only this part exposed to ground
Fuselage belly absorbs impact first
```
**Cavity specifications:**
- Depth: ~120mm (of 166mm total gimbal height)
- Opening: ~170 × 125mm (15mm clearance on each side of 153 × 95mm gimbal body)
- Reinforcing frame: S2 FG layup around cavity edges, ~50-80g
- Lens protrusion below belly: ~40-45mm
- Foam bumper strip around opening: EVA 15mm, ~30-50g
**Why clearance matters:** 10-15mm gap between gimbal body and cavity walls prevents physical contact during vibration. If the gimbal touches the walls, aircraft vibration transmits directly to the camera sensor, defeating the damping system and causing jello/blur.
#### Vibration & Stabilization Analysis
Semi-recessed mounting does NOT degrade image stabilization — it improves it compared to a protruding mount:
| Factor | Protruding Mount | Semi-Recessed Mount |
|--------|-----------------|-------------------|
| Pendulum arm length | 8-10 cm (full gimbal below belly) | ~4 cm (lens ball only) |
| Pendulum sway amplitude | Higher — longer arm amplifies aircraft oscillations | Lower — shorter arm, less amplification |
| Aerodynamic buffeting on gimbal | Full exposure to 17 m/s airflow | Shielded — gimbal body inside fuselage cavity |
| Turbulence source | Direct airflow on gimbal housing + arm | Minor cavity vortex only (blowing across opening) |
| Damping system function | Works as designed | Identical — same damping board, same balls |
| Active stabilization (3-axis) | ±0.02° — handles remaining vibration | ±0.02° — same; less input vibration to cancel |
The Z40K's stabilization is a two-stage system:
1. **Passive** (damping balls/board): decouples gimbal from high-frequency aircraft vibration (motor buzz, prop harmonics). The "float" is intentional — do NOT rigidly fasten the camera to reduce wobble, as this defeats the passive stage and overloads the active stage.
2. **Active** (3-axis gimbal motors): cancels low-frequency movement (aircraft roll/pitch/yaw). Achieves ±0.02° precision. Works identically regardless of mounting position.
If image wobble is observed, the correct fix is **at the vibration source** (balance propeller, soft-mount cruise motor, stiffen fuselage skin), not at the camera mount. Optionally, slightly stiffer damping balls (harder durometer) can reduce sway amplitude without compromising high-frequency isolation.
#### Parachute Landing Failure Modes (with Semi-Recessed Mount)
| Failure Mode | Probability (per sortie) | Consequence | Mitigation | Residual Risk |
|--------------|-------------------------|-------------|-----------|---------------|
| Parachute non-deployment | 1 in 200+ | Aircraft loss ($17k) | Dual triggers (autopilot + RC manual); spring-loaded hatch; pre-flight chute inspection | Very Low |
| Lens ball ground contact | 1 in 20-50 (moderate wind) | Lens scratch or crack ($200-500 lens replacement) | Foam bumper around cavity opening provides ~15mm standoff; belly skin contacts ground first | Low |
| Belly skin damage from landing impact | 1 in 5-20 | Cosmetic to minor structural ($200-500) | Replaceable belly panel; foam bumper strip | Low — acceptable wear |
| Post-landing drag in wind | 1 in 5-15 | Abrasion to skin, antennas | Parachute release mechanism; wind-aware recovery area selection. Semi-recessed camera NOT exposed to drag abrasion | Low-Medium |
| Landing in inaccessible terrain (wind drift) | 1 in 10-30 | Recovery difficulty, time loss | GPS tracking; plan recovery area with 300m margin; recovery team | Low-Medium |
| Parachute lines tangled on aircraft structure | 1 in 100+ | Incomplete chute inflation → hard landing | Clean exterior (semi-recessed camera reduces snag risk); proper packing | Very Low |
| Gimbal contacts cavity wall (vibration) | Continuous if undersized | Image quality degradation (jello, blur) | Maintain 10-15mm clearance on all sides; opening ~170×125mm for 153×95mm gimbal | Negligible with proper sizing |
**Parachute Landing Protection (recommended additions to Draft 04):**
| Enhancement | Weight | Cost | Benefit |
|-------------|--------|------|---------|
| **Semi-recessed gimbal cavity** (structural cutout + FG reinforcing frame) | +50-80g | $30-60 | Camera shielded by fuselage structure; no moving parts; no retraction mechanism needed |
| Replaceable belly panel (S2 FG sandwich, 2mm) | 0g (replaces existing skin section) | $50-100 per panel | Swap every 50-100 landings; absorbs cumulative impact |
| Belly foam bumper strip around cavity (EVA foam, 15mm) | 30-50g | $10 | Additional impact absorption + ~15mm standoff for lens ball |
| Parachute release mechanism (servo cutter) | 30g | $40 | Cuts risers after touchdown to prevent wind drag |
| **Total** | **110-160g** | **$130-210 initial** | **Camera protected; no moving parts; lighter and simpler than retractable** |
Compared to retractable gimbal approach: **saves 100-150g, saves $70-140, eliminates retraction servo failure mode, no timing sequence needed.**
#### FoV Trade-Off (Semi-Recessed)
| Pan Angle | View Direction | Available? | Notes |
|-----------|---------------|-----------|-------|
| 0° (forward) | Along flight path | ✅ | Primary reconnaissance direction |
| ±30° | Forward oblique | ✅ | Full quality |
| ±60° | Side-looking | ✅ | Slight vignetting at cavity edge |
| ±70° | Wide oblique | ⚠️ | Cavity wall partially blocks — usable at reduced quality |
| ±90° (perpendicular) | Direct side | ❌ | Blocked by cavity wall |
| ±180° (rear) | Behind aircraft | ❌ | Blocked |
For reconnaissance at 2 km altitude: ±60-70° pan covers a ground swath of ~4.6 km wide (±tan(70°) × 2 km). This is sufficient for most reconnaissance profiles. The 360° pan of a protruding gimbal is rarely used — the aircraft itself rotates to look at different areas.
### Component: Catapult System Reliability
| Failure Mode | Probability (per sortie) | Consequence | Mitigation | Residual Risk |
|--------------|-------------------------|-------------|-----------|---------------|
| Pressure seal leak | 1 in 500+ | Cannot launch → mission abort | Carry spare seals; pre-launch pressure test | Very Low |
| Carriage jam | 1 in 1,000+ | Cannot launch → mission abort | Pre-launch dry run; lubricant | Very Low |
| Battery depletion (Makita 18V) | Negligible | Cannot pressurize | Carry 2-3 spare Makita batteries ($30 each) | Negligible |
| Rail damage from transport | 1 in 200+ | Misaligned launch → UAV damage | Transport padding; pre-launch rail alignment check | Low |
| **Complete catapult failure** | **1 in 2,000+** | **Fleet grounded** | **Carry field repair kit; backup launch method (hand launch for reduced MTOW)** | **Low — SPOF** |
## Reliability Comparison Matrix
### Per-Sortie Risk
| Risk Category | Quad VTOL (Variant A) | Catapult+Parachute (Variant B, with protection) |
|---------------|----------------------|------------------------------------------------|
| **Catastrophic aircraft loss** | 1 in 500-2,000 (motor/ESC fail during hover) | 1 in 200+ (parachute non-deploy) — but parachute is simpler and more reliable than 8 electronic components |
| **Camera/gimbal damage** | Near-zero | Very Low — lens scratch possible; semi-recessed mount shields gimbal body |
| **Airframe damage** | Near-zero | 1 in 5-20 (belly panel — cheap, replaceable) |
| **Mission abort (no aircraft loss)** | Near-zero | 1 in 500+ (catapult failure) |
| **Recovery difficulty** | Near-zero (precision 1-2m) | 1 in 10-30 (wind drift to awkward terrain) |
### Fleet Lifetime Risk (5 UAVs × 300 sorties = 1,500 sorties)
| Risk | VTOL Expected Cost | Catapult+Parachute Expected Cost |
|------|-------------------|--------------------------------|
| Aircraft loss (motor/ESC or chute failure) | 1-3 incidents × $17k = **$17,000-51,000** | 0-1 incident × $17k = **$0-17,000** |
| Camera damage (lens scratch/crack) | ~$0 | 0-3 × $300 = **$0-900** (lens replacement; gimbal body protected) |
| Belly panel replacements | ~$0 | 15-30 × $100 = **$1,500-3,000** |
| Catapult maintenance | $0 | 5 years × $750-1,250 = **$3,750-6,250** |
| VTOL motor replacements | 5 UAVs × 5 years × $300 = **$7,500** | $0 |
| **Total expected damage/maintenance cost** | **$24,500-58,500** | **$5,250-27,150** |
### Reliability Verdict
| Factor | VTOL | Catapult+Parachute | Winner |
|--------|------|-------------------|--------|
| Catastrophic failure risk (aircraft loss) | Higher — ESC desync during hover | Lower — parachute is passive/reliable | **Catapult+Parachute** |
| Camera/payload safety per landing | Better — precision soft landing | Good with semi-recessed mount; lens ball slightly exposed (~40mm) | **VTOL** (slight edge) |
| Airframe wear per landing | Better — no ground impact | Worse — 190-762 J per landing, cumulative | **VTOL** |
| System complexity (failure points) | Worse — 8 additional electronic components | Better — passive parachute + simple mechanical catapult | **Catapult+Parachute** |
| Single point of failure | None (distributed) | Catapult (fleet grounded if broken) | **VTOL** |
| Maintenance cost over 5 years | Higher ($7,500 motor replacements) | Lower ($5,250-6,250 panels + catapult) | **Catapult+Parachute** |
| Failure consequence type | Catastrophic (aircraft loss) | Incremental (repairable damage) | **Catapult+Parachute** |
| Fleet lifetime expected cost | $24,500-58,500 | $5,250-27,150 | **Catapult+Parachute** |
## Parachute Landing — Wind Impact Analysis (New)
Draft 04 analyzed only calm-air parachute landing (4.6 m/s vertical, 190 J). Real-world wind significantly changes the picture:
| Wind Speed | Horizontal Drift (100m deploy) | Resultant Velocity | Impact Energy | Damage Profile |
|------------|-------------------------------|-------------------|---------------|----------------|
| Calm (0 m/s) | 10-20m | 4.6 m/s | 190 J | Vertical drop — belly panel absorbs |
| Light (5 m/s) | 110m | 6.8 m/s | 416 J | Angled impact — sliding risk |
| Moderate (8 m/s) | 176m | 9.2 m/s | 762 J | Hard angled impact — tumbling likely |
| Strong (12 m/s) | 264m | 12.9 m/s | 1,499 J | Severe — airframe structural risk |
| DeltaQuad max VTOL wind | — | — | — | 12.5 m/s (VTOL limited too) |
**Key insight**: At moderate wind (8 m/s), parachute landing energy is 4× calm-air estimate. Belly panel and protection systems must be designed for moderate wind case (762 J), not calm-air (190 J).
At strong wind (12 m/s), parachute landing becomes dangerous — but VTOL hover is also marginal at 12+ m/s wind. Both systems have degraded reliability in strong wind.
**Mitigation for wind**: Deploy parachute at higher altitude (200m) to give more time for wind assessment; choose recovery area downwind with soft terrain; auto-release parachute risers after touchdown to prevent drag.
## Updated Weight Budgets
### Variant A — Quad VTOL (21 kg MTOW) — with reliability enhancements
| Component | Weight (kg) | Change from Draft 04 |
|-----------|-------------|---------------------|
| Draft 04 Variant A total | 20.2-21.2 | — |
| ESC capacitors (4×) | +0.04 | New |
| Redundant BEC | +0.03 | New |
| Battery health monitor | +0.01 | New |
| **Revised total** | **20.3-21.3** | **+80g** (negligible) |
### Variant B — Catapult + Parachute (18 kg MTOW) — with semi-recessed camera mount
| Component | Weight (kg) | Change from Draft 04 |
|-----------|-------------|---------------------|
| Draft 04 Variant B total | 17.9-18.9 | — |
| Semi-recessed cavity reinforcing frame | +0.05-0.08 | New (replaces retractable mechanism) |
| Belly foam bumper around cavity | +0.03-0.05 | New |
| Parachute riser cutter | +0.03 | New |
| **Revised total** | **18.0-19.1** | **+110-160g** |
At 19.1 kg conservative: slightly over 18 kg MTOW. Options: accept 19 kg MTOW (minimal endurance impact: ~7.5-8.0h) or trim 160g from airframe. Saves 100-150g vs retractable gimbal approach.
## Updated Cost Impact
### Variant A — VTOL reliability enhancements
| Item | Per UAV | ×5 Fleet |
|------|---------|----------|
| Draft 04 Variant A total | $16,696-17,096 | $83,481-85,481 |
| ESC capacitors + BEC + monitor | $75 | $375 |
| Annual VTOL motor replacement (5 years) | $300/year | $7,500 total |
| **Revised total (5-year)** | | **$91,356-93,356** |
### Variant B — Catapult+Parachute with semi-recessed camera mount
| Item | Per UAV | ×5 Fleet |
|------|---------|----------|
| Draft 04 Variant B total | $19,551-21,551 | $97,756-107,756 |
| Semi-recessed cavity (reinforcing frame, built into airframe) | $40 | $200 |
| Belly bumper + riser cutter | $50 | $250 |
| Replacement belly panels (5 years) | $500 | $2,500 |
| **Revised total (5-year)** | | **$100,706-110,706** |
## Recommendation — Updated
| Operational Scenario | Recommended | Rationale (Reliability Focus) |
|---------------------|-------------|------------------------------|
| **Maximum reliability, accept ground equipment** | **B: Catapult+Parachute** (with semi-recessed gimbal) | Lower probability of catastrophic loss; failure modes are incremental/repairable; passive parachute has fewer electronic failure points |
| **Maximum operational flexibility, accept higher risk** | **A: Quad VTOL** (with reliability enhancements) | No ground equipment SPOF; precision landing protects payload; accepts 1-3 motor/ESC incidents per fleet lifetime |
| **Highest-value payloads (expensive cameras)** | **A: Quad VTOL** | Near-zero camera damage per landing; semi-recessed mount for parachute variant is good but lens ball still slightly exposed |
| **Budget-constrained operations** | **A: Quad VTOL** | Lower 5-year fleet cost ($91k vs $101k) despite higher aircraft loss risk |
| **Risk-averse operations (conflict zone, irreplaceable assets)** | **B: Catapult+Parachute** | Each UAV is $17k in a supply-constrained environment; losing fewer aircraft matters more than operational convenience |
## Answer to User's Questions
**1. "VTOL can suddenly break during faulty of 1 of the motor during takeoff or landing"**
**Confirmed risk.** ESC desync is the most common propulsion failure mode and is triggered by exactly the conditions present during VTOL hover: sudden throttle changes, high current draw, voltage sag. Quad configuration provides partial redundancy at altitude (> 30m) but is likely fatal below 10m due to < 2 seconds reaction time. ArduPilot quadplane firmware has no built-in single motor failure compensation. Over 1,500 fleet sorties, 1-3 such incidents are plausible. Each incident at low altitude = ~$17k aircraft loss.
**Mitigations**: Low-ESR capacitors, DShot protocol, fresh VTOL battery per sortie, 6-month motor replacement interval, pre-flight motor spin test. These reduce but do not eliminate the risk.
**2. "Landing on the parachute can damage the UAV, especially having sticking out AI camera on the gimbal"**
**Confirmed risk, but solvable.** A belly-mounted protruding gimbal like the Viewpro Z40K hanging 8-10cm below the fuselage IS highly vulnerable during parachute landing — it will be the first ground contact point. In wind, impact energy increases 4× (190 J → 762 J at 8 m/s wind). Post-landing drag from the parachute can cause additional abrasion damage.
**Recommended solution: Semi-recessed gimbal mount.** Mount the same Z40K inside a 120mm-deep belly cavity using its standard damping board. Only the lens ball protrudes ~40mm below belly. The fuselage structure around the cavity acts as a natural bumper — the belly skin contacts the ground first, not the camera. This approach:
- Needs NO retractable mechanism (no moving parts, no timing sequence, no servo failure mode)
- Saves 100-150g and $70-140 compared to retractable approach
- Provides better vibration isolation than protruding mount (shorter pendulum arm, wind shielding inside cavity)
- Restricts FoV to ±60-70° pan (vs 360° protruding) — sufficient for reconnaissance at 2 km altitude
- Small residual risk: lens ball scratch in rough terrain or tumbling landing — replaceable lens ($200-300)
The S2 FG airframe itself handles parachute landing forces well — a replaceable belly panel ($50-100) absorbs cumulative wear.
**3. "It depends on the actual camera design and position of the parachute"**
**Correct.** The damage risk is entirely design-dependent. Camera mounting options ranked by parachute landing compatibility:
| Mounting | Landing Damage Risk | Notes |
|----------|-------------------|-------|
| Protruding gimbal (8-10cm below belly) | **HIGH** | First ground contact; incompatible with parachute recovery |
| **Semi-recessed mount (recommended)** | **LOW** | Fuselage shields gimbal body; only lens ball slightly exposed (~40mm) |
| Retractable gimbal | **VERY LOW** | Works but adds 150g, $100-200, and retraction servo failure mode |
| Internal turret with window | **NEAR-ZERO** | Maximum protection but limits FoV and adds optical window |
Parachute Y-harness at CG → default nose-down attitude → further protects belly-mounted components since the nose contacts ground first. Semi-recessed mount combined with nose-down harness attitude gives excellent camera protection with no moving parts.
**Important: do NOT rigidly fasten the camera** to reduce perceived wobble. The damping balls/board are intentional passive isolation. Rigid mounting defeats vibration isolation and causes jello/blur. If wobble is observed, fix at the source: balance propeller, soft-mount cruise motor. The Z40K's 3-axis stabilization (±0.02°) handles the rest.
## Testing Strategy (Additions for Draft 05)
### VTOL Reliability Tests
- ESC desync provocation test: induce voltage sag on VTOL battery during hover at 30m, verify no desync with mitigation hardware
- Single motor shutdown test: kill one motor at 30m altitude, measure altitude loss and control degradation
- Motor thermal endurance: 10× back-to-back VTOL cycles, monitor motor temperatures and ESC performance
- VTOL battery degradation test: track VTOL battery internal resistance over 200 cycles, correlate with ESC performance
### Parachute Landing & Semi-Recessed Camera Tests
- Cavity clearance verification: confirm 10-15mm gap on all sides between Z40K body and cavity walls at all gimbal angles; verify no physical contact during flight vibration
- Image quality comparison: fly same route with protruding mount vs semi-recessed mount, compare stabilization performance and image sharpness
- Wind landing impact: drop UAV from 1.5m with 5 m/s horizontal velocity onto grass/dirt, verify lens ball clearance and belly panel integrity
- Lens ball contact test: drop UAV belly-first from 0.5m onto gravel, inspect lens ball for damage — establish whether foam bumper standoff is sufficient
- Belly panel replacement: verify panel swap in < 10 minutes with field tools
- Parachute riser cutter: 20× cut tests, verify clean separation within 3 seconds of touchdown
- Drag abrasion test: drag UAV 5m across gravel with parachute attached, verify semi-recessed camera is not damaged (vs protruding gimbal baseline)
- Cavity turbulence test: smoke visualization or tuft test at cruise speed to verify no harmful vortex inside cavity
## References
1-72: See Draft 04 references (all still applicable)
Additional sources:
73. ArduPilot quadplane reliability tips: https://ardupilot.org/plane/docs/quadplane-reliability.html
74. DeltaQuad Evo preventative maintenance: https://docs.deltaquad.com/tac/maintenance/preventative-maintenance
75. Brushless motor lifespan: https://www.mepsking.shop/blog/how-long-do-brushless-drone-motors-last.html
76. ESC desync diagnosis: https://oscarliang.com/fix-esc-desync/
77. ESC common faults: https://www.mepsking.com/blog/esc-faults-and-fixes-for-fpv-drones.html
78. Fruity Chutes parachute integration guide: https://fruitychutes.com/uav_rpv_drone_recovery_parachutes/integrating-a-drone-parachute
79. UAS recovery tutorial: https://fruitychutes.com/uav_rpv_drone_recovery_parachutes/uas-parachute-recovery-tutorial
80. DRS-25 parachute system: https://harrisaerial.com/drs-25-drone-parachute-recovery-system-15-25-kg-uav/
81. ScanEagle 150,000 hours: https://boeing.mediaroom.com/2009-04-13-Boeing-Insitu-ScanEagle-Logs-150-000-Service-Hours-in-Iraq-and-Afghanistan
82. ScanEagle 1,500 recoveries: http://www.globalsecurity.org/intell/library/news/2009/intell-090107-boeing01.htm
83. Drone impact energy transfer study: https://pmc.ncbi.nlm.nih.gov/articles/PMC12900295/
84. Aludra SR-10 parachute performance: https://files.core.ac.uk/download/478919988.pdf
85. Runway-free recovery methods review: https://www.mdpi.com/2504-446X/8/9/463
86. ViewPro Z40K manual: https://www.manualslib.com/manual/2385515/Viewpro-Z40k.html
87. Parachute repositioning event design: https://airborne-sys.com/wp-content/uploads/2016/10/aiaa-2009-2911_basic_design_of_a_reposit.pdf
88. UAV payload retraction patent: https://patents.justia.com/patent/11975867
89. ArduPilot landing gear retraction: https://ardupilot.org/plane/docs/common-landing-gear.html
90. NASA eVTOL propulsion reliability: https://ntrs.nasa.gov/citations/20240005899
91. Multi-rotor UAV fault tree reliability analysis: https://link.springer.com/chapter/10.1007/978-981-10-6553-8_100
92. ArduPilot thrust loss/yaw imbalance detection: https://ardupilot.org/copter/docs/thrust_loss_yaw_imbalance.html
93. ViewPro Z40K dimensions/specs (RCDrone): https://rcdrone.top/products/viewpro-z40k-4k-gimbal-camera
94. ViewPro Z40K manufacturer specs (ViewproUAV): https://www.viewprouav.com/product/z40k-single-4k-hd-25-times-zoom-gimbal-camera-3-axis-gimbal-uav-aerial-photography-cartography-and-patrol-inspection.html
## Related Artifacts
- Previous drafts: `solution_draft01.md` through `solution_draft04.md`
- Research artifacts: `_standalone/UAV_frame_material/00_research/UAV_frame_material/`