This vote is to approve or reject the creation and initial funding phase of the ‘Project Quiver', as proposed here.

If approved, an amendment to AIP-007 would be made to add ‘Project Quiver’ to the list of projects. It’s current status would be listed as ACTIVE along with relevant information such as project lead, funding status, spending caps, start and expiration dates.

1. Project Summary

Project Quiver is a multi-purpose multi-rotor electric vertical take-off and landing (eVTOL) unmanned aerial vehicle (UAV). The project aims to develop an aircraft compliant with Part 107 of the Federal Aviation Regulations (FARs), featuring a universal attachment interface that allows users to integrate various payloads and mission-specific equipment without custom modifications. The project team has successfully designed, built, and flown its first and second prototypes, demonstrating real-world capabilities.

2. Project Requirements

The project requirements were agreed upon by the community before the project started.

Project Requirements

3. Project Scope

3.1. Prototype Development and Enhancement

• Incrementally develop and enhance prototypes focusing on structural refinement, weight reduction, and integration of innovative and reliable technologies.

3.2. Advanced System Integration

• Integrate precision navigation systems, standardized payload connectors, automated mission planning, and custom electronic components to improve operational efficiency and reliability.

3.3. Manufacturing Readiness and Scalability

• Optimize airframe design for production, facilitate decentralized manufacturing, and conduct Design for Manufacturing (DFM) reviews to ensure cost-effectiveness and scalability.

3.4. Testing, Validation, and Product Life Cycle

• Execute rigorous ground and flight testing, including decentralized flight campaigns, to validate performance, safety, and component durability. Continuously refine designs based on operational feedback.

3.5. Market Entry and Commercialization

• Prepare the product for commercial distribution, including branding, packaging, and user manuals.

4. Project Timeline

Phase 1: Prototype #3 (PT3) (April-May 2025)

• Waterproof & Dustproof Cockpit
• Customized Transport Case
• Foldable / Retractable Landing Gear
• Incentive Programs for Enlarging Attachment Library
• Standardized Mission Attachment Connector
• Minor Flight Mission Planning & Automation
• RTK & Precise GNSS
• PCB for Kill Switch
• Refined Structure for Weight Reduction
• Open Source Structural Components
• Review & Fixes from Previous Prototypes

Phase 2: Prototype #4 (PT4) (June-October 2025)

• Promotion of In-House Custom Motor & ESC Programs
• Finalized Airframe Design
• Major Flight Mission Planning & Automation
• Revised Remote Controller with LCD Screen
• Promotion of Custom Ground Station Software Development
• Initialization of Decentralized Flight Test Campaign
• Product Life Cycle Testing for Components
• DFM Review
• Review & Fixes of Previous & Current Prototypes

Phase 3: Productification (November-December 2025)

• Kit Development
• Branding & Aesthetics
• User Guide / Flight Manual
• Sale of 10 UAV Kits

5. Budget Cap

The project requires a budget to compensate skilled engineers specialized in research and development, real-world hardware testing, prototype construction, and flight tests.

• Labor Costs: $35,000/month
• Hardware Costs: $10,000/month
• Total: $45,000/month

Labor and hardware-related expenses will vary from month to month; thus, the stated budget includes a margin. Actual monthly expenses are expected to often be lower, around $40,000/month. The project will end at the end of 2025.

During Phase 2, activities related to promoting custom motor, ESC, and ground station software development programs are not included in the project budget. Additional funding is likely to be required for the decentralized flight test campaign in Phase 2.

A multisig wallet will be established after approval to receive funds. The seats on the multisig will be; Project Lead (alperenag) and GBC.

6. Governance

Project Charter

This document will be presented in the GitHub repository upon project approval.

7. Project Lead

I, alperenag, will be responsible for leading the Project Quiver team, overseeing the technical direction, coordinating development activities, and ensuring successful achievement of milestones and objectives.

8. Project Team

I, alperenag, will assemble the project team under the approved Project Quiver budget upon project approval.

9. Deliverables

• Prototype UAVs: Development and refinement of UAV prototypes through each project phase.
• Engineering Reports: Prepared for each major milestone, clearly outlining technical specifications, decisions, and current project status.
• Design Files: CAD models, PCB layouts, and software repositories accessible for community collaboration.
• User Guide / Flight Manual: Comprehensive manuals detailing UAV operation, maintenance, and troubleshooting.
• Manufacturing Guides: Up-to-date instructions & bill of materials enabling community-built prototypes.
• Meeting Summaries: Documentation of meeting attendance, key decisions, and action items recorded and shared via GitHub.
• Structured Documentation: Documents assigned unique identifiers for transparency, consistency, and version control.
• Operational UAV: Development of a commercially-usable, lightweight, long-endurance, and energy-efficient multi-rotor UAV ready for diverse operational scenarios.