Van's Air Force

The definitive Van's Aircraft support community! Buying, building or flying an RV? Join our exclusive family of mentors and enthusiasts!

Night flight with an engine failure

BenNabors

Well Known Member
I had an engine failure at night a couple of weeks ago. I was five miles out from a grass field airport with trees, power lines and other considerations such as a berm at one end of the runway. I was familiar with the area and the airport. There was no warning, and the failure was so violent that I did not even bother attempting a restart.

First thing I would say is that everything is different than what you might have rehearsed and practiced. It is unlikely that you will be on a standard approach path or at a standard pattern altitude like we often practice. You will have maintained as much altitude as you can when you arrive over your landing area. Flight characteristics can be different with a stationary propeller. You must gage glide characteristics keeping in mind that winds may influence your glide distance when you change directions.

In my case, I arrived at the airport at 1000' AGL and had to turn away from the airport while judging distance and altitude. I remember looking over my shoulder as the airport was out of view. I chose the landing direction that had space to overrun the far end of the grass runway, but that had bad results on the approach end if I mismanaged distance, trees, power lines, ditches etc. The opposite direction had a tree line 1000 feet from the approach end but had an unmanageable berm at the far end in case of an over run. When I was assured to make the field, I had excess energy in the form of speed and altitude. I pulled flaps and initiated a hard slip. I bounced on my initial touchdown as I did not fully arrest my descent from the hard slip and still had a little excess speed. I could have floated the speed out but I wanted the option of braking if need, I have a tailwheel. From my touchdown to final stop was about 1500 feet, I had 600 feet of additional runway, and another 1000 feet of field before the next tree line. I rolled to within 20 feet of my runway exit and did use my brakes, ;-). No injuries, no bent metal, so I consider it a massive success.

From the time of the engine failure to touchdown was 5 minutes. In that time, I located the airport, reversed direction, flipped to the local approach frequency which I had on stand-by, (I keep the local approach frequency or 121.5 on standby), gave a mayday call, was given and entered a squawk code, gave souls on board and fuel, had ATC request that I write down a phone number to call after landing which I refused and called out my cell number, assessed position and ability to make airport, considered risk of land RWY 9 or 27, and maneuvered to chosen runway. In the meantime, I enjoyed the quiet and vibration free glide, I can remember thinking how beautiful the lights were and how serene and peaceful it was with the engine quiet. In hindsight, I find that surprising.
In the time it took me to unbuckle, shutdown everything, and climb out, take a deep breath, I saw someone with an off-road light driving around the airport. It turned out to be a sheriff's deputy. With-in 5 minutes, there were several more deputies. The first deputy did not see me right away and I thought that was odd as I had left my navigation lights and strobes on as I was still on the runway. It made me think about what if I had been upside down in a field, or forest somewhere.

With this experience, what would I tell someone to practice? From an altitude that you normally fly at, pull power and glide to an airport with a non-standard approach arriving at above or below the standard pattern altitude, practice turning away from the airport to consume excess altitude and energy. Have the muscle and mental memory to pitch down and transition to best glide speed at the moment of an engine failure. I was in a climbing turn at around 105 MPH when I had my catastrophic engine failure. Designate and fly with, on every flight, a minimum maneuvering speed (MMS) that you never fly below. Stall/Spin is the number 1 killer of GA pilots. I use 80 MPH MMS for convenience, which is about 1.4 times stall speed, actual number is 77. I credit Dan Gryder of the YouTube channel, Probable Cause, with my knowledge of and use of MMS. On this emergency flight, looking at my ADSB data, I had 1 data point at 76 with all the others between 89 and 93. It shows that I had speed variation that I did not know about in the moment of my emergency but that I had excess energy to maintain a safe speed that would not stall at a reasonable turning rate. In flight, the only time I remember looking at my speed was establishing best glide and when I was in the final phase of flight and trying to ensure that I did not have an insane speed, either high or low. I did not find a stationary propeller to have a such a significant impact that I it was a challenge to assess glide characteristics, it seemed perfectly normal. Since it was night, it may be hard to assess, but I do not think it made any difference with a fixed pitch propeller. ADSB says I was losing 710 to 720 Feet per minute at 90 miles per hour which is 425 feet altitude per mile. In terms of experience, I have about 450 hours of flight time.

