|
|
Post by yankeegolf on Apr 15, 2018 6:47:36 GMT -5
Hello, That is definetely unfair!!! While in flight with my DC3C, engine 1 quit and, being unable to keep my altitude I had no option but an emergency landing at the nearest airport. I declared an emergency and was able to land succesfully on a dirt strip. All pasengers evacuated safely. Nobody was injured and I was very proud of myself. I thought I would get a high mark for this feat. No way!! minus 10 point for arriving early!!! Are you kidding me? I will file an official complain for unfair treatment  Is thera a way to correct this manually in my flight log? |
|
|
|
Post by peter on Apr 15, 2018 10:36:59 GMT -5
Hi Yankeegolf, well, FSCaptain strives to make your flight experience more realistic, and since the world isn't fair, why should the score be?  More seriously, I am pretty sure Trav and Dutch may want to see your logs. Feel free to send it to us Cheers, Peter |
|
|
|
Post by ret41 on May 27, 2019 16:14:27 GMT -5
Hello. I'm still a beginner, but faced the same situation. Depressurization occurred in flight. I made an emergency landing at the nearest airfield. In the FCDU log file there is an entry "Emergency declared! Successful Emergency Landing!" And for this they gave few points and this is not right. Really for a successful emergency landing should not be encouraged? +0 looks like a mockery) Sorry for my English and thank you very much for the excellent program.   Full log-file |
|
|
|
Post by peter on May 28, 2019 4:08:07 GMT -5
Hello Ret41, welcome to the FSCaptain forum. Your English is perfectly fine, and that's a nice Stratocaster that you have there The +0 that you got for several items are strange indeed. They could be a consequence of airline policies, or of a bug. To better understand the reason, can you send us (see blue link below) a zip file with your FSCaptain\Data\Log folder? Please send the email to all of us and copy the address of this thread into your message so that everyone on the FSCaptain team knows what the logs are for. Cheers, Peter |
|
|
|
Post by ret41 on May 28, 2019 6:08:39 GMT -5
Many thanks for answering my question and your attention to my Stratocaster).
After a while, I'll be at home. I'll drop you a folder with the Log files on the email to deal with this issue.
|
|
|
|
Post by Travis on May 28, 2019 12:30:26 GMT -5
Hello Ret41,
No more logs are needed - I see the one that you posted, and it tells me that you were caught in a 'shadow area' when it comes to an emergency.
Your cabin altitude (pressure) did not seem to be properly regulated - for whatever reason we can't say, except it wasn't a system failure - and eventually crept to over the equivalent of 10000 ft. That's when your FO noted this to you.
Here's the values we noted on the ground when loading and unloading... and at a waypoint during your flight just before the FO callout....
Loading: Plane Altitude: 630 == CabinPressure: 650
After TOC: Plane Altitude: 36906 == CabinPressure: 9900
Going ON: Plane Altitude: 58 == CabinPressure: 6250
Going IN: Plane Altitude: 57 == CabinPressure: 4400
The difference between landing and ending the flight makes me think the aircraft's pressure system might not have been set properly. (IIRC, the PMDG NGX has a 'realistically complex' pressure system.)
Now it always is the Captain's decision to declare an Emergency. That's why we no longer penalize for a 'bad call.' So that's why you see "Emergency declared!" in your FCDU log.
Your landing was nice and everyone was safe, so we log "Successful Emergency Landing!" Later when we looked at the emergency conditions, we couldn't find a system failure (or a random event) to justify an Emergency, so your Administrator shows "Landed w/o incident". That's 0 extra points.
----
And yes it's possible for us to flag a cabin altitude of over 10000ft and have that be worth points for a "minor Emergency." But there are other ways by which you could normally finish such a flight....
If you encounter the same condition in another NGX flight, check your cabin pressure and adjust as needed. If that doesn't seem to accomplish much, you could drop to a much lower altitude and continue your flight. Just keep monitoring your cabin pressure - that's the value we need to be below 10000ft - not just your altitude!
----
Please let us know your thoughts on this!!
Best,
|
|
|
|
Post by Travis on May 28, 2019 12:37:16 GMT -5
While in flight with my DC3C, engine 1 quit and, being unable to keep my altitude I had no option but an emergency landing at the nearest airport. I declared an emergency and was able to land succesfully on a dirt strip. All pasengers evacuated safely. Nobody was injured and I was very proud of myself. I thought I would get a high mark for this feat. No way!! minus 10 point for arriving early!!! Are you kidding me? I will file an official complain for unfair treatment Is thera a way to correct this manually in my flight log? If you can find the FCDU log for this flight, shoot it over to us and I'll see if I can find what happened. ----- My primary PC is borderline iffy. After my splurging a week or so ago on installing P3D4, my C: drive is 99% full and I'm needing to work on it over the next day or three to keep things running. (One day back in the late 90s, one of my work servers -- Windows NT 4 - eeek! -- had less than 100MB free space on its primary partition and the box began to freeze up. It took multiple reboots and working with some CLI tools to delete enough old server logs to get it back into operation. Too bad I didn't think to add an "alert me when C space drops below 5% free" to my current PC.) Best, |
|
|
|
Post by ret41 on May 29, 2019 1:30:13 GMT -5
Travis, thanks for the reply! If I understand you correctly, then this is my mistake. In fact, I never came across this, did not assume that it was also modeled. I did not set the height of the cruiz - Flt Alt (and left 10,000 ft), and cracking the glass apparently occurred. The Pressurization Mode Selector was in the AUTO position - and I did not install the cruise altitude, I thought the pressure would be maintained automatically. Now I will be more careful and serious about the preparation of the flight. We recently had a case in Russia, the crew of the Tu-154 on the flight level destroyed 3 generators themselves, еhe flight engineer allowed the increased load of the batteries, as a result of which there was a thermal acceleration of the batteries,and landed on an abandoned airfield in the taiga, catching the artificial horizon in a glass filled with water (the instruments were not functioning). They sat down safely, the captain and co-pilot were given the star of the Hero of Russia en.wikipedia.org/wiki/Alrosa_Mirny_Air_Enterprise_Flight_514 |
|
|
|
Post by ret41 on May 29, 2019 16:08:31 GMT -5
Sorry that off topic branches. But I was again fined for not putting pressure on the altitude of the transition (Altimeter not STD over TA (-5)). When climbing to a flight level, the dispatcher told me to take an altitude of 18,000 feet, I took this altitude from the take-off airfield pressure and set the STD. While descending it was also, I dropped to 18,000 feet and set the pressure of the arrival airfield. Why was I fined? What am I doing wrong? Log files of this flight are attached: yadi.sk/d/rute2GE86jiWcAThanks in advance for the answer! |
|
|
|
Post by peter on May 30, 2019 2:01:59 GMT -5
Hello Ret41, the transition altitude (TA) at which you should switch from local to standard pressure is different for each country, and sometimes even for different airports in the same country. Your flight went from EGGD to EIKY, which have TA of 6000' and 5000', respectively. Your log contains the line FCDU.GAU:: 22:18:24 PENALTY - Altimeter not set to standard @ Lat 51.399725 Long -2.932594 Altitude 8804 Indicated 8801 Altimeter 1016 Hence, you were penalized because your altimeter was still set to 1016 when you were about 2800' above TA near Bristol. FSCaptain generates a release document for each of your flights, which contains information about TA for your airports under "Remarks". Something like - NOTE TRANSITIONS: CYHZ=18000 (TA), CYFC=FL180 (TL), CYQM=FL180 (TL). There is a small difference between transition altitude (TA) and transition level (TL), see en.wikipedia.org/wiki/Flight_level#Transition_altitude Cheers, Peter |
|
|
|
Post by ret41 on May 30, 2019 3:11:51 GMT -5
Thanks Peter! In general, about the Altitude transition, do we need to take the height from the FCDU, TA to look at it, and not to take 18,000 feet according to the American rules? Do I understand you correctly? I just fly with a computer traffic controller built into the simulator, and he has a TA of 18,000 feet, it will be problematic to agree with him. |
|
|
|
Post by Travis on May 30, 2019 11:42:33 GMT -5
In general, about the Altitude transition, do we need to take the height from the FCDU, TA to look at it, and not to take 18,000 feet according to the American rules? Do I understand you correctly? I just fly with a computer traffic controller built into the simulator, and he has a TA of 18,000 feet, it will be problematic to agree with him. Yes, you did understand Peter, but FSCaptain is nothing if not configurable. If you look at Appendix 6 in your FSCaptain User guide, you should see this: should you prefer to use default ATC or to worry about keeping this data updated,
you can delete the Transitions.cfg file and rename the file \FSCaptain\Config\Transitions_18.cfg to
replace it. Rebuild your airport database with SceneryScanner, and all airports worldwide will
have a Transition Altitude of 18000ft.
If you do this, then SceneryScanner will not honor the Navdata TA and TL values! Every aerodrome
/ airfield / airport / airstrip will have a TA of 18000ft and a TL of FL180.
So when you're climbing above 18000 ft you should switch your altimeter to STD and leave it there until you pass back down below 18000 ft again. (Starting with the current version of FSCaptain, after you have passed Top of Descent, you can request early clearance approach, and once you have clearance approach you are then free to switch to local / station pressure at any time you choose.) And if you don't want to be bothered with TA/TL at all, you can set the option DISABLE_STD=1 and there will be no more penalties. We hope this helps, |
|
|
|
Post by ret41 on May 30, 2019 12:02:42 GMT -5
In general, about the Altitude transition, do we need to take the height from the FCDU, TA to look at it, and not to take 18,000 feet according to the American rules? Do I understand you correctly? I just fly with a computer traffic controller built into the simulator, and he has a TA of 18,000 feet, it will be problematic to agree with him. Yes, you did understand Peter, but FSCaptain is nothing if not configurable. If you look at Appendix 6 in your FSCaptain User guide, you should see this: should you prefer to use default ATC or to worry about keeping this data updated,
you can delete the Transitions.cfg file and rename the file \FSCaptain\Config\Transitions_18.cfg to
replace it. Rebuild your airport database with SceneryScanner, and all airports worldwide will
have a Transition Altitude of 18000ft.
If you do this, then SceneryScanner will not honor the Navdata TA and TL values! Every aerodrome
/ airfield / airport / airstrip will have a TA of 18000ft and a TL of FL180.
So when you're climbing above 18000 ft you should switch your altimeter to STD and leave it there until you pass back down below 18000 ft again. (Starting with the current version of FSCaptain, after you have passed Top of Descent, you can request early clearance approach, and once you have clearance approach you are then free to switch to local / station pressure at any time you choose.) And if you don't want to be bothered with TA/TL at all, you can set the option DISABLE_STD=1 and there will be no more penalties. We hope this helps, Thank you Travis, this is a complete answer. (As for Appendix 6, I appeal to the management as needed, since it is difficult to read everything in a non-native language, sorry for many of my questions). There are some solutions to this problem, it’s super and I think I can configure FSCaptain as it suits me. P.S. I did not understand how to put a quotation under the spoiler. |
|
|
|
Post by Travis on May 30, 2019 12:39:01 GMT -5
No need to apologize - please feel free to ask anything you'd like here! Best, |
|
|
|
Post by ret41 on May 31, 2019 3:46:07 GMT -5
How can I remove the restriction on departure for weather conditions? I could not fly to UUEE from the EDDF, it was windy yesterday in Moscow. Although in the settings of the "Airline Definitions" I configured the maximum crosswing 200 knots. The manual seems to talk about it, but how? "If the winds are above maximums before departure, you will be placed on “weather hold”, but you can request that the hold be lifted, and you can attempt the flight."  |
|
