# Project Quiver - October 2026 Progress Report

**URL:** <https://dao.arrowair.com/t/project-quiver-october-2026-progress-report/194>\
**Category:** General\
**Created:** [November 7, 2026, 6:53pm UTC](https://dao.arrowair.com/t/project-quiver-october-2026-progress-report/194 "2026-11-07T18:53:20Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![errrks.eth](https://yyz2.discourse-cdn.com/flex004/user_avatar/dao.arrowair.com/errrks.eth/32/11_2.png) [@errrks.eth](https://dao.arrowair.com/u/errrks.eth)\
**Post date:** [November 7, 2026, 6:53pm UTC](https://dao.arrowair.com/t/project-quiver-october-2026-progress-report/194/1 "2026-11-07T18:53:20Z")

</div>

## 1. Executive Summary

October was Phase 2 of the roadmap, Attachments, and it did not go to plan. The aircraft crashed on October 6 when the kill switch was bumped during a return to launch, and it stayed on the ground until October 25. None of the three Phase 2 exit criteria closed, and the three Phase 1 criteria carried into the month stay open. This report doubles as the roadmap checkpoint, and section 5 states the rescope.

The month still moved the project. On October 1 the aircraft flew its first autonomous mission with avoidance active and returned to launch through obstacles on several flights. The obstacle avoidance payout terms were settled and the first tranche was paid. Julius completed the GPS replication test on his own build, which narrows the interference investigation to something the two affected units share physically. The crash repair took 80 minutes and produced a flight ready check, a wider crash inspection rule, and a kill switch guard. Build123d replaced Fusion as the CAD master, the Holybro NEO-F9P became the default primary GPS, and the team filled a Dev Kit v1.1 improvements board with 23 threads. One finding changes the product. The forward radar used in the avoidance campaign operates in a band that US rules prohibit aboard aircraft in flight, so US dev kits need a different forward sensor.

The treasury transfer arrived on October 6. The bounty reserve is whole again, the September retainer and retroactive grants are paid, and the multisig matches the ledger to the cent. No new funds are requested in this report. The next funding request publishes in the last week of November.

The team meets at the ranch in November for the open field avoidance test and the endurance flights. Its results come in the November report. The Dev Kit v1.1 change list is decided by the lead on the improvements board by November 30.

* * *

## 2. Project Progress

### Team Formation

No change from September. The Project Lead (errrks.eth) is the only retained contributor, at 20 hours per week. Julius, Zeynep, alperenag, Dow Fisher KBM, and 21stCenturyAlex are core contributors paid through the priced task board and monthly retroactive grants in $ARROW.

* * *

### Progress Summary:

**Treasury and payments:** The [September report](https://dao.arrowair.com/t/project-quiver-september-2026-progress-report/190) was published on October 5. On October 6 the treasury sent $29,520 USDC, the $35,520 approved in September less the November retainer. It refilled the $17,520 the bounty reserve had fronted for the July and August back pay and funded the September and October retainers. The September retainer and retroactive grants went out the next day as direct transfers, and the QGB-FLEX consolidation was booked on arrival.

**Obstacle avoidance (QGB-02):** The autonomous phase started on October 1. The aircraft flew a two waypoint mission in the backyard on the dense environment parameter set, with the second waypoint between two trees: both waypoints reached with no pilot takeover, 89 seconds in AUTO over a 21 m leg, the closest fused return never under 3.68 m. Eight flights flew that day, and on several a return to launch cleared trees on the way home. Zeynep adopted the values as the dense environment reference set. Flights on October 2 and 3 pushed into denser parts of the yard, and stop and slide held up as long as the space was not too crowded. One limit showed: nothing looks up, and one flight came close to a branch overhead.

The remaining test is the open field flight against set obstacles on the open terrain values. It was planned for October 6, did not fly because the aircraft was down from that day until October 25, and moves to the ranch. The payout terms were settled on October 8: the $4,000 splits 70/30 between the lead, who flew every test, and Zeynep, who wrote the test plan and reviews the logs. The first tranche, $2,800 for the ground, sensing, stop, and slide phases, was paid on October 27. The remaining $1,200 releases on the exit review against the 15 campaign criteria and the first obstacle detour mission on the flight tracking platform.

**Crash and repair:** On October 6 the kill switch was bumped while the pilot released the return to launch switch. On the three position switch only the run position keeps the main power relay closed, and the middle position cuts power like the full kill position. The aircraft fell from about 7 m. The visible damage was a snapped motor arm connector and a destroyed landing gear set. With the enclosure off, more appeared: bent cockpit support beams, a deformed battery wall, a damaged landing gear adapter, and broken enclosure mounts.

The repair waited 19 days on parts from ranch stock and on the lead’s travel. The work took 80 minutes on October 25, with $215.96 of parts at BOM prices. The check flight on October 26 was 4.1 minutes in LOITER. Motor balance and hover throttle matched the last flight before the crash. Vertical vibration peaked at 17.0 m/s² against 8.6 before, a watch item with three suspects: the enclosure not yet fully secured, the new connector without threadlocker, and the loose landing gear adapter. The team’s call on October 27 was to keep flying on the bent beams as a documented exception, since replacing riveted plates is harder than building a new chassis. Two more flights followed and are still to be uploaded. That brings the Houston unit to sixteen flights in October: twelve before the crash flight, the crash flight itself, and three after the repair.

Three things changed because of it. Every transmitter now carries a guard cover over the kill switch run position, written into the Pilot’s Handbook on October 8. A crash inspection now requires the main enclosure off. And the repair produced a flight ready check for use after any structural repair, plus a maintenance record for the unit with cost, parts, time, and checks.

**GPS interference (open item):** This gate did not close, and the evidence improved. Julius recreated the Houston operating setup on his own build and flew it on October 2 as task T-13. With the Ethernet switches installed and a live Mission Planner session over TCP, the M9N held 19 to 21 satellites. With the switches unplugged it held 24. The F9P read 26 to 32 throughout. So the switches cost that build about four satellites and it arms soon after power on, where the Houston unit needs about ten minutes and recovers only when the switches come out. Same parameters, same traffic, different outcome. That points away from the parameter set and from Ethernet traffic, and toward something the two affected units, wired and laid out the same way, share physically. The task was accepted on October 27 and paid.

Alex arranged a call with an outside GNSS specialist, whose first read was interference entering through the antenna. That leads back to the two fixes already on the table, relocating the module or shielding the switches, and the specialist was introduced to Julius. The bench test record gained a planned set of discriminator runs on October 27, each changing one thing to find what recovers the receiver: separate GPS power, the switches powered down, and the module moved on a longer cable. No analyzer measurement was taken in October.

**Forward radar and US rules:** Thomas found that the MR82 forward radar cannot legally fly on a drone in the US. It operates in the 76 to 81 GHz band, and [47 CFR 95.3333](https://www.ecfr.gov/current/title-47/section-95.3333) prohibits radar in that band aboard aircraft in flight. The FCC set the rule in 2017 to protect radio astronomy and restated it in 2024, with no waivers found. Even flight tests in the US need an FCC experimental license. Dev kits for the US therefore need a different forward sensor, and this joins GPS interference and avoidance clearance as a gate on US shipping. What can fly in the US is a 60 to 64 GHz radar below 400 ft, a 24 GHz radar certified under Part 15, a lidar, or cameras. The downward 24 GHz altimeter is not affected. The campaign results stay valid as engineering data for the avoidance logic. The replacement sensor is being chosen on the improvements board, and the team is working out what the rule means for the remaining campaign flight.

**Dev Kit v1.1:** On the October 1 call the team agreed the next hardware step is one more dev kit iteration, not a final version. Thomas set up an improvements board in the Arrow super app, which froze on October 14 with 23 threads and 32 positions, among them a lighter top cap and enclosure in ASA Aero filament, a machined attachment interface plate, battery voltage on the attachment ports, and relocating the M9N. The design review was not held in October. The lead now decides the v1.1 change list on the board, with an outcome recorded on every thread by November 30 and team input taken at the ranch where time allows.

**CAD and hardware baseline:** Thomas brought the Build123d model to parity with the last Fusion version, all 82 parts posed, and retired the Fusion master in [PR #266](https://github.com/Arrow-air/project-quiver/pull/266), merged October 24. [PR #267](https://github.com/Arrow-air/project-quiver/pull/267), merged October 30, makes the Holybro H-RTK NEO-F9P the default primary GPS with the Here4 as an option and retires the Wren Mini.

**Task board:** The Attachment Developer Guide (T-05) was closed at its first milestone on October 6: chapters 1 to 3 accepted, $200 paid, the $300 second milestone open for a new author. The GPS replication test (T-13) was accepted and paid. The V1 latch and camera information notes (T-11) got their final review on October 30, which opened the V2 latch and V2 camera tasks to claims. Ben took the task to configure a unit from the guide alone (T-16) on the dev kit in Los Angeles. The four open documentation pull requests got reviewers on October 27, each review priced at 427 $ARROW, the first board tasks priced in $ARROW.

The Platform Engineering Report task drew 24 automated applications and no credible one, so the lead writes it in November. Three lead tasks slipped. The configuration guide finalization (T-02) missed October 15. The flight campaign payment mechanics (T-17) were drafted on October 29, a month late, adopted by the lead on November 5, and merged with a team approval the next day, which closed the task. The QuiverHub bring up (T-18) ran past its October 10 date and the two hours priced. Alex posted the state on November 6: sessions on November 3 and 4 briefly connected the Hub development server, the companion computer, and the flight controller, then testing paused on an unstable development server and a manual companion install. He is moving the Hub to a local deployment with a single command install.

**Attachments:** This was the phase’s headline and it moved least. The interface replacement was not decided or ordered. What exists is a requirements draft written on October 29, the 12 V rail limit in issue #234, and the board threads. Thomas owns turning it into a specification, and a bounty is written against that specification. The V2 latch and V2 camera tasks opened on October 30 with a scope milestone due November 30, and each scope has to name the interface it targets, because the current plate is out of production.

**Endurance (QGB-03):** Nothing flew. The plan was posted on October 30: six flights at 0, 5, and 7 kg, each as a hover and as an autonomous figure 8 on a 300 m by 100 m course, every flight ending at the 25 percent battery stage. The flights are planned for the ranch, with heat checks by thermal camera between them.

**Community and prospects:** Alex introduced Frank as the lead engineer for the Lagos node, where the University of Lagos is drafting a memorandum for a six month pilot. Thomas suggested supporting the first builds remotely instead of shipping a unit, and nothing moves until the node has its licenses. Alperen brought a possible yacht delivery use case from Turkey, and Thomas took a call with an agricultural drone contact in Romania. A landing dock is being built at the ranch under Javelina Propeller Laboratory.

**Next, the ranch:** The team meets at the ranch in November with the Houston unit and the Los Angeles dev kit. The plan covers the open field avoidance test, the six endurance flights, the Starlink Mini retest, the dock landing test, and the configuration of the Los Angeles dev kit from the guide. The results come in the November report.

* * *

## 3. Documentation:

**Merged in October:**

- **CAD sync and Build123d as the CAD master** ([PR #266](https://github.com/Arrow-air/project-quiver/pull/266), Thomas, October 24).
- **Primary GPS options** ([PR #267](https://github.com/Arrow-air/project-quiver/pull/267), Thomas, October 30). Holybro NEO-F9P default, Here4 optional, Wren Mini retired.
- **Dead log links removed** from the PT1 flight test reports ([PR #244](https://github.com/Arrow-air/project-quiver/pull/244), Thomas, October 19).

**Merged on November 6:**

- **Dev Kit Engineering Report corrections** ([PR #275](https://github.com/Arrow-air/project-quiver/pull/275)), reviewed by KBM.
- **SDK guide network map and CubeNode addressing** ([PR #276](https://github.com/Arrow-air/project-quiver/pull/276)), reviewed by Alex.
- **Flight test campaign payment mechanics V1** ([PR #283](https://github.com/Arrow-air/project-quiver/pull/283), T-17), approved by KBM. See section 7.

**Published outside the main repository:**

- **V1 payload latch and V1 multispectral camera information notes** , final review committed to the [payload-systems repository](https://github.com/Arrow-air/payload-systems) on October 30.

**In review:**

| PR | Content | Reviewer | Status |
| --- | --- | --- | --- |
| [#273](https://github.com/Arrow-air/project-quiver/pull/273) | Baseline parameter files | Zeynep | No review yet. Gates the deviation pull request |
| [#274](https://github.com/Arrow-air/project-quiver/pull/274) | Pilot’s Handbook first field pass and the First Flight Checklist | Zeynep | Reviewed November 3, changes requested on four points, among them one flight mode map for every unit. Edits pushed November 7, second review pending |
| [#232](https://github.com/Arrow-air/project-quiver/pull/232) | Initial Configuration Guide | Held | Waits on the split and consistency pass (T-02) |
| [#270](https://github.com/Arrow-air/project-quiver/pull/270) | Attachment Developer Guide, chapters 1 to 3 | Erick | Milestone paid. Not merged, commits unsigned |

**Drafted in October, not yet in the repository:** the endurance test plan, the Maintenance Guide crash and repair additions, the Houston unit maintenance record, and the GPS discriminator runs.

**Still to come:** the deviation pull request after #273 merges, the Platform Engineering Report, and the obstacle avoidance campaign record after the ranch.

* * *

## 4. October Goals:

The September report set twelve goals for October.

| # | Goal | Status |
| --- | --- | --- |
| 1 | Close the obstacle avoidance campaign: open field test, QGB-02 payout terms, campaign record | 🟡 Payout terms settled, first tranche paid, first autonomous mission flown. The open field test did not fly and moves to the ranch, the record follows |
| 2 | GPS: analyzer measurements, replication flight (T-13), outside specialist, choose a fix, restore dual GPS | 🟡 Replication test complete and paid, specialist consulted, NEO-F9P set as the default primary GPS. No analyzer measurement, no fix chosen, dual GPS not restored |
| 3 | Merge the five documentation pull requests, open the deviation and Manufacturing Guide pull requests, finalize the configuration guide (T-02) | 🔴 None of the five merged in October. Two merged November 6, one reviewed with changes requested, two with no review. T-02 missed October 15. Three other pull requests merged |
| 4 | Receive the treasury transfer, refill the reserve, start the lead retainer, book the QGB-FLEX consolidation | ✅ $29,520 received October 6, reserve refilled, September retainer paid October 7, consolidation booked |
| 5 | Publish the flight test campaign payment mechanics (T-17) and make the first payments | 🟡 Drafted October 29, adopted by the lead November 5, merged November 6 (#283). No payment from the pool yet |
| 6 | Fly the endurance payload matrix and deliver the study (T-03, QGB-03) | ⚪ Not flown. Plan posted October 30, course agreed with KBM, flights planned for the ranch |
| 7 | Accept or bounce the Attachment Developer Guide milestones (T-05), reprice open tasks in $ARROW | 🟡 First milestone accepted and paid, second milestone open for a new author. Repricing started with the four review tasks only |
| 8 | Bring up QuiverHub on the Houston unit (T-18), scope its next milestones (T-12) | 🟡 In progress with Alex, past its date and the hours priced. Connections came up briefly November 3 and 4, testing paused. Next scope not written |
| 9 | Attachment interface requirements, Dev Kit v1.1 proposals, design review | 🟡 23 threads frozen October 14, requirements drafted October 29. Design review not held, the lead decides the change list by November 30 |
| 10 | Scope the V2 latch and V2 camera (T-06, T-07) | ⚪ Opened to claims October 30, scope milestone due November 30 |
| 11 | File the marketing discovery deliverable | ⚪ Not filed. Carried into the next funding period by decision |
| 12 | Run the roadmap checkpoint in the October report | ✅ Section 5 |

* * *

## 5. Roadmap Checkpoint:

The phased proposal made this report the checkpoint: exit criteria against the record, the retroactive grant request, task pool replenishment, the wind limit study renewal, and any Phase 3 rescoping. The roadmap changed materially, so this report is also the forum notice the proposal requires before Phase 3 spending continues.

**Exit criteria against the record**

| Phase | Exit criterion | Status |
| --- | --- | --- |
| 1, carried | Avoidance enabled flight flown | 🟡 Flown September 3, autonomous mission flown October 1. The campaign closes on the open field test and the exit review |
| 1, carried | GPS interference characterized and dual GPS restored | 🔴 Not met. Replication test done, no measurement, no fix applied |
| 1, carried | Documentation backlog merged to GitHub | 🟡 Two of five merged on November 6. One reviewed with changes requested, two with no review |
| 2 | Attachment interface redesign decided and replacement ordered | 🔴 Not met. Requirements drafted, no specification, no order |
| 2 | First attachment flying on the interface | 🔴 Not met. Written against the redesigned interface, which was never ordered |
| 2 | Endurance study delivered | 🔴 Not met. Plan posted, flights planned for the ranch |

Phase 2 closes with none of its three criteria met. The aircraft was down for 19 days, which blocked every item that needed a flight, and the interface replacement needed a requirements process the team had not run before, which started on October 1 and has not finished.

**The rest of the Phase 2 list**

| Phase 2 item | Status |
| --- | --- |
| V2 latch and camera, dispenser path, floodlight | 🟡 V2 tasks open to claims. Dispenser with Javelina. Floodlight not addressed |
| Starlink Mini telemetry on the side interface | ⚪ Retest moved to the ranch |
| Remote ID identity entry | ⚪ Waits on the FAA workstream under Javelina. Declaration of Compliance resubmitted in September, approval pending. No update in October |
| Compliance boundary for attachment changes under 55 lb | ⚪ Not delivered |
| Attachment Developer Guide | 🟡 Chapters 1 to 3 accepted, chapters 4 to 9 open for a new author |
| QuiverHub on the Raspberry Pi | 🟡 Sessions November 3 and 4, testing paused, moving to a local deployment |
| First deliberate autonomous mission, Handbook flight mode map | ✅ Mission flown October 1. One mode map for every unit decided in the Handbook review: ALTHOLD, LOITER, AUTO with RTL on channel 10 |
| Docking station go or no go | ⚪ Dock V0 under construction, landing test at the ranch |

**Rescope**

November was Phase 3, product definition and operations scale. It now finishes the flight and documentation work first.

- **In November:** the ranch campaign (open field avoidance test and QGB-02 closeout, six endurance flights, Starlink Mini retest, dock landing test), the Dev Kit v1.1 change list and the attachment interface requirements, the GPS measurement and a mitigation design, the documentation merges, second operator onboarding with Ben (T-16), and the Platform Engineering Report, now written by the lead.
- **Moved to the next funding period:** the interface specification, bounty, and order, the V2 latch and camera builds, the forward sensor selection for US units, the external demonstration of the agricultural surveying workflow, the reliability metrics page and the sales page (the $1,000 commercial readiness earmark stays held), and the marketing discovery filing ($375, carried).
- **Phase 3 items kept in November:** the product refinement scope, dev kit pricing with an updated bill of materials cost baseline, and the California dev kit disposition. The Project Lead owns the v1.1 scope: the board holds the proposals, the lead records an outcome on every thread by November 30, and the adopted list becomes the scope. The California dev kit is the Los Angeles unit Ben configures under T-16, and its disposition is decided once that task closes.

**Retroactive grants.** No new $ARROW is requested here. The September distribution drew on the held reserves and the October distribution does the same. The next allocation is part of the funding request.

**Task pool.** No replenishment is requested here. One surplus folds into QGB-FLEX unassigned at this checkpoint, as recorded in September: $450 from QGB-03, where the study was priced at $150 against $600. After the fold QGB-FLEX holds $4,489.17 unassigned, $300 of it priced to T-16 and T-18. The $250 from the Attachment Developer Guide reprice stays on its QGB-01 line for now. The pool is sized in the funding request.

**Wind limit study.** Not renewed. There is no flight dataset to analyze yet, and the $3,000 already moved into QGB-FLEX in September.

**Next funding request.** The current proposal funds the project through November 30. The next request publishes in the last week of November and covers the lead retainer, task pool replenishment, the retroactive $ARROW allocation, and a hardware line for the Dev Kit v1.1 work.

* * *

## 6. Goals for Next Month:

- Fly the open field autonomous avoidance test at the ranch, file the exit review, release the QGB-02 holdback, and publish the campaign record.
- Fly the six endurance flights and deliver the endurance study (T-03, QGB-03), with the heat check between flights.
- Run the GPS bench discriminators and the first analyzer measurements, design the mitigation, and restore dual GPS after a clean validation flight.
- Record an outcome on every Dev Kit v1.1 board thread by November 30, adopt the change list as the product refinement scope, and decide the attachment interface requirements.
- Publish dev kit pricing and an updated bill of materials cost baseline.
- Open the forward sensor selection task for US units.
- Merge the documentation pull requests still in review, open the deviation pull request, and push the configuration guide split and consistency pass (T-02).
- Take the team’s feedback on the flight test campaign payment mechanics (T-17), now published, and make the first payments from the pool.
- Close the open mechanical items on the Houston unit and recheck vibration on a full length flight.
- Write the Platform Engineering Report (T-09).
- Post the QuiverHub bring up result (T-18) and scope its next milestones (T-12).
- Configure the Los Angeles dev kit from the guide with Ben at the ranch (T-16) and decide the disposition of that unit.
- Publish the next funding request in the last week of November.

* * *

## 7. Budget & Resource Allocation:

**Team Members Compensation**

October is the second month under the restructure. One retainer, a priced task board paid on acceptance, and monthly retroactive grants.

**October 2026 - Total Budget: $6,000 USDC + 4,000 $ARROW, plus task board draws from funds already on the multisig**

| Category | Budget |
| --- | --- |
| Project Lead retainer | $6,000 USDC, on the multisig since October 6, paid in November for October’s work |
| Task board | Funded by the bounty reserve already allocated to the multisig, no new ask |
| Flight Test Campaign | 10,000 $ARROW (carried from April) |
| Retroactive Grants | 4,000 $ARROW from the 11,700 held in reserve, no new ask |

> **Disbursement status:** One transfer arrived and four payments executed in October, all verified on chain against the ledger: the treasury transfer ($29,520 USDC, October 6), the September retainer and retro batch ($6,000 USDC and 6,400 $ARROW, October 7), the Attachment Developer Guide first milestone ($200, October 7), the first obstacle avoidance tranche ($2,800, October 27), and the GPS replication test ($150 to Julius, October 30). The test instruments reimbursement ($645.16) followed on November 5. The October retainer, $6,000, is held on the multisig and pays in November. The November retainer, the last $6,000 of the $35,520 approved, has not arrived as of November 7. On that date the multisig holds $20,064.17 USDC and 21,700 $ARROW, matching the ledger to the cent.

**Obstacle Avoidance payout terms (QGB-02)**

Settled on October 8. The $4,000 splits 70/30 between the lead and Zeynep and pays in two tranches.

| Tranche | Covers | Erick | Zeynep | Status |
| --- | --- | --- | --- | --- |
| 1 | Ground, sensing, stop, and slide phases, closed in September | $1,960 | $840 | ✅ Paid October 27 |
| 2 | Autonomous phase closeout | $840 | $360 | 🟡 Held. Releases on the exit review against the 15 campaign criteria and the first obstacle detour mission on the platform |

**Grants & Bounties: the Task Board**

The March allocation of $26,240, plus the $726.94 surplus folded into QGB-FLEX in August, funds the board. $12,902.77 has been paid to date and $14,064.17 remains, all of it in cash on the multisig. $3,150 was paid from the reserve in October and $645.16 on November 5. The table shows the buckets after the checkpoint fold described in section 5.

| ID | Name | Reward | Status |
| --- | --- | --- | --- |
| QGB-01 | Documentation Wrap Up | $6,519.79 | 🟡 $4,169.79 paid. $2,100 open as priced tasks: configuration guide (T-02) $300, Pilot’s Handbook (T-04) $1,000, Attachment Developer Guide second milestone (T-05) $300, Platform Engineering Report (T-09) $500. $250 reprice surplus held on the line |
| QGB-02 | Obstacle Avoidance System | $4,000 | 🟡 $2,800 paid October 27, $1,200 held for the autonomous closeout |
| QGB-03 | Endurance Metrics Study | $150 (was $600) | 🟡 Study to KBM (T-03), flights paid from the campaign pool. $450 folded into QGB-FLEX |
| QGB-04 | Wind Limit Study | $0 (was $3,000) | 🔄 Consolidated into QGB-FLEX in September. Not renewed at the checkpoint |
| QGB-05 | Attachment Development | $3,000 | 🟡 V1 notes final, V2 latch and camera open to claims (T-06, T-07) |
| QGB-06 | Transport Case | $1,000 | ✅ Paid April 20 |
| QGB-FLEX | Open Bounty Bucket | $12,297.15 (was $11,847.15) | 🟡 $4,932.98 paid, $2,875 earmarked, $300 priced (T-16, T-18), $4,189.17 unassigned |
| QGB-FLEX | T-01 Battery Failsafe Review | $75 | ✅ Paid September 30 — Julius |
| QGB-FLEX | T-13 Ethernet Build GPS Test | $150 + one campaign flight | ✅ $150 paid October 30 — Julius. The flight pays 300 $ARROW from the campaign pool in the October batch |
| QGB-FLEX | T-16 Configure a Unit From the Guide | $200 | 🟡 Assigned — Ben, on the Los Angeles dev kit |
| QGB-FLEX | T-18 QuiverHub Bring Up | $100 USDC + $ARROW for the time beyond two hours | 🟡 Assigned — Alex. $100 USDC and the $ARROW both pay on completion |
| QGB-FLEX | Test Instruments | $645.16 | ✅ Paid — Erick, November 5, against receipts |
| QGB-FLEX | Operator Onboarding Fund | $1,500 | ⚪ Earmarked |
| QGB-FLEX | Commercial Readiness | $1,000 | ⚪ Earmarked — T-14 and T-15, scoped in the next funding request |
| QGB-FLEX | Marketing & Sales Page Discovery | $375 | ⚪ Carried into the next funding period |
| QGB-FLEX | Expense Reimbursements | $2,982.82 | ✅ Paid |
| QGB-FLEX | QuiverHub V1 Completion & Release | $1,080 USDC + 600 $ARROW | ✅ Paid in April |

**Retroactive Grants**

The September distribution, 6,400 $ARROW, executed on October 7, leaving 11,700 in held reserves. The October distribution below draws from them and executes after this report is published.

| Contributor | Amount |
| --- | --- |
| KBM | 800 |
| Alperen | 800 |
| Alex | 800 |
| Thomas | 600 |
| Julius | 600 |
| Zeynep | 400 |
| **Distributed** | **4,000** |
| Held in reserve | 7,700 |

Board work paid in $ARROW draws on the same reserves in the same batch, listed separately here. The QuiverHub time beyond the two hours T-18 was priced for pays when the bring up is complete.

| Task | Reviewer | Amount | Status |
| --- | --- | --- | --- |
| T-19, review of #273 | Zeynep | 427 $ARROW | ⚪ Review not submitted |
| T-20, review of #274 | Zeynep | 427 $ARROW | 🟡 Complete. Submitted November 3, accepted November 7, payable |
| T-21, review of #275 | KBM | 427 $ARROW | 🟡 Complete. Reviewed October 29, approved November 6, payable |
| T-22, review of #276 | Alex | 427 $ARROW | 🟡 Complete. Approved November 6, payable |
| T-18, QuiverHub time beyond two hours | Alex | 427 $ARROW per hour, one hour so far | 🟡 Work continuing. Paid on completion, not in this batch |
| **Payable in this batch** | | **1,281 $ARROW** | T-20, T-21, and T-22 |

**Flight Test Campaign: 10,000 $ARROW**

The pool stays held on the multisig, undistributed. The payment mechanics were adopted by the lead on November 5 and merged on November 6 with a team approval ([PR #283](https://github.com/Arrow-air/project-quiver/pull/283)). They are [published in the repository](https://github.com/Arrow-air/project-quiver/blob/main/docs/Operations/flight-test-campaign-payment-mechanics.md), open to revision on team feedback, with the differences from the task as written listed on [T-17](https://github.com/Arrow-air/project-quiver/issues/263). A campaign flight pays 300 $ARROW once validated on the flight tracking platform. A free flight pays 10 $ARROW per logged minute from five minutes up, to a maximum of 150. Milestones pay once per operator, such as a first flight, ten clean flights in a row, and a new endurance record. One operator can draw at most 2,500 $ARROW per funding period.

**$ARROW remaining after the October batch: 16,119, with 6,419 in held reserves and 9,700 in the flight test campaign pool.**

| Draw | Operator | Amount | Status |
| --- | --- | --- | --- |
| T-13 replication flight, flown October 2 | Julius | 300 $ARROW | 🟡 Payable in the October batch. A 28 second hover, under the 60 second floor, flown and accepted before the mechanics existed, paid once as a stated exception |
| Endurance matrix, six campaign flights (T-03) | Erick | 1,800 $ARROW | ⚪ Planned for the ranch. Paid after KBM confirms the six logs |
| **Pool after both** | | **7,900 $ARROW** | |

**Total:**

The multisig holds $20,064.17 USDC ($14,064.17 bounty reserve plus the $6,000 October retainer) and 21,700 $ARROW (11,700 held retro reserves plus the 10,000 flight test pool). $29,520 arrived in October and $9,150 left, with the $645.16 instrument reimbursement following on November 5. The $6,000 November retainer is still to come from the treasury. No new funds are requested in this report. The next funding request publishes in the last week of November.