Jump to content

andrewflies

Members
  • Posts

    3
  • Joined

  • Last visited

1 Follower

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

andrewflies's Achievements

Newbie

Newbie (1/14)

  • One Year In
  • One Month Later
  • Reacting Well Rare
  • Week One Done
  • First Post Rare

Recent Badges

1

Reputation

  1. So I had a few questions regarding go around procedure as I'm somewhat new to the Challenger. If I set up the appropriate go around altitude and then press the TO/GA button to initiate a go-around, I follow the FD and work through the go-around checklist. My question is with respect to FMS sequencing. The legs of my current flightplan usually end at the end of the go around procedure. What is the correct procedure to transition from the go-around to a new approach? I've done it by either selecting DEP/ARR and reselecting the approach and executing it as well as by copying a saved secondary flightplan to active and then execute a direct to the IAF. Which is the proper way of doing this? In addition, how would I go-around and divert? I'm unsure how to append the alternate flightplan to the end of the existing flightplan (like how the Airbus FMS does it) or whether this is even possible in the Proline 21. My current method is to create an "alternate" flightplan and save it in the route menu before taking off. Then while working through the go-around procedure I load and activate this stored flightplan. But this seems kind of clunky and becomes awkward if runways have changed. How is an alternate supposed to be dealt with?
  2. So I've flown a few more flights to try and figure out what is happening. There is no slow battery drain. Rather the main battery and/or the APU battery go from full charge 98-100% down to 0% instantly. Causing the respective battery offline message to appear in the EICAS. Study page confirms 0V, as does the DC elec page which also has the battery no longer green. It seems to be able to occur in any stage of flight: on ground, in cruise, on approach. Reloading to before such an event took place results in it not happening. Whenever it does happen, the HYD page shows a display overflow of digits. The battery does charge again subsequently. There are no active failure scenarios. Below are some screenshots of a new airframe (newly created and first flight) on its maiden flight with the main battery dropping to zero after being enroute for around 45-50 minutes. Showing DC, AC, HYD, overhead panel, electrical study page for the failed battery. The summary was taken a few minutes later. I'm running the latest stable xplane 12 version on an M1 mac.
  3. So I've been learning the CL650 and on most of my flights I seem to have constant main and APU battery drain resulting in them turning off when their voltage reaches zero. I'm pretty sure I'm following the checklists properly so not sure what's causing this, I do have the main generators on during flight. Any thoughts?
×
×
  • Create New...