GreenGriffon Posted February 17, 2009 Posted February 17, 2009 Hi guys, I'm working on a series of videos for YouTube that show some of my worst mishaps and crashes. I wanted to share these with my friends who are also going through some "growing pains" while they transition from LOMAC to Black Shark. Anyway, in my second video, I crash just before I reach the runway. My main hydraulics were out along the way, then suddenly my pitched bucked upward, and the EKRAN kept saying "danger, engine vibration", followed by an engine fire right afterward that dropped me like a rock. This is the clip (at about 1:20 is when this happens): Any idea what I did to cause this? All I was trying to do was keep her slow and level enough to land. Thanks for any insight, GG
Doomhawk Posted February 18, 2009 Posted February 18, 2009 The mission sets up failiures to challenge you, It was supposed to happen.
Nate--IRL-- Posted February 18, 2009 Posted February 18, 2009 Would have to see your gearbox oil pressure and various other fluid levels to make a guess, not a lot to go on in that vid. Nate Ka-50 AutoPilot/stabilisation system description and operation by IvanK- Essential Reading
GreenGriffon Posted February 18, 2009 Author Posted February 18, 2009 @Doomhawk - Ah, I had no idea. I thought it was something I did. @Nate - Good point. I never saved the track, so I couldn't go back and record what my gauges looked like. I was recording that on-the-fly. However if that particular problem was scripted, then I'm not terribly curious as to how it happened. I just thought it was my flying :)
Doomhawk Posted February 18, 2009 Posted February 18, 2009 Heh I had the same problem, I found out by opening it up with mission editor.
JDski Posted February 18, 2009 Posted February 18, 2009 Looks like you would have lived if you didn't bail. At least until your crew chief got hold of you.
GreenGriffon Posted February 18, 2009 Author Posted February 18, 2009 Yeah, it was very surprising that the aircraft was mostly intact after I hit the ground (no pun intended). I didn't realize until last week that you could script mechanical failures into missions, which is why I never bothered to look in the mission editor when this happened. Just thought it was my newb flying that caused it.
zdXu Posted June 24, 2009 Posted June 24, 2009 (edited) At 1:29 you had +5m/s climbrate and 6 sec later you had -6m/s climbrate. Engine-vibration only(?) occurs when the rotor is not intact. So i think there was a light rotor-clash caused by overpushing the cyclic to loose altitude to reach the runway. The RPM after the clash and before the fire was at 85 % (at 1:40). So overspeeding and engine-management-failure causes the engine-fire is doubtfull. Other suggestions for this accident? Edited June 24, 2009 by zdXu
Feuerfalke Posted June 24, 2009 Posted June 24, 2009 (edited) You already had a warning on the EKRAN before the engine vibration killed your engine. Probably coming from the hydraulics, according to your description. If you sustained damage, you have to watch for other damage-symptoms, as not all will cause a warning. You may have lost oil all the way or a problem with the engine controls. So it's more likely cascading damage than a preprogrammed engine failure or something like that. (Engine vibration can have various causes, from lack of oil and mechanical damage to collecting to much dust or ice.) Edited June 24, 2009 by Feuerfalke MSI X670E Gaming Plus | AMD Ryzen 7 7800X3D | 64 GB DDR4 | AMD RX 6900 XT | LG 55" @ 4K | Cougar 1000 W | CreativeX G6 | TIR5 | CH HOTAS (with BU0836X-12 Bit) + Crosswind Pedals | Win11 64 HP | StreamDeck XL | 3x TM MFD
Recommended Posts