tantonovich

Members
  • Content Count

    11
  • Joined

  • Last visited

Community Reputation

5 Neutral

About tantonovich

  • Birthday 03/13/1984

Profile Information

  • Gender
    Male

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    VATSIM
  • Virtual Airlines
    No
  1. Just had this issue on Win10. Here's what worked for me: Go to Device Manager and find your stick/yoke or a device showing as Unknown Device. Right click, Update Drivers... Browse my computer for driver In the path box, type C:\windows\winsxs and hit enter. This should install the driver generically, then you can run the Saitek driver installer to complete the setup. Hope this helps someone!
  2. tantonovich

    Saitek X52 and Windows 10

    Just had this issue on Win10. Here's what worked for me: Go to Device Manager and find your stick/yoke or a device showing as Unknown Device. Right click, Update Drivers... Browse my computer for driver In the path box, type C:\windows\winsxs and hit enter. This should install the driver generically, then you can run the Saitek driver installer to complete the setup. Hope this helps someone!
  3. Mindstar, I fly various C172's IRW and purchased this application because I thought that it modelled the real-life 430/530. From all that I can see, this is really nothing more than a re-skinned default GPS. The GPS Map display looks absolutely nothing like the real one, and there is no terrain modeling. The airport info pages are not correct (I bought the RealData subscription too). You cannot create a flight plan, or if you can, I can't figure it out and there's no documentation for it. This does not allow you to do WAAS approaches. In all, I feel that I wasted $50 on a product that is nothing more than a bezel for the FSX/P3D default GPS. So I wonder, am I experiencing issues with the product, or is this really what it is? Hoping that this ends up being something I'm doing wrong... Tom Antonovich
  4. tantonovich

    Question re: DC BUS 1 Failure

    KevinH, I think you may have misunderstood, neither myself nor the NTSB report talked about a need for instrumentation in >identifying< the problem; as you are correct that there's really no way to do that with an entire bus failure. Training and systems knowledge are necessary to recognize this type of failure and confirm that's what you have experienced if it happens. What I'm getting at is the part of the report that talks about there being no workaround procedures. Sure, pilots can figure it all out themselves, however isn't the point of documented checklists and procedures to eliminate human error? What I'm saying is that it seems strange there's no documentation for what to do AFTER you've identified the bus failure. Another odd thing regarding the speedbrakes: I followed the NNP and deployed manually, but they were INOP anyways. Go figure, right? Haha!
  5. tantonovich

    Question re: DC BUS 1 Failure

    I agree, I think going through each item gives a thorough understanding of each individual issue. Plus, I would imagine that IRW the crew would write down all of the deferred items as they went through the items, then make sure they hit all of them before descent/approach/landing as appropriate. I guess I'm just surprised that, since a bus failure affects so many systems, there isn't either a certified NNC or anything like that. Keep in mind I'm not complaining, reporting a bug, or anything like that. Just raising this because it's an interesting issue and it makes me wonder how it would be handled IRW. I found an incident from 1994 of almost the exact same issue and the NTSB remarked on the absence of such a procedure, pretty interesting reading! I would be very interested to hear from a real-world ATP about this. I'm sure it's an extremely rare possibility, but given the amount of systems connected to these buses I would be scared to death of losing a bus if I were a 737NG driver. http://www.fss.aero/accident-reports/dvdfiles/US/1994-04-26-US.pdf
  6. tantonovich

    Question re: DC BUS 1 Failure

    So I fly with random failures and had a doozy today: had my AP disengage during cruise, lost Yaw Damper, Mach Trim, Speed Trim, Pressurization AUTO FAIL, Captain's F/D fail, ANTI-SKID INOP all at once!! I pretty quickly discovered that I could re-engage AP on CMD B and got the aircraft controlled that way, then went to work troubleshooting. I figured this was all due to a single common failure, but rather than break out the electrical schematics I figured the QRH would lead me in the right direction if I started checking out the individual failures. That didn't happen... So after I got nowhere that way (except fixing the pressurization by switching to ALTN), I checked out the schematics and traced this down to a loss of the entire DC BUS 1 (verified by cheating and looking in the FMC failures page). What I'm wondering is this: Is it normal that the QRH/FCOM doesn't have any procedures to deal with the loss of an entire bus? I mean, the information is there, but it's quite scattered. Since there are so many systems attached to the buses, it seems to me that Boeing would have some kind of Deferred Checklist for a failed bus so that all of the little caveats were able to be noted in one place. Since this is not available in the docs, a pilot has to first find the list of all systems attached to the failed bus, then individually look them up in the QRH to see if there are deferred items to take into consideration before landing. For instance, since I'm ANTI-SKID INOP, I need to not arm Speedbrakes before landing. I will also not have thrust reversers on engine 1 (I think?). Anyways, just asking out of curiousity while I'm waiting for this flight to finish... Tom Antonovich PANC
  7. tantonovich

    Takeoff V-Speed problem

    I just had this issue when using TOPCAT 2.74Beta to calculate my derate. On the Flaps -> Optimum setting, it recommended Flaps 20 for me, which the 777 doesnt like apparently. I had TOPCAT recalculate using Flaps 15 specifically and the FMC gave me v-speeds.
  8. tantonovich

    initialize irs : not allowed

    I know that this issue is almost always due to human error, however I just had this happen to me... and I'm perfect so it wasn't human error :-) My situation somehow appears to have loaded with the GNS not functioning correctly. So I had the same issue where I went to align my IRS using the "Initialize IRS" option on the CDU, and it returned a "NOT ALLOWED" error. To fix, I selected REF on the CDU, then POS REF (LSK4L), then cycle the GNS Inhibit option (press LSK5R to inhibit, then again to Enable). After this, I went back to the INIT page and was able to Initialize IRS successfully. Hope this helps!
  9. tantonovich

    VERT PATH FULL

    I just received the error while trying to use the FRDMM1 STAR at KDCA. The 'cure' was to remove a couple of the altitude/speed restrictions in the LEGS page. After removing 2, the message went away. Any ideas on a better solution? My route was: SEA J90 MWH HLN DPR MCW JOT J30 BUCKO FRDMM1. I highly doubt the real NGX restricts using this STAR...