Keeping Your Margin

Just south of the equator in the mountains of Papua, Indonesia on the island of New Guinea, pilots spend their days carrying food, building supplies, doctors, pigs, and passengers into some of the most remote and extreme airstrips on the planet. That’s where I fly.

Each morning I load my Cessna Grand Caravan with 2,600 lbs of (insert strange cargo here) and depart my home base of Wamena just after the sun sends its first rays of light across the waking skies above. I spend my day winding through narrow valleys and crossing high altitude mountain passes with building clouds and poor communication, only to land on short, narrow airstrips with steep slopes and little room for error. Most of these one-way in, one-way out runways require me to commit to landing well before touchdown due to terrain that is too close to allow for a safe go-around. Everything better be right when I cross that decision point or I could be in for some excitement.

DCIM100GOPRO

The need to keep wide margins of safety might seem obvious in environments like mine, but that doesn’t make them any less important where you fly. You may be a new pilot or an old timer, but keeping your margin should always be on the top of your priority list.

Let’s unpack this further. Margin is not just maintaining the regulatory requirements for cloud clearances or minimum altitudes. It’s more than planning for an alternate airport or carrying the required fuel reserve. Margin is breathing room. It is that extra maneuvering room, the Plan C, the well thought out options that provide you multiple “outs” in any given situation. Margin is what gets you home when things take a turn for the worse.

Margin comes in all shapes and sizes. For myself it includes maintaining double my required turn radius in narrow valleys or choosing not to land when my groundspeed is just 1 knot too high at a short and slippery airstrip. For you, it could be determining a ceiling or visibility minimum requirement that is more conservative than the legal ones or setting a wind limitation that you know is reasonable. When it comes down to it, keeping your margin means you don’t push to the ragged edge of your skill or the aircraft’s capability.

Margin can also refer to your mental or emotional capacity. Are you mentally prepared to divert and miss that important event because the weather is getting bad? Are you ready to handle the disappointment of passengers when you arrive over your airstrip and choose not to land due to approaching rain or a factor that is difficult for a non-pilot to understand? Are you willing to cancel a flight on an important client because you are coming down with a cold or didn’t get adequate sleep? As the PIC of your flying machine, you alone are responsible for the safety of the aircraft and the people on board and those are the tough calls that only you can make.

Fatigue, overconfidence, and complacency are the biggest obstacles to keeping your margin. They are all very subtle dangers and you may be experiencing them without even recognizing it. Fatigue can slow down your thought process leaving you behind the plane and backed into a corner before you know it. Overconfidence might cause you to push weather or commit to a course of action that has no favorable alternatives. Complacency will lead you to believe that, because you have 2000 hours in a particular make and model, you don’t need to do a thorough preflight or complete the pre-landing checklist.

Regardless of experience level, operating environment, fancy avionics, and level of proficiency, margin is something that we all need plenty of. So as you go about your upcoming flights, be asking yourself what you can do to build in more margin. It just might be what gets you home.

Pete Greenwald is a transplant to Atlanta, Georgia who has fallen in love with all things Southern, including his wife, Ashley.  As a pilot and A&P with Mission Aviation Fellowship, he flies the Cessna Grand Caravan in Papua, Indonesia serving people who live in isolation. In his spare time he is on the hunt for the best burger around.

Similar Posts

  • The Diamond DA62: The Ultimate Twin

    Late last year, the Diamond Aircraft Corporation announced a brand new twin engine, the Diamond DA62. At first glance, this is a pretty cool airplane.  It seats 7 passengers, spread out amongst 3 rows, with 2 massive doors, leading to an “SUV” type feel, according to Flying Magazine.  That is only one of the “neato” features of the Diamond DA62.

    The thing that will make pilots believers is the fuel burn.  According to Flying Magazine, which did a test flight of the airplane, at 14,000 feet and 60% power, the airplane was only burning 12 GPH, but still doing 170 KTAS.  Remember, this is a twin.  That’s about the same as a normally aspirated Cirrus SR22 at the same altitude.

    Diamond DA62

    How does Diamond do it?  Jet A.  The company put two Austro AE330, 170 Horsepower, Jet A burning piston engines on the Diamond DA62.  You may say, well, yeah, at 60% power, that’s great, but I want to go places. How much fuel does it burn then?  Even at max continuous power of 95%, it’s still only burning 18.5 GPH total and cruising at 195 knots.  Paying Jet A prices, that’s pretty sweet.

    The range on the airplane is quite nice too.  Again, according to Flying Magazine, the range with full fuel (86.4 gallons with aux tanks) is about 1,300 miles.  You can carry the whole family too, as the full fuel payload is 1,000 pounds.  Golf clubs?  No problem.  Just stick them in the nose.

    The Diamond DA62 is probably one of the easiest twins to manage, engine-wise, too.  The Fully Automated Digital Engine Control (FADEC) system that Diamond installed leaves the pilot with only 2 power levers, instead of 6 on the typical piston twin.  All that needs to be done at cruise is set a percent power and the FADEC computer does the rest.

    Need air conditioning, built in oxygen, and TKS?  Diamond can set you up.  The G1000 system complete with digital backup instruments is standard in the airplane.  What more can you really ask for?

    If you haven’t figured it out, I really like this airplane and would be aching to fly it.  I enjoy the DA40 and have a good amount of DA42 experience, but I’d really like to hop in a Diamond DA62.

    Read the whole Flying Magazine article here.

    Sources:  Flyingmag.com

    Late last year, the Diamond Aircraft Corporation announced a brand new twin engine, the Diamond DA62. At first glance, this is a pretty cool airplane.  It seats 7 passengers, spread out amongst 3 rows, with 2 massive doors, leading to an “SUV” type feel, according to Flying Magazine.  That is only one of the “neato”…

  • Oh, Deer (Part 1)

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

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

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

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

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

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

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

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

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

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

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

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

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

    To Be Continued…

    (Read Part 2 Here)

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

    As far as I knew when I woke up, October 26, 2016 would be an ordinary day for me. It was a Wednesday, and I was scheduled to fly our Company’s BE58 Baron on a charter from Wings Field (KLOM), a non-towered airport just north of Philadelphia, to Pittsburgh International Airport (KPIT) and spend the…

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

    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…

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

  • Is The Approach Active? Flying Garmin Instrument Approaches Seminar

    Hank Gibson from Texas Top Aviation will be presenting a seminar on flying Garmin instrument approaches with the different Garmin GPS units.  Whether you have a Garmin 530/430 unit, a Garmin GTN 750/650 unit, or a Garmin G1000, all will be discussed.  You’ll walk away with some tips and tricks, plus a better understanding of your Garmin unit.

    WINGs credit will be given for attending.  The seminar is hosted by Redbird Skyport at the San Marcos Airport (KHYI) in Redbird’s large conference room.  The seminar will begin at 10am on Saturday, June 30th, 2018.

    It’s always quicker to fly than drive and Redbird has plenty of ramp space to accommodate seminar attendees.

    Registration is required.  Please visit the registration page on FAASafety.gov.  Space is limited to 20 individuals, so please make sure you register if you want to attend.

    Hank Gibson from Texas Top Aviation will be presenting a seminar on flying Garmin instrument approaches with the different Garmin GPS units.  Whether you have a Garmin 530/430 unit, a Garmin GTN 750/650 unit, or a Garmin G1000, all will be discussed.  You’ll walk away with some tips and tricks, plus a better understanding of…

One Comment

  1. Pingback: Contact Approaches

Leave a Reply

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