Other things I would tell someone? In an emergency, do not accept actions or requests from ATC that will distract you from flying, particularly if you are already task saturated. I was at 1500 feet AGL, without power, maneuvering, evaluating landing direction, and a host of other tasks when ATC asked me to copy a number. My Mayday call was so that someone would know to look for me, not so I could write down a number. I also figured if I ended up in a crumbled ball, they could geo-locate my cell phone with my number. I debated accepting the squawk code, but it was a moment in time when everything was stable, gliding strait, airport in sight, runway lights on, and it had the benefit of positively identifying my radar position for search and rescue which I suspected that I was going to be needing. The last ADSB reading was at the runway threshold at 250 AGL. The ADSB data completely missed my over flight of the airport and flying away from the airport. So, if you are ever looking at ADSB data on an accident flight, it may not be telling the whole story.

Finally, if you are going to fly at night, ask yourself if it is worth the risk. I looked at it as a 1/2000 risk which is reasonable until you find yourself gliding and unable to tell if that dark area is a farmer's field, a lake, a mountain, or a forest. It gave me a new perspective. The whole event was very non-emotional until I started telling someone about it days later, I felt my emotions as it could have ended up very differently.
I am glad that I have my feet planted firmly on the ground, no damage, no injuries, and alive to tell the story.
 
Great write up of your experience. We can all learn from this. Very glad you came out unscathed. Let us know what happened to your engine when you find out. This is one of my main concerns about night flying and why I choose not to take that risk.
 
Ben,

Outstanding job. Any engine failure is no joke, and one at night is even more so, especially to a grass strip with obstacles. Thanks for relating your story and the "lessons learned". You made some great decisions, electing not to try writing down phone numbers or changing squawk codes in the middle of what you were doing. As you fly away from the airport, even going a few seconds too far out can put that field out of reach if you're not paying attention. I too would have used the "unable" word quite a bit with that controller.

I recently made a night flight with my son, and while he did the flying, I played a long game of "what if" for just such a scenario as we flew up the coast. We weren't within glide distance of an airport for the entire flight, but certainly for most of it. I think the strategy one uses might vary depending on where you're flying. Sounds like you were in a more rural area, whereas I was operating between San Diego, Orange County, and Riverside -- which is to say, a much more congested area.

Night flying has additional risks. But, in my view, additional rewards as well. Cooler, smoother air, better performance, better service from ATC, less traffic, and in urban areas, a beautiful vista outside. But I do fly a lot higher at night for just the situation you found yourself in.

I read somewhere that the #1 cause of engine stoppage was running out of fuel. #2 was pilot mismanagement of the engine. Catastrophic mechanical failure of a well-maintained powerplant is certainly not unheard of, but it's relatively uncommon.

--Ron
 
Congrats on a safe outcome. I like flying at night, but avoid for exactly this reason, glad it all worked out well. Let us know what caused the failure when/if you find out!
 
Great write up. Never considered the suggested practice approach idea from cruise to arrive at non-standard altitudes. Good point.

Tim
 
well done, go buy a lotto ticket and a gift you have always wanted. you deserve it in spades. I have very few night hours! only do it when I have to.
 
I read somewhere that the #1 cause of engine stoppage was running out of fuel. #2 was pilot mismanagement of the engine. Catastrophic mechanical failure of a well-maintained powerplant is certainly not unheard of, but it's relatively uncommon.

--Ron
I believe those statistics are correct. However, the number one cause of night fatal accidents remains pilot error. Pilots fly perfectly good airplanes into things they cannot see - hills, trees, towers/high tension lines, etc. And the fatalities per flight hour is much worse at night, for these reasons. I personally enjoy night flying, but try to always stay above ifr minimum altitudes in the area.
 
I believe those statistics are correct. However, the number one cause of night fatal accidents remains pilot error. Pilots fly perfectly good airplanes into things they cannot see - hills, trees, towers/high tension lines, etc. And the fatalities per flight hour is much worse at night, for these reasons. I personally enjoy night flying, but try to always stay above ifr minimum altitudes in the area.

Likewise. My home airport, Corona (KAJO) is at 533' but just 4 miles away is a 4,007' peak and a ridgeline with even higher terrain. Knowing the terrain and obstacles is critical.

