Cirrus CAPS Pull in Arkansas

Cirrus CAPS pull #55 took place at the beginning of November over Fayatteville, AR.  From initial reports, it appears a clamp broke on the oil cooler, causing a loss of oil pressure.  It does not appear that the engine immediately quit, but an annunciator alerted the pilot that the engine was losing oil pressure.  At this point, it appears the pilot elected to do an emergency descent to an airport below him, but ended up not timing it right, missing the airport and pulling the parachute.

As an experienced Cirrus flight instructor, there appears to be some suspect decision making in handling this operation.  I teach in a Cirrus that if an oil light comes on, given that a pilot has some altitude to work with, it is a better option to physically shut the engine down, leaving control of the situation in the pilot’s hands.  This way, the pilot knows when the engine is stopping and is prepared for it, instead of the engine acting erratically and causing problems on the descent.

After checking the engine gauges and shutting the engine down, a pilot should establish best glide first, not nose down and descend at a high rate trying to make an airport.  Best glide gives the pilot many more options and a lot more altitude to work with, further allowing him/her to plan how to make an airport directly underneath the airplane.

To pontificate, it seems that if the pilot had adjusted the plane to best glide, instead of performing an emergency descent, there is the possibility that Drake Field would have been reachable, the chute would not have been needed, and the driver of the truck would not have had to visit the hospital.  Hindsight is 20-20, but this may be an overall training and decision making issue that may need further emphasis.

The initial NTSB report as well as a link to the CBS story is below.

http://www.cbsnews.com/live/video/pilot-forced-to-deploy-emergency-parachute-in-arkansas/

NTSB Identification: CEN16LA026
14 CFR Part 91: General Aviation
Accident occurred Tuesday, November 03, 2015 in Fayetteville, AR
Aircraft: CIRRUS DESIGN CORP SR22T, registration: N857SW
Injuries: 3 Minor, 1 Uninjured.
This is preliminary information, subject to change, and may contain errors. Any errors in this report will be corrected when the final report has been completed. NTSB investigators may not have traveled in support of this investigation and used data provided by various sources to prepare this aircraft accident report.
On November 3, 2015, at 0950 central standard time, a Cirrus SR22T airplane, N857SW, descended under the canopy of the cirrus airframe parachute system (CAPS) and landed on a road in Fayetteville, Arkansas. The pilot, pilot rated passenger and one person on the ground received minor injuries. One passenger in the back right seat was uninjured. The airplane was substantially damaged. The airplane was registered to WG Aviation LLC, Rogers, Arkansas, and operated by a private individual under the provisions of 14 Code of Federal Regulations Part 91 as a personal flight. Visual meteorological conditions prevailed at the time of the accident and an instrument flight rules (IFR) flight plan was filed. The flight departed from the Bentonville Municipal Airport (VBT), Bentonville, Arkansas, at 0934 and was en route to the Waco Regional Airport (ACT), Waco, Texas.

According to the pilot, after departure from ACT he leveled off around 10,000 ft mean sea level (MSL) and was in “VFR on top” conditions. The pilot noticed that the crew alerting system (CAS) flashed a yellow caution light for oil pressure; the engine was still producing power. The pilot notified air traffic control (ATC) of the issue and received vectors to the nearest airport, Drake Field Airport (FYV), Fayetteville, Arkansas. The pilot descended and maneuvered toward FYV as the CAS indicated a red warning light for oil pressure, which had dropped below 10 psi. The engine was producing inconsistent power as the airplane descended to 3,300 ft and FYV was still not in sight due to cloud coverage. The pilot was unable to maintain altitude and the airplane’s stall warning horned sounded. The pilot deployed the Cirrus airframe parachute system (CAPS) and descended to the ground. During the landing the airplane collided with a truck and then came to rest on a four lane road.

At 0953, the weather observation at FYV reported wind from 190 at 9 knots, gusting to 17 knots, 10 miles visibility, clear sky, temperature 61° F, dew point 57° F, and altimeter setting 30.11 inches of mercury.

