May 24th, 2013, 13:46
Part of the issue is how knowledgeable the model designer is about the meaning of those speeds when translating from sometimes very inexact historical data. Innumerable sources quote simply one 'max speed' (not even specifying KIAS, KTAS, MPH) and certainly not recording whether this was "max. attainable speed in level flight" or design Vne. Often a modeler will not question or cross-check this data and simply "makes it so". In fact some of the historical data from the WW II era was deliberately vague in this regard for propaganda purposes. However, we have found examples where Vne was used in the .cfg file, but then the model was tweaked to allow it to reach toward/near this in powered level flight, not just as a limit in a dive. Alternately, aircraft models that can reach real-world Vne (interpreted by the modeler as "max. speed" - level) in level flight then have a .cfg limiting speed much higher to enable speed to increase in a dive. These anomalies don't always show until the model is flight tested against r/w data. Others have more-or-less accurate numbers but the model has been crafted to reach that number at the worst altitude and thus is far too fast at Sea Level.
For things like the events of which Paul speaks then would require corrections to be made (and somehow enforced) or the model rendered unacceptable since there is no current way to monitor changes or accuracy of an individual's flight model.
While I agree that it would be useful to be able to decompile the data from the tables, building a tool to do so might be more hours of work ( P likes to play with data :icon_lol: ) than the flight testing if done on an ongoing basis.