|

Dry Motoring a PT6

When it comes to turboprop engines, a hot start is a really bad thing. For you piston drivers out there thinking, “What’s the big deal, you are just starting a hot engine,” then here’s a little education for you.

In a PT6 turboprop engine, there is a very important temperature gauge that a pilot monitors very closely during each and every start. It is called the Inter-Turbine Temperature gauge, or ITT. This temperature is a measurement of the exhaust gases between the compressor turbine and the power turbine (s). In the picture below, the probe is located where the blue and red colors meet.

In a turboprop engine, specifically the Pratt & Whitney PT-6 in all it’s different sizes and variations, there will always be a specific temperature that the pilot will want to keep the ITT below. This article will deal specifically with a Piper Meridian.

A Piper Meridian starts hotter than almost any other PT6 engine because of the way it’s air intake is designed. Unlike other turboprops, the Meridian has a permanently open inertial separator. This means that not all the intake air makes it to the engine during start because some of it goes out the inertial separator opening. So, coming to a Meridian from operating other turboprop engines can lead to a little bit of a surprise on the ITT temperature being higher than what a pilot is used to when starting.

As a rule of thumb, when starting a Meridian, never let a start continue when the ITT hits 875 degrees. Based on the chart below, you are still in the safe zone at 875 and have about a 50 degree buffer before you have to start getting worried.

On cold starts with a good battery or a GPU, 875 is typically not an issue. Most starts when cold are going to be in the high 700s or low 800s. On a cold start, if you are seeing starts in the mid to upper 800s, try starting with a GPU and see if that lowers the start temperature. If it does, then that means your battery is weak and needs to be replaced. Another tell-tale sign of a weak batter is the Ng doesn’t spool up properly (meaning it settles around 12-13%) or takes a really long time to spool up. Also, never start on the battery with less than 24 volts.

When there are multiple flights in one day, the pilot has to take into consideration the warm engine prior to starting. If the ITT, prior to the start sequence, is above 150 degrees, it is time to do some motoring of the engine.

What is motoring? It is simply using the starter to turn the engine, which leads to air being sucked into the engine allowing the engine to cool off prior to start. The theory is, the cooler your engine prior to start, the cooler the ITT peaks at during start.

Here’s the steps on how to dry motor a Piper Meridian:

  • Battery on
  • Strobes on
  • Fuel Pumps and Ignition off
  • Throttle idle
  • Condition Lever feather/cutoff
  • Push the start button
  • Monitor the ITT temperature
  • Reaching 150 degrees, if less than 30 seconds have elapsed:
    • Fuel Pumps on
    • Ignition On
    • Condition Lever run
  • Reaching 150 degrees, if 30 seconds have elapsed:
    • Push Manual/Stop button to stop the start
    • Let starter rest for 30 seconds

The starter has a 30 second limit on the Meridian, followed by a 30 second rest period. You can do the sequence twice, then, after the 3rd start, there is a 30 minute rest period. Typically, if the ITT won’t cool down to 150 after the 3rd time, there is probably something wrong.

The most important thing a pilot can remember is never, ever push the condition lever forward if the ITT is above 150 degrees. You’ll be well on your way to avoiding hot starts that way.

