December 31, 201114 yr I don't think FSX knows the difference between CAT II or CAT III or CAT I for that matter. To me, any aiport with an ILS is a potential autoland with 100 Radio minimums. Until i learn to program AS2012 with thick fog to 50 feet, my mins are always 100 Radio. I guess I need to expand my FSX experience.The minimums for any approach is stated on the approach charts. Mostly it is given in both Height (DH=using RADIO altimiter) and Altitude (DA=using BARO altimiter). Often depicted as exeample; CAT II DA(H) 157 (72), where 157 is the descision Altitude above sealevel on a local QNH (or altimeter setting), and 72 is the height above the ground messured on a Radio altimeter...If both a BARO minimums and RADIO minimums are on the chart, you can use which ever you like...FSX couldn't give less about the approach CAT, but you as a pilot should however ;)And the usual disclaimer: I'm not a RW pilot, so my answer is not the almightys law - feel free to challenge everything I wrote ;)Happy New Year!MAs Martin Jensen
December 31, 201114 yr ...The radar altimeter is not legal for use except on approaches where the DH is specified as RA--that's Cat II/III ILS only. Minimums on a Cat I ILS are baro, as a Cat I approach is not designed, certified, or flight tested for use of RA settings--this can be a problem for approaches where the DH is reached over water, or when there is significant terrain just off the approach end of the rwy.Exactly. If you use radio altimeter on certain approaches where the airport is elevated compared to the surroundings and the visibility is very low you will be flying your plane straight into the ground during your approach. Johan Pettersen
December 31, 201114 yr It's as simple as adding a separate hotkey to increment/decrement the mins by 100s. FWIW, assigning a hotkey and holding it down is the best solution right now, but still slow and tedious.The radar altimeter is not legal for use except on approaches where the DH is specified as RA--that's Cat II/III ILS only. Minimums on a Cat I ILS are baro, as a Cat I approach is not designed, certified, or flight tested for use of RA settings--this can be a problem for approaches where the DH is reached over water, or when there is significant terrain just off the approach end of the rwy.+1
December 31, 201114 yr I assigned mine to the number pad '9' and '3' keys so I can just hold down to set BARO mins.I mainly use Radio for my mins.I use same option, looks to me so far this is the fastest known option. I9-13900K | ASUS ROG Strix Z790-E Gaming LGA 1700 | MSI Gaming GeForce RTX 4090 24GB | CORSAIR iCUE H150i ELITE LCD Liquid Cooler | CORSAIR DOMINATOR PLATINUM 64GB (2X36) 5200MHx DDR5 | Thermaltake GF3 1650W 80+ Gold PSU | Samsung QN90C Neo QLED TV 50”
December 31, 201114 yr The minimums for any approach is stated on the approach charts. Mostly it is given in both Height (DH=using RADIO altimiter) and Altitude (DA=using BARO altimiter). Often depicted as exeample; CAT II DA(H) 157 (72), where 157 is the descision Altitude above sealevel on a local QNH (or altimeter setting), and 72 is the height above the ground messured on a Radio altimeter...If both a BARO minimums and RADIO minimums are on the chart, you can use which ever you like...FSX couldn't give less about the approach CAT, but you as a pilot should however ;)And the usual disclaimer: I'm not a RW pilot, so my answer is not the almightys law - feel free to challenge everything I wrote ;)Happy New Year!MAsOf course, you are completely correct. I've gotten lazy lately (actually a little longer than lately) and have not been using any charts. Just FS Commander and the FMS. Now that I think about it, I don't even know if minimums are available without the charts. I'm going to upgrade my experience with real world minimums. Should be fun.... except for that darned Baro minimums adjustment knob. Dennis Trawick Screen Shot Forum Rules
December 31, 201114 yr Did you guys try to set a key command in the PMDG setup menu in the FMC?It works like a charm for me, I set 5506 BARO for Denver rwy ILS 26 in just a couple of seconds! ;-DJust like Raven I assigned it to NUM9 and 3. ------------------------ Mattias Nordin ESOW
January 1, 201214 yr Of course, you are completely correct. I've gotten lazy lately (actually a little longer than lately) and have not been using any charts. Just FS Commander and the FMS. Now that I think about it, I don't even know if minimums are available without the charts. I'm going to upgrade my experience with real world minimums. Should be fun.... except for that darned Baro minimums adjustment knob.As far as I can recall, the charts are the only place to find those minimums...I flew online a couple of months back, and Inbound Stockholm Arlanda in Sweden, I was clrd on a STAR findbound some ILS approach.. So I flew, and at that time I didn't wanne get the chats out and all - I mean, I had the thing on the FMC so no prb, right? Well all of a sudden, ATC said I was coming in too high, and that I should hold at TRS (i think it was) as published... It was terrible - I had overlooked an Altitude restriction on the chart, and also I had no idea how the published holdng was supposed to be - I messed that appoach up really bad - and since then - I ALWAYS crossref the FMC with the actual charts ;)About RADIO vs. BARO, I alwasy use RADIO for the same reason that I don't wanne spend the time dialing that BARO knob - is it because you guys fly into airports with no RADIO DH?Happy new year anyways!Mas Martin Jensen
January 1, 201214 yr The hotkey or button push I can add, but how do I access the "incr/decr by 100s" function?* OrestYou can't, unless/until PMDG adds that capability to the NGX. Bob Scott | President and CEO, AVSIM Inc ATP Gulfstream II-III-IV-V Sys1 (MSFS20+24/XPlane12+11): AMD 9800X3D, water 2x240mm, MSI MPG X670E Carbon, 64GB GSkill 6000/30, nVidia RTX4090FE Alienware AW3821DW 38" 21:9 GSync, 2x4TB Crucial T705 PCIe5 + 2x2TB Samsung 990 SSD, EVGA 1000P2 PSU, 12.9" iPad Pro Thrustmaster TCA Boeing Yoke, TCA Airbus Sidestick, Twin TCA Airbus Throttle quads, PFC Cirrus Pedals, Coolermaster HAF932 case Sys2 (P3Dv5/v4): i9-13900KS, water 2x360mm, ASUS Z790 Hero, 32GB GSkill 7800MHz CAS36, ASUS RTX4090 Samsung 55" JS8500 4K TV@60Hz, 3x 2TB WD SN850X 1x 4TB Crucial P3 M.2 NVME SSD, EVGA 1600T2 PSU Fiber link to Yamaha RX-V467 Home Theater Receiver, Polk/Klipsch 6" bookshelf speakers, Polk 12" subwoofer, 12.9" iPad Pro PFC yoke/throttle quad/pedals with custom Hall sensor retrofit, Thermaltake View 71 case, Stream Deck XL button box Sys3 (DCS/P3Dv4/ATS/ETS): AMD 7800X3D, MSI MPG X870E Carbon, Noctua NH-D15S, 64GB GSkill 6000/30, EVGA RTX3090 Alienware AW3420DW 34" 21:9 GSync, Corsair HX1000i PSU, 4TB Crucial T705 PCIe5 + 2TB Samsung 970Evo Plus, TM TCA Officer Pack, Saitek combat pedals, TM Warthog, TM RS300 FF wheel/pedals, Coolermaster HAF XB case
January 1, 201214 yr Author Hee, hee. Well, that I already knew. I thought you had discovered a cool trick. Oh well.* Orest Orest Skrypuch President & CEO, UVA www.united-virtual.com
Create an account or sign in to comment