• Announcements

    • turbofandude

      Proper Problem Reporting for the TFDi Design 717   07/09/2017

      Folks, As the user count is increasing, it is becoming more of a task for us to stay on top of problem reports. We are also receiving an increasing amount of incomplete reports that we are unable to follow up on (which frustrates everyone, us included). On that note, we are going to be enforcing a stricter formal problem reporting system. There are a few main points that need to be addressed. ALL problem reports must be submitted via the Bugs and Suggestions system. Open discussion on the forums is fine, but our team simply cannot respond to every single comment (especially when the majority of doing so is asking for information the Bugs and Suggestions system already asks for). Incomplete reports will be ignored. This means reports like "my FPS is bad" will not be given weight. This isn't because we don't care. It is because a report like that does absolutely nothing for anyone - we can't fix it based on that. Please include EVERYTHING you can possibly think of regarding the problem and take as many steps as you can to isolate it. Prepar3D v4, despite what you have heard, can still be unstable. Yes, it is definitely possible to fly flights without issues. But it is still relatively new, as are most of the addons available for it. Please refrain from attacking us or other developers because of this. We have already had one scenario where a 717 CTD was resolved by an update to Prepar3D itself. This is likely not the only time that will be the case. You are still free to report the crashes, as it may help whoever the developers of the faulting code are solve the issue. Duplicate reports will be deleted/merged. For the sake of sanity for us trying to prioritize and evaluate issues, if we discover multiple reports of the same thing, we may merge/delete the duplicates. We strongly encourage you to search and see if your problem has been reported before. Thank you all in advance. This may seem overbearing, but this is the only way we are going to be able to stay on top and continue heading in the direction we, and the community, want.
David Katona

Flex Temperature - 18.5 Engine Variant

Recommended Posts


I have uploaded the take-off performance figures into my database and prepared a simple website to calculate flex temperatures. Haven't had much time to test it, but if somebody wants to give it a go, feel free. Enter the ICAO code, runway heading and length. Click on initialise - this will download the metar and calculate headwind component as well as pressure altitude. Enter your Actual Take-off Weight, and if derated take-off is possible, it will offer the maximum Flex.
Flaps 13 only, and 18.5 engine rating (the higher variant is coming shortly, and engine anti-ice on calculations as well). Unfortunately I don't have data for other flaps settings than 13 degrees.

This tool can be found on www.wabpro.eu

Let me know if something doesn't look alright, it doesn't calculate, or if you overrun the runway :)




Screen Shot 2017-10-22 at 19.44.01.png

  • Like 1
  • Thanks 1

Share this post

Link to post
Share on other sites

There was an issue with the calculation getting stuck when the OAT wasn't a round number but had decimals. I have fixed that. 

Also, in a couple of days I am adding a new page to calculate ZFW CG and also to show MAC envelope.

If you have any ideas what might be helpful, just let me know and I will include.


Screen Shot 2017-10-27 at 12.54.39.png

  • Like 1

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now