Brazilian manufacturer Embraer recently received FAA certification for it’s “mid-light” Legacy 450. Capable of Mach .83 and a 2,500 mile range, this is one sweet airplane. Embraer designers gave passengers headroom as the cabin stretches up to 6 feet in height down the center. Complete with fly by wire controls and a full glass cockpit configuration, Embraer did a wonderful job with this airplane. The club seats even fold down to a bed!
The airplane’s list price is $16.5 million. To learn more about the Legacy 450, visit Embraer’s website.
When the Epic E1000 was finally certified in the spring of 2020, there was much celebrating across the aviation world. Epic Aircraft expended a lot of time and energy getting the E1000 certified and into production (more information on that journey here and in Flying Magazine here).
The airplane is amazing. In the single engine, 6 seat turboprop market, it easily blows away the competition. With it’s 1,200 SHP PT6-67A, it has double the horsepower of the M600 (600 SHP), and 350 more horsepower than the TBM 940 (850 SHP). It’s 60 KTAS faster than the M600 and, even though the TBM can keep up (both airplanes have equal top cruise speeds of 330 KTAS), the Epic E1000 can carry a payload of 1,024 pounds with full fuel, while the 940 can only carry 584 pounds with full fuel. The TBM carries about 15 minutes more of fuel, but to me, that’s pretty negligible.
Did I mention climb rates? The E1000 climbs at an average of 1500 FPM at Vy (it’s capable of 4,000 FPM), making it to 25,000 feet in 10 minutes. The TBM climbs at 1000 FPM, taking 13 minutes to climb to the same altitude, while the M600 settles in at about 800 FPM, reaching FL250 in 21 minutes.
If you expand the comparison to include the Pilatus PC-12, the two airplanes have 1,200 SHP, but the Epic is 50 KTAS faster and they both have about the same weight carrying ability.
In the most important arena, price, the E1000 is around a million dollars cheaper than the TBM 940.
The one drawback to the Epic E1000 that immediately was noticeable was the autopilot. Epic originally installed the STEC 2100 autopilot to pair with the G1000 (and later the G1000 NXi). Epic decided to stick with the STEC 2100 through certification for the plane since that autopilot was on all of the E1000s paperwork going through all the levels of FAA approval. To change to the GFC 700 during the certification process would have been a massive undertaking that probably would have delayed certification.
The STEC 2100 is a good autopilot, but, as any G1000 pilot can tell you, the lack of integration between any STEC autopilot and Garmin panel leaves some to be desired. Not all the bugs talk, which often requires dual data entry, which can lead to forgetting to do both the bug and the autopilot when things get busy. Hello, altitude deviation.
The goal for Epic was never to leave the STEC autopilot in the airplane. The first E1000s were rolled off the line with the STEC, but Epic didn’t take long to change the autopilot to the much more integrated Garmin GFC 700. That took place this winter (2020), and the E1000 received it’s first upgrade, with Epic dubbing the airplane the Epic E1000 GX.
I expect the innovators in Bend, OR, where Epic is based and where tons of innovation in aviation happens (Lancair/Columbia started in Bend while RDD is based there as well), to quickly come out with more avionics upgrades for the airplane. I wouldn’t be surprised to see a G3000 version at some point, complete with auto throttles and the new Garmin Autoland. Epic would be smart to follow in the steps of Daher and offer two models, one with the G1000 and one with the G3000 (the TBM 910 has the G1000 NXi while the TBM 940 has the G3000).
I have yet to fly in an Epic E1000, but I would certainly jump at the chance to do so. Someone asked me yesterday what airplane I would buy if I had a blank check. With the GFC 700 now in the Epic, it would absolutely be the E1000 GX.
There was a bill introduced in Congress recently to take control of Air Traffic Control away from the FAA and give it to a private, for profit, corporation. The initial reaction of pilots is “Ahhh! User fees!” which we are all adamantly opposed to. There are a myriad of reasons why this is a bad idea (the “Flying” article makes a comparison to giving NASA to Richard Branson and Jeff Bezos) and we as pilots should be against it.
Recently, I was training a customer who had a brand new instrument panel installed in his TBM 700. The avionics shop that did the work (Abilene Aero, who I highly recommend for any panel installs, located at KABI) told us when we picked the plane up that the new Garmin GTN 750Xi had the most recent software update, which included the Garmin Smart Glide.
I had never used the Garmin Smart Glide before, so I was eager to check it out during our training. When we got to engine failures, we pushed the Emergency button on the Home page of the GTN 750Xi, and then the magic happened.
The plane was also equipped with a Garmin G600TXi PFD and the Garmin GFC 600 Autopilot. In order for Smart Glide to work, there has to be either a GTN 750Xi or GTN 650Xi installed, along with a G500TXi or G600TXi and a Garmin Autopilot. Garmin is working on getting the legacy G500 as well as the GI 275 and G5 to work with the above GPS units for Smart Glide as well.
Here’s what happens. The plane loses it’s engine. The pilot’s workload and stress level suddenly goes way up. Trim the airplane for best glide, find the nearest airport, attempt restart. Do it quickly so you have time to focus on the glide. Oh yeah, squawk 7700 and declare your emergency. All the while plummeting toward the ground in a somewhat controlled crash. Yikes.
Garmin Smart Glide takes over the flying part, allowing the pilot to handle the restart, while making it much easier to squawk, talk and plan the engine out landing. On the home page of the GTN 750Xi/650Xi, the pilot simply taps the Emergency icon on the bottom of the screen. The Autopilot comes on and goes into IAS mode and maintains best glide while descending. The GPS immediately analyzes the Glide Advisor, and turns to the nearest airport in the glide ring (if there is no airport within gliding distance, the GTN 750Xi advises the pilot). Then, the Autopilot flies directly to the Nearest airport, allowing the pilot the ability to take attempt a restart.
Once it is determined that the engine won’t start, the Garmin Smart Glide has excellent situation awareness tools. On all screens, the pilot is constantly being advised of how high AGL the plane is currently, while advising also of how high AGL the plane will be over the airport that the glide is set up for. There is also a short cut on the screen to tap to squawk 7700 as well as runway length information at the airport.
The Garmin Smart Glide Button wasn’t installed yet in the TBM, but that will make things even easier when it is (it will be certified in January). This is amazing technology that all Garmin GTN 750Xi pilots should have their software updated to. Remember, you have to have a Garmin Autopilot and a Garmin PFD for it all to work.
Type Clubs Lead By Example with Standard Operating Practices
This article appeared in the May 2019 edition of EAA’s Sport Aviation Magazine. It is used with permission. For other articles by Charlie Precourt, please visit EAA.org and join for a full subscription.
Imagine a year when there are no fatal accidents in general aviation. Does that seem impossible? The airlines achieved that many years ago, and so can we if we focus on the right things in our safety pro- grams. In fact, the overall trend in GA accident rates over the last few years is very encouraging. AOPA’s Air Safety Institute published its annual GA Accident Scorecard recently (see www.EAA.org/ extras), revealing fatal accidents from 2008 to 2017 are down more than 30 percent. Nevertheless, there were 185 fatal accidents in 2017, so we still have a long way to go. But, there are many developments in safety programs across GA that can keep the trend going.
One such development that I’ve advocated through a couple of type clubs is establishing standard operating practices (SOP). When I flew for both the U.S. Air Force and NASA, we had what we called standard operating procedures. They were the law for our flying. That is, we had to follow them procedurally because the folks that paid our salaries said so. The objective was to ensure we all used the same playbook, minimizing the risk that one of us might develop a bad in-flight habit that increased risk to the organization.
One way to think about SOPs is to recognize the difference between procedure and technique. For example, you have to follow the manufacturer’s pilot’s operating handbook (procedure)where it says to lower the landing gear before landing. If you don’t, you are in for a bad day. However, it does not tell you exactly when to lower the gear; that’s left to technique.
In the middle, between procedure and technique, is a best practice. In this example, lowering the gear just before the final approach fix is a “standard practice.” It is the generally accepted “best” place to lower the gear. In GA, however, aircraft owners don’t generally answer to a boss, so I prefer the term practices instead of procedures.
However, whether or not someone is paying us to fly, following best practices just makes sense. If you have a good set of practices, they enable you to do things the same way every time, leaving lots of brain cells to manage the unusual, the things that might go wrong. The safest approach to accomplishing a flight task is one that leverages consistency. On the other hand, if you are inconsistent, doing flight tasks differently each time, you’ll always be struggling to keep up. So, in my involvement with the safety committees for both the Malibu Mirage Owners and Pilots Association and the Citation Jet Pilots Association, there has been broad acceptance of recently developed standard operating practices.
The good news in this development is that a culture of safety is growing broadly across most sectors of GA through these type club initiatives. Perhaps more importantly, there is much to learn from each other about the effectiveness of these various initiatives. EAA has seen a four-year drop of 47 percent in fatal accidents among homebuilts! So, there must be something right going on there — a major focus on appropriate transition training before flying a new homebuilt (as a standard operating practice) is paying off.
So, what is covered in the SOPs these type clubs have developed? The following outlines the kinds of standard practices other type clubs have set up and represent SOPs you could establish for yourself regardless of the type of aircraft you fly. You just have to fill in the blanks for your particular type and commit to sticking to them in your flying. These are notional and are practices (not mandatory procedures). They don’t tell you how to fly your aircraft; they give you things to think about when you do. If you take a bit of time to set your own SOPs and then stick with them, you’ll be a far safer pilot. Here are some ideas:
Duty Day
Set the maximum number of hours of flight time during a calendar day and rest hours off between flying days. One example is a maximum of eight hours in the air and a minimum of 10 hours off until flying again.
Cargo
Establish best practices for what you will carry as cargo. One example is no lithium batteries in the baggage compartment.
Flight Planning and Preparation
What are your limitations for the types of flight you’ll take on? Consider SOPs such as designating a suitable alternate airport for all flights. Another might be for first flights after significant maintenance, such as no flight at night or in IMC until a day-VMC functional check flight has been done.
Runway Field Length Guidelines
Establish an appropriate minimum field length for your aircraft and commit to not going into shorter fields. Consider sea level operations and high-altitude airports as well.
Surface Operations
What should be your maximum wind conditions for taxi, takeoff, or landing? Maximum acceptable crosswinds on landing? Set them in your SOP and stick to them.
En Route
Consider establishing practices like no non-operationally necessary conversation below 10,000 feet MSL, during any segment of an approach procedure, or during the last 1,000 feet before leveloff during climb or descent. Also consider declaring “minimum fuel” when the fuel state becomes less than fuel to destination plus 45 minutes at current burn, even if flying day VFR.
Approach and Landing
Consider establishing personal minimums in your SOPs for things like visual approaches. Perhaps use a 1,500-foot ceiling and 3 miles’ visibility for day and 5 miles for night, even though these exceed the FAA’s requirements.
Pilot Limitations, Training, & Currency
FAR Part 91 rules allow us to fly with pretty marginal levels of currency. Consider setting your own SOP to something more appropriate for the kind of aircraft you fly and the kind of flying you do in it. For example, consider these ideas as SOPs:
If you have less than 100 hours of time-in-type or have not flown at least 15 hours as pilot in command in the last 90 days, use a minimum planned fuel reserve of one hour.
Also, if flying IFR in this situation, use a minimum visibility for takeoff of 1 mile.
On instrument approaches, increase the published minimums by one- half mile visibility and add 200 feet to the decision altitude or minimum descent altitude.
Perform landings at a weight that allows a full stop in 60 percent of available runway length.
Consider an SOP that establishes you will fly with a CFI on a refresher flight before flying as pilot in command if you have not logged at least an hour of flight time and one takeoff and landing in an aircraft of the same type within the preceding 45 days.
Maneuver Standards
Wherever there are “techniques” associated with things like takeoffs and climbs, cruise, use of autopilot, power settings, and approaches and landings, you can write down your preferred technique as your own SOP. Describe each maneuver in enough detail (speeds, altitudes, power settings, configurations, etc.) to define a routine you will use each time. This ensures you fly consistently each flight and leverage the power of the standard operating practice, that is, to give you the bandwidth you need should you encounter an unexpected event or an emergency.
SOPs are among the exciting concepts underway to make safety programs work for us. Hats off to type clubs like MMOPA and CJP and many others that are taking the initiative. But even if you’re not in this kind of group, you can still set up your own SOPs. Let’s all look forward to our first year in GA without a fatal accident — and let’s make it soon! Fly safe!
Charlie Precourt is a former NASA chief astronaut, space shuttle commander, and Air Force test pilot. He built a VariEze, owns a Piper JetPROP, and is a member of the EAA board of directors.
In the Pre-Takeoff Checklist for any Cirrus aircraft, it calls for pilots to perform a Cirrus Autopilot Check. It is prudent to check the autopilot before your flight to ensure that all aspects of the autopilot are working properly. The only problem is, the checklist doesn’t spell out how to perform the Cirrus Autopilot Check. You would have to go to the POH for the airplane, which is usually in the back seat or a bag somewhere and therefore hard to get to, in order to find the procedure.
The procedure for checking the autopilot is slightly different depending on what autopilot is in your airplane. The procedures for all three are below.
S-TEC 55x
Sync the heading bug to your current heading
Activate heading mode on the autopilot
Twist the heading bug left and right to ensure the ailerons move left and right
Sync the heading bug to your current heading
Activate vertical speed mode on the autopilot
Move the vertical speed bug (or the vertical speed on the altitude pre-selector if you have a steam gauge Cirrus) up and down to ensure the elevator moves accordingly
Ensure you can overpower the autopilot
Press the autopilot disconnect switch to ensure the autopilot shuts off
Avidyne DFC 90
Press the AP button to activate the autopilot
Ensure AP, ROLL, and PITCH Annunciations are depicted in green on the top of the PFD
Set the heading bug 90 degrees from the current heading
Press the HDG button on the autopilot
Ensure the ailerons are moving in the proper direction and HDG is annunciated on the top of the PFD
Ensure you can overpower the autopilot
Press the autopilot disconnect switch on the stick and ensure the autopilot has disconnected
Garmin GFC 700
Press the AP button to activate the autopilot
Ensure you can overpower the autopilot
Press the autopilot disconnect switch on the stick to ensure the autopilot has disconnected
It’s winter time, which means it’s time to use those Piper PA46 de-ice boots a little more often. Most of us know the winter flying rules, don’t stay in ice, get rid of frost, etc. However, most of us aren’t as familiar with how to maintain those Piper PA46 de-ice boots. The do need some TLC every couple of months to keep them in tip top shape.
Below is the recommendation from Goodrich (the maker of the boots) on what to use to clean and polish the boots and how often to do it.
Steps 1-3 below are your twice a year items to make your Piper PA46 de-ice boots last through the lifetime of the aircraft.
Step 1-ShineMaster Prep
ShineMaster Prep strips all the dirt, grime, grease, oil, silicone products and old ShineMaster on the Piper PA46 de-ice boots to prep them for Step 2.
AgeMaster is your second step the in the Piper PA46 de-ice boot preservation and protectant process. AgeMaster is a rubber preservative that protects against weathering, ozone, and ultraviolet rays.
Make the first application when your de-ice boots are 6 months old, then re-apply every 150 hours (or twice a year) after that.
Step 3 in the Piper PA46 de-ice boot care is ShineMaster. As the name implies, ShineMaster shine’s the boots up after getting rid of all the old gunk & grime with ShineMaster Prep and after AgeMaster is applied. 2-3 coats should be sufficient.
During icing season, Goodrich recommends ICEX II. ICEX II is an ice inhibitor that should be applied every 50 hours during ice season. This will help prevent ice from sticking to the Piper PA46 de-ice boots. ICEX II can be found here.
Finally, for general cleaning of the boots after each flight, utilize Goodrich Aerospace Cleaner to debug, then follow up with Goodrich Aerospace Protectant. Goodrich claims their Protectant will resist dust, soiling, and staining. There may be less bugs to clean each time!
With just a few hours a couple times a year spent working on the Piper PA46 de-ice boots, owners will never have to worry about the hefty price tag of boot replacement!