Capture.JPG
 
You’re a braver man than me! Talk about lucky!
You comment……..if your are going to fly at night, ask yourself if it is worth the risk…….after 45 years driving planes to me it’s an easy answer, NO, it’s not worth the risk In a SE aircraft.
Well put together explanation of events you described👍 Let’s not hear another one though, okay?👍
 
Great job Ben. Complications during night flying are always exponential. The simple rule of Aviate, Navigate, and lastly , Communicate is ever enduring.
 
Thanks for sharing your story. Glad you and your plane made it okay. I definitely take your experience into account while honing the skills to fly my airplane.
 
You’re a braver man than me! Talk about lucky!
You comment……..if your are going to fly at night, ask yourself if it is worth the risk…….after 45 years driving planes to me it’s an easy answer, NO, it’s not worth the risk In a SE aircraft.
Well put together explanation of events you described👍 Let’s not hear another one though, okay?👍
I respectfully disagree. He wasn’t lucky; he displayed good skills and decision making. And actual crash data continue to show that light twins flown under part 91 have a worse fatal accident rate than singles, and a rate comparable to high performance singles. Luck has little to do with it.
 
I respectfully disagree. He wasn’t lucky; he displayed good skills and decision making. And actual crash data continue to show that light twins flown under part 91 have a worse fatal accident rate than singles, and a rate comparable to high performance singles. Luck has little to do with it.
Even good skills and decision making might have yielded a different outcome if he had not been "lucky" enough to be within gliding distance of an airport.........

We've all had a measure of lucky outcomes in our flying journey, we'll take them when they come!
 
Even good skills and decision making might have yielded a different outcome if he had not been "lucky" enough to be within gliding distance of an airport.........

We've all had a measure of lucky outcomes in our flying journey, we'll take them when they come!
I think good decision making includes go/no-go decisions like flying over inhospitable terrain or cold water regardless of whether day or night. For all we know this pilot deliberately chose a route that kept him within range of reasonable landing sites. Or maybe he was just lucky, I don’t know. But I guess that what I meant to say was that IMHO the risk can be low enough to be acceptable, to me. But so many people worry about an engine failure at night, while the real risk is running into a hill; that’s emotions, not logic, talking.
 
Even good skills and decision making might have yielded a different outcome if he had not been "lucky" enough to be within gliding distance of an airport.........

We've all had a measure of lucky outcomes in our flying journey, we'll take them when they come!

Indeed. As a man once said, it's better to be lucky than good.

But I think Ben was both. There may have been an element of luck to it. For example: lucky that the engine failure didn't involve covering the canopy with oil. Heck, you could even say that the fact that the engine failure was catastrophic enough that any idea of restarting or troubleshooting was immediately abandoned was actually lucky, because it allowed Ben to focus wholly on flying the airplane.

But as far as being within gliding distance of an airport, that's something we as pilots do have some control over. It might be a tad unrealistic to expect oneself to always remain within glide distance of an airfield, but we can route ourselves and select high enough altitudes that our time without a good option is minimized.

--Ron
 
Ben

Congratulations on a job well done. Keeping a cool head and carrying on calmly.
Really impressed you actually used the Mayday call as it lets everyone know immediately the situation.
Personally I can’t believe an ATC controller could be so unprofessional and clueless as to ask you to copy a phone number. This really needs following up. Sadly long gone are the days when controllers used to be taught to fly and had a good understanding of the pilots predicament in a situation like this.

regards Peter
 
I respectfully disagree. He wasn’t lucky; he displayed good skills and decision making. And actual crash data continue to show that light twins flown under part 91 have a worse fatal accident rate than singles, and a rate comparable to high performance singles. Luck has little to do with it.
 
Great write up and thinking Ben. Funny what one remembers - - I was headed off into the brush on my CB500, at speed but braking as hard as possible (self inflicted stupid decision) and saw someone on a porch and thought - they are watching me crash and saying "what an idiot".

For most props - not turning is a lower drag situation.

I only hope my head will be that clear if it ever happens - - very glad you are here in one piece to tell the story.
 
Ben

