Please put your post in the correct forum.
Today we had to move over 150 posts manually.  We do feel the forum structure is logical and the section names are clear. As redirecting posts pollute the forum a lot we will not add them anymore. So if you are unable to find your post, look for it in the most logical forum section.

Jump to content

LuisVargas

members
  • Content Count

    114
  • Joined

  • Last visited

Everything posted by LuisVargas

  1. Please, left this post in stand by until I have more informations to confirm if I have ou not a issue. Thanks.
  2. I made flight LOWILFMN01 and everything worked fine. I saved the flight when I passed by NERAS to have a point to return and practice GO AROUND and alternative routes. I returned later to the saved flight and continued it. The speed was 230 kts. When the call out "APPROACH CL: STARTS IN 4.7 MILES ..." appeared, I pressed the '1' and the approach cl was sung. After the call out "FLIGHT ATTENDANTS PREPARE FOR LANDING." I activated in the MCDU the approach phase, FLAPS 1 was deployed automatically but the speed dropped to 200 kts and not 170 kts as I suppose it should have been. I waited for a while and I entered in the grand final. Then, manually, I changed the speed to 170 kts. Upon hearing "LOCALIZE ALIVE", I pressed the APPR button on the FCU and passed the ROSE to LS. I was stabilized at 170 kts and then I commanded the speed for managed. The speed began to rise to 200 kts. I changed again to 170 kts. At 2000" of altitude the FLAPS 2 and speed had not yet dropped, so I manually applied FLAPS 2 and then I heard "GEAR DOWN" and only then did the speed begin to drop. From then on, FLAPS 3 and FLAPS FULL were automatic deployed and the remainder of the flight went smoothly. I ask for help or instructions. Thanks. LOWI-LFMN-NERAS.wx LOWI-LFMN-NERAS.abx LOWI-LFMN-NERAS.fxml lowi-lfmn-neras.fms lowi-lfmn-neras.asc
  3. I made flight LOWILFMN01 and everything worked fine. I saved the flight when I passed by NERAS to have a point to return and practice GO AROUND and alternative routes. I returned later to the saved flight and continued it. The speed was 230 kts. When the call out "APPROACH CL: STARTS IN 4.7 MILES ..." appeared, I pressed the '1' and the approach cl was sung. After the call out "FLIGHT ATTENDANTS PREPARE FOR LANDING." I activated in the MCDU the approach phase, FLAPS 1 was deployed automatically but the speed dropped to 200 kts and not 170 kts as I suppose it should have been. I waited for a while and I entered in the grand final. Then, manually, I changed the speed to 170 kts. Upon hearing "LOCALIZE ALIVE", I pressed the APPR button on the FCU and passed the ROSE to LS. I was stabilized at 170 kts and then I commanded the speed for managed. The speed began to rise to 200 kts. I changed again to 170 kts. At 2000" of altitude the FLAPS 2 and speed had not yet dropped, so I manually applied FLAPS 2 and then I heard "GEAR DOWN" and only then did the speed begin to drop. From then on, FLAPS 3 and FLAPS FULL were automatic deployed and the remainder of the flight went smoothly. I ask for help or instructions. Thanks.
  4. Does anyone succeeding in entering and executing an alternate flight plan?
  5. Dave, you were right. I was using FSXWX. I repeated the flight using weather default and clear skies. In the first image below, the moment I saved the flight. In the second image, when the flight was resumed. Both situations are equals now! Flight before save. Flight after restart. PS: By the way, but what a complex code are you developing, huh? I am a retired TI professional (IBM mainframe) and I could imagine the complexity of the code (what language?) by yours logical reasoning about the probable (and correct) cause of the issue. Congratulations! Thank you for your help. Best regards.
  6. I saved a flight before starting the 'DESCENT PREP CL' (in CRZ level) and the TD in the MCDU was shown one minute later after the waypoint PAGOG and the next waypoint SP007 (FL131) was six minutes after PAGOG. So I did the rest of the flight normaly and closed the simulator. Minutes later I was back to the simulator and load the saved flight. I saw that the TD was no longer showed in the MCDU and the fixed SP007 (FL131) was only two minutes (instead six like before) after PAGOG. I think that is not OK. Am I wrong? MCDU image before save flight. MCDU with saved flight loaded.
  7. Thank you, for me this post already can be closed but Let's see what Richard Portier has to say about it.
  8. At last (I swear), I was curious. How did you conduct your approach tests for SBSP (or any others)? Did you save the flight using some appropriate software (which?) to get back to the saved point and start over there?
  9. By the way, when by simmer's failure the checklist is forgotten to be executed (and lost), is there any way to retrieve it starting in the next checklist step? Thanks for your effort.
  10. For SBSP, what values do you suggest for DH and MDA?
  11. I set my A318/319 to "TAKE-OFF STATE" like sugested above. Thanks.
  12. What? I did not know I had to act like I was installing a pirated product. I use Microsoft Window Defender. I am going to uninstall, take the internet from the wall outlet and redo the installation. I will return with news about it. Thank you.
  13. I am confused. I need help. The A318/319 start with none state selected (first image) and the A320/321 start in TAKE-OFF STATE (second image). A318/319 ACFT STATE at aircraft loading. A320/321 ACFT STATE at aircraft loading. In the case above I need press COLD DARK STAT twice, because in the first press the MCDU3 do not turn off (first image bellow) and the overhead panel is in a confuse way (second image bellow). After first press COLD DARK STATE Overhead panel after first press COLD DARK STATE After second press COLD DARK STATE the MCDU3 turns off (bellow) and the overhead panel seems to be OK (second image bellow). Overhead panel after second press COLD DARK STATE.
  14. By the way, some models (that I no longer remember which) when being loaded are coming in "cold & dark state" and others in "takeoff state". When I change the status to "Cold & dark", the MCDU3 continues turned on (some buttons on overhead panel also) and I need to press "Cold & dark" again to turn the MCDU3 off (and overhead panel). I'm sorry not have explained the issues better because of the limitations of my bad English. Regards, LuisVargas
  15. I did another flight and I can confirm that all checklists for the A319 IAE are running except the call out LANDING that is not heard but is executed. The landing was on a runway (SBGL) that practically is at sea level. The route was "SBSJ UBS1A.DORLU ROPA1A DONGI SBGL", departing from rwy 15, crz at FL190 and landing using the ILS of rwy 10.
  16. I flew from LOWS to LIPZ using route "DETS1A.DETSA LAREN LARE1C" and landing at runway 04R (ILS 109.95). I used the A319-132 IAE GERMANWINGS D-AGNS and I can almost say that all the checklists went well, but I confess that I did not remember has been hearing the call out "LANDING" although it has ben executed (COPILOT ON). In short, it was a flight without any problem. *I used Navigraph instead of NavDataPro.
  17. Aerosoft A320 professional AIR BERLIN D-ABMS A320-214 CFM SHARK Aerosoft A320 professional BRITISH AIRWAYS G-EUUU A320-232 IAE Airbus A319 TAM PR-MAN A319-132 IAE
  18. What you mean about "... the rest is working well."? Is the "rest" the AFTER LANDING and PARKING?
  19. Ok, I did the reverse way, i.e instead to go from Rio de Janeiro (at sea level) to São Paulo state (much above sea level) I came from São Paulo to Rio de Janeiro and the all checklist items worked ok this time. My P3D v4.3 has no other add-ons than Aerosoft Airbus Family Professional and PMDG 737NGX. Nothing more because my hardware is an entry-level. In my opinion the airport elevation can be one of the things that is contribuinting to the observed fail on the checklist after the LANDING checklist to be call out and the aircraft land sucessfully.
  20. With A320 used "A320-214 CFM SHARK" and "A320-232 IAE". I also have the same problems using "A319-132 IAE".
  21. The FINAL and LANDING works OK. The AFTER LANDING and PARKING are the steps not executed. Something like if the code do not recognize that the aircraft was landed and is already on the ground and leaving the runway, so much so that on the last flight to SBGR, when I taxied to the gate, stoped and activated the parking brake the call out was "HUNDRED ABOVE" that is a call out for LANDING.
  22. uhmm... "think about it what is different" this can be the way. I did another flight to a third airport (SBGR) at the same state (São Paulo) and again the checklist stoped at LANDING. So I have three unsuccessfully flights against two well done. The first difference that comes to mind is the altitude of the airports. The three failed flights were to airports above sea level, i.e. SBSJ (2119 ft), SBSP (2631 ft) and SBGR (2457 ft). The two well done flights were to LFMN (13 ft) and EHAM (-10 ft). Ok, the next flight will be to an airport at sea level. Let's see. Thanks for you help.
×
×
  • Create New...