Proposed outcome
Build a 230-250 mm wheelbase development quadcopter that can be flown manually, hold position, execute a short geofenced waypoint mission, return or land on fault, and record enough data to explain every test.

Aerial robotics project
Build a roughly 9-inch (230-250 mm) motor-to-motor quadcopter with 5-inch propellers, PX4 flight control, telemetry, and a logged autonomous mission.
Build a 230-250 mm wheelbase development quadcopter that can be flown manually, hold position, execute a short geofenced waypoint mission, return or land on fault, and record enough data to explain every test.
Use a carbon-fiber 5-inch-prop frame with an approximately 9-10 inch motor-to-motor diagonal. A compact PX4-supported autopilot such as a Pixhawk 6C Mini, a matched 4S propulsion system, GPS/compass, telemetry radio, and independent RC link make the aircraft large enough to assemble and instrument without moving into heavy-lift territory.
Review the skills, goals, acceptance tests, and safety limits before committing to the build.
Parts are cumulative. Pass the exit gate before buying for or starting the next phase.
Learn PX4 flight modes, mission planning, geofencing, return behavior, and command-loss handling before selecting or powering hardware.
Complete ten simulated takeoff-hover-land cycles plus radio-loss, low-battery, geofence, and return-or-land scenarios.
Choose components as a matched system and document weight, voltage, current, mounting, connectors, and propeller clearance before ordering.
The proposal includes an all-up-weight estimate, thrust margin, peak-current budget, wiring diagram, connector list, and verified propeller clearance.
Build a serviceable frame, solder the high-current path, and verify power integrity without installing propellers.
Pass polarity, continuity, short-circuit, fastener, wire-clearance, strain-relief, center-of-gravity, and smoke-stopper inspections.
Install PX4, mount sensors away from vibration and magnetic interference, and establish independent command and telemetry links.
QGroundControl reports healthy sensors, calibrated controls, correct orientation, valid power readings, GPS lock outdoors, and a stable telemetry link.
Prove motor mapping, direction, actuator response, arming rules, and every automatic stop or recovery path before generating thrust.
Pass motor order/direction, arm/disarm, manual kill, RC loss, telemetry loss, low battery, estimator fault, and reboot-to-disarmed tests.
Perform conservative line-of-sight hover tests, confirm trim and stability, and inspect logs between every configuration change.
Complete five consecutive 60-second hovers and safe landings with healthy vibration, estimator, link, and battery logs.
Validate altitude and position hold, then progress from one waypoint to a short geofenced mission with return-or-land behavior.
Complete position hold, one-waypoint, multi-waypoint, geofence, and return-or-land tests without removing manual override.
Bridge vehicle state and bounded mission commands into ROS 2, record a rosbag, and run the same mission interface in simulation and hardware.
Complete at least four of five geofenced missions and publish the architecture, configuration, code, logs, plots, demo, and postmortem.
Use these established platforms, guides, and repositories to validate component choices and implementation details.
A 250 mm reference airframe in the same size class, available with Pixhawk 6C Mini, 2207 motors, 5-inch props, GPS, and telemetry options.
PX4's maintained documentation for the compact autopilot used as the proposal reference.
The open flight-control, estimation, mission, and failsafe software stack.
A MAVLink bridge commonly used to connect PX4 vehicles with ROS 2.
Current U.S. recreational flight, TRUST, airspace, registration, and operating guidance.
Links and recommendations reviewed July 10, 2026.
Compare the ground and aerial platforms before choosing where to invest your build time.