Fiorentoni

For the route and weights below, according to Simbrief I should use about 4000kg more fuel with cost index 400 (compared to the CI 45 I did the original flight plan with). So trip fuel should be about 4-5ts more than on the screenshot. However, neither the fuel predictions nor the actual usage (!) increased during the flight with cost index 400. In other words: I was able to fly with cost index 400 and use about the same amount of fuel compared to cost index 45. EBBR/25L ROUSY2P ROUSY DCT GTQ DCT POGOL DCT LASAT DCT MOROK DCT GILIR DCT GEVEA DCT KOGAS DCT MEDAM DCT VEVAR DCT BARSO DCT KOLON DCT RARQU DCT NESUL DCT ETOIL DCT CIRTA UA605 DJA UB730 DIR UG862 BUN DCT ASEKA DCT MUBAK DCT EGREK EGREK1B HRYR/10 I can reproduce this on every flight. The highest (!) fuel usage actually comes with cost index 0. So there's something fundamentally wrong.

At MLW (190t) with flaps full, VREF should be 140 and VAPP 145. 132 knots should be VREF for about 20t less (so 170t ldg weight). How much did you have is the question. In general the A340 has large wings and will have a slower approach speed than one would think for such a heavy aircraft. Same for the A330.

I'm having the same problem on the intersection 04L/31L. PG is off. With PG on it's gone, but what is also gone is my framerate. I really think a big developer like iniBuilds should be able to fix this in 6 months. On one of their biggest / best selling sceneries. A bit disappointed here.

Most PBD waypoints I try do not work, especially with nav waypoints but also a lot of VORs. It says "Waypoint not in database". Sometimes using only the waypoint (without bearing and distance) works, sometimes not. E.G. VTK at WSSS works as a pure waypoint but not as a PBD.

(Copy from other thread) I had something similar happening after an entry in the FMC, all controls (knobs, dials, gauges etc.) became unresponsive (i.e. they turned, but nothing changed). What I did was entering a bearing/distance waypoint in the FPLN page, then deleting it with CLR, then deleting the disco. After that it locked up. All during cruise by the way.

I had something similar happening after an entry in the FMC, all controls (knobs, dials, gauges etc.) became unresponsive (i.e. they turned, but nothing changed). What I did was entering a bearing/distance waypoint in the FPLN page, then deleting it with CLR, then deleting the disco. After that it locked up. All during cruise by the way.

Since I like to fly real life routes with the appropriate aircraft, I probably wouldn't buy a A310F unless it's low-priced, but I surely would buy an A300F.