Jump to content

LuisVargas

members
  • Content Count

    95
  • Joined

  • Last visited

Everything posted by LuisVargas

  1. Is there a more recent list? The one that is available is the first of July.
  2. My last contribution. I finally tested the A318-CFM. I had problems with the descent from start to finish. After activate de descent to 4000 feet the altitude dropped very fast and I almost collided with the hills below. I repeated the flight this time controlling the V / S and so went well until I captured the localizer and started the descent ramp on the G / S. This time the problem was the wrong reading of the altitude. A difference of 300 feet, because while it was at 500 "on the altimeter was sung 200". I did not hear the "MINIMUNS". I landed, applied the reverse til 60 KIAS, I take the reverse off and leaved the runway, but the message "LEAVE RUNWAY" not shown. Already towards the gates I heard "SEVENTY KNOTS" as if I were still in a situation of applying the reverses. The rest of the checklist (AFTER LANDING CL and PARKING CL) occurred normally. Okay, now I'm going to wait for SP1 to be released and I'll test all the models again. I love this Airbus and I will have a great pleasure in continuing contributing. Best regards and see you.
  3. Not all IAE. I did now a test with the A321-IAE and it did not have any problems during the flight. To my surprise, he, unlike the other A319 and A320, followed the SID's flight patch in the ND with absolute perfection... the better of them, except A318 with which I have not yet flown.
  4. Ok, I Will stay in stand by until the next patch. Best regards.
  5. I forgot to say that A320-IAE also has another problem that I have not found in the others. During takeoff and climb executing the SID It did not got follow the flight patch in Navigation Display with accuracy and got lost. I had to enter with a 'DIR TO' to the waypoint BRENO. Here are the files with the saved position before NERAS (20nm before "APPROACH CL STARTS IN 4.7 NM...) when I was at 4000 feet and 250 KIAS. A320-IAE-NERAS.wx A320-IAE-NERAS.fxml a320-iae-neras.fms a320-iae-neras.asc A320-IAE-NERAS.abx
  6. All of the five flights I have salved in a two distincts points to be able to back to them and repeat the remainder of the flight. A point after the message "DESCENT PREP CL" and another more close to destination and before the message "APPROACH CL STARTS IN...". I come back to this second one with A320-IAE BRITISH AIRWAYS and I continued the flight. My speed should be with 250 KIAS (speed at saved flight) instead I am at 228 KIAS. No problem. I entered in the final (G/S) with 198 KIAS but the speed increased to 202 KIAS as in the original flight (see attached screenshot). I applyed spoilers and the speed went to line bellow 200 KIAS but when I take the spoilers off the speed increased to 202 KIAS again. This time I selected 195 KIAS in the speed button at FCU. I was at 1700 feet and the FLAPS2 had not yet been automatic launched so I did this manually, the speed dropped and FLAPS3 happened automaticaly as FLAPS FULL and all remainder of the flight occurred without problems. As exposed above (again I beg your pardon for my english) I really feel a problem with A320-IAE in what concerns the G/S speed profile and FLAPS management at the final of a landing. Best regards.
  7. I'm still investigating the original problem, but during the tests I found the problem described below. I did five flights using the route LOWILFMN01 with aids of the checklist/copilot. Three of them with success. In the fourth I had a issue because flaps 2 was not applied automatically and I already was at 1700 feet in the final ramp to runway 04l. I have observed that the speed increase from 198 KIAS to 202 KIAS and maybe this can my have been the origin of the problem because flaps 2 must be applied with speed below 200 KIAS, isn't? So I manually set to flaps 2 (the bus complained because of speed!) and only after is that I heard "GEAR DOWN" and the speed begun to drop. From this point to the end (landing) everything went good. I repeated all the flight and again the same thing has been occured, that is, I had to manually dropped flaps to 2 and again the remainder of the flight run well. The aircrafts used with success in the first three flights were A319-IAE GERMANWINGS, A319-CFM AIRBERLIN and A320-CFM AER LINGUS. In the last two flights were I had problems I flew with A320-IAE BRITISH AIRWAYS. So I think that A320-IAE has an issue with controlling speed at approach descent.
  8. Please, left this post in stand by until I have more informations to confirm if I have ou not a issue. Thanks.
  9. 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
  10. 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.
  11. Does anyone succeeding in entering and executing an alternate flight plan?
  12. 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.
  13. 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.
  14. Thank you, for me this post already can be closed but Let's see what Richard Portier has to say about it.
  15. 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?
  16. 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.
  17. For SBSP, what values do you suggest for DH and MDA?
  18. I set my A318/319 to "TAKE-OFF STATE" like sugested above. Thanks.
  19. 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.
  20. 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.
  21. 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
×
×
  • Create New...