fjacobsen Posted April 6, 2014 Posted April 6, 2014 Can anyone explain what might have caused this: During approach to the carrier, I heard a "puf" and both engines failed and caught fire. I was fully configured - Hook down. Gear down, flaps extended. Throttles was set to keep the approach speed of 270 km/h. FinnJ | i7-10700K 3.8-5.1Ghz | 64GB RAM | RTX 4070 12GB | 1x1TB M.2. NVMe SSD | 1x2TB M.2. NVMe SSD | 2x2TB SATA SSD | 1x2TB HDD 7200 RPM | Win10 Home 64bit | Meta Quest 3 |
uboats Posted April 6, 2014 Posted April 6, 2014 Can anyone explain what might have caused this: During approach to the carrier, I heard a "puf" and both engines failed and caught fire. I was fully configured - Hook down. Gear down, flaps extended. Throttles was set to keep the approach speed of 270 km/h. FinnJ It should be AOA too large that the engine touch deck Check replay [sIGPIC][/sIGPIC] My DCS Mods, Skins, Utilities and Scripts | Windows 10 | i7-4790K | GTX 980Ti Hybrid | 32GB RAM | 3TB SSD | | TM Warthog Stick | CH Pro Throttle + Pro Pedal | TIR5 Pro | TM MFD Cougar | Gun Camera: PrtScn |
fjacobsen Posted April 6, 2014 Author Posted April 6, 2014 Track? Sorry I forgot to save a track, but it simply came out of nowhere... But I also had too high AOA in mind, though I rather expected a flameout rather than an engine fire to evolve. On the otherside if airflow is disrupted while still spraying fuel into the engine, to little amount of bypass air could be present to cool down the engine core. I just don´t expect that the FC3 aircraft are that detailed. FinnJ | i7-10700K 3.8-5.1Ghz | 64GB RAM | RTX 4070 12GB | 1x1TB M.2. NVMe SSD | 1x2TB M.2. NVMe SSD | 2x2TB SATA SSD | 1x2TB HDD 7200 RPM | Win10 Home 64bit | Meta Quest 3 |
JNASova Posted April 6, 2014 Posted April 6, 2014 My English is not so good,and internet translatror dont help much. You said you was at aproach. So you had fire at engine until you was in the air or when touch the runway at carrier? Смрт фашизму,слобода народу! www.jna.site50.net
fjacobsen Posted April 6, 2014 Author Posted April 6, 2014 My English is not so good,and internet translatror dont help much. You said you was at aproach. So you had fire at engine until you was in the air or when touch the runway at carrier? Both engines simply went on fire in midair when I was just 30 seconds from landing on the carrier. FinnJ | i7-10700K 3.8-5.1Ghz | 64GB RAM | RTX 4070 12GB | 1x1TB M.2. NVMe SSD | 1x2TB M.2. NVMe SSD | 2x2TB SATA SSD | 1x2TB HDD 7200 RPM | Win10 Home 64bit | Meta Quest 3 |
Zabuzard Posted April 6, 2014 Posted April 6, 2014 Mh i guess itll be pretty hard to find the reason without the track... :(
MauganRa84 Posted April 7, 2014 Posted April 7, 2014 Multiple simultaneous bird strikes? =P ...Sheila rides on crashing nightingale. Intake eyes leave passing vapor trails... [sIGPIC][/sIGPIC]
betatrash Posted April 7, 2014 Posted April 7, 2014 Multiple simultaneous bird strikes? =P one bird. went in one engine, out the other.
fjacobsen Posted April 7, 2014 Author Posted April 7, 2014 one bird. went in one engine, out the other. Ah - that makes sense :music_whistling: | i7-10700K 3.8-5.1Ghz | 64GB RAM | RTX 4070 12GB | 1x1TB M.2. NVMe SSD | 1x2TB M.2. NVMe SSD | 2x2TB SATA SSD | 1x2TB HDD 7200 RPM | Win10 Home 64bit | Meta Quest 3 |
Zabuzard Posted April 7, 2014 Posted April 7, 2014 Bird strikes only occure if enabled in the settings (or mission settings)
Nate--IRL-- Posted April 7, 2014 Posted April 7, 2014 Sounds like random damage options set in the mission. Without a track it will be impossible to tell. Nate Ka-50 AutoPilot/stabilisation system description and operation by IvanK- Essential Reading
Recommended Posts