THE DIRECT ANSWER

Counting rotors or motors does not establish how an aircraft behaves after a failure. Ask for evidence about the whole system, the failure conditions assessed and the limitations of any emergency capability.

More components raise more questions

Our research framework asks whether nominally separate components depend on shared power, software, sensing or structure. The relevant question is what the documented system assessment covers, not whether a brochure uses the word “redundant.” We do not infer independence from a diagram or photograph.

Keep regulatory categories in view

EASA publishes systems and failure-condition requirements for small-category vertical-capable aircraft. Its framework distinguishes categories and their safety objectives. This European reference illustrates why the category and conditions matter; it is not a U.S. approval or proof that any aircraft meets the requirements.

Emergency claims need boundaries

For any claimed emergency feature, request the documented operating envelope, conditions, crew actions and supporting evidence. Ask which phases of flight it covers. A generic statement about a backup system cannot establish the outcome in every situation.

Do not turn a web guide into a procedure

We provide questions for evaluating documents, not instructions for handling failures. Approved aircraft procedures and qualified type-specific instruction govern that task. Record unresolved questions in the evidence checklist rather than converting them into a guessed score.

Sources & context

Reviewed September 23, 2026. These sources support the distinctions explained above; they do not endorse this publication. Our research questions are editorial suggestions.