Congratulations on a job well done. Keeping a cool head and carrying on calmly.
Really impressed you actually used the Mayday call as it lets everyone know immediately the situation.
Personally I can’t believe an ATC controller could be so unprofessional and clueless as to ask you to copy a phone number. This really needs following up. Sadly long gone are the days when controllers used to be taught to fly and had a good understanding of the pilots predicament in a situation like this.

regards Peter
I agree ATC needs educating
 
Update from author based on comments

I had performed some general maintenance on the plane during the day in preparation for an 800-mile trip to see my wife’s family, we were going to leave at first light in the morning. I had replaced a tire and lubricated the wheel bearings, checked brakes, checked connections (found tail beacon loose), washed plane, changed the oil and filter, and gave the plane an overall condition inspection even as the plane was still in current condition inspection. This was a newly rebuilt engine and its first oil change. I never fly anyone with out a checkout flight after maintenance of any kind. I did not want to perform a checkout flight in the morning with my wife watching. She is a nervous flyer and the perception of arriving in the morning and saying stand here and watch me fly it to make sure it is safe are not the words I wanted to use. As pilots, we do everything we can to make sure that passengers are always safe.

After my initial climb, I had turned 90 degrees to limit my distance from the airport, I would have soon turned another 90 degrees to head back in the general airport direction. At the moment of engine failure, I was not sure if I was in glide distance to the airport and suspected I was not, actually, pretty certain I was not. In my initial write up, stated that I suspected that I would be needing emergency services, hence “radar position for search and rescue which I suspected that I was going to be needing.” How close was I? About one mile of margin, or another 36 seconds of flight time away from the airport and I would have not made it. There are comments below about skill verses luck. Absolutely both! I was lucky to be within glide distance and it took full utilization of my skill level. There was also the aeronautical decision making to stay close to the airport on a checkout flight. My decision to keep excess energy for safety margin on final approach, I was high and fast compared to a standard power-on approach, made the landing less than perfect. The bounce was not bad but not perfect, and I did grease the landing after that. I held my slip to maximize drag until the absolute last moment which is not a normal landing methodology. It is probably not a bad thing to practice for emergency purposes. Depth perception at night probably also played a role. There is a reason that there is a separate requirement for night currency, and yes, I was current. When I first started building an RV, I read every accident report in the RV fleet except for the RV-4. Ironically, this flight was an RV-4. One of the take-aways was there was not a single fatality in a plane that made it to an airport, some bent metal from loss of control, but no fatalities. There are many stall spins just off the airport the end of the airport. Lesson is that if your vertical speed is zero and all of the objects to you can run into, such as trees and ditches, are removed (the normal airport environment). You will live to see another day.

What failed? The engine was locked up in the proper rotation direction, I have rotated it about 10 degrees in the opposite direction, and it re-locks at the same place when rotated in the proper direction. I pulled the spark plugs and found some slight debris in the rear two cylinders and both rear cylinders are not connected to the crankshaft. They do not move when the crank is moved. I am guessing that the connecting rods failed or possibly the crank is in two pieces. I have a small hole in the top of the case between the rear two cylinders, about a ¼” diameter.
 
Sorry, but I have one more question. Out of an abundance of caution, would you mind sharing with us who did your engine overhaul?

Does it matter? It's not even clear from the account so far that the engine stopped due to a bad overhaul.

- mark
 
Glad you made it out safe! Please do keep us posted on what you find out when the engine is disassembled.
 
Firstly, congratulations on a job well done.

Second... Thank you for taking the time to fully document this experience such that others (ok, so that I) might learn from it. This sharing of tribal knowledge is essential to our tribe members staying alive. You get many extra bonus points and huge respect for having braved the often harsh criticisms of the crowd on this site.

I won't begin to be a Monday morning quarterback because, frankly, I don't believe you could have done anything better than what you did.

I will mention that my selection of avionics was based, at least in part, with a hard requirement for terrain and obstacle awareness in support of night and limited visibility operations. You haven't commented on whether or not you had such "situational awareness enhancing equipment" installed and whether you may have referred to it at some point in the incident sequence. Perhaps at some point you might have the patience to consider this point and share your reflections?
 
Procedure for night, engine out landing. Obtain best glide speed, fly down real low, turn on landing light. If you don't like what you see, turn light off.

I agree that after many, many years of flying professionally, flying at night in a SE airplane just exceeded my risk versus reward limit.
 
Back
Top