| |

A Tow Pilot’s Near Disaster

by Lance Stick & Hank Gibson

A couple of months ago, I had a life-threatening experience while flying. Thankfully, with my flight training, along with a lot of luck, I am here to talk about it.

One of my many piloting jobs is as a glider tow pilot. For those not familiar with gliding, since a glider doesn’t have an engine, every time a glider pilot goes and flies, it’s a team effort. A powered airplane (anything from a Super Cub to a turbine powered Air Tractor) is attached to the glider via a tow rope, which is about 200 feet long. Once the glider pilot gives the go ahead over the airport’s CTAF, then the tow plane begins it’s takeoff roll, pulling the glider along behind it.

The glider becomes airborne prior to the tow plane, then the tow plane will circle the airport environment till it get’s to the pre-determined altitude to release the glider. Some tows are pattern tows and some are higher (not usually above 3,000 AGL), depending on the request from the glider pilot. Once the altitude is reached, the glider pilot pulls a handle in the glider to release the tow rope, then begins his glide. The rope stays attached to the tail of the tow plane, which in turn descends back down to the runway and lands. The tow plane also has a tow rope release handle in case of emergency.

On this particular tow, the plan was to tow the glider up to 3,000 AGL. Upon reaching 2,500 AGL, the glider pilot called me on the radio and stated that his rear canopy had opened up. I looked over my shoulder and sure enough, the rear canopy was fully opened while he was still in level flight behind me. I asked him if he wanted me to tow him closer to the field, but he didn’t reply.

Now, as an experienced tow pilot, I know a glider canopy popping open should not be an emergency situation. It’s definitely abnormal, but would be similar to a door or window popping open in a powered airplane. Not a big deal. If too much force from the relative wind is applied to the canopy, it would snap off; however, a glider can easily land without a rear canopy.

About 5 seconds after I radioed the pilot (and received no reply), I felt my tail instantaneously lift up into a completely vertical position, which caused my nose to go straight down. The next thing I knew, a whole lot of earth suddenly filled my windscreen and I was in what’s known as a graveyard spiral.

A graveyard spiral (as defined from the Airplane Flying Handbook pg 4-23), “is a descending turn during which airspeed and G-load can increase rapidly….the airplane is flying very tight circles, in a nearly vertical attitude and will be accelerating since it isn’t stalled.” It’s also known as a spiral dive.

Back to the story. At this point, I tried to reach for the glider release handle. Unfortunately, due to the shoulder straps holding me against the seat, plus the g’s, and also the quart of oil and tow bar that flew forward and hit me in the back of the head, I couldn’t reach it. I was semi-upside down at a certain point, which dislodged the oil and tow bar from the floor of the baggage compartment. They sailed over the seat and nearly gave me a concussion.

At this point, 2,500 feet above the ground, I had a choice to either fight for my life at a very low altitude or to sit back and become part of a big explosion.

I decided to fight for my life.

As I was spiraling to the ground, I felt the tow rope snap. Up to this point, I had still been attached to the glider. The rope snapping was a good thing, as my airplane was now under my control, not attached to, and being affected by, a glider (more on that later). I now had a lifeline, no pun intended.

After I felt the rope snap, my instincts and training kicked in. I initiated the spin recovery procedure using the PARE acronym. This task was difficult to do as I had a lot of debris flying from the rear of the plane to the front, blocking my view out of the windshield. There was also debris around my feet, hampering my ability to use the rudder pedals. The spiral finally stopped and I recovered approximately 500 feet above the tree tops. It took my heart a lot longer to stop spinning.

After barely regaining my emotions, I tried to evaluate the condition of the plane. Were all the pieces of the plane still there, was the engine damaged, did my control surfaces still work?

Once I advanced the throttle and saw an increase in my engine RPM, I started an immediate climb to give me altitude to get back to the airport. I had engine power but I wasn’t sure how long it would last if I had damage. Now, what they don’t teach you during spin training is that when this happens unexpectedly, you will become very disorientated. You have just been spiraling unexpectedly and your equilibrium will be out of whack. As I leveled out just over the tree tops, I was too low to visually see any landmarks, nor could I see the airport. Once I was able to climb, I was able to orient myself and figure out where the airport was.

