Bunyap Posted January 3, 2015 Posted January 3, 2015 On the Range #43 is up covering emergency procedures for an engine fire in the A-10C. I hope you enjoy it and there is more to come soon. Bunyap Sims Youtube Channel 1
Fakum Posted January 3, 2015 Posted January 3, 2015 Yeah, really good,, there are procedures you performed that I never did in the past. Question though,, I have no idea what caused the engine fire to begin with, I do understand if you took a hit, but I did not see that was the case,, so if you did not take a hit, would you take the position of trying to do a restart of that engine in that case? I understand that was not the point of the video, but it sparks a question, at least for me,,, thanks. Windows 10 Pro - 64 Bit / ASUS ROG Strix B650E-F Gaming / AMD 7800X3D / G.Skill Trident Z5 NEO 64GB DDR5 6000 Ram / SSD M.2 SK hynix Platinum P41 2TB / MSI Gaming GeForce RTX 4090 SUPRIM Liquid X 24G / SteelSeries Arctis 7 Headset /LG-Ultragear 38" IPS LED Ultrawide HD Monitor (3840 x 1600) / Track IR4 / Thrustmaster TPR Pendular Rudder Pedals / Virpil HOTAS VPC Constellation ALPHA-R & VPC MongoosT-50CM3 Throttle
chaos Posted January 5, 2015 Posted January 5, 2015 Liked the video a lot. It shows that you're putting a lot of thought into these. That 'extra' problem regarding terrain and performance is often overlooked. re: bold faced procs. Take you're time completing these. Yes, they're supposed to be done without delay but you wouldn't be the first to cut the 'live' engine in an effort to contain the problem. Go through it methodically and "think" before you start throwing switches. You might have done that but it wasn't apparent from looking at the video. I realize I'm just nitpicking here but it would be good point to make, I think. "It's not the years, honey. It's the mileage..."
ttaylor0024 Posted January 5, 2015 Posted January 5, 2015 (edited) so if you did not take a hit, would you take the position of trying to do a restart of that engine in that case? No. If your engine catches on fire you immediately want to put the fire out, shut it down, secure it, and RTB. Your aircraft can fly just fine with one engine, use it to let maintenance do their job so you can safely and effectively do yours in the future. Liked the video a lot. It shows that you're putting a lot of thought into these. That 'extra' problem regarding terrain and performance is often overlooked. re: bold faced procs. Take you're time completing these. Yes, they're supposed to be done without delay but you wouldn't be the first to cut the 'live' engine in an effort to contain the problem. Go through it methodically and "think" before you start throwing switches. You might have done that but it wasn't apparent from looking at the video. I realize I'm just nitpicking here but it would be good point to make, I think. Problems regarding altitude performance is a relatively easy one to handle once you know the procedures. In the event of an engine failure you immediately pitch to VYse (best rate of climb on a single engine). I do not know this number exactly for the A-10C to be honest. If you are above the maximum service ceiling then it will be your best drift down speed, or in which you lose the least amount of altitude per a given unit of time. Regarding the cutting the live engine, yes, unfortunately this is a real issue. It happens every year with multi-engine pilots, and if you go watch the movie "Unbroken" right now, you can see that very thing happen. "Dead foot, dead engine," is the saying we use to identify the dead engine. This applies to the fact that if you lose your left engine lets say, then you will need to use right rudder in order to keep the aircraft coordinated. This is rather difficult to do quickly in the sim because you cannot feel the aircraft like you could in real life, thus could misinterpret the yaw for the roll that immediately follows. The proper saying for the procedure is "Identify, Verify, Troubleshoot, Feather, Secure." The feather part won't apply to the A-10C, however multi-engine pistons it would, in which you would feather the prop to reduce drag. For this discussion, simply remove that and think Identify, verify, troubleshoot, secure. Identify the dead engine, verify the dead engine, troubleshoot it (did it just fail, on fire, what happened? As long as it's not on fire, you really are alright with trying to restart for the most part. Battle damage usually won't restart for obvious reasons, and could lead to major issues), secure (turn it off, fuel off, etc). Edited January 5, 2015 by ttaylor0024 1
fltsimbuff Posted January 5, 2015 Posted January 5, 2015 Very informative. You might add though, that if you do happen to end up with fuel imbalance between wing tanks, you can use the "TX Gate" switch to re-balance the fuel (set to on). That has helped in the past when I forgot to enable cross-feed after a single engine failure. I can't find it now, but read somewhere this basically opens a fuel transfer connection between the tanks.
Yurgon Posted January 5, 2015 Posted January 5, 2015 On the Range #43 is up covering emergency procedures for an engine fire in the A-10C. I hope you enjoy it and there is more to come soon. Great video, very informative, thanks! :thumbup: The proper saying for the procedure is "Identify, Verify, Troubleshoot, Feather, Secure." The feather part won't apply to the A-10C, however multi-engine pistons it would, in which you would feather the prop to reduce drag. [...] Good addition, thanks as well! :)
Aviators Posted January 5, 2015 Posted January 5, 2015 ;) L'importante non è stabilire se uno ha paura o meno, è saper convivere con la propria paura e non farsi condizionare dalla stessa. Ecco, il coraggio è questo, altrimenti non è più coraggio ma incoscienza.
Recommended Posts