|
|
Post by legendli on Oct 4, 2018 8:11:44 GMT -5
Dear, Yes, it's me again. One simple question about Trans Level and Trans Alt, I noticed there is only one entry in transition.cfg for one airport. for example ZUCK in the cfg file is 9842. Shall I use this number for both climb and decent? Because I found in Jeppesen Charts the Trans Level is FL118 vs Trans Alt:98xx and as I know TL is for decent and TA for climb.  |
|
|
|
Post by alaskanflyboy on Oct 4, 2018 17:38:50 GMT -5
You would use transition altitude as that's what FS captain is concerned with. To correct you, it's not a matter of one for climb and one for descent. Transition altitude is the point at which you must set your altimeter to standard rather than field pressure. Transition level is the lowest cruising level allowed. So on either climb or descent, you'll go to 29.92 In. Hg. (1013mb) above 9850 ft. Above 9850, you cannot have a final cruise level below FL118.
|
|
|
|
Post by Travis on Oct 5, 2018 11:43:10 GMT -5
John is mostly correct, but something small is changing....
Originally we used a global TA database that I put together after studying lots of charts many years ago. That's the transitions.cfg file you have pulled up. It's still useful, but it no longer needs to be updated since as of last year there is a better solution.
Starting with version 1.8.0, if you have access to Aerosoft or Navigraph "navdata" you can configure FSCaptain to look at a set of AivlaSoft (v1) or FSCaptain navdata. Once you do that, when you run SceneryScanner, it will pull the TA (and sporadic TL) data and we will use that updated data when it conflicts with the ancient TA database.
Aerosoft has kindly supplied us with data (currently from AIRAC 1702) if you don't have a subscription to either provider. Check your User Guide for information on how to use all of that.
So since 1.8.0, if an airport has a defined TL (and if that data's in one of the Navdata datasets) then you will be given that as your "TL" on your flight. (Otherwise in your Dispatch Release, you'll see something like "TL:FL098+".) There the plus sign indicates it's actually the TA value.
HOWEVER... I just checked ZUCK, and it did not have a TL value in our airport.cfg file. But I see there is "11811" in my latest Navdata. So I checked again, and none of my airports have a defined TL!!
So there is a bug which I will work to fix today. Thanks for the heads-up!
----
And I did mention "changing" earlier. Beginning with FSCaptain 1.8.1 Beta 2, once you receive "Approach Clearance" from your airline via the FCDU, you can freely set local pressure no matter your vertical profile! (The "Approach Clearance" message on your FCDU will include the latest station pressure setting, to hopefully make it easier. But you can set whatever pressure setting you feel is correct.)
Regards,
|
|
|
|
Post by Travis on Oct 5, 2018 12:52:16 GMT -5
Okay the "bug" applies to me and recent Testers. I had renamed the option "NAVDATA_PATH" to "PATH_NAVDATA" and I hadn't updated SceneryScanner yet.
Still though - whew! I'm glad it was caught now.
It works nicely for me now:
- NOTE TRANSITIONS: OMDB=13000 (TA), ZUCK=FL118 (TL), ZUUU=FL118 (TL).
We currently use the exact data we read - so the TA for ZUCK is still 9842, and that's what we would expect. IIRC, some charting agencies will "round up" to the next 10ft value on TAs. (So TAs from 9841 to 9850, would all be printed on charts as "9850".)
If anyone would like, I could make this a new option - TA_ROUND_UP_10=1. ??
Best,
|
|
|
|
Post by legendli on Oct 9, 2018 19:42:32 GMT -5
I do have navigraph, and updated it to 1810 recently for fscaptain, I got a -5 for didn't set the correct QNH during decent, my habits is just check the Transition.cfg but I do hear my FO said set to local pressure or something like that at the different attitude as it in the cfg , that's the reason I asked this. And thanks a lot Travis.
|
|
|
|
Post by Travis on Oct 11, 2018 13:04:22 GMT -5
Your very welcome!
Just have your path to the Navdata set correctly and SceneryScanner will override the old data from transition.cfg.
Your Dispatch Release will have the correct value for each flight.
-----
If you can find the FCDU log for that flight, send it over and I'll see what happened.
Best,
|
|
|
|
Post by legendli on Oct 14, 2018 21:43:47 GMT -5
Your very welcome! Just have your path to the Navdata set correctly and SceneryScanner will override the old data from transition.cfg. Your Dispatch Release will have the correct value for each flight. ----- If you can find the FCDU log for that flight, send it over and I'll see what happened. Best, -5!!! The flight has been erased  |
|
|
|
Post by Travis on Oct 24, 2018 22:20:00 GMT -5
If you wish to check out 1.8.1 Beta 2, you will notice a subtle change that will no longer penalize you for setting "non-standard pressure" on your altimeter after you've received Approach Clearance from your airline. (The FCDU message for Approach Clearance should include your destination's last reported altimeter setting if you're running a weather engine - although you are not required to set your altimeter to that specified value.) Regards,
|
|
evolae
Trainee
Nosey Parker
Posts: 36
|
Post by evolae on Dec 3, 2018 5:09:45 GMT -5
Hello, I just started with FSCaptain and I love it so far. But I alway fly with IVAO and I`m getting the penalty of the transition level. As I learned, when an ATC gives you a altitude in feets (Descent to 5000feet, QNH 1020, for example) you MUST set your altimeter subscale to the local air pressure. The ATC must give you mandatory the QNH when he allows you to descent to a a sltitude, no matter if you are at fl060 or fl100.
How can I manage this in FSC to avoid this penalty?
Yesterday I installed 1.81 Beta 2.
|
|
|
|
Post by Travis on Dec 3, 2018 14:47:29 GMT -5
If you do not have a \Config\options.cfg file present, look for \Config\options.bak, and rename it "options.cfg".
Open your options.cfg file and search for this line:
DISABLESTD=0
Change the 0 to a 1 and save the file.
You should not then be pestered by FSCaptain to do anything.
I don't recall if we list the TA/TL values in the FCDU or on the Dispatch Release if we're not tracking them. I could easily remove them from the DR, if you prefer....
Best,
|
|
|
|
Post by Travis on Dec 3, 2018 15:14:57 GMT -5
Hello, Evolae! I have two questions for you: - Does IVAO accept requests to exceed the 250kt speed restriction below 10000ft?
- If they do accept such requests, do they ever grant those requests?
Regards, |
|
evolae
Trainee
Nosey Parker
Posts: 36
|
Post by evolae on Dec 3, 2018 16:19:29 GMT -5
You can never exceed the 250kts restriction bellow FL100, I think. Never asked to...but I think they cannot alow you to exceed it.
Thanks, I will try that.
|
|
|
|
Post by Travis on Dec 17, 2018 23:11:19 GMT -5
You can never exceed the 250kts restriction bellow FL100, I think. Never asked to...but I think they cannot alow you to exceed it. Thanks, I will try that. Please let us know if it's better / worse / no different for you! If you're confident they won't ever allow you to exceed 250kt, then I can code that as an option for a future feature for "this airline uses 'online rules'." Until then, if you're certain they won't ever allow such, you can set your options.cfg file's entry for "ODDS_TO_DECLINE_250" to this:
ODDS_TO_DECLINE_250=100And then you'll never have "FSCaptain ATC" allow you to exceed its speed limit. ---- I don't recall if we list the TA/TL values in the FCDU or on the Dispatch Release if we're not tracking them. I could easily remove them from the DR, if you prefer.... The current build of Release Candidate 1 should not display TA/TL data on the FCDU or in the Dispatch Release if the DISABLESTD option is active. Best, |
|
|
|
Post by alaskanflyboy on Dec 18, 2018 14:21:12 GMT -5
I'm sure IVAO accepts and grants the requests on a realistic basis. It's rare to my knowledge even in the real world as there has to be a safety-related need, such as the aircraft is unsafe to fly at those speeds. If you're flying some of the heavies like the older 747s and MD-11s near max gross, minimum maneuvering speeds can easily get into the high 200s. Here's what the FARs have to say about the matter, specifically paragraph (d): 14 CFR 91.117- (a) Unless otherwise authorized by the Administrator, no person may operate an aircraft below 10,000 feet MSL at an indicated airspeed of more than 250 knots (288 m.p.h.).
- (b) Unless otherwise authorized or required by ATC, no person may operate an aircraft at or below 2,500 feet above the surface within 4 nautical miles of the primary airport of a Class C or Class D airspace area at an indicated airspeed of more than 200 knots (230 mph.). This paragraph (b) does not apply to any operations within a Class B airspace area. Such operations shall comply with paragraph (a) of this section.
- (c) No person may operate an aircraft in the airspace underlying a Class B airspace area designated for an airport or in a VFR corridor designated through such a Class B airspace area, at an indicated airspeed of more than 200 knots (230 mph).
- (d) If the minimum safe airspeed for any particular operation is greater than the maximum speed prescribed in this section, the aircraft may be operated at that minimum speed.
|
|
