Jump to content

rsvit

Members
  • Content Count

    553
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

16 Neutral

About rsvit

  • Rank
    Wingleted

Profile Information

  • Gender
    Male
  • Location
    UKBB

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    Other
  • Virtual Airlines
    No

Recent Profile Visitors

866 profile views
  1. Try pushing CLR button, if not working, check this page. https://support.precisionmanuals.com/kb/a92/dll_xml-information-and-troubleshooting.aspx
  2. Can you point out some rading on this topic? Curiuos case.
  3. So you say it makes a turn with autopilot already off? By most SOP you must turn autopilot off not sooner than MDA minus 50'. Especially it's important for backcourse approach, when you have to overfly localizer, at this point signal is lost, because LOC doesn't beam upwards (maybe there is some protection in real autopilot, which willl force the plane to keep wings level). "Just before the touchdown" AP disengagement will be right in this zone, so fly manually earlier. IIRC NGX is disengaging autopilot automatically at 100RA for IAN approch, which is also too late. Have flown BC approach many times, the only problem I don't have FD's. Ryan said they fixed the bug in 2012, hopefully we'll get the update someday.
  4. The digit color and font were changed in SP1c to red and there is no option to get the blue back, except to install earlier version.
  5. Even if FMS not used for navigation, it's nice to have performance data calculations and not to have EGPWS warning. It doesn't take long to edit airports.dat (by ascending latitude) and wpnavapt.dat (same order as airports.dat). http://support.precisionmanuals.com/kb/a60/pmdg-navdata-glossary.aspx
  6. Both master F/D and autopilot must be choosen for PF's side. Because when you select autopilot it sets the FD on a corresponding side as a master. So if flying as FO - you use FD B and AP B. Two FCCs are calculating flight path differently using their own sensors and flight computers, thus their data might mismatch sometimes. And you don't want captain and FO FDs to show different things, so master-slave logic is used, where slave just "copies" the master FD guidance. However, on approach, probably due to safety reasons, slave FD requires its own nav radio to be set for ILS frequency, otherwise it will not show GS. That is because on automatic approach both FDs become masters and the GS data is compared between them and only if tolerances on and between both the FDs are met, autoland would be available.
×
×
  • Create New...