Hello sir, thanks for answering.

I will try and explain how I do it, and then you can perhaps tell me what I am doing wrong and why?

I almost always use real world SOP from two particular company provided. One for Boeing 737-800 and one for Airbus A319/A321

Now I use a tool to estimate the ball park of enroute distance and time. Here is a link to it Flight Manager: Worldwide provider of international trip support and corporate flight handling tools & services.

This gives me an idea on what to set as scheduled time and in the example of ENGM to ENBR as inducated as “very short” in your feedback, it plays out like this.

- According to Flight Aware the real flight time is as low as 0:34 minutes and as high as 0.55 minutes.

- All depending on weather, traffic etc. We all know this.

- When entering ENGM - ENBR with the ground speed of 450 into this tool, you get 0:38 minutes including 15 minute bias on ground.

- That is pretty realistic and I have as mentioned use it as a ball park to estimate enroute time

So let me use Simbrief example

Scheduled time is generated to 1 hour 10 minutes:

Taxi out = 15 minutes

Taxi in = 10 minutes.

Taxi out on ENGM does not alot more than 5 minutes, less than or equal to 5 minutes at ENBR

Deduct 10 minutes from ENGM

Deduct 5 minutes from ENBR

= 15 minutes deduction

So basically, the logic is that you then deduct 15 minutes from scheduled time = 0 hour, 55 minutes

Correct so far?

Well what I do is this:

Take the time of 0:38 provided by the time and distance calculator which include 15 min bias

Set that as scheduled time

Since TAXI in and TAXI out is already set to 15/10 per default in Simbrief, ill just deduct 5 minutes from TAXI in time.

Now deduct those 5 minutes from scheduled time (which already include 15 minutes aka taxi out)

it results to 0 hours 33 minutes which is darn realistic in terms of time real world

Now the funny part is this…

It does not matter if I choose ENGM to ENBR or ENGM to what ever place in Europe, I always get CI 80 when choosing Boeing 737-800 and 60 when choosing A319 for example.

Am I completely wrong or is there any possibility there is a bug or broken logic somewhere? Could it be something with the stored aircraft profiles I am using, which by the way is created based on real world weight data.

Cheers

Tom