Mobility technology / under evaluation
Ground First.
Flight When the Task Requires It.
GMAM is an air–ground mobility concept. We are evaluating selective flight only where it adds measurable operational value.
Concept evaluation / integrated driving and flight unvalidatedMobility should follow the mission.
For repeated observation and approach tasks, we are evaluating ground movement as the default. Flight is considered where a defined task cannot be addressed as effectively by a ground option or a separate drone.
Integrated driving and flight capability has not yet been validated. The public portfolio describes intended functions and decision gates—not manufacturing drawings or flight-control instructions.
Functional relationship / not vehicle geometry
One task.
Compare the options.
Ground operations as a proposed default. Selective flight is a research question, not a proven advantage.
The alternatives
Integration has to earn its place.
We are not assuming that a combined vehicle outperforms separate equipment.
Ground-only platform
A baseline for surface access, repeat observation and approach tasks.
Question: Is flight necessary for this task at all?
Separate UGV + UAV
A ground vehicle and an unmanned aircraft assigned to distinct tasks.
Question: Does separation reduce integration complexity?
Integrated GMAM
A combined mobility concept considered against the simpler baselines.
Question: Is any added value worth the added complexity?
Development logic
A decision framework, not a performance claim.
The comparison must be based on an agreed task and operating environment. Candidate measures include mission completion, operator workload, energy use, maintenance, controllability and safe interruption. No comparative advantage or target performance is presented as a measured result.
Our submitted development material includes conceptual mobility work and non-physical state-logic testing. Those activities do not establish flight dynamics, structural reliability or integrated field capability.
Public design boundary
Detailed mechanisms, dimensions and control algorithms are not included. A mechanism-level technical exchange requires prior review of disclosure scope, rights, confidentiality and applicable export controls.
Explore the validation gatesStart a focused conversation
Help define the useful integration question.
A 30-minute, non-confidential conversation about the use case, current assets and next development milestone.