ClausHoffmann Posted January 4, 2020 Posted January 4, 2020 While constructing a training mission for navigation on the NTTR map I stumble on a problem I cannot understand. In the Mission Editor under the weather settings the QNH is set to 29.92 inHg. It is my understanding that this means, if altimeter is set to this value, it will show an altitude of zero. In the mission the tower in Nellis gives me a QFE of 28.06 inHg. This value cannot even be dialed into the altimeter of the F/A-18C Hornet. 28.10 inHg is the minimum to be dialed in and then the altitude is shown as close to zero. In fact Nellis AFB is roughly 1.850 ft high. This should be shown on the altimeter. What am I getting wrong here? Thank you very much for your support.
iFoxRomeo Posted January 4, 2020 Posted January 4, 2020 QNH gives your altimeter the reference to mean sea level. So if you set the QNH you would only see 0ft when you´re swimming on the water. QFE would show you 0ft when on the runway. But at the elevation figures in NTTR not many altimeters can set the required values. Fox 1 Spoiler PC Specs: Ryzen 9 5900X, 3080ti, 64GB RAM, Oculus Quest 3
ClausHoffmann Posted January 4, 2020 Author Posted January 4, 2020 Okay, thank you. I mixed up the terms obviously. Still I am wondering, why ATC in Nellis gives me the QFE, which is not of use for anything and cannot be dialed in in the jet anyway.
Hippo Posted January 10, 2020 Posted January 10, 2020 (edited) QFE gives you your height above the runway. I don't know what the USAF does IRL at Nellis or elsewhere, and I'd certainly be interested to know (QNH?). I think QFE is used by some airforces around the world (e.g. UK RAF), and for some reason ED has hard coded using QFE into the game's ATC, and so we're stuck with it (for now). Clearly you'd not have the same issue at the Caucausus airbases. Still, it's a curious choice, since using QNH is much more common throughout the world. *EDIT* From a quick browse around, it seems that QFE is used in Russia, so that explains the ED choice. For Nevada, I would just dial in the QNH into the altimeter instead (available from the briefing iirc, or just dial in the airfield altitude from its chart). *EDIT* And it seems that I Don't RC. QNH is not given in the briefing (althought it really, really should be) - sorry. *EDIT* PS Shamelessly copied and pasted from elsewhere: 1 inch mercury is approximately equal to 900 feet. This calculation is therefore also approximate but is good for airfield elevations to several hundred feet since we round to the nearest hundredth inches. Divide the airfield altitude in feet by 900 to get the number of inches above MSL. Add this to the QFE to get QNH or subtract it from QNH to get QFE. For example, the airfield elevation is 300 feet. Diving by 900 gives us 0.33r. The QFE is 30.12. Add 0.33 to get 30.45 which is the QNH. If the airfield elevation is below sea level, subtract rather than add and vice versa. Edited January 11, 2020 by Hippo 2 System spec: Intel i7 12700k @ stock, ASUS TUF Gaming GeForce RTX 3080 Ti 12GB GDDR6X, Gigabyte Z690 UD DDR4, Corsair Vengeance LPX 32GB (2 x 16GB) DDR4 3200MHz C16, Samsung 980 EVO 500 GB NVME M.2 SSD (system drive), WD Black SN 850X 2TB NVME M.2 SSD (games drive), Thermalright Assassin Spirit 120 Evo Cooler, Asus XG43UQ Monitor, Oculus Quest Pro, Thrustmaster Warthog HOTAS Prev System spec (leaving here because I often reference it in my posts): Intel i9 13900KF @ stock, Gigabyte GeForce RTX 4090 Gaming OC 24GB GDDR6X, Gigabyte Z690 UD DDR4, Corsair Vengeance RGB PRO SL 32GB (2 x 16GB) DDR4 3600MHz C18, Samsung 980 EVO 500 GB NVME M.2 SSD (system drive), Samsung 970 EVO 1 TB NVME M.2 SSD (games drive), Cooler Master ML360 Illusion CPU Cooler, Asus XG43UQ Monitor, Oculus Quest Pro, Thrustmaster Warthog HOTAS, MFG Crosswind Rudder Pedals
Yurgon Posted January 10, 2020 Posted January 10, 2020 Still I am wondering, why ATC in Nellis gives me the QFE, which is not of use for anything and cannot be dialed in in the jet anyway. It's ancient DCS behavior. And you're right, with most of the Nevada airports QFE can't even be dialed in. For now I guess we have to accept it. But today's newsletter mentioned the ongoing plans to implement a new ATC for land based airfields. I'm pretty sure the old QFE-problem will be revisited with the new ATC. Plus, they mentioned improved weather, dynamic weather and weather/pressure fronts. In a more dynamic environment, we might finally get to see a real pressure difference across the maps and over time. In any case, as long as the mission uses Static Weather, I believe the air pressure will be static across the entire map, so you can just dial in QNH before takeoff, maybe take a note of the pressure setting in case you transition to standard pressure/flight levels, and then dial that same QNH back in before you land. Should be close enough for most cases. There's also the possibility to calculate QNH from QFE and vice versa for a given altitude; I don't have a formula at hand, but that should be easy enough to google. So if you have dynamic weather, bad visibility and you really need a proper QNH, you could still calculate that from the QFE that the tower gives you.
DarkFire Posted January 13, 2020 Posted January 13, 2020 I'm hoping with the new ATC coding we'll get the option of full METAR reporting. That way everyone will be accommodated - QFE for VKS & RAF, QNH for our USAF & USN friends. I'm vaguely amazed that NATO didn't standardize on one pressure reading standard. System Spec: Cooler Master Cosmos C700P Black Edition case. | AMD 5950X CPU | MSI RTX-3090 GPU | 32GB HyperX Predator PC4000 RAM | | TM Warthog stick & throttle | TrackIR 5 | Samsung 980 Pro NVMe 4 SSD 1TB (boot) | Samsung 870 QVO SSD 4TB (games) | Windows 10 Pro 64-bit. Personal wish list: DCS: Su-27SM & DCS: Avro Vulcan.
Recommended Posts