I had to be very careful getting back to the airport and landing without radio communication, since my radio was knocked out with all of the FOD from the baggage area. Thankfully, the landing was uneventful. After I landed, I saw the glider limp in over the trees. The rear canopy was totally gone, while the front canopy and other parts of the glider had suffered major damage. Miraculously, my airplane wasn’t damaged, except for the wire from the radio which came loose during the spiral.

So, how did all this happen, you ask? Well, the glider pilot made 2 huge mistakes. First, in gliding, the moment the glider pilot loses visual sight of the tow plane, you are supposed to release the tow rope. He did not do that and almost killed both of us.

Second, as pilots we are taught to always fly the airplane first. Everything else, no matter what it is, always comes after flying the airplane. As I stated previously, the loose canopy is not an emergency situation, but since the glider pilot did not aviate first and was distracted, it was almost a fatal day for 2 people and 2 airframes.

So, what caused this chain of events? By getting distracted by the open canopy, the glider pilot inadvertently pulled back on the stick while trying to close the canopy. Then, by not releasing the glider from the tow plane, the glider pilot climbed rapidly with an excessive rate of climb while still being attached to me. The rapid climb is what pulled my tail up, causing my nose to drop and put me into the spiral. The tow rope snapping set into motion my recovery, since up till that point, I literally had no control. An extremely high lift wing was attached to my tail, pulling it up, and there was absolutely nothing I could do about it.

We all spend time practicing and demonstrating emergency maneuvers during our flight training and during flight reviews. Many times you might think, I’ll never need to use this stuff. Thankfully, some of the procedures I learned in the past kicked in at a time of need, even though my heart was beating out of my chest.

At some point in every pilot’s career, some type of spin training or Upset Recovery Training would be highly recommended. Then, when things go wrong, remember to always aviate first, then handle all the other things that need to be handled.


Interested in spin training or Upset Recovery Training (UPRT)? Check out the list of Malibu & M-Class Owner’s and Pilot’s Association (MMOPA) approved UPRT vendors and schedule UPRT training today.

