Jump to content

roundy

Members
  • Content Count

    26
  • Donations

    $0.00 
  • Joined

  • Last visited

Posts posted by roundy


  1. I'm running P3D v3.2 and can't get the slew command to respond. As a matter of fact, when I check the control list there are only 3 slew commands listed: Slew on/off (Y), Slew tilt left and Slew tilt right with out any keys assigned.

     

    I'm sure that it's mentioned somewhere in the forum but I couldn't find it.

     

    If anyone has any suggestions I would appreciate hearing them.

     

    Thanks,

     

    Don Bohr


  2. I've had good luck finding multi-stop flights by going to Flight Aware and searching a major Southwest Airlines hub under Airport Activity. Select a Southwest flight and you'll sometimes be suprised how many airports a single flight number will visit in one day. For instance, enter KJAX and the click on SWA 1783. That flight will visit 7 airports before the day is done.Good Luck,Don Bohr


  3. First of all, PMDG is to be congratulated for the excellent job done on the new B747-400X. I particularly like the new views and sounds that were built into the model. The aircraft is a pleasure to fly and to look at.However, there seems to be a problem in the LNAV/Navigation Display. My first flight in the


  4. I'm having the tracking problem also. I noticed it on my first flight with the 400X on a flight from KSFO to PANC. Here's the scenario:B747-400XFFlight plan entered manuallyWeather set to clear (no wind)The aircraft flew over every fix and then started to turn. After initiating the turn it continued to diverge from the course line (sometimes as far as 8.8 nautical miles) than it slowly began to converge and reached the course line at the next fix where the whole process started over again.It seems to me that the FMC commands the aircraft to fly-by a fix instead of fly-over a fix. After the fly-by the logic appears wrong in that it does not command the aircraft to intercept the course and/or airway.I haven't done the same flight in FS9 but will in the near future.Don B.


  5. I would guess the "Expect" altitudes are placed on an STAR because ATC issues those altitudes a great majority of the time, maybe as high as 90%. There may be occassions when a different altitudes are assigned (pilot request, slower traffic on the STAR, etc.) but I would bet that the assigned altitude would be higher, rather than lower, than 10,000. I just did some flight plan checking and it looks like the MIP STAR is a heavily used route from ORD with aircraft entering the STAR from over Keating (ETG).What we need is for someone to go to Chicage, buy a ticket on UAL to LGA, tune in Channel 9 on the Inflight Entertainment System, and take notes. I'd go myself but it looks much to cold in the east for this California boy. :-sun1 Don


  6. Michael:I now see what you were trying to explain. We were working on different sides of the same page.I find it easier to amend the procedures myself, either through the FMC or within the SIDSTAR database. I've run into several other errors, the LOOP departure off LAX being a prime example. Eventually I'll get around to fixing the ones I know are wrong.Merry Christmas and a Happy New Year.Don


  7. Michael:I hate to disagree, but there is no "at or above" 8000'on this STAR unless it is assigned by ATC for ATC reasons only. Pilots cannot arbitrarily use 8000'. Every altitude will be assigned by ATC. If ATC doesn't assign 8000', an aircraft cannot fly at that altitude. Note the restriction on the STAR: "For aircraft capable of 210K IAS or greater", therefore, in all likelyhood, this is a turboprop/turbojet STAR only and these aircraft will be descending for high altitude and not anxious to use 8000'.If Terry doesn't amend the STAR, I can do it and forward it to you.Don Bohr

×
×
  • Create New...