Similar Posts

  • MMOPA Spring Safety Standdown

    MMOPA will be hosting it’s second Safety Standdown event at many locations across the country for Piper PA46 owners and pilots. The first iteration of MMOPA Safety Standdown in the fall of 2019 was a big hit. Each event was very well attended by MMOPA members.

    What is Safety Standdown you ask? Safety Standdown was put together as a mid-year training event as part of the MMOPA Master Aviator program. It’s goal is to allow PA46 owners and pilots to fly in to a location at a reasonable time (the event starts at 10am local time), received some good quality ground training over relevant safety topics by highly experienced PA46 instructors, have a free lunch, then depart mid-afternoon to arrive back home before dark.

    The event is free to all attendees. Lunch will be provided at each location. This event is not exclusive to MMOPA members, either. Any PA46 owner or pilot, or just anyone interested in the PA46 world, are invited to attend.

    Texas Top Aviation is hosting the South Central Region Spring Safety Standdown at the Henrickson Jet Center at the Austin Executive Airport (KEDC). Hank Gibson and Pedro Vargas-Lebron will be presenting on the following topics:

    • MMOPA Operational Practices review and importance of stabilized approaches
    • Crosswind Takeoffs and Landings
    • High Density Altitude Operations
    • A discussion of thunderstorms, resources in the cockpit for weather avoidance, and accidents that have occurred involving thunderstorms

    The MMOPA Spring Safety Standdown will take place on Saturday, April 18th, 2020. Registration is required for the event. The link for registration can be found here.

    Come on out for some high quality training and free BBQ with 50 of your closest PA46 buddies!

    MMOPA will be hosting it’s second Safety Standdown event at many locations across the country for Piper PA46 owners and pilots. The first iteration of MMOPA Safety Standdown in the fall of 2019 was a big hit. Each event was very well attended by MMOPA members. What is Safety Standdown you ask? Safety Standdown was…

  • The Go Around Button

    Back in the old days, when flying an approach in an early Cirrus SR22 (circa 2004; yes, in airplane technology, those were the old days), performing a missed approach procedure was a lot of work.  You were low to the ground and weren’t able to see the runway.  Then, you had to start climbing so you don’t hit the ground, then push a lot of buttons in order to get the GPS and autopilot set fly the missed approach procedure.  It was very easy to get distracted with button pushing, then forget to fly the airplane, putting yourself and passengers in very unsafe circumstances.  The go around button has changed all that.

    Going Missed the Old Fashioned Way

    Let’s stick with our example of the 2004 Cirrus.  The SR22 in 2004 was equipped with the Avidyne Entegra system, complete with dual Garmin 430 GPS units, and an STEC 55x Autopilot.  A very capable IFR flying machine (we could use the same example of a 2004 or 2005 Lancair Columbia 350 or 400 that was equipped the same way, except the screens were vertical instead of horizontal).

    Avidyne Cirrus Go Around Button

    We’ll use the ILS 15 at the Temple airport, KTPL, for our example.  You pass TPL, the outer marker at 1,683 with the glide slope already centered.  Everything is going well so far.  The number 1 Garmin 430 is set to VLOC and the autopilot is showing NAV and APR for the lateral guidance and GS on the vertical, tracking the glide slope.  The last weather report stated the clouds were Broken at 500 feet, so it appears like you’ll be able to get in on the approach.

    As you get closer to the Decision Altitude, the clouds aren’t letting up at all.  You hit 1,000 feet on your altimeter, 120 feet above the minimums, and you still can’t see a thing.  Another 100 feet lower doesn’t change anything, so you elect to proceed with the missed approach.  This means things are about to get busy.

    Here’s the process:

    • Fly the airplane first, meaning shut off the autopilot, pitch the nose up to about 7 degrees, TRIM, add full power, retract the flaps, and step on the right rudder
    • The Garmin 430 is now in SUSP mode, meaning the missed approach point is locked in as the active waypoint.  So, you have to press the OBS button to cause the GPS to cycle over to the missed approach procedure
    • You have to press the VLOC button on the Garmin 430 in order to change the CDI back to GPS
    • You have to re-engage the autopilot by pressing NAV twice (which engages GPS Steering mode)
    • You have to reset your altitude bug (if you hadn’t set it for the missed approach altitude previously)
    • You have to press VS and ALT on your autopilot to have the STEC continue the climb

    That’s a lot of work, isn’t it?  Plus, that’s an extensive amount of head down time in the cockpit, with your eyes looking elsewhere other than the instruments while hand flying.  All very low to the ground, I might add.  Can you see how this can be dangerous?  (Note:  The Avidyne IFD 550 has made this a little easier with automatically switching from VLOC to GPS and automatically engaging the missed approach procedure in the flight plan)

    The advent of the Go Around Button has streamlined the process, leading to safer operations where it matters most.  The functions of the Go Around Button vary based on the airplane, but here are three examples, the Garmin G1000 Cessna Corvalis TT, the Garmin G1000 Piper Mirage, and the Garmin Perspective Cirrus SR22.

    Cessna Corvalis TT

    We’ll take the above situation and swap out the airplanes.  Gone is the 2004 Cirrus SR22.  Insert a 2008 Cessna Corvalis TT, equipped with the Garmin G1000 suite and the GFC 700 autopilot.  The go around button is positioned directly above the twist in throttle.

    Cessna Corvalis G1000 Go Around Button

    When you push the Go Around Button, here’s what the system does:

    • Disconnects the Autopilot
    • Sets the Flight Director for 7.5 degrees pitch up (which is about your normal climb angle) and wings level
    • Switches the CDI back to GPS
    • Takes the GPS out of SUSP mode and cycles the flight plan to the first waypoint on the missed approach procedure

    Here’s what you have to do:

    • Follow the flight director by pitching the nose up and TRIM
    • Add full mixture, prop and throttle (prop & throttle should be full already)
    • Retract the flaps
    • Step on the right rudder
    • Re-engage the autopilot, then press NAV and VS (or FLC) and set your altitude bug if it isn’t already set

    Not too bad, eh?  Makes the whole situation streamlined and safer.

    Piper PA46-350P Mirage

    Same situation, different airplane.  You’ll notice the procedure for the Piper Mirage is almost exactly the same as the  Corvalis procedure.  The difference between the two airplanes is where the autopilot controller is.  In the Corvalis, the autopilot controller is positioned on the left side of the MFD, making it easy to scan back and forth while pushing buttons on the autopilot.

    The Piper Mirage autopilot controller is positioned below both screens and in front of the power quadrant. With this positioning, the pilot’s eyes have to go a lot further to see which autopilot button he is pushing. In this case, it becomes very important to get the airplane climbing and trimmed before going down to engage the autopilot.

    As in the Corvalis, here is what the Go Around button does:

    • Disconnects the Autopilot
    • Sets the Flight Director for 7.5 degrees pitch up (which is about your normal climb angle) and wings level
    • Switches the CDI back to GPS
    • Takes the GPS out of SUSP mode and cycles the flight plan to the first waypoint on the missed approach procedure

    And here’s what you have to do:

    • Follow the flight director by pitching the nose up, then TRIM
    • Add full mixture, prop and throttle (prop & throttle should be full already)
    • Retract the flaps
    • Step on the right rudder
    • Re-engage the autopilot, then press NAV and VS (or FLC) and set your altitude bug if it isn’t already set

    Cirrus SR22

    Cirrus Perspective Go Around Button

    This time, we’ll use the 2010 Cirrus SR22T with the Garmin Perspective and GFC 700 Autopilot. One thing I really like about how Cirrus configured their system is where the Go Around button is.  It’s actually on the throttle itself, making it much more intuitive.  This way, you can press the Go Around button while adding full throttle.

    There is one major difference between the Garmin Perspective in the Cirrus and the G1000 in the Corvalis. When you press the Go Around button in the Cirrus, the autopilot actually stays on.

    Here’s what happens when you press the Go Around button in the Cirrus:

    • Flight Director pitches to 7.5 degrees pitch up and wings level
    • AP Mode switches to Go Around mode, following the flight director
    • GPS comes out of SUSP mode
    • CDI switches back to GPS

    All the pilot really has to do is add power, take the flaps up, then press NAV on the GFC 700 to get the autopilot following the missed approach procedure.

    If you aren’t familiar with the Go Around button or haven’t used the one in your plane lately, it’s good to go up with a knowledgeable instructor and fly a couple of approaches where you perform the published missed approach afterward.  That way, he or she can assist you through the first missed approach, then give you pointers until  you get comfortable with the Go Around button.

    Back in the old days, when flying an approach in an early Cirrus SR22 (circa 2004; yes, in airplane technology, those were the old days), performing a missed approach procedure was a lot of work.  You were low to the ground and weren’t able to see the runway.  Then, you had to start climbing so…

  • The Aunt Betty Directive: PFD Failures

    Glass panel displays, ballistic parachute aircraft recovery systems, portable tablet computers enabling paperless cockpits, and widely available three axis autopilot systems have changed the way we fly, the way we train, and the way we are expected to perform on check rides. Our training and testing paradigms have tried to stay in synch, yet always seem to be catching up to the latest levels of technology.

    This is very apparent when we instructors are preparing a student for an FAA practical test. When training aircraft had no autopilots, no GPS, and certainly no parachutes, the general philosophy was that during training, the student should have the lowest level of technology available. This was also the expectation on the check ride. This theory has changed over the years and now the Practical Test Standards require that an applicant integrate all available technology while demonstrating mastery of his or her aircraft. This raises numerous questions from instructors and students about what technology will be available for each task.

    One example of this dilemma is found when contemplating an instrument airplane practical test in a Cirrus SR20/SR22. The test requires the task “Instrument Approach without Primary Flight Display”, which has taken the place of what was the partial panel approach, accomplished without use of gyroscopic heading and attitude indicators. In the Cirrus, the standby attitude indicator, standby airspeed, and standby altimeter are available, as is the Multi-Function Display. Guidance from the FAA has us shooting a GPS approach using the moving map display on the MFD after disabling the PFD. Those of us who trained and tested in steam gauge aircraft think that this task should be fairly easy. With a fully functional Attitude Indicator and a nice big moving map display showing our course, a reasonably competent instrument pilot should have little trouble adapting to this setup and flying a good approach.

    But, in the Cirrus specifically, and perhaps in other aircraft as well, another question comes up. Can the applicant use the autopilot (which still works just fine after a display failure) during the approach without the PFD? A rather famous DPE who writes for a national magazine says “yes”, opining that not to allow its use would be introducing simultaneous multiple systems failures, which is strictly forbidden in the minds of some. If we follow this logic, we would not test simulated engine failure emergencies in these aircraft either, because to do so would imply failure of not only the engine, but the CAPS parachute system as well. In my former role as a pilot examiner, I always said no, that the approach should be hand flown. Here is my logic.

    I was amazed that flight instructors and examiners would accept the substitution of autopilot technology for the skill required to fly an approach without the PFD. I would argue that the intent and the well described emphasis of the PTS is that the applicant must demonstrate the ability to control the airplane after a loss of the primary flight display, not observe and monitor the autopilot controlling the airplane! This argument was generally unpersuasive, so I approached from a different point of view, that of a concerned family member.

    “Aunt Betty” represents a future passenger flying with the soon to be rated instrument pilot. Here is the question posed to Aunt Betty: “When we train and test pilots for instrument proficiency, we require them to demonstrate the ability to safely and skillfully fly the airplane without their primary instruments. Now, Betty, in this airplane, we can test this task in one of two ways. We would like your input on which way you would prefer, seeing as you will be a frequent passenger with your nephew. We can either have the pilot (might be your son, brother, husband, or nephew) demonstrate that he can fly the airplane by hand without the PFD, which does require a little more skill and a slightly different technique, or, we can require the pilot to perform this task using the autopilot so that the pilot basically monitors the airplane flying itself on the approach.

    “Now, Aunt Betty, a pilot allowed to use the autopilot system on this approach may not have the skill or technique to fly the approach by hand in the clouds should the autopilot shut down due to turbulence or mechanical failure. Should this happen to a pilot without the skill and practice normally required, the odds of a fatal accident occurring would be quite high.

    “So what do you think, Aunt Betty? Would you feel more comfortable flying with this fellow if he has demonstrated mastery of the aircraft (sans PFD) without the autopilot or only with its assistance?”

    This leads us to a larger discussion about the use of other technology, iPad, GPS moving map, and more. If technology is used as a replacement for pilot proficiency during training and testing, we end up with less skillful, less competent and ultimately less safe pilots. But, if we require that our students demonstrate mastery with the lowest available level of automation and technology (which, by the way, implies excellent fundamental aircraft control skills) then, when technology is added into the equation, we have a safer pilot.

    Technology can be a value added safety multiplier, or it can be a crutch needed to make up for lack of fundamental and advanced skills. Crutch or Safety Multiplier, which one will you choose? I know which one Aunt Betty prefers.

    Charles McDougal is a flight instructor, corporate pilot, and former DPE ‎who offers basic and advanced flight instruction in the San Antonio area.  To find out more information about Charles or to contact him, visit his website, www.flighttrainingcoalition.com.

    Glass panel displays, ballistic parachute aircraft recovery systems, portable tablet computers enabling paperless cockpits, and widely available three axis autopilot systems have changed the way we fly, the way we train, and the way we are expected to perform on check rides. Our training and testing paradigms have tried to stay in synch, yet always…

  • Learning From Other’s Mistakes:  An Overview of the 2024 Piper PA-46 Accidents

    The Piper PA-46 series, which includes models like the piston engine Piper Malibu and Piper Mirage, and the turboprops Piper Meridian, M500, and M600, is a popular choice for private pilots and business aviation. Known for its impressive speed, range, and pressurization, the PA-46 is a very capable single pilot aircraft. However, like all high-performance aircraft, it presents its own set of challenges and risks, especially when pilot error or adverse conditions come into play.

    The 2024 PMOPA (Piper M-Class Owner’s and Pilot’s Association) Convention was the first weekend in November and one of the sessions every year is the PA-46 Safety Review.  Sadly, in 2024, the accidents involving various PA-46 models pointed out several areas related to decision making that all pilots need to put be aware of. These accidents highlight critical issues in weather awareness, pilot training, and decision-making, and they provide valuable lessons for other pilots in any type of aircraft.

    Overview of the 2024 Piper PA-46 Accidents

    The Piper PA-46 is generally regarded as a reliable and capable aircraft, but the safe outcome of a flight often times depends on the pilot’s decision making.  There always can be mechanical malfunctions, but those still require good pilot decision making to be able to walk away from the accident.

    In 2024, multiple accidents occurred involving different variants of the PA-46, with many of the accidents occurring during critical phases of flight like takeoff or landing. Some of the key factors contributing to these accidents included:

    1. Weather Challenges: In several cases, adverse weather conditions, such as low visibility, thunderstorms, or high winds, contributed to accidents. Despite most PA-46’s being equipped with NexRad and weather radar, pilots sometimes underestimated or misjudged the weather risks.
    2. Pilot Decision-Making: A recurring theme in these accidents was pilot error—specifically, poor decision-making when faced with challenging conditions. In some cases, pilots continued flights despite deteriorating weather or failed to react appropriately to emergency situations.
    3. Mechanical Failures: As with every airplane, systems fail on a Piper PA-46.  Several accidents were due to engine power loss.  Proper training teaches pilots how to have the right mindset and skills to handle those engine power loss situations, taking a bad situation and having the best possible outcome due to good decision making and gliding skills.

    Three Key Lessons for Pilots

    The Piper PA-46 accidents of 2024 serve as valuable reminders about the importance of pilot preparation, decision-making, and risk management. Here are three critical lessons pilots can take away from these accidents:

    1. Prioritize Pre-Flight Weather Planning

    Poor weather conditions were a significant factor in some of the crashes in 2024. Pilots of high-performance aircraft must place a strong emphasis on weather pre-flight planning, especially when flying into regions prone to rapidly changing weather or severe conditions and across frontal systems. Pilots should:

    • Stay up-to-date with weather briefings before and during the flight, including calls to Flight Service Station if there is serious weather along the route.
    • Be proactive in altering flight plans or delaying departures when weather conditions become unfavorable.
    • Utilize onboard weather radar and other tools to monitor changing conditions in real time and avoid nasty looking weather systems.  ADS-B and XM Weather are delayed information.  They are not meant to be used to find holes through storm systems.
    • Finally, don’t try to shoot through holes!  They are called sucker holes for a reason.

    2. Master Emergency Procedures

    Pilots of all aircraft, not just PA-46 models, need to practice engine-out procedures multiple times a year with an instructor, not just at recurrent training.  The goal is to make emergency procedures second nature which creates the right mindset to handle the emergency, creating a much better outcome. Training should focus on:

    • Engine-out procedures immediately after takeoff, climbing out at low altitude, and at cruise.
    • Performance with the propeller feathered and unfeathered, recognizing how the feathered prop increases glide range.
    • Practicing forced landings and other emergency scenarios regularly to build confidence and competence.

    3. Always Plan for an Emergency Landing

    It is very important to know your options in the event of an emergency. When flying over mountainous or remote areas, pilots should always have a contingency plan for where to land if something goes wrong.  An emergency engine out brief should be a part of every pre-takeoff briefing to put the pilot in the right mindset. Pilots should:

    • Brief an engine failure on the runway, low altitude, and at an altitude that allows for a safe return to the airport in the event of an engine failure as part of every pre-takeoff briefing.
    • Study the flight route in detail and identify suitable emergency landing sites along the way, especially when flying in areas with limited options.
    • Consider the terrain, weather conditions, and available options in the event of an engine failure or other emergency.
    • Use terrain awareness and other onboard tools to help identify suitable landing areas in real-time, including the ForeFlight Glide Advisor.

    Conclusion

    The Piper PA-46 series, while a capable and reliable aircraft, demands a high level of skill and preparation from its pilots. The accidents in 2024 serve as a sobering reminder of the critical importance of weather awareness, emergency training, and proper flight planning. By learning from these accidents, pilots can make better decisions, have the right mindset, and reduce the risk of similar accidents in the future.

    By prioritizing weather awareness, mastering emergency procedures, and always having a contingency plan for forced landings, pilots of the Piper PA-46 can improve their ability to handle the challenges posed by these high-performance aircraft. These lessons are not just for PA-46 pilots, but for all pilots striving to fly safely and confidently.

    The Piper PA-46 series, which includes models like the piston engine Piper Malibu and Piper Mirage, and the turboprops Piper Meridian, M500, and M600, is a popular choice for private pilots and business aviation. Known for its impressive speed, range, and pressurization, the PA-46 is a very capable single pilot aircraft. However, like all high-performance…

  • Flying Through Rain

    For the most part, flying through rain is a non-event. If the NexRad or Radar is showing light green or dark green, usually there aren’t that many bumps and your plane just gets a wash. Sometimes the visibility drops down a little bit making us IFR pilots have to transition to our instruments.

    It get’s a little more exciting when the precipitation on your screen turns to yellow. This means there is a lot more precipitation echoes either in the clouds or coming out of the clouds, meaning harder rain. I usually tend to stay away from yellow unless it’s absolutely necessary to go through it.

    I had a situation a few weeks ago where I deemed it necessary to fly through some yellow NexRad returns. I was flying a G1000 Columbia into Monroe, Louisiana, KMLU. The winds were mostly light, but slightly favoring runway 04, which was the runway in use. As I got closer, a decent size rain shower with mostly yellow returns was sitting over the final approach fix for runway 04 and slowly tracking to the northeast.

    I didn’t particularly want to spend the entire approach getting beat on with rain, so I decided to fly the RNAV 14 approach at MLU and circle to land on runway 04. The rain hadn’t quite reached the airport yet, so I decided that circling to 04 should be no problem.

    I started the RNAV 14 at the FLESH IAF. Since I was approaching from the west, I did not need to do the procedure turn, so I joined the Final Approach Course (FAC) after crossing FLESH.

    In the meantime, that rain shower was inching closer to the FAC for the RNAV 14. I wasn’t concerned about my safety if I flew through some of it and I didn’t have passengers on board who would get nervous, so I elected to continue. I wasn’t seeing any lightning coming out of the clouds, so it appeared to only be moderate rain.

    Just before I got to JIVEY, the FAF, I entered the clouds and the rain. About 20 seconds later, my altimeter and airspeed started bouncing around a lot. Now, based on all I’ve said so far, what would cause that, and what would you do?

    (Jeopardy theme song playing while contestants ponder questions)

    The answers? Due to the moderate precipitation, water had gotten into my static port and caused the unusual readings on my altimeter and airspeed indicators on the G1000.

    I had experienced this before, so I knew what to do. I reached down and turned the static source from primary to alternate, which starts taking static pressure from inside the cabin in the Columbia. Instantly, everything went normal.

    The other time I had experienced this was also in a Columbia, so I’m under the impression that the way the Columbia static ports are designed, they are a little bit more susceptible to water creeping into them than other airplanes.

    Moral of the story? If your pitot/static instruments start jumping around, the first thing you do is turn your alternate static source on.

    For the most part, flying through rain is a non-event. If the NexRad or Radar is showing light green or dark green, usually there aren’t that many bumps and your plane just gets a wash. Sometimes the visibility drops down a little bit making us IFR pilots have to transition to our instruments. It get’s…

  • Oh, Deer (Part 3)

    Read Part 1 & Part 2

    Throughout the whole event, I learned quite a few things both about flying and about myself. Here are some of the lessons which I have taken away from the accident:

    1. No flight is routine: When I took off that morning I was about as relaxed as I could have been while going to fly. I was flying an airplane that I knew well, in beautiful weather, to familiar airports and even carrying passengers which I had taken on this exact trip more than a dozen times. The accident brought into startling clarity that anything can happen at any time. I had done everything right that morning (preflight, weather briefing, planning, etc) , and none of that did anything to stop the deer from jumping out onto the runway. All we can do is ensure the items we do have control over are covered and try to be prepared to deal with anything else that arises. This ties directly into my next point:
    2. Making sure everything is correct: When you do go fly, make sure that you have all your paperwork and personal details taken care of. I can think of a few times over the course of my flying career where something wasn’t quite right with the paperwork, or perhaps I had forgotten my wallet and I was tempted to go fly anyway. “It’s 8pm on Sunday, I’m not going to get ramp checked.” Well, I can assure you that the paperwork and questionnaires which were required to be submitted to the FAA, NTSB, and Insurance companies would have uncovered any discrepancies in my logbooks, currency, or legality. It isn’t worth the risk of flying without having everything in place just in case something happens. It isn’t just a random ramp check which can get a pilot into trouble.
    3. Ask for help: The story of my collision with a deer would have had a very different outcome if it weren’t for the help that I received from countless the people on the ground. If you’re ever in a situation where you could use a hand, don’t be afraid to ask for help. If I had simply turned around and landed back at Wings, I wouldn’t even have had any idea that my landing gear was missing! The people in the control tower, the maintenance guys, the approach controllers in Philly, the emergency responders, and many more people all played their part in orchestrating a successful outcome.

      Airplane sitting on the runway after the firefighters had checked it out
      Photo credit: www.lancasteronline.com
    4. Dealing with the Paperwork: I have had dealings with the FAA before, but never for an accident. I was afraid that the investigation would be a witch hunt and I would have to defend myself while someone poured over all my planning and paperwork looking for potential errors. But, my fears were totally unfounded. Although I did have to answer many phone calls, write many reports, and fill out much paperwork, the FAA, NTSB, and Insurance companies were very patient in waiting for my responses and even complimentary in how the situation played out. I really enjoyed working with all of them and appreciated their encouragement and help.
    5. Emotional Response: After the dust had settled and the smoke had cleared, I was left standing on the side of the runway with the passengers and my boss. I offered to fly them back to Philadelphia or continue to Pittsburgh and assured our Chief Pilot that I was feeling fine and ready to fly again. Fortunately, there wasn’t a need. Over the next week or two, I noticed a change in myself. I wasn’t fine. I have never had headaches, but shortly after I landed I developed a headache that didn’t go away for days. I had trouble focusing on anything and I had trouble finding motivation to do much but sit and stare at a wall. I wasn’t sharp and I caught myself making silly mistakes in my normally routine activities. I wasn’t depressed, or sad, it was just an unwanted mental and physiological response to the stress and shock of what happened that morning in the Baron. I didn’t feel like myself for quite some time and I even found myself a little on edge whenever I lined up for takeoff on subsequent charters for while afterward. Eventually I started to feel normal again, but it was a slow process.
    6. Feather the Props: I can’t tell you what a difference it makes when those props go from wind milling to feathered. It became clear to me that feathering a prop could make a huge difference in deciding the outcome of an emergency situation.
    7. Good training and checklists usage: This one is pretty straight forward, but it’s worth mentioning. Good training and proficiency make all the difference when the odds are against you. Make sure that you use all your resources when your back is against the wall, and that includes the checklists. Under the stress of the flight I had forgotten to close the cowl flaps and would likely have landed with them open without the aid of the Emergency Procedures Checklist. This would have resulted in unnecessary damage to the airframe.
    8. No need to rush: There is no denying that I had things stacked in my favor that day. I had nice weather, extra gas, daylight hours, and even the luxury of landing at my home airport. But, regardless of all those variables, there is no need to rush into anything. Ask questions, find answers and come up with a plan. Obviously not all emergencies present the pilot with the luxury of time, but use all time and resources you have to your advantage.
    9. Polish up those procedures: The deer accident really made me want to go out and brush up on all the emergency procedures which I hadn’t performed since my last checkride. The realization that I could need any of them at any time was really hit home after I hit that deer. Additionally, make sure you know who to call if something ever does happen.
    10. Know the systems: Familiarity with the systems on the airplane makes it easier to troubleshoot and solve issues on the fly and makes it easier to spot a problem in the first place. Knowing how systems work and what their normal indications should be helps make decisions regarding when to divert and where to land easier.

    The irony isn’t lost on me that the last article that I wrote for this newsletter dealt with how to avoid making gear up landings and the high cost required to repair one. I never would have imagined when I wrote that article last fall that I would be writing one only a few months later detailing my own gear up landing.

    The bottom line is that there is nothing a person can do to prepare for every situation which might arise throughout the course of a flight, and it’s also impossible to know which emergency you may have to deal with if a situation arises. All we can do is stack odds in our favor by making sure that we address the things within our control such as aircraft maintenance, careful flight planning, checking weather, and having personal minimums set in place to keep us from flying outside of our skill sets and comfort zones.

    Additionally, ensuring that you are knowledgeable and proficient in your aircraft’s procedures will give you the best chance for success. When things start going wrong, keep calm, and ask for help. Work the problem instead of guessing or rushing into a less than desirable solution. No one wants to be caught in an emergency like a deer in a landing light!

    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 & Part 2 Throughout the whole event, I learned quite a few things both about flying and about myself. Here are some of the lessons which I have taken away from the accident: No flight is routine: When I took off that morning I was about as relaxed as I could have…

Leave a Reply

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