Similar Posts

  • Textron Aviation’s New Single Engine Turboprop

    An 8 seat, cabin class, single engine turboprop is set to come to market in 2018 from the new aviation conglomerate Textron Aviation (Textron owns Cessna, Hawker, and Beechcraft).  Details were announced last week at the European Business Aviation Conference and Exhibition.  The as yet unnamed aircraft will be equipped with Garmin’s G3000 avionics and will be outfitted with a GE 1,240 Shaft Horsepower engine.

    Cessna TurbopropThe GE engine will be equipped with a FADEC (Fully Automated Digital Engine Control) computer that will allow the pilot to make all necessary power adjustments using just one lever.

    Range will be about 1,600 miles at 285 knots, giving the airplane the same legs as a PC12 at slightly faster speeds, but a smaller cabin.  The cabin will be equipped with a belted lav if desired.

    To read more, check out the AOPA Article here.

  • Oh, Deer (Part 1)

    As far as I knew when I woke up, October 26, 2016 would be an ordinary day for me. It was a Wednesday, and I was scheduled to fly our Company’s BE58 Baron on a charter from Wings Field (KLOM), a non-towered airport just north of Philadelphia, to Pittsburgh International Airport (KPIT) and spend the day there waiting for my 3 passengers to finish up their meetings. The plan was to fly them back to Wings that evening and then make the short hop back to home base at Lancaster, PA. (KLNS).

    It was a flight that I had done countless times, and I was comfortable with the airports, the passengers, and the airplane. Everything went smoothly that morning and my short flight from Lancaster to Wings was uneventful. I even made it there in time to spill coffee all down the front of my pants before my passengers arrived. The weather was clear, calm and beautiful as we loaded into the Baron and the sun was just starting to come up as I taxied toward runway 24 for departure. I was departing VFR and had an IFR plan on file which I intended to pick up with Harrisburg Approach once we were airborne. According to my calculations, I was on schedule to be drinking my coffee at the Pittsburgh FBO right around 8:30.

    At 7:05, I advanced the throttles for departure. A few moments later, I received a very unpleasant surprise. I was quickly approaching rotation speed when 2 deer ran onto the runway directly in front of the aircraft. It was still dark enough that I was relying on my landing/ taxi lights to illuminate the runway for take-off.  As a result, I was unable to see the animals before it was too late. I don’t remember making a conscious decision to pull back on the yoke, but it was that or plow directly into them at about 85 knots. I pulled up as quickly as I could and the airplane rotated immediately.  A fraction of a second later I heard and felt a sickening THUD.

    There was no doubt that I had hit one of them, but, somewhat unbelievably, the airplane was climbing as though nothing had happened. I put the nose down to get the airspeed back up and began to try and piece together what damage the airplane had sustained. Based on the noise and the feeling of the impact, my suspicion was that I had hit the deer with the left main landing gear. A review of the instrumentation showed no abnormalities and the airplane was behaving normally, so I didn’t suspect any damage to the airframe/ flight controls. I couldn’t see anything out the windows that looked unusual, and somewhat unbelievably I still had 3 green lights.

    After gaining a safe amount of speed and altitude, I turned around and told the passengers that we had hit a deer. It was obvious that we had hit something and I was sure that they wanted to know what was going on. Then, I checked all my indications again and satisfied with what I was seeing, tried to bring up the landing gear. No dice. When I pulled the gear lever to the up position, the master “GEAR UP” warning light came on and I got a horn. There was never any change in the 3-green indication and the gear motor never came to life at all.

    At this point it was obvious that, minimally I was going to have to divert to Lancaster and have the maintenance guys look at the airplane to see if anything was broken. I figured that they would either give me the green light to continue or I would just jump into one of our PC12s and complete the trip while they worked on the Baron.

    The landing gear’s refusal to come up was my first indication that there was substantial damage. I set course for Lancaster and called our Chief Pilot. After explaining the situation to him, we agreed that KLNS was the best option and that he would let the maintenance guys know that I was coming.

    The logic was that proceeding to Lancaster would allow a visual check of the landing gear by maintenance people as well as the tower and result in the safest outcome if an emergency landing were required. Lancaster would likely have better services available in terms of emergency responders and, not to mention, I was fairly certain that there was a dead deer on the only runway at Wings that I didn’t feel like hitting for a second time. In addition, the relatively long runway at Lancaster combined with light traffic at that time of day made it the ideal option to divert to.

    I again turned around to brief the passengers. I told them that we were going to have to make precautionary landing before continuing to our intended destination and that I would be performing a few low passes for the tower.

    Due to the drag from the landing gear, the flight to Lancaster seemed to take forever. The long cruise home, however, gave me time to try and reach someone on the ground at Wings in hope of having the runway inspected and cleaned off before other traffic tried to use it. After several attempts to raise anyone on the Unicom/ CTAF frequency, I called Philadelphia Approach for help instead. Philly answered right away and I explained to them what had happened. I requested that they call over to Wings on the phone or send someone out to check the runway. They told me that they would get it done and asked if there was any other way that they could assist me. I told them I was headed to Lancaster and that I appreciated their offer, but didn’t require any further assistance. I then switched over to Lancaster Tower and let them know that I was about 15-20 minutes out, but I would need to perform a couple of passes to have them check my gear. The tower cleared me for a low approach over runway 26.

    I arrived at LNS at about 7:30. I performed my first low pass by the tower, not really expecting anything to appear out of place. I figured I had bent something or damaged the squat switch, but not much more. I climbed to pattern altitude and awaited the good word. Shortly after the fly-by, Tower reported that the left main gear didn’t appear to be down and locked. They suggested that I make another pass. The airport maintenance personnel chimed in, reporting the same. We had just started discussing whether cranking the gear a little by hand might help when Philly approach called the Lancaster tower on the phone.

    Philly informed Lancaster that someone had inspected the runway at Wings and found the left main strut and wheel in the grass. I quickly concluded that cranking the gear down probably wouldn’t help!

    This was found in the grass by the runway at Wings Field

    To Be Continued…

    (Read Part 2 Here)

    Andrew Robinson is an airline pilot for Piedmont Airlines.  He is a former 135 Charter Pilot and flight instructor who lives with his wife and 2 daughters in Pennsylvania.  He instructs in Beechcraft Bonanzas.

  • Mooney’s Now Come With Two Doors

    Mooney announced last week the redesign of their current Ovation and Acclaim models.  The biggest change that Mooney pilots will love is the addition of a pilot’s door, allowing the pilot to enter on the left side instead of having to crawl over the passenger seat.

    Other upgrades include a keypad for easier data entry on the G1000 and an all in one, digital standby instrument that includes attitude, airspeed, and altitude.

    This raises the question, will Piper and Beechcraft follow suit?

    Mooney Acclaim

  • Scud Running

    I was speaking with a pilot a few months back who was not instrument rated.  He was telling me of his flying experience while continually speaking fondly of scud running.  He told me several stories, most of the time with a smile on his face, about scud running to his destination while staying clear of clouds.  While he was talking, my mind was cycling through the numerous accident reports I’ve seen where a scud running VFR pilot has crashed into terrain or an obstacle.  Needless to say, scud running is not a very good idea.

    This pilot’s stories got me to thinking, how common is the practice of scud running amongst VFR only pilots?  As an instructor, I always teach my private students about personal minimums and making that no-go decision when clouds are below those personal minimums.  The act of scud running falls under several of those dangerous pilot mindsets, get-there-itis, invincibility, and macho-ism, to name a few.

    To bring everyone on the same page, let’s define scud running.  Wikipedia has a very good definition:

    Scud running is a practice in which pilots lower their altitude to avoid clouds or instrument meteorological conditions (IMC). The goal of scud running is to stay clear of weather to continue flying with visual, rather than instrument, references. This practice is widely accepted to be dangerous, and has led to death in many cases from pilots flying into radio towers and high tension wires; however, even instrument-rated pilots sometimes elect to take the risk to avoid icing or embedded thunderstorms in cloud, or in situations where the minimum instrument altitudes are too high for their aircraft.

    To put some numbers with that definition, a scud running VFR pilot would takeoff with a 1200-1500 foot ceiling and stay 700-1000 feet above the ground, right in the area where towers, hills, and rapidly rising terrain reside.

    Scud Running

    How do we change this mindset?  Well, if someone has been scud running for years without incident, the practice becomes normal, like the pilot I mentioned above.  The mindset of invincibility sets in and the practice continues.  This particular pilot can also lead other pilots to adopt the same practice, encouraging them that nothing will happen to them, since we all know that our pilot peers know better than our flight instructors (insert heavy sarcasm here).

    In order to change this mindset, instructors need to emphasize personal minimums from day one.  This includes ceilings, visibility, and winds.  For a seasoned pilot, a review of accident statistics might help the process.

    Scud running is not a safe practice.  If you’re a scud runner, you need to rethink your attitude.  Is getting there really worth it?

    Still not convinced?  Read this pilot’s experience from AOPA.

  • Cirrus Announces The New Cirrus G6 SR20 & SR22

    Earlier this month, Cirrus announced the new Cirrus G6 SR20 and SR22.  To the naked eye, they look like incredible airplanes.  There is new lighting and the updated Cirrus Perspective+ avionics in both models, plus the SR20 is now a Lycoming powered airplane.

    The Perspective+ in the Cirrus G6 is based on Garmin’s G1000 NXi platform.  The keypad is updated to a QWERTY keypad, allowing for quicker inputting of data since our fingers are already used to the setup.  A home button was added to the center stack to get back to the map page without having to hold down the CLR key.  The bug knobs were moved down to the autopilot, while the display of the GFC 700 was altered slightly to match the Vision Jet setup.

    Cirrus G6 Perspective+

    The Perspective+ also boasts a 10-fold increase in processor speed, allowing the system to move quicker than the standard Perspective.  The ability to wirelessly update databases has also been included.

    The exterior of the Cirrus G6 SR22 and SR20 models has changed as well.  Cirrus has added the Spectra wing tip lighting system to the Cirrus G6.  It incorporates an entire light panel that runs the length of the wing tip.  The LED dual strobe setup helps with aircraft visibility and ramp appeal.

    Cirrus G6

    The SR20 engine has been changed to the Lycoming IO-390, 215 HP engine.  The Continental IO-360-ES 6 cylinder engine comes out of the SR20 and the 4 cylinder Lycoming goes in.  2 less cylinders will help with useful load and the extra 15 HP will help with takeoff and climb performance.

    SR20 Lycoming

    The new Cirrus G6 is available for order and delivery immediately.  To read all the details and specs on the Cirrus G6, you can check out Cirrus’ website.

  • Garmin G1000 Updates

    You have just received the keys of your shiny new (to you) airplane complete with a beautiful Garmin G1000 glass panel flight deck. Synthetic Vision, WAAS, and ADS-B are all installed. You are ready to cruise in high technology.

    You turn on the PFD and MFD and notice one problem. All your databases are expired. No big deal, right? Your Garmin 530W was easy as pie to update with it’s single data card.

    You start looking around and can’t find the data card. Then you notice that there are several SD cards in slots on the panels. SD cards won’t fit in your Blue Jepp Skybound card reader. Confusion sets in which quickly leads to full on panic.

    What have you gotten yourself into?!

    No need to fear, Texas Top Aviation is here to help with your Garmin G1000 database update confusion (and hopefully not panic).

    Database Update Providers

    First, you have to choose who to get your Garmin G1000 updates from. You have two options. One is Garmin (fly.garmin.com; always use either Firefox or Chrome to update, don’t use Safari). The other is Jeppesen.

    Honestly, there is no difference between the data that each provides. If you had a 530 or 430 before, you used Jepp already. Just keep the Jepp account, call them, and have them get you set up for your Garmin G1000 updates.

    If you didn’t have a Jepp account before, I would use Garmin, for a couple of reasons. You get multiple downloads in case you mess something up (Jepp NavData gives 1 download per month, while Safe Taxi, etc. you get 2-3). On Jepp, you have to call in and have them reset the account, which can be a pain if it’s after hours or a Saturday or Sunday.

    The other problem with Jepp is since Boeing bought Jeppesen, I have found it extremely difficult to find online where to set up a new account and purchase databases. Yes, you can always call, but, again, problematic after hours or on a weekend.

    The only problem with Fly Garmin for your Garmin G1000 updates is Garmin is constantly updating their program. You have to update their downloader quite often, which can be a bit frustrating.

    I’m going to use Fly Garmin as my example.

    What to Buy

    Garmin gives you a couple of different bundle options for your Garmin G1000 updates, the OnePak and the PilotPak. The main difference between the two is the PilotPak includes approach charts that display on your PFD and the OnePak doesn’t. Therefore, the OnePak is about $200 cheaper.

    Both include Navigation Data, SafeTaxi, Obstacles, Airport Directory, Terrain, and the BaseMap.

    How to Update

    Once you have followed all the instructions on Garmin’s website (or gotten Jeppesen set up), here is what to put on which SD card.

    NOTE: YOU WILL NEED TO PURCHASE ONE OR TWO BLANK SD CARDS FOR THE NAVIGATION DATABASES. DO NOT PUT THE NAVIGATION DATA ON THE SD CARD THAT IS ALREADY IN THE TOP SLOT ON THE MFD. THAT IS FOR ENGINE DATA LOGGING ONLY. NO NAVIGATION DATA SHOULD EVER BE PUT THAT ON THAT CARD.

    Bottom Card, PFD

    • SafeTaxi
    • Obstacles

    Bottom Card, MFD

    • SafeTaxi
    • Obstacles
    • Airport Directory
    • Flite Charts

    Top Card, PFD & MFD (This is the new blank SD card(s) you bought)

    NOTE: REMOVE THE TOP SD CARD IN THE MFD THAT IS ALREADY IN THE SLOT AND DON’T PUT ANY DATABASE INFORMATION ON IT.

    • Navigation Data

    Garmin G1000 NXi Users (or Cirrus Perspective + Users)

    Ignore everything above and put all databases on the bottom card of the MFD. You have database sync, so you don’t have to mess with multiple cards. When you do an update though, go to the AUX chapter on the MFD and scroll down to the Databases page. Ensure that all dates match what you just put on the SD Card.


    For you Jeppesen users, check out the new Bad Elf Wombat updater that works with the iPad JDM app for updates.

Leave a Reply

Your email address will not be published. Required fields are marked *