|

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

  • Texas STOL Roundup

    Looking for a fly in this fall?  Check out the Texas STOL Roundup at the end of September in Hondo, KHDO.  Interested in entering?  All are welcome!  There are several different categories including LSA, Experimental, and others.  Come in for a fun weekend and see how short an airplane can be landed!

    There will be bands, a STOL seminar, and even a hangar dance.

    Fly in or drive in.  Camping will be available on the airport.

    For more information, you can visit the event website.

    Looking for a fly in this fall?  Check out the Texas STOL Roundup at the end of September in Hondo, KHDO.  Interested in entering?  All are welcome!  There are several different categories including LSA, Experimental, and others.  Come in for a fun weekend and see how short an airplane can be landed! There will be…

  • 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…

  • Determining Pattern Altitude

    Figuring out the pattern altitude at an airport should be pretty simple, right?  But, in this day of helpful technology, most pilots actually get it wrong.  How can you always get it right?  Well, it just takes about an extra 15 seconds.  Here’s how.

    Traffic Pattern
    John Wayne Airport Traffic Patterns

    As outlined in the Aeronautical Information Manual, section 4-3-3, “traffic pattern altitudes for propeller-driven aircraft generally extend from 600 feet to as high as 1,500 feet above the ground.”  Further, in the Pilot’s Handbook of Aeronautical Knowledge on page 13-10, it states:  “1,000 AGL is recommended pattern altitude unless established otherwise.”

    Okay, so for piston driver’s, we’ve got it narrowed down to 1,000 AGL (Above Ground Level for those who don’t like acronyms).  But wait!  There’s that very important phrase at the end of the last quote:  “unless established otherwise.”  That means not all airports have traffic pattern altitudes of 1,000 AGL, or else they wouldn’t put that line in there!

    How do you find out what the TPA (Traffic Pattern Altitude) is for a certain airport if it’s not 1,000 AGL?  Great question!  Your first guess is probably to look on Foreflight.  Though this is a good start, it is not the full answer.

    Let’s use an example.  Look up KAQO, the Llano Airport on Foreflight.  At the top of the page, the airport elevation is stated as 1,101′ MSL and the pattern altitude is stated as 1,902′ MSL.  From what we just learned, 1,902′ MSL is not 1,000 AGL, so is 1,902′ MSL otherwise established?

    On the Airports page with KAQO pulled up, tap the A/FD tab, second to last on the left.  Scroll down to Llano Muni.  Read the whole entry.  Does it state in the entry that pattern altitude is different than 1,000 AGL?  It sure doesn’t.  So, because it is not otherwise established, pattern altitude at KAQO is 2,102′ MSL not 1,902′ MSL.

    Where did Foreflight get that?  I have no idea.  Too often, though, pilots look at the Foreflight pattern altitude and don’t actually check the Airport Facilities Directory (A/FD).  Then, they get the pattern altitude wrong.

    What does it look like when pattern altitude is otherwise established?  Look up KSGR, Sugar Land Regional, on your Foreflight app.  Foreflight states the elevation as 82′ MSL and the Pattern Altitude as 1,000′ MSL.  Is this correct?  Well, tap that A/FD button again and let’s find out.

    On the second line of the A/FD entry, it says TPA-See Remarks.  Down in the remarks section, we find the following:

    TPA-1000 (918) single engine piston acft, TPA-1500 (1418) for twin and turbojet acft, TPA-500 (418) for helicopters within 2NM.

    Foreflight got it right this time for single engine pistons, but if you are in a twin, the pattern altitude is different.  What’s the lesson here?  Always check the A/FD and don’t always go by what Foreflight says.  The A/FD is always right and usually has a little more detail to help set you straight.

    One last thing.  Both the AIM and the Pilot’s Handbook of Aeronautical Knowledge, when talking about pattern altitude, state, “When operating at an airport, traffic pattern altitudes should be maintained unless otherwise required by the applicable distance from cloud criteria in…section 91.155.”  91.155 defines basic VFR weather minimums.  So, to fully interpret what the AIM is saying, we have to take into account the type of airspace we are in to determine if we can safely and legally operate at pattern altitude at a particular airport.

    For example, let’s say we are at KCVB, the Castroville Airport.  Pattern altitude there is 1,602 feet, which is 829 AGL.  CVB is Class G airspace up to 700 AGL, then Class E above that.  Let’s say there is a 700 AGL broken cloud layer.  Pattern altitude is 829 AGL, so you won’t be able to get up that high with a broken ceiling.  What altitude can you do pattern work at to stay legal?

    Class G VFR weather minimums during the day below 1,200 AGL is 1 SM visibility and clear of clouds.  So, legally, you could fly at 699 AGL (which at CVB would be 1,472 MSL) while in the pattern and be legal.  Safe?  Maybe, but probably not if you are skimming the base of the clouds.  Is 1300 MSL a safer pattern altitude in this example?  Well, that is 527 AGL, so probably not, since towers tend to stick up that high sometimes.

    Let’s go back to KSGR and put a 1,000 AGL overcast ceiling there.  SGR is Class D airspace and we already determined pattern altitude there was 1,000 MSL for piston singles.  VFR visibility and cloud clearance requirements in Class D airspace are 1,000 feet above clouds, 500 feet below clouds, and 2,000 feet horizontally from the clouds with 3 SM visibility.  In order to stay 500 feet below the clouds, you would be flying a 582 MSL pattern.  Safe?  Probably not, though it is legal.

    To summarize, don’t take Foreflight’s word for pattern altitude.  Cross reference the A/FD (it only takes 15 seconds at the most) to verify.  If it’s cloudy, it’s really best to stay on the ground, but if you want to find out your legal pattern altitude with a cloud deck, cross reference 91.155.  I don’t recommend flying below pattern altitude because it is there for a reason.

    Figuring out the pattern altitude at an airport should be pretty simple, right?  But, in this day of helpful technology, most pilots actually get it wrong.  How can you always get it right?  Well, it just takes about an extra 15 seconds.  Here’s how. As outlined in the Aeronautical Information Manual, section 4-3-3, “traffic pattern…

  • Flying WAAS GPS Approaches

    When flying a WAAS GPS approach, there are several different levels of WAAS signal that a GPS receiver can get. The most precise is an LPV signal. LPV stands for Localizer Performance with Vertical guidance. An LPV approach has the lowest minimums of all the WAAS GPS approaches, typically in the range of 200-300 feet AGL. A GPS glide path (GP) is guaranteed with an LPV approach and the minimum altitude is a decision altitude (DA).

    Just like a localizer, an LPV course width get’s tighter and the CDI becomes more sensitive the closer the plane get’s to the runway. Even though the LPV approach minimums are so low and the approach is down to a DA, they still aren’t considered precision approaches by the FAA (which leads to some extra planning when selecting an airport as an alternate that only has GPS approaches, since the AIM specifies only the LNAV minimum are to be considered if an alternate airport only has GPS approaches, bringing the 800 foot ceiling requirement to bear)

    An LNAV/VNAV approach is still a WAAS approach that has a GPS glidepath, but is slightly different than an LPV approach. An LNAV/VNAV final approach course does not get more sensitive the closer the plane gets to the runway. The smallest course width on an LNAV/VNAV approach is 0.3 miles either side of center. LNAV/VNAV approaches will, most of the time, have higher minimums than LPV approaches and can have minimums no lower than 250′ AGL.

    The third type of WAAS approach is strictly a non-precision approach with a Minimum Descent Altitude (MDA). These are designated LP approaches, which stands for Localizer Performance. These are like old school Localizer only approaches that, similar to the lateral portion of an LPV approach, the course width tightens the closer to the runway that a pilot is. There is no glide path by definition of an LP approach, though there is a caveat.

    Now, by looking at an approach plate that is a WAAS approach, but only has LP minimums listed, a pilot would assume there would be no glide path. Depending on what type of GPS unit the airplane has, that pilot could be wrong. Garmin Perspective units (Cirrus G1000), all GTN 750s and GTN 650s, All G1000 NXi units, most Garmin 430W and 530W, and all Avidyne IFD 550/540 and 440 units will display an advisory glide path on an LP approach, designated LP+V.

    What does LP+V indicate? An advisory glide path is just advisory, but it is totally legal to follow down on a non-precision LP approach. The kicker is obstacle clearance is not guaranteed and the pilot needs to keep an eye on minimum altitudes at the different waypoints on the approach. The big thing I tell people is, when you arrive at the MDA and the runway is in sight, following the advisory glide path below the MDA could get you in trouble with obstacles. Don’t just hone in on your instruments when you break out of the clouds. Look out the windscreen and make sure you won’t hit anything.

    If you arrive at the MDA on the advisory glide path and the runway isn’t in sight, DON’T GO BELOW THE MDA! Most autopilots won’t level off at the MDA, even if that altitude is set in the altitude pre-select, so this will involve turning off the autopilot before the MDA and manually leveling off, or engaging the altitude mode of your autopilot at the MDA.

    One other type of GPS approach that you will encounter is an LNAV approach. This is a non-WAAS approach down to an MDA, but your GPS unit may still give you a +V. Most modern ones will.

    When flying a WAAS GPS approach, there are several different levels of WAAS signal that a GPS receiver can get. The most precise is an LPV signal. LPV stands for Localizer Performance with Vertical guidance. An LPV approach has the lowest minimums of all the WAAS GPS approaches, typically in the range of 200-300 feet…

  • The Avidyne Equipped Cirrus Upgrade

    A History Lesson

    11 years ago, in April of 2009, the Avidyne Corporation unveiled the much bally-hooed Release 9, or R9 as it is commonly known, as a hardware replacement for the Avidyne EX5000 Entegra system in Cirrus Aircraft. The Entegra system was way outdated by that point. Even though Avidyne was the first company to put together a glass PFD in a single engine piston airplane, the company had quickly fallen behind Garmin in keeping up with the ever changing technology landscape.

    Rewind to 2008. Cirrus had been going strong with the Avidyne Entegra since the SR20 and SR22 went to full glass in 2003 (a PFD and an MFD; prior to that, Cirrus aircraft only had an MFD with steam gauges and a Sandel Electronic HSI). Cessna, on the other hand, vaulted past the Avidyne Entegra and went straight to the Garmin G1000 in it’s aircraft, starting in 2004 with the 182 G1000 and 2005 with the 172 G1000. Beechcraft and Columbia went to the G1000 (Columbia started with the Avidyne as well) in 2005.

    Garmin’s technology in 2007 was so much better than Avidyne’s technology that Cirrus decided to switch. I’m sure there were many promises made by Avidyne to Cirrus about what Avidyne was working on (the R9), but the G1000 was out there, available, and being used in a lot of different airplanes with very good results.

    So, in 2008, Cirrus made the switch from the Avidyne Entegra to the Garmin G1000, dubbing it the Cirrus Perspective by Garmin avionics package. Avidyne finally got the R9 to market in 2009, but by that time, Piper was the only airplane manufacturer left putting factory Avidyne panels in their airplanes, and they switched to G1000 later that year.

    The R9 is a fabulous product. It’s fully integrated, has great graphics, has fully redundant displays, a QWERTY keypad (which, by the way, Garmin didn’t do for another 8 years), and a lot of other neat features. There’s a bit of a learning curve, but it’s a really good product for what it is.

    Avidyne, though, was late to the game with their technology. By the time it debuted in 2009, all the GA aircraft manufacturers had long since switched to the Garmin G1000 and weren’t looking back. That left Avidyne with the retrofit market for the many different Avidyne Entegra Cirrus aircraft out there. The only problem was, the retrofit was $80,000 ($95,000 if you wanted to throw in the DFC 100 Autopilot, which is a must have) and not many owners were up for paying that much money, then or now.

    To sum up our brief history lesson, Avidyne knew the Entegra needed to go, but couldn’t get the R9 out quickly enough to convince anyone to stick with Avidyne products. The retrofit market didn’t amount to many sales, so Avidyne doesn’t even make the R9 anymore.

    As a side note, I really, really like the Avidyne R9 and am sad that it didn’t make it into more airplanes.

    So, when the Avidyne Entegra starts to have issues, what’s an owner to do? Keep reading!

    There is Hope

    There are thousands of Cirrus aircraft out there flying with the Avidyne Entegra instrumentation, which is basically 20 year old technology (I’ve had a computer engineer tell me the programming in an Entegra is Windows 98 tech). These things are going to start having problems at some point (many already have), but what solution do owners have that is cost effective and get’s them new technology?

    Remember that little company named Garmin? Well, they have come through again. Announced this summer, the Garmin G500 TXi is now certified as a replacement in the Cirrus Avidyne Entegra equipped aircraft. This means pulling out both the PFD and MFD and replacing them with the G500 TXi on both sides. Engine data is also displayed on the G500TXi MFD, including the percent power and TIT indications, if equipped.

    Cirrus SR22 Equipped with Dual G500 TXi Screens and Dual Garmin GTN 650Xi GPS Units

    The cost for the panel? Two 10.6″ G500 TXi’s run about $16,000 apiece for the units, not including labor. $32,000 for a brand new panel isn’t terrible. Plus, the G500 TXi’s work with the DFC90 autopilot if the Cirrus is already equipped with it. If not, the Garmin GFC 500 autopilot is now approved for the Cirrus at a relatively low price of $7,000, including the servos.

    Still have the original Garmin 430s in your Cirrus? Upgraded to the Avidyne IFD 540/440 stack? Put in dual GTN 650Xi’s? Put in a GTN 750Xi? All are compatible with the G500 TXi panel.

    Want to upgrade everything? It does get kind of pricey at that point, but for just equipment, the cost for a complete panel conversion is somewhere in the area of $65,000 plus labor, still below what the R9 cost, but not cheap either. That would include 2 G500 TXi’s, 2 GTN 650Xi’s, a GFC 500 Autopilot, and all the engine monitoring equipment that the G500 TXi would need.

    Cirrus SR22 Equipped with Dual G500 TXi Screens, a GTN 750Xi, and a GTN 650Xi

    Thankfully, some new technology has finally come to the Generation 1-3 Cirrus. Oh, and by the way, your steam gauge Cirrus is fully upgradable as well.

    Want to read more? Check out Garmin’s website.

    A History Lesson 11 years ago, in April of 2009, the Avidyne Corporation unveiled the much bally-hooed Release 9, or R9 as it is commonly known, as a hardware replacement for the Avidyne EX5000 Entegra system in Cirrus Aircraft. The Entegra system was way outdated by that point. Even though Avidyne was the first company…

  • Angelina County Airfest

    The Angelina County Airport in Lufkin, TX (KLFK) will be hosting the Angelina County Airfest on Saturday, October 10th.  The airport will open up at 9am.

    Prepare for a day of food, fun, and some great performances.  There will be warbirds and many other classic airplanes on display, not too mention a number of aerobatic performances as the day goes on.

    To learn more about the Airfest, visit the Angelina County Airfest website.  Tickets start at $10 for adults.

    Angelina County Airfest

    The Angelina County Airport in Lufkin, TX (KLFK) will be hosting the Angelina County Airfest on Saturday, October 10th.  The airport will open up at 9am. Prepare for a day of food, fun, and some great performances.  There will be warbirds and many other classic airplanes on display, not too mention a number of aerobatic…

Leave a Reply

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