Nealius Posted January 6, 2019 Posted January 6, 2019 (edited) After Jabber's video there's been some discussion elsewhere about the airspeed indicator--namely how it lacks information in knots: With marshal airspeeds at 250kts, CASE I initial-to-break speeds usually 350kts, and all carrier departures at 300kts until exit at 7DME, what's the procedure in the Tomcat when there's no airspeed indicated in knots between 200kts and 450kts (according to that screen shot)? The NAVAIR 01-F14AAA-1 says the indicator displays 80kts to 850kts, but I don't see that in the screenshot. I'm a bit confused. Edited January 6, 2019 by Nealius
BlackLion213 Posted January 6, 2019 Posted January 6, 2019 Both the window and the background (IAS in knots) move so that it displays your current airspeed. Even in VR it is very readable and easy to interpret once you see it in action. -Nick
Nealius Posted January 6, 2019 Author Posted January 6, 2019 Aha! The manual mentioned the Mach tape moved, but without a visual I couldn't figure out how it was supposed to work. Is the Mach tape actually stationary, and that window that indicates 450-650 the part that moves?
RustBelt Posted January 6, 2019 Posted January 6, 2019 Aha! The manual mentioned the Mach tape moved, but without a visual I couldn't figure out how it was supposed to work. Is the Mach tape actually stationary, and that window that indicates 450-650 the part that moves? It's like this, here's the Airspeed and Mach Indicator: You can see TWO white pointers running radial from the center of the dial, those rotate around the dial together (they are both connected to the disk with the window in it.) They move ONLY in relation to Knots Indicated Airspeed. The green area is Airspeed in Knots Indicated Airspeed x10 from 80 to 200 knots. That is big and shown on the outside scale because at those speeds KIAS matters A LOT. The Line (Blue Rectangle) at 200 Knots is where the outer needle transitions to Mach number and the Inner needle in the window (blue circle) then takes over reading Knots Indicated Airspeed from 200 - 800 Knots on that inner scale behind the window. The red area is the Mach indicator, and that whole part of the indicator moves because MACH has to do with Density Altitude caused by Barometric Pressure and air temperature and all kinds of Air Data Computer stuff. (Mach is basically True Airspeed plus Compression compensation in relation to the speed of sound in the air you're moving through) So it changes depending on lots of factors depending on where the airplane is in the air. It's behind the face of the dial, if you look you can see the window cutout it shows through. So as the needle passes 200 Knots the IAS is read on the window in the blue circle while the needles, and that whole central disk, keep rotating Clockwise past 200 Knots. The Mach indicator moves Clockwise or counter clockwise to read the mach number on the outer needle as the needle sweeps along still indicating IAS now on the inside window of the disk. The Mach indicator is an on the fly calculation dependent on Knots Indicated Air Speed so it changes in relation to a given KIAS due to Density Altitude.
Pyker Posted May 23, 2020 Posted May 23, 2020 May I ask what the two white triangles / arrows at one o'clock and ten o'clock are for ? Thank you in advance.
Victory205 Posted May 23, 2020 Posted May 23, 2020 May I ask what the two white triangles / arrows at one o'clock and ten o'clock are for ? Thank you in advance. Those can be set as a reference independently using the GIGANTIC knob. Turn for Knots, Push and Turn for Mach. Fly Pretty, anyone can Fly Safe.
Shaemus ODonnelly Posted May 23, 2020 Posted May 23, 2020 I was today years old when i found out the Tomcat had an airspeed/mach bug, thanks Victory205! Obviously i had to jump in and try it out. Sadly, both arrows seemed to be attached to the Mach scale, so i couldnt set a consistent KIAS target, only 2 Mach targets. Any input from Heatblur wether that is intentional or a bug/modelling fault?
AvroLanc Posted May 23, 2020 Posted May 23, 2020 I was today years old when i found out the Tomcat had an airspeed/mach bug, thanks Victory205! Obviously i had to jump in and try it out. Sadly, both arrows seemed to be attached to the Mach scale, so i couldnt set a consistent KIAS target, only 2 Mach targets. Any input from Heatblur wether that is intentional or a bug/modelling fault? + 1 I confirm this as well. Only sets 2 Mach targets. Been like it since day 1. Bug unfortunately.
eatthis Posted May 24, 2020 Posted May 24, 2020 i never even knew it was 2 needles not 1 lol 7700k @5ghz, 32gb 3200mhz ram, 2080ti, nvme drives, valve index vr
sublime Posted May 24, 2020 Posted May 24, 2020 May I ask what the two white triangles / arrows at one o'clock and ten o'clock are for ? Thank you in advance. Is the answer you got right? Because they move without me touching them. I Thought based on observation the lower is stall speed (and it moves at diff altitudes and wing angles) Top is max speed. And guess what.. its usually around mach 1.2 and goes up if im.lighter or way higher.
AvroLanc Posted May 24, 2020 Posted May 24, 2020 Is the answer you got right? Because they move without me touching them. I Thought based on observation the lower is stall speed (and it moves at diff altitudes and wing angles) Top is max speed. And guess what.. its usually around mach 1.2 and goes up if im.lighter or way higher. They are not preset to anything, they are completely manual control, purely set by the pilot as a reminder. Not linked to systems. The reason they move is that they both incorrectly respond to Mach number, when only one should.
Pyker Posted May 24, 2020 Posted May 24, 2020 + 1 I confirm this as well. Only sets 2 Mach targets. Been like it since day 1. Bug unfortunately. +1 Very annoying bug. The speed is already difficult to read. If it worked like it should, it would help me maintain the correct speed when landing. Has this bug been reported already?
Golo Posted May 24, 2020 Posted May 24, 2020 +1 Very annoying bug. The speed is already difficult to read. If it worked like it should, it would help me maintain the correct speed when landing. Has this bug been reported already? And why would you be looking at your airspeed indicator when landing?
Pyker Posted May 24, 2020 Posted May 24, 2020 And why would you be looking at your airspeed indicator when landing? I meant before landing (approach, ´on speed aoa' and so on). My English and my flying are equally bad.
Whiskey11 Posted May 24, 2020 Posted May 24, 2020 I meant before landing (approach, ´on speed aoa' and so on). My English and my flying are equally bad. On speed AoA is an AoA measurement only. The speed is largely irrelevant when landing, only the AoA matters due to hook to airframe angle to catch wires on the deck. My YT Channel (DCS World, War Thunder and World of Warships) Too Many Modules to List --Unapologetically In Love With the F-14-- Anytime Baby! --
sLYFa Posted May 24, 2020 Posted May 24, 2020 You would still want to cross-check your computed and actual speed at 15AoA. Well IRL you would, in DCS I guess this doesnt matter since neither the AoA probe nor the pressure sensors can fail. 1 i5-8600k @4.9Ghz, 2080ti , 32GB@2666Mhz, 512GB SSD
Sublimearrepentido Posted May 25, 2020 Posted May 25, 2020 They are not preset to anything, they are completely manual control, purely set by the pilot as a reminder. Not linked to systems. The reason they move is that they both incorrectly respond to Mach number, when only one should. Ah ok thanks
MRSHADO Posted January 7, 2021 Posted January 7, 2021 (edited) +1 I am curious which is the Mach pointer and which is the airspeed index pointer. Any word on getting one of these to function as the stationary airspeed index pointer? Edited January 7, 2021 by MRSHADO i7-8700K / 64GB RAM / ASUS Strix GTX 1080 Ti / (Win 10 Pro) / Oculus Rift S
flybull Posted January 7, 2021 Posted January 7, 2021 I've brought this to HBs attention in the past (twice) and never received a reply.
Recommended Posts