VTOL Aircraft Case Studies

Completed reports

VTOL Aircraft Case Studies

Structured case reports that separate confirmed evidence from what still needs bench proof.

These examples are not donor files to copy blindly. They show how Arimota turns parameter evidence into a safer props-off verification plan before another retest.

Case 01

Heewing Ranger T1 VTOL — Stable Baseline Configuration Profile

Airframe & Hardware Setup

Lift-plus-cruise VTOL reference aircraft with a known-good parameter export used as a comparison baseline for grouped review lanes.

Observed Symptom

No active instability in the reference file. The value of the case is stable behavior that can be contrasted against a problem aircraft without assuming the hardware is identical.

Parameter File Clues

Orientation, VTOL enablement, output ownership, transition lanes, and failsafe structure read as internally consistent. No obvious mismatch was found between hover-motor roles and fixed-wing forward-thrust ownership.

Bench Verification

Use the file as a checklist source only: confirm controller orientation, control direction, output mapping, tilt geometry, and failsafe paths on the actual baseline airframe.

Controlled Retest Result

The baseline remains the comparison reference because its setup lanes support orderly hover and transition review. It should guide fault isolation, not blind value copying.

Case 02

ZOHD Altus Forward-Pitch on Takeoff — Resolution of Output Ownership & Tilt Reversal

Airframe & Hardware Setup

Problem aircraft reviewed against a known-good VTOL reference after unstable forward-pitch behavior raised immediate flight-safety concerns.

Observed Symptom

The aircraft pitched forward during takeoff attempts and did not present as a normal tuning-only problem. The behavior indicated a likely ownership, geometry, or correction-direction fault lane.

Parameter File Clues

Comparison signals pointed toward output ownership and tilt direction mismatches before gains became the leading suspect. The ranked differences concentrated around hover-related control authority rather than cosmetic tune drift.

Bench Verification

Props-off checks focused on actuator direction, tilt-servo travel, neutral geometry, and which outputs actually owned hover thrust versus forward-thrust responsibilities.

Controlled Retest Result

The safe resolution path was to clear output ownership and tilt reversal first, then move to short logged retests. The case demonstrates why blind tuning would have hidden the real fault lane and increased crash risk.

Use the pattern

Turn another unstable aircraft into a bounded review problem

When a current aircraft diverges from a known-good reference, compare grouped setup lanes first and leave gains until orientation, outputs, and geometry are proven.