Mass & payload
How added weight changes endurance, response, and the energy required to stay airborne.
FLIGHT DYNAMICSLearning how things fly by changing one variable at a time, measuring what happens, and building on what the data says.
PhysicsFlight investigates how measurable changes in a flight system affect the way it behaves.
How do mass, center of gravity, propeller configuration, drag, and battery state change a drone’s flight?
A working question, answered through controlled experiments—not assumptions.Change a single variable.
Capture conditions and response.
Look for patterns in the data.
Refine the next experiment.
A starting point for repeatable tests and useful comparisons.
Establishing a consistent reference flight before changing the configuration.
What does a repeatable baseline flight look like?
Flight time, battery state, stability, and configuration.
Controlled route and conditions to be documented.
Developing the protocol. No results recorded yet.
Focused questions that can grow into individual experiments as the project develops.
How added weight changes endurance, response, and the energy required to stay airborne.
FLIGHT DYNAMICSWhat happens to balance and control when the distribution of mass shifts.
STABILITYExploring the relationship between propeller configuration, battery state, and useful flight time.
POWER SYSTEMSTesting how physical configuration influences resistance and flight behavior.
AIRFLOWEvery test deserves a record. This is where conditions, configurations, observations, and findings will live.
Configuration and conditions to be documented
To be defined after the baseline
↳ Planned work, not flight records. No test flights have been logged here yet.
A place for measured values and clear comparisons once flight testing begins.
Values intentionally blank until measured.
PhysicsFlight is an ongoing independent engineering investigation. It brings together applied physics, aerospace thinking, experimental design, coding, and data analysis to ask better questions about flight.
The work is simple in principle: build, test, document what happened, and use it to make the next test better.
Back to top