A10Yoda Posted December 6, 2017 Posted December 6, 2017 Was dabbling with range on the Harrier and was pushing speed above 26,000 feet when I received an OT warning light on the UFC right border. After the warning I was experiencing degraded thrust and found no way to recover the lost thrust. I am guessing I over-throttled the turbine and broke the turbine. Anyone have any specific knowledge of what happened and is it recoverable? Sent from my SM-N950U using Tapatalk
MadDog08 Posted December 6, 2017 Posted December 6, 2017 Whenever I have had an over temp warning I have simply reduced my RPM a bit and the JPT cools pretty quickly. Not sure of you exact situation, or if you tried pulling back on the throttle to allow JPT to cool down or not, but that has always worked for me. MadDog [sIGPIC][/sIGPIC]
noisy_lightning Posted December 6, 2017 Posted December 6, 2017 I had one today launching from a carrier. Right at the critical point of take off I got the OT and despite quickly throttling back I still ended up in the drink. Can't say what caused it as I had launched a good number of times over the evening in the same way.
Essah Posted December 7, 2017 Posted December 7, 2017 I consistently have OT warnings immediately on mission start, despite sitting at idle. I suspect there's a bug. If not then I'm not sure whats up with the engine.
rinao0o Posted December 7, 2017 Posted December 7, 2017 OT warning can happen after pushing the engine over its limits too much, check manuel for details. Also if you run the engine during jetborn flight with water off and max thrust, the fan rpm will be at 109% and the maximum allowed time is 15 minutes under this configuration. Use 100%RPM or less during cruise and only kick the engine into full when in combat
Kelevra9987 Posted December 7, 2017 Posted December 7, 2017 During the first flights I got OT Warnings too and scratched my head why I'd get degraded engine performance. But like rinao0o allready said, don't push that engine too hard. I can happily cruise at 400KIAS with 65% RPM in low altitudes with flaps at 0°. Also you save a lot of fuel that way. Modules: Well... all of 'em ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ Motherboard: ASUS Maximus VIII Hero | CPU: i7-6700K @ 4.6GHz | RAM: 32GB Corsair Vengance LPX DDR4 | GPU: GTX TITAN X (Maxwell) | SSD1: 256GB NVMe SSD System | SSD2: 250GB Games | HDD 4TB WD Red
DartzIRL Posted December 7, 2017 Posted December 7, 2017 Might be a sign of hot gas ingestion and recirculation? I've only ever seen it when I'm doing high-G sustained VIFF turn and the speed drops right off under maximum throttle.
A10Yoda Posted December 7, 2017 Author Posted December 7, 2017 OT warning can happen after pushing the engine over its limits too much, check manuel for details. Also if you run the engine during jetborn flight with water off and max thrust, the fan rpm will be at 109% and the maximum allowed time is 15 minutes under this configuration. Use 100%RPM or less during cruise and only kick the engine into full when in combatUnderstood. But this was for small duration (maybe a minute) but I was above 25000 feet which could have contributed to over exertion. I was cruising at 390 knots after a slow climb to cruising altitude. Was trying to get air speed up before setting engine to a cruise setting. Haven't been able to recreate the failure since.. Sent from my SM-N950U using Tapatalk
smallberries Posted December 7, 2017 Posted December 7, 2017 (edited) I consistently have OT warnings immediately on mission start, despite sitting at idle. I suspect there's a bug. If not then I'm not sure whats up with the engine. I can't say it with 100% confidence, but I have been paying a lot of attention to JPT to try to learn to VTOL/land with a load, properly, and in some of my missions that involve many attempts and just re-selecting my role and trying again....it seems the OT state can remain from an old plane when you spawn a new one. A fresh plane should start off saying OT 4 secs on the ENG page in the MFD, and I have noticed a fresh plane saying 43 secs (a sign of overheating, although I don't really know what it means yet), and ofc the OT warning light is on, immediately after spooling up normally. This is immediately following a normal cold start, so I think the bug is that the OT state is persistent within a mission between spawns, or can be perhaps, based on your DCS install. I have also been getting a bug where trying to get the ground crew to reduce my fuel has resulted in fuel being added, or the ground crew claiming to change the loadout (without any changes being requested to weapons) instead, and I've had to request this several times before it happens properly, but none of my friends have reported it, so maybe it's quirky and it's just some of us getting some odd bugs (British humour)? Edited December 7, 2017 by smallberries
Sneak69 Posted December 7, 2017 Posted December 7, 2017 I have also been getting a bug where trying to get the ground crew to reduce my fuel has resulted in fuel being added, or the ground crew claiming to change the loadout (without any changes being requested to weapons) instead, and I've had to request this several times before it happens properly, but none of my friends have reported it, so maybe it's quirky and it's just some of us getting some odd bugs (British humour)? I have had this happen to me as well. I could not rearm even after rebooting dcs and my system. I had to spool the engine up then i got rearmed. I also have had OT problems on new planes without going over rpm limit of 102 and temp of 645. I wonder if there is some kind of carry over bug. Sent from my SM-G930W8 using Tapatalk
Recommended Posts