Jump to content

voske

Members
  • Content Count

    231
  • Donations

    $25.00 
  • Joined

  • Last visited

Posts posted by voske


  1. I have the exact same issue after updating AILG. I noticed today in the PSXseeconTraffic log file that a lot of options were removed because of non-cargo aircraft at cargo positions, but checking the aircraft they all have the line "atc_parking_types=CARGO".


  2. 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).

    • Like 1

  3. 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.


  4. 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.

    • Upvote 1

  5. 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.


  6. 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.


  7. 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.

×
×
  • Create New...