voske

You’ll probably have to cool the brakes first. FS Actions -> Ground Maintenance.

I am pretty sure that you can paste the password using the right mouse button (Ctrl + V didn’t work). 

Navigraph has some parking stand charts for the 748 or type F aircraft in general (for example EGLL 10-9C2, EDDF 10-9C3). In some cases the 748 taxi map will show the available stands (for example KMIA and KLAX). If those charts aren't available, I'd probably use Flightstats or Flightradar24 to lookup the real world gate used. Of course, you can always change the maximum allowed wingspan for a stand in GSX (page 30 and 34 of the manual).

That plan definitely came from Flightaware. I’ve seen numerous flight routes that started with such PBD-waypoint on Flightaware. I’m not sure why, but my guess is that it might be related to aircraft being vectored on departure instead of following a published departure procedure.

The MyTraffic 6 scenery files could be the cause of the issue. See for example http://www.fsdreamteam.com/forum/index.php?topic=16177.0

My guess is that you didn't switch the fuel crossfeed valves 1 and 4 to on (the unguarded fuel crossfeed switches) before the flight. As a result, Main Tank 1 was supplying engine 1, Main Tanks 2 and 3 (and the Center and Stab Tanks if they contained any fuel) supplying engines 2 and 3, and Main Tank 4 supplying engine 4. However, Main Tanks 2 and 3 can hold much more fuel than Main Tanks 1 and 4. Therefore, you have to switch the crossfeeds valves to on to use Main Tanks 2 and 3 (and Center and Stab Tanks) to supply engines 1 and 4 with fuel if you depart with more than 54.400 kgs / 120.000 lbs of fuel.

www.simbrief.com

Perhaps it has something to do with the fact that the Scandinavian countries and some other European countries have switched to Free Route Airspace: http://www.eurocontrol.int/articles/free-route-airspace

Btw, a good source for real world European flightplans is www.edi-gla.co.uk/fpl Registration is required but it's free. 

I had the exact same issue on my first flight after installing the update. After completing the flight I started the OC and got the option to install the update (again). Tried to install it, but same result upon restarting the OC. Before another attempt I deleted the short and long panel states (which still had the same datestamp as the default and Cold & Dark panel states). I tried to install the update again, and this time it was succesful.

There’s a number of maps of routes on http://www.cbi-theater.com/ under ATC Air Routes, in particular http://www.cbi-theater.com/maps/map1118.html

Also: http://www.cbi-history.com/cbi_air_routes.html

Interesting issue that I noticed today in the 737-700:

Before takeoff I entered a flight level for a step climb on the CRZ page. After takeoff I noticed that the 250/10000 wasn't followed by the AP and the CLB page showed a dotted line below SPD REST. Solved the issue with speed intervention. During the flight I performed the step climb, but I did not clear the field on the CRZ page. While doing the descent preparation, I noticed ---/----- below SPEED REST on the DES page. Entering 240/10000 and pressing Execute resulted in the same dotted line. However, clearing the STEP field on the CRZ page resulted in 240/10000 showing up on the DES page below SPEED REST. Just to be sure that I didn't make this up, I tried to replicate the issue and it did occur every time I entered a flight level for a step climb on the CRZ page.

I'm having the exact same issue, but in my case the radar screen is stuck. Restarting RealTraffic fixes the issue for a while, then it wil stop updating again.

11 hours ago, threegreen said:

Between the KRUGG IAF and the FAF are two waypoints, EFEXX and ZESTY. The approach chart shows no altitude for EFEXX but 4000 for ZESTY. The FMC showed 6000A for EFEXX and 4000A for ZESTY 

The segment between KRUGG and EFEXX has a minimum altitude of 6000 according to the chart. That's the reason why the FMC shows 6000A at EFEXX.

Perhaps it's caused by a corrupt panel state file. That was mentioned as a possible cause in a thread about the 777:

5 hours ago, Stingray said:

On the other side my engine trouble continues.

Did you switch from low blowers to high blowers?

Good luck. Just make sure you slow down at cruise altitude. With a 1000 BHP cruise you might make it (Simbrief comes up with a trip fuel of 19663 lbs). Browsing through historical timetables, I noticed that often flights from KJFK to EGLL made a fuel stop at either CYQX, EINN or both. 

In addition, there are two different fuel tank layouts for the DC6: with 8 or 10 fuel tanks. The PMDG DC6 as 8 fuel tanks which obviously limits the range.

The issue might be with PFPX or the data input in PFPX. I tried Simbrief with the following data:

KMSP-TNCM, alternate TIST

RST8 ALO DCT KK57K DCT KM45M DCT BNA J45 MCN DCT OMN Y585 ELMUC L451 SLUGO A638 PJM

Cruise: 1000 BHP

ZFW: 69968 lbs

Altitude: 11000

The result was a trip fuel of 16706 lbs and 9h41m of air time, which leaves sufficient room for alternate, contingency and reserve fuel.

Press Abort on the AFE screen.

On Friday I completed both tutorial flights without any issues.

On Saturday morning I had CTDs at EHAM during taxi or during takeoff (if I skipped the taxiing), but no errors showing up in AppView.

I had the throttle setup in FSUIPC. Removing the ini file and setting up the throttle in P3D didn't solve the issue: another CTD on takeoff. Deleting the throttle axis and using keyboard and mouse to control the throttle so far solved the issue for me (so far).

2 hours ago, beachdog2001 said:

I think the tutorial waypoints of the ILS 34L aren't in P3Dv4 or the GPS

They are. When you push PROC on the GPS you can load an approach which will add those waypoints to the flightplan.

Were the packs on/auto and the engine bleeds on?

If so, I'd consider the option of a corrupt panel state file.

5 hours ago, gregmorin said:

Thank you for your suggestion.

You're welcome. I'm glad you got it solved.

Do you have hardware brakes? If so, you might Perhaps be able to confirm whether or not they're the source of the issue by disconnecting them and doing a flight without them connected.

It landed at San Bernardino (SBD).

Something else you could try: