Request a VTOL Review
Send the aircraft details, files, and symptoms needed for a useful review.
Use this intake path when you need a configuration review, a known-good comparison, or a post-incident troubleshooting pass grounded in the actual aircraft files and evidence.
Choose the review that matches the aircraft problem
Parameter file review
Focused on one aircraft and one current configuration when you need a grounded first-pass setup check.
Known-good vs problem comparison
Best when there is a stable reference aircraft and a current unstable setup that needs to be compared lane by lane.
Crash or incident follow-up
Centered on symptoms, setup history, recent changes, and the next safe verification steps before another flight.
Start with the details that make the first review useful
Aircraft and electronics
- Name and email
- Aircraft model and airframe type
- Flight controller and firmware version
- Receiver and transmitter
- GPS / compass hardware
- ESC, motor, and servo setup summary
Review evidence
- Problem description and when it happened
- Known-good parameter file when available
- Problem-aircraft parameter file
- Logs, photos, or wiring diagrams
- Bench-test notes and requested review type
Do not refly to gather more evidence
If the aircraft already showed unstable hover, bad transition behavior, wrong control direction, or a hard landing, start with a props-off bench check instead of another flight. Good review intake reduces risky guesswork.
Use the contact form and attach the current parameter file when you have it
The current Contact Form 7 path stays active here. Use the checklist above so the review starts with useful aircraft details, actual files, and the symptom summary instead of a long clarification loop.
Accepted parameter-file formats: .param and .parm, matching the VTOL parameter tool.
Attach the current problem-aircraft export first. If you already ran the parameter tool, attach the saved result report too. If you do not have a current export yet, say that clearly in the message instead of uploading a random text file.
What happens after the form is submitted
A useful first pass starts by checking the aircraft identity, firmware, parameter files, and symptom history for obvious setup risks. If those basics are in the message, the review can begin with real evidence instead of a generic back-and-forth about what aircraft is on the bench.
When the review is finished, the completed result is archived under a unique date code. Raw submitted parameter files are not retained as the long-term record once the review is complete.