Jump to content

LuisVargas

members
  • Content Count

    108
  • Joined

  • Last visited

Everything posted by LuisVargas

  1. Today I was able to achieve success using checklist and co-pilot in a flight from SBRJ to SBSP. I do not know what I did of different this time. Sorry. Now I'm sure it's some fault of mine during the flight. I'm satisfied and I'm going to explore other airports from now on. Thank you, Hanse.
  2. Hanse, could you please tell me the STAR and TRANSITION you have used in your landing on to the runway 17R (or 35L) of SBSP? Can you confirm the MDA 2820 into BARO if 17R is the runway in use? I will try to reproduce your flight. I think that doing this I will have parameters to talk better with you.
  3. Hi, Hanse. Today is Sunday and you should be with the family, in any case, thanks for your aid. Yes, we've already discussed this problem. I was guessing that the code with problem, for some reason, was active again. Speaking from developer to developer (I am a retired developer), these things can happen. Glad to know that was not the case. I'm going to review my concepts and keep trying here. Thank you.
  4. Since I am not knowing how to target an airport above sea level, as SBSP (2630 feet), I did a SBCT-SBFL at FL220, where SBFL is an airport that stays at 16 feet. This time everything went perfect with the checklist. route SBCT BUVB1A.OGPAK OGPAK UTEBIA.EDIVI MUKAL SBFL Sumarizing, here in the southern hemisphere (Brazil), my flights only have the cheklist working well when the destination airport is almost at sea level. In the northern hemisphere everything works perfect in any airport.
  5. I repeated the flight SBRJ-SBSP. The descent this time was on runway 17R of SBSP. The landing was good and when I applied the brakes my speed already was less than 60 knots and I still had a good runway length to give the LEAVE RUNWAY message time to be shown but it was not shown and the checklist stopped (no AFTER LANDING CHECKLIST and so on). The last item in the checklist was LANDING CHECKLIST. In the image bellow (before the landing) I show the exact moment MINIMUS was call out. There is a msg LDG INHIBIT on ECAM. Why this? The second image is from MCDU3 just after landing.
  6. Flight from SBRJ to SBSP (2631") using A319 EASYJET G-EZAX (v1.2.4.0) at FL280. Route "SBRJ SID(IH1C.UMBAD) UZ44 PAGOG STAR(PAGOG2A) SBSP ILS35LX". At PERF APPR page the QNH, temp and wind were got from ATIS 127.650. Intercept GS set to 5000 feet and DA 2829 feet acording chart for SBSP ILS 35 (site AISWEB). Using Navigraph 1806. Checklist worked well until the LANDING CHECKLIST was call out and after that the AFTER LANDING was not call out. After landing and still in the runway, the message LEAVE RUNWAY was not show and the checklist has stopped working. I only applied the brakes (after reverses) when the speed was under 60 knots. The image on the MCDU3 shows a confuse checklist just after landing. I'm sorry to be returning to this subject, but my flights (using checklist and copilot) in Europe and USA always work out.
  7. I just finished a flight using route LEMG / DAOO (FL270 - LEMG PEK01H ON DAOO) and the checklist worked perfectly, but I still with problems with checklist on my domestic flights in Brazil, especially those with destinations at airports above sea level and relatively short runways.
  8. I like this flight tutorial from LOWI to LFMN. About the reported problem, It was my fault. Probably I forgot to click on 'ALIGN IRS' in INIT page the last time. You can close this topic. Best regards.
  9. The probable problem (can be my mistake) that I reported in number 2 of the list shown in first post occurred after the completion of START CHECKLIST, that is, I had not yet programmed the route, which makes in my opinion the route irrelevant.
  10. I used the route LOWI-LFMN in "Volume 6 Step By Step Tutorial Rolf Fritze Version 06-01-09" for Airbus version 1.31(32 bits).
  11. I made a full fresh installation of version 1.2.4.0 and started a flight using checklist and co-pilot. The flight was the one in tutorial step-by-step LOWI-LFMN using the A320-232 IAE SHARK. Problems (maybe): (1) In MCDU3, LOAD and FUEL, PAX, the START BOARDING still does not blink when clicked; (2) After the START CHECKLIST was done, after more than 5 minutes of the ADIRs were aligned (first picture bellow), after I have entered with the route and just before to start the pushback, the PFD and ND were as shown in the second picture bellow; (3) I gave up to keep trying.
  12. I was starting the aircraft setup on MCDU3 and I noticed that the 'START BOARDING' was not working although the door was opened. I am with the update for version 1.2.3.4, the aircraft is TAM A319-132 IAE and airport is SBRJ (parking at GATE 3). The number of passengers was 145.
  13. Roger... Aircraft: A319-132 IAE (TAM PR-MAN) version 1.2.3.2 (the latest). Flight Plan: SBRJ/SBSP AT FL260 ACTIVE NAV DATA BASE: 1806 (NO SECOND NAV DATA BASE) ROUTE/SID/STAR: SBRJ (RWY 02R) SID(IH1C.UMBAD) UZ44 PAGOG STAR(KOMG3A.PAGOG) SBSP (ILS17RY)
  14. I repeated the flight twice and in both flights my A319-IAE (TAM version) is losing speed in descent and entering in A.FLOOR speed mode.
  15. Ok, you all are right. It's ok now. Thank you.
  16. The bus (TAM A319 IAE) not properly following the waypoints' altitudes. It's arriving too down to the programmed altitude.
  17. Thanks, Mathijs. Downloaded and solved!
  18. Receiving this message error at startup. Version 1.2.3.2.
  19. I confirm managed speed drops during descent and I am not using any third part add-on. Managed speed is also making a mess during climb. It stays changing fom THR CLB to SPEED, SPEED to TOGA LK, to AFLOOR...
  20. By the way, are the reverses slow the speed down in a realist way? It's seems to me they spend too much time to reduce the speed to 70 kts when so I begin to apply pedal breaks.
  21. Ok, I will try on others airports with less than 2000 meters at sea levels and above it. I will back with notices about.
  22. I repeated the flight, turned off the AP far way the airport and manually managed to land very close to the headboard of the runway. I applied the reverse and the brakes and I used only 2/3 of the runway to landing. I continued bellow 30 kts on the remainder 1/3 of runway. After a few seconds of silent I heard "APU ON" and nothing more. The A319-IAE was almost arriving to end of a runway when the "AFTER LANDING CL" was executed and finished just when the runway arrived to its end. The "LEAVE RUNWAY" message was not shown. I leaved the runway and taxed to the gates. When I break and stopped the message "SET PARKING BREAK ON" was shown, I did this and the "PARKING CL" was executed with success. I think I still continue making any mistake. Could you please tell me which rules are embedded into the source code for the execution of the message "LEAVE RUNWAY"?
  23. Hello, I am back home (and to simulator). I landed on SBSP which has a relatively short track with 6352 '(1940 m) in extension. The reverse and the braking ended almost at the last exit of the runway. I applyed the brakes until I got the speed less than 30 kts. This time the "AFTER LANDING CHECKLIST" was executed (great!), but as I was already practically on the exit of the runway the "LEAVE RUNWAY" message did not appear and instead of came the message "SET PARKING BREAKS ON" (???). I leave the runway and parked in a gate. I applyed the parking breadk and the "PARKING CHECKLIST" was executed with success. So my 'problem' now is about the "LEAVE RUNWAY" that was not displayed.
×
×
  • Create New...