← back to work

SENTINEL 650 — Long-Endurance UAV

Founding and leading a 3-person team building a long-endurance ArduPilot UAV for civil surveillance. 28 INCOSE-traceable requirements, V&V plan, prototype in flight test.

SENTINEL 650 is a long-endurance UAV prototype I’m building with a 3-person team I founded. Mission: civil surveillance — search-and-rescue, infrastructure inspection, environmental monitoring. The platform is an ArduPilot quadcopter scaled for endurance, with a documented requirements baseline and a V&V plan you could hand to an aerospace systems-engineering lead and recognise.

28 INCOSE reqs
3 team members
EASA UAS A1/A3 + A2

What I own

End-to-end delivery: I converted the mission constraints and stakeholder feedback into a delivery roadmap, maintained the requirements traceability matrix (28 reqs → tests → flight cards), ran the weekly design-review cadence with the team of 3, and planned integration and field-validation readiness across flight control, telemetry, and mission payload.

Why systems engineering

Civil-surveillance UAVs fail in three ways: requirements drift between teams, integration surprises in the field, and fragile interfaces between flight control, telemetry, and payload. The INCOSE methodology addresses each of those failure modes head-on, so we adopted it before writing a single line of mission code. 28 traceable requirements isn’t bureaucracy — it’s how three people stay coherent across a multi-month build.

Status

Working prototype currently in flight test. V&V documentation lives in the team’s shared workspace (not public for IP reasons). Next milestones: 90-min endurance baseline, payload integration, and a field-trial brief in collaboration with a regional civil-protection partner.

Tools

ArduPilot · Mission Planner · Linux · INCOSE SE methodology · EASA UAS regulatory framework