Dear Techwinder,
I hope you are doing well.
I am currently working with Flow5 on a Three Surface Aircraft (TSA) configuration. The model is based on the default aircraft template provided in Flow5, with modifications applied only to the geometry. For this analysis, I am not including a fuselage.
I would like to ask about a behavior I have observed regarding the Cnb and Clb plots.
It appears that the signs of Cnb and Clb may be inverted in the way they are displayed. My reasoning is based on the following observations:
- When I increase the lateral surface area, Cnb becomes more negative while Clb becomes more positive. This trend would be physically consistent if the plotted signs were reversed.
- When I relocate the vertical surface to a position forward and below the center of gravity, both Cnb and Clb plots appear to invert. In this configuration, the aircraft seems statically stable according to the plots.
- However, in this second case, the spiral mode pole becomes positive, indicating dynamic instability, which was not present in the initial configuration.
This leads me to suspect either a sign convention issue or a possible misunderstanding on my side regarding how these coefficients are defined and presented in Flow5.
Additionally, I would like to better understand how Flow5 defines and handles multiple vertical surfaces. This question comes in part from my experience with XFLR5, where it is possible to define a single vertical tail entity, whether it consists of one or two physical surfaces. In contrast, it seems that Flow5 may treat lateral areas differently, which could be influencing the results.
I am particularly interested in:
- H-tail and U-tail configurations
- The use of dorsal fins
- Vertical surfaces located outside the main tail assembly
- Whether it is possible to model endplates in Flow5, and how they are interpreted aerodynamically
It seems that adding or modifying these surfaces produces unexpected effects on both Cnb and Clb, and I would like to better understand how their contributions are modeled.
Finally, regarding fuselage modeling: in configurations where vertical surfaces are not connected through a central fuselage extension, but instead mounted on twin booms, would it be appropriate to represent this by adding two slender fuselages? I would appreciate any guidance on how to best approach this type of configuration in Flow5.
Thank you very much for your time and for developing Flow5—it has been a very valuable tool in my work.
Best regards,
Sorendgy
Dear Techwinder,
I hope you are doing well.
I am currently working with Flow5 on a Three Surface Aircraft (TSA) configuration. The model is based on the default aircraft template provided in Flow5, with modifications applied only to the geometry. For this analysis, I am not including a fuselage.
I would like to ask about a behavior I have observed regarding the Cnb and Clb plots.
It appears that the signs of Cnb and Clb may be inverted in the way they are displayed. My reasoning is based on the following observations:
This leads me to suspect either a sign convention issue or a possible misunderstanding on my side regarding how these coefficients are defined and presented in Flow5.
Additionally, I would like to better understand how Flow5 defines and handles multiple vertical surfaces. This question comes in part from my experience with XFLR5, where it is possible to define a single vertical tail entity, whether it consists of one or two physical surfaces. In contrast, it seems that Flow5 may treat lateral areas differently, which could be influencing the results.
I am particularly interested in:
It seems that adding or modifying these surfaces produces unexpected effects on both Cnb and Clb, and I would like to better understand how their contributions are modeled.
Finally, regarding fuselage modeling: in configurations where vertical surfaces are not connected through a central fuselage extension, but instead mounted on twin booms, would it be appropriate to represent this by adding two slender fuselages? I would appreciate any guidance on how to best approach this type of configuration in Flow5.
Thank you very much for your time and for developing Flow5—it has been a very valuable tool in my work.
Best regards,
Sorendgy