An initial postaccident examination was conducted on November 4, 2015, in Fayetteville. Engine oil was observed on the underside of the fuselage. The oil cooler cross fitting was broken and oil was observed in the engine compartment.

The airplane’s recoverable data module and three data cards were removed and sent to the NTSB Vehicle Recorders Laboratory for download.

The airplane has been retained for further examination.

Similar Posts

  • Circle to Land Approaches

    When I was doing my instrument and multi-engine training, we did a lot of circle to land approaches.  As a student, I could never figure out why these types of approaches would ever be practical when you could an approach straight in to another runway.  But, as a good student, I never asked my instructors the purpose of them, I just did them to the best of my ability.

    Now, having been flying in the IFR system for almost a decade, I’m finally beginning to fully understand the practical purpose of a circle to land approach.  I have actually elected to do an approach where I had to circle to land on several occasions in actual IMC conditions.

    One important note to remember on circle to land approaches is that the minimum descent altitude (MDA) is always higher than on a straight in approach.  The reason for this is that you are basically joining the pattern for a different runway and you have to be able to visually keep yourself clear of towers and other obstacles.  So, you need a higher visibility and a higher ceiling than if you were just lining up to come straight in.

    Here are a couple of practical circumstances where it would make sense to do a circle to land approach.

    Airports with only 1 straight in approach

    This one is easy.  There are a number of airports scattered around the US that have only 1 straight in instrument approach published for it.  Around my part of Texas, the first one that pops into my mind is the RNAV 31 at T85 in Yoakum, TX.  Most of the year, the prevailing wind is out of the south, so 13 is the favored runway at T85.  During the winter is when most of the IMC weather happens in South Texas, so that is why the approach is for 31.

    Of course, especially this year during the summer, there are some IMC days where an approach to T85 would be necessary.  When there is a strong wind out of the south, landing on 31 is impractical, so a pilot would fly the approach to 31, then circle to land on 13.

    Approaching from the opposite direction

    Take a look at the RNAV 19 at KBMQ, Burnet, TX.  The two initial approach fixes (IAF) are IXANY and JIBAJ.  If a flight is approaching BMQ from the west or north, this is an easy approach to join.  If a flight is coming from Austin (directly the the east and a little south) or San Antonio (almost directly south), it would be a bit of extra flying to get configured properly for the approach.  Especially coming from Austin, because the degree of turn to join at JIBAJ wouldn’t make the approach practical.

    Well, how about vectors?  Unfortunately, Houston Center doesn’t have this approach depicted so vectors aren’t a possibility.  Center can give you vectors north to make the angle a little easier to join at JIBAJ, but they can’t vector you onto the approach.

    Direct DLORA to join is another option, but again, if you are approaching from the southeast, the angle is wrong.

    Insert the RNAV 01 approach with a circle to land.  AMUSE is right on V163, so it’s really easy to join the approach there coming from the south.  Coming from Austin, joining the approach at SUBIE works out great. Fly down to the MDA, join the left downwind for 19, and everyone is happy.

    VOR Circle to Land Approaches

    Every instrument pilot has had an instructor “force” them to do a VOR A or VOR B approach and no one enjoys them.  I personally think they are good practice.  With the number of RNAV systems and RNAV approaches out there, though, VOR approaches are becoming a bit archaic.

    They do have a place in this discussion, though.  A VOR approach is given an A or B designation when the angle of the final approach course is greater than 30 degrees to the runway (VOR A KLZZ), or the final approach course is lined up with the runway, but the MDA is too high to practically descend and land (VOR A KGRK or the VOR/DME C KASE).

    So, there are practical uses for a Circle to Land approach.  The next time you do some IMC work with an instructor, ask him/her if you can include one.

    When I was doing my instrument and multi-engine training, we did a lot of circle to land approaches.  As a student, I could never figure out why these types of approaches would ever be practical when you could an approach straight in to another runway.  But, as a good student, I never asked my instructors…

  • Aviation News: The Formation of ONE Aviation

    Earlier this month, Eclipse Aerospace and Kestrel Aircraft merged to form ONE Aviation.  Most pilots are familiar with Eclipse, who makes the Eclipse 550 jet, but not many have heard of Kestrel Aircraft.

    Kestrel K350

    Kestrel Aircraft is run by Alan Klapmeier, co-founder of Cirrus Aircraft and brother to Dale Klapmeier, who still runs Cirrus.  Klapmeier joined Kestrel in 2010 and brought innovation to the K350 Turboprop design that Kestrel was developing.  Kestrel has been lacking in investors to further their project, but the merger will help a lot in getting more funding.  Klapmeier assumed the CEO role for ONE Aviation.

    Eclipse 550

    The merger will also help bring more innovations to the Eclipse 550.  The original Eclipse Jet was a miserable failure and the company went into bankruptcy in 2009. The Eclipse Jet came back to market in 2013 as the Eclipse 550 with many much needed improvements, including making GPS a standard amenity.

    Klapmeier and his genius will lead ONE Aviation in good directions.  The K350 will come to market a lot sooner as more investors will be drawn to the company, while the Eclipse 550 will continue to see new and innovative developments.

    Earlier this month, Eclipse Aerospace and Kestrel Aircraft merged to form ONE Aviation.  Most pilots are familiar with Eclipse, who makes the Eclipse 550 jet, but not many have heard of Kestrel Aircraft. Kestrel Aircraft is run by Alan Klapmeier, co-founder of Cirrus Aircraft and brother to Dale Klapmeier, who still runs Cirrus.  Klapmeier joined…

  • Jeppesen vs. Aeroservices Charts

    Many people ask, which set of charts is better? Should I use the FAA Aeroservices charts on Foreflight or pay extra for the Jeppesen charts? Since you have to pay for Jeppesen, they are probably better, right?

    I am not here to say which one is better as a chart preference is just that, a preference for one over the other or for certain features. After a while, muscle memory and routine take over and you probably wont even notice the difference.

    History

    In 1934, Elroy Jeppesen began making his own charts and sold them to other pilots. His little company grew into the giant Boeing chart company we know today. Jeppesen charts are used internationally and therefore include information that might otherwise seem common knowledge, like transition altitudes. The key is, you cannot get FAA Aeroservices charts for international destinations. Jeppesen is the only option for outside the US.

    National Aerospace Charting Office (NACO), or the new(er) name “Aeroservices” or FAA chart, whatever you decide to call them, are United States government issued charts. In addition to civilian use, Aeroservices charts are used by the military so there will be some terminology that does not apply to civilians. The best part about FAA Aeroservices charts are… they’re free!

    If you are in the middle of a transition or trying to decide which charts to use, you have come to the right place. Here are a few key differences.

    Obstacle Departure Procedure Chart
    KAXX (Angel Fire, New Mexico) ODP

    1. Frequencies: FAA Chart provides the AWOS so you have all departure frequencies in once place.
    2. Airport: Jeppesen highlight the airport, which is a nice feature so you can easily see the flow from the airport.
    3. Notes and Remarks: Jeppesen bolds the speed restriction all over the chart so you won’t miss it. All other requirements are in the top right corner. Note the transition altitude 18,000′. Since Jeppesen is used internationally, it is published on the chart since other countries have different transition altitudes. It takes up a chunk of chart real estate, but it’s clear, easy to read, and always in the same place. The FAA charts post all the requirements and restrictions as notes off to the side. Since it’s in the same space as the chart graphic, it’s easy for the eyes to catch while studying the plate.
    4. Take off Minimums: NOT APPLICABLE for PART 91 – however, it’s wise for all pilots to look and abide by them. Jeppesen displays the standard take off minimums table, as well as the rate of climb table, which is nice to have all in one place. The FAA chart gives the non standard information but you need to know/look up the rest in the Digital Terminal Procedures Supplemental document. (Hint: It’s in the Documents section of Foreflight)
    5. Take Off Obstacles: About the same on both charts
    6. Route Description: Similar on both charts, but larger font and clearer description on the FAA chart. When there are different routes from different runways, the FAA chart layout is really helpful.
    7. Graphic Layout: Jeppesen and FAA use the same graphics for all their different charts and plates which makes it easy to read once you are familiar with the respective charts. FAA charts are easy to read and distractions are kept to a minimum. Jeppesen charts make things bold and enlarge pertinent information so you won’t miss it.
    8. Airport altitude: This is only on the Jeppesen chart (the FAA chart doesn’t include it), but it is very helpful for situational awareness. As you brief the arrival altitudes, I think it’s important to have an idea what AGL you are at.

    Approach Charts

    One thing pilots love about Jeppesen approach charts is the clear set up for an approach brief. The top section is created as a “briefing strip” starting with the frequencies, then navigation frequencies, minimums, airport elevation and the missed approach. It’s very natural and user friendly.

    FAA charts have a slightly bigger picture of the approach planview, but the profile view and minimums section can get a bit cluttered. It can feel a little discontinuous when briefing the approach to bounce all over the page. However, some pilots really like the small airport diagram in the corner, which I find really helpful for situational awareness (particularly for students learning circle approaches). Non- standard alternate and takeoff minimums are also clearly noted, but unfortunately we must hunt elsewhere to find them. The Jeppesen alternate minimums and takeoff minimums will both be on the airport diagram

    1. Frequencies: Getting weather and tuning radios is easy on the Jeppesen charts – just follow the briefing strip. The frequency section on the FAA charts is still easy to read, but closer to the center of the page. It’s split up from the nav frequencies and other important briefing information.
      a. FAA charts are created by the government and have military specific information, which are the odd looking frequencies and channels on the chart.
    2. Approach Navigation: On a Jeppesen chart, you will continue to the next line to verify your frequency, course and set minimums (assuming you are straight in on the ILS). On the FAA chart, you will then have to skip to the top of the chart to get the frequency and course, and then scan to the bottom of the page to input your minimums. However, since you could be flying a localizer approach or a circle to land, it’s a good reminder that not everyone using this approach chart will be using the same Decision Altitude (DA). The FAA chart also includes runway distance information so pilots can make determinations of approach speeds and stopping distance if the runway is wet or icy.
    3. Missed Approach – Textual
    4. Approach Lighting
    5. Missed Approach- Graphical: The missed approach information is the same on both charts. The lighting information is key for determining a missed approach and is next to the missed approach text on the FAA chart. It’s found next to the missed approach graphic on the Jeppesen chart. Personally, I find it easier to find and read the lighting information on the Jeppesen chart. Remember, on both charts, the placement of the PAPI on the chart indicates the physical location of the lights (left or right of the runway).
    6. Notes: Both charts have a notes box, but they use them a little differently. Once again, remember that Jeppesen charts are used internationally and include the transition altitudes and altimeter setting info. On both charts, the notes section will be where other critical information will be shared which isn’t really applicable for this airport. On the FAA chart, the tower frequency is starred to note that there are operating hours (you’ll have to check the chart supplement AF/D to find out what those hours are). There is also an L next to the frequency to indicate it is the pilot controlled lighting frequency. You will also find the note about the VGSI and the Approach Glide path next to the profile view on the FAA chart, whereas the Jeppesen chart has that note in the notes section at the top. The FAA chart also has the T and an A in black triangles to note that this airport has non- standard alternate and take off minimums. Again, those are found in separate documents when using FAA charts and on the Airport Diagram when using Jeppesen charts.
    7. Minimum Sector Altitude: Similar on both charts, but in different locations (reminder: ATC vector altitudes may be lower. It is the pilot’s responsibility for safety of flight to maintain safe obstacle clearance, so if you are ever concerned about going below the MSA – just ask ATC).
    8. Planview: Other then differences in size, visuals, and text, the information displayed on both is very similar.
    9. Profile View: Again, the displays look different and pilots will have their preference, but the information is the same.
    10. Minimums: Jeppesen charts not only note the category for each approach with its designated letter, but also displays it in knots. It is recommended that if you increase your approach speed (based on flaps or gusty winds or perhaps a faster speed for a circle to land approach) that you should use the higher category minimums. The reference guide makes that easy to look up. The other benefit of the Jeppesen charts is right the table that contains the time from the final approach fix to the missed approach point for a localizer approach, it also shows the rate of descent with the associated ground speed to maintain a 3 degree glideslope. Now there is no excuse not to set pitch and power! The minimums posted in parenthesis are for the military, but RVR in statute miles is also included.
    11. Airport diagram: Only on the FAA charts, this particular feature is particularly useful for situational awareness. The arrow pointing to the runway shows the direction the approach is arriving from so planning a circle to land is a cinch. There is also a lot of other information that can be gathered from the airport diagram for quick reference or to help a disoriented pilot: lighting, displaced thresholds, closed taxiways, and runway placement and lengths. This is easily one of the best perks of an FAA chart.

    Arrival/ Departure Charts: Sewzy 5 Arrival KAUS

    The Jeppesen lay out is very attractive and draws the pilots eye in a clear way to all the important information. The colors pop out, so the required altitudes and speeds are easy to read and remember. The chart, which is the proper scale, shows MORAs , easy to find airports (and runway layouts) and is over all easy to follow. However, the texts, while very clearly laid out, are small and difficult to read and pushed to the very edges of the chart. FAA charts are simple and fairly easy to read, but the airports are not as obvious and the flow to the airport requires a good look. The table on the Jeppesen chart is a really nice format, but the text and Notes for arrivals on the FAA chart are easy to find and much easier to read quickly.

    1. Frequency: FAA charts include the approach frequency on the arrival, which is helpful for having radios tuned. During a busy time when the controller changes your frequency, all you have to do is verify the frequency you already set, rather then totally stop what you’re doing to switch it. The Jeppesen charts add the airport elevation next to the ATIS, which really aids situational awareness.
    2. Notes: Jeppesen notes are clearly numbered and tucked away nicely in a box, but the FAA chart notes pop out in the middle of the page and are easy to skim for pertinent information.
    3. Planview: I think Jeppesen is the clear winner here- it is so easy to read, it only takes one glance to know where the primary airport is and how the arrival flows. The chart being at the proper scale offers the pilot important geographical information and over all is a clean look. Notice the small series of arrows after SMRFF on the the Jeppesen chart; those indicate the pilot should expect radar vectors. The FAA charts include those instructions in the text, but I find the visual reference on the chart helpful. The FAA charts are equally clean, with altitude and speed restrictions easy to read even if they don’t jump out. When there are multiple airports that the arrival serves, the airports are clearly marked, though, I think it would be nice to have a little more information surrounding the primary airport for better situational awareness.
    4. MSA: only on the Jeppesen chart
    5. Primary airport: The runway alignment and grey highlight on the Jeppesen chart stands out very clearly, while the FAA airports are a little more obscure.
    6. Arrival route description: The table on the Jeppesen chart is easy to follow but the text is very small and pushed to the bottom. The route description is much easier to find and read on the FAA chart.

    Airport Diagram

    The Jeppesen Airport Diagram page has it all: frequencies, airport diagram, runway info, take-off minimums, departure procedures and alternate minimums. It’s a one-stop shop. It makes preflight planning easy when its all at your fingertips.

    The FAA charts usually require a little more searching for different pieces of airport information. The Airport Diagram itself is just the airport layout. Above, you will see a simple FAA Airport diagram. It’s clean and simple, perfect for a knee board print out.

    In the flight planning process, as you look at what approaches you will be using for the airport, you might see an A or T inside a triangle. Those indicate that you will need to look in the Alternate Minimum or Take off minimum documents for more information. The Takeoff Minimums document (see below) is also where you will find any obstacle departure procedures for that airport. Apps like Foreflight help you out by posting the take off minimums under the departure tab. Even though it’s a little more difficult to read, I didn’t crop out the airport information so you can see what it looks like in context.

    FAA Alternate Minimums on the Left and Takeoff Minimums and Obstacle Departure Procedures on the Right

    Many people ask, which set of charts is better? Should I use the FAA Aeroservices charts on Foreflight or pay extra for the Jeppesen charts? Since you have to pay for Jeppesen, they are probably better, right? I am not here to say which one is better as a chart preference is just that, a…

  • Chuck’s Aircraft 10 Year Anniversary Fly In

    Chuck’s Aircraft, the Austin Cirrus Service Center located at the Austin Executive Airport (KEDC), is celebrating it’s 10 year anniversary this month. What better what to celebrate than to fly in for Texas BBQ? That’s what they thought too!

    Chuck’s Aircraft will be hosting its 10 Year Anniversary Fly In on Friday, June 25th from 1pm to 5pm on their ramp at EDC (see airport diagram below). Chuck’s Aircraft always provides quality maintenance for Cirrus and other aircraft, so come show your appreciation for them.

    Please RSVP to erin@chucksaircraftllc.com. Hope to see you there!!!

    Chuck’s Aircraft is the hangar circled in green

    Chuck’s Aircraft, the Austin Cirrus Service Center located at the Austin Executive Airport (KEDC), is celebrating it’s 10 year anniversary this month. What better what to celebrate than to fly in for Texas BBQ? That’s what they thought too! Chuck’s Aircraft will be hosting its 10 Year Anniversary Fly In on Friday, June 25th from…

  • Flight Watch to be Discontinued

    The FAA has decided to discontinue the dedicated En Route Flight Advisory (EFAS or Flight Watch) frequency 122.0.  The effective date will be September 24th, but Flight Service will continue to monitor the frequency for an additional six months to direct pilots to Flight Service Station frequencies.

    EFAS services will still be provided by Flight Service, though, on the published Flight Service Station frequencies (and 122.2).

    To me, this makes some sense.  In the past, if I accidentally contacted Flight Service on one of their frequencies to issue a pilot report or get a weather update, they would send me over to Flight Watch on 122.0.  More than likely, the Flight Watch operator was sitting right next to the Flight Service operator, but I had to flip frequencies.  This will help alleviate some confusion for pilots.

    The deactivation of Flight Watch had been coming for years since the advent of Foreflight and other iPad and tablet apps giving pilots much easier access to weather, both in flight and on the ground.  With Nexrad and Stratus, there isn’t much need for Flight Watch anymore (though you still can’t file a PIREP over the XM Weather!).

    For more information, check out AOPA’s website.

    The FAA has decided to discontinue the dedicated En Route Flight Advisory (EFAS or Flight Watch) frequency 122.0.  The effective date will be September 24th, but Flight Service will continue to monitor the frequency for an additional six months to direct pilots to Flight Service Station frequencies. EFAS services will still be provided by Flight…

  • Oh, Deer (Part 2)

    Read Part 1 Here

    Only now did I begin to realize the severity of the situation. The deer had completely broken the left main gear off of the airplane. Obviously, landing in this condition would not be ideal. Landing without a nose wheel is one thing, but landing without one of the mains would be a very dangerous and undesirable proposition.

    The company’s maintenance guys arrived on the scene while I executed a few more low passes so that they could take a look. We all came to the same conclusion that the best situation for landing would be to retract the other two wheels so I could land on the belly. Unfortunately, the landing gear wouldn’t retract. Cranking the emergency gear handle didn’t work either as it is not designed to bring the wheels up, only to put them down.

    I flew circles around the airport for a while as different options were all discussed. I owe a lot to the guys on the ground who were digging through the manuals coming up with solutions. Eventually, it was decided that I would try cranking the gear up by hand, even though the checklist in the airplane said that it could only be used to lower the gear. Even if we damaged the hand cranking mechanism, it would be worthwhile…plus, I’d already torn off the left main entirely, surely a little damage to the retraction mechanism wouldn’t be the end of the world!

    Following the checklist, I pulled the CB for the gear motor and started cranking. To my great relief, the “in transit” light illuminated and the three green indication went away. It was difficult work to crank the gear up manually. The handle is in a very poor location in Barons and Bonanzas, plus I was working against gravity. It is also possible that there was some debris from the missing wheel causing friction or binding. While I was cranking, the rescue crews were being coordinated while extra vehicles and people had been called in from the city for support.

    After some time had passed, enough to get a slightly sore arm from cranking, the lights indicated that the gear was up and locked. I lined up for one more pass hoping to verify that the landing gear was up and the landing gear doors were closed. After the final go ahead from everyone on the ground, all that was left was the landing.

    I had been doing my best to keep the passengers informed of what was happening throughout the whole flight, but I felt bad for them as the news changed from the beginning of the flight: “precautionary landing” was quite different than the briefing I ended up giving them before we landed. I informed them that I was going to be “… killing the engines and landing with the gear up….” They did an impressive job of staying calm and being responsive. Before we landed, I made sure that they were all briefed on what to expect, how to unbuckle, and how to evacuate from the airplane. It is difficult to convince someone that everything is going to be fine when there are hordes of emergency vehicles (including ambulances) waiting next to the runway in anticipation of your landing.

    Shortly before landing, I went through my flows and callouts, then verified by use of the checklist to ensure I hadn’t missed anything. I distinctly remember sitting in the airplane preparing for the landing, all the while being in complete disbelief that this was a real situation. I never imagined that I could be flying an airplane that was missing a wheel strut. Previously, my assumption had been that if there was an event serious enough to shear off one of my mains, the airplane wouldn’t continue flying. It all seemed like a bad dream.

    I elected to use runway 26 since it was the longest. I wanted to be able to carry extra speed in order to give myself extra time between pulling the mixtures and landing so that I could feather the props and turn the fuel shut off valves to the off position (never thought I’d have to do that!) without being rushed. As I made my final approach with the engines shut off, I went through my final memory items and couldn’t help but laugh about just how backwards everything was from normal arrival procedure. GUMPS: Gas- Off (normally on the fullest tank), Under carriage- Up (Definitely not normal), Mixtures- Idle cut off (I normally save this for when I’m parked on the ramp), Props- Feathered (Again, never thought I’d have to do that in real life), Seatbelts- On (the only one that stayed the same!).

    On final approach for runway 26 with the gear up and the props feathered.
    Photo Credit: www.lancasteronline.com

    I’ve had several remarks about how quiet the airplane must have been during the final un-powered glide to the runway, and while that is absolutely true, I must confess that I never noticed. I was so focused on the task at hand that the silence in the airplane simply wasn’t something that stuck out to me. What did make an impression on me, however, was the acceleration the airplane experienced when the props were feathered. I’ve heard it preached many times the importance of feathering the propeller on a dead engine, but never truly appreciated the importance of it until I did it myself. I remember the airplane accelerating noticeably as though I had hit a boost button which was hidden somewhere in the cockpit for just such an occasion.

    Although I didn’t notice the lack of noise upon killing the engines, the sickening, deafening noise which was produced during the touchdown and deceleration is something which I will never forget. Another thing that surprised me was the smoke which filled the cockpit and cabin as we slowed down. This was produced by the friction between the belly and the runway, although nothing was burning.

    I don’t know how long the airplane actually slid for after touching down, but it felt like an eternity. However, when the noise subsided and the motion stopped everything returned to real time. I unfastened my seat belt, opened the door and climbed out onto the wing. I helped the passengers evacuate and we retreated to a safe distance on the side of the runway while the firefighters rushed in to do their job.

    It was 8:35 am. So, from the time we took off to the time we landed was almost exactly an hour and a half. Not surprisingly, the passengers elected not to continue on to Pittsburgh and instead accepted a ride home in a car. The rest of my day was a blur of paperwork, reports, and phone calls.

    To Be Continued…

    Read Part 3 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.

    Read Part 1 Here Only now did I begin to realize the severity of the situation. The deer had completely broken the left main gear off of the airplane. Obviously, landing in this condition would not be ideal. Landing without a nose wheel is one thing, but landing without one of the mains would be…

Leave a Reply

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