Ever wanted to be a Cirrus owner, but the economics of being a single owner just don’t make sense for you? If you’re in the San Marcos/New Braunfels/Austin area, you now have a chance to join a Cirrus SR20 partnership at the San Marcos Municipal airport, KHYI.
The Cirrus SR20 partnership group is looking for 2-4 more members to buy in to a 2006 or 2007 Cirrus SR20 GTS. The plane will be kept at KHYI and the group already has a hangar for it.
For those of you who frequent the Houston area, make sure to check your NOTAMs. The Houston Executive Airport (KTME) in Katy recently opened a control tower. The Houston Executive tower information won’t show up on the sectional chart till the new chart comes out in the spring. The only way to get the information about the tower and the airspace will be via NOTAMs or when the new Airport/Facilities Directory comes out on November 3rd. The tower opened October 1st.
According to AOPA, the airspace will remain Class G around the airport, even though there is a control tower in place. Since the Houston Executive tower is there, it will be mandatory to contact the tower when passing through the airspace. KTME’s airspace stretches up to 2,000 feet MSL and goes out to a 4 sm radius around the airport. It is a VFR Only tower, so the controllers do not have radar.
The tower is open from 6am-10pm, local time, 7 days a week.
L-3 has jumped into the ADS-B transponder game with their Lynx line of products. Aircraft owners have a myriad of options with the Lynx line, from simply becoming ADS-B compliant with the NGT-1000 ($2,100, with ADS-B out that works with the GTX 327 and GTX 330), or going all in with the NGT-9000 touch screen transponder complete with ADS-B In, a traffic screen and NEXRAD ($6,800).
The NGT 1000/2000/2500 line works with the existing transponder in the airplane (as long as it’s a Garmin GTX 327 or 330). The 2000 gives ADS-B In capability, allowing the pilot to access NEXRAD and traffic, plus has a Wifi source to broadcast all the information to an iPad. The 2500 includes all of that, plus gives the pilot MFD capability as well. An optional control panel is available if the airplane is not equipped with one of the aforementioned Garmin transponders.
The L-3 Lynx NGT-9000 is an actual transponder replacement. It is a touch screen device that has a multitude of ADS-B features that, quite frankly, are really cool on a transponder. The ADS-B traffic is displayed on the unit itself and can also be sent, via the optional Wifi connection, to an iPad on the WingXPro or SkyRadar apps. The optional L-3 NextGen Active Traffic can also be installed to receive traffic callouts (this does not include resolution advisories). Already have SkyWatch? The L-3 Lynx can use the equipment.
The L-3 Lynx NGT-9000 is also capable of displaying NEXRAD as well as METARs, TAFs, NOTAMs, and TFRs and a myriad of other weather products, all on it’s moving map. It seems that L-3 has taken the transponder and turned it into something awesome.
To read more about the L-3 Lynx line of transponders, you can visit their website.
We’ve all heard it said…”reduce the throttle by no more than 1-inch every minutes to ensure you don’t shock-cool your engine”. Does this advice apply to a PA46 engine? Can a PA46 engine (Lycoming 540 or Continental 520/550) really be shock-cooled? How should the engine temperature be managed?
Metals expand and contract with temperature, and the various metals in an air-cooled aviation engine expand and contract at a different rates. Shock-cooling supposedly occurs when the engine changes temperature quickly and the different metals in the engine cool (and therefore change shape) at different rates. When the change occurs dramatically supposed scoring, rubbing, and marking of the metal can occur, which can cause catastrophic results.
So, let’s back to the original question…can a PA46 engine suffer shock-cooling and should a pilot operate the engine so as to avoid shock cooling? Simply put, I’ve never seen nor heard of any piston PA46 engine suffer shock-cooling. In 5000+ hours flying the piston PA46 and 16 years of flying/managing/training in the Malibu/Mirage/Matrix, it simply has not happened to me nor anyone I know. Does it mean that it cannot happen or has never happened? No. But, it is certainly not a prolific threat to our fleet.
Should the owner/pilot operate the engine with a cautious eye cast toward the potential of shock cooling? Well, sort of…but, let’s flesh this out. My suggestion is that a pilot should operate the engine with conservatism in movement of temperature, but only because this is a good operating practice with any machine, and any flying machine is (by definition) not “overbuilt”. And, there are many ways to change the temperature of the engine…not just by reducing power. Here’s a partial list of ways to cool your PA46 engine:
Reduce power: Obvious…yes. When the engine produces less power, less heat is generated. Reducing power in a piston engine will almost always result in less temperature.
Lower the nose: By descending (and leaving power in a cruise setting) the airspeed will increase and cool the engine.
Enrichen the mixture: Fuel has a cooling effect on the engine, so the richer the mixture the cooler the engine.
Lower the landing gear: Yes…you read that right…engine cooling will occur when you lower the landing gear because more air will flow over the cylinders. Notice the landing gear doors on the PA46 have air louvers. Air flows into the engine nacelle on the front, passes down through the cylinders (along with the oil cooler, intercoolers, and other components) and then out the louvers of the closed gear doors. When the landing gear is lowered the “back door is opened” and a LOT more airflows over the cylinders.
My suggestion is that a pilot only perform ONE of these actions at a time when beginning a descent. This suggestion was presented to me by Chad Menne (Owner, Malibu Aerospace) some time ago and I’ve operated engines this way ever since. If you are at a higher altitude and simultaneously reduced the power, lowered the landing gear, started a big descent, and enrichened the mixture in one flail swoop, I think there’s a chance that your engine would suffer some negative effects that could be called “shock cooling”. So, when you do start a descent, pick one “cooling action” to accomplish at a time. I’m sure you’ll not hurt your engine.
Simply put, shock cooling is not a huge factor in the PA46 community, and a PA46 pilot does not need to be overly cautious. The “one inch per minute” rule may apply in some other airframes, but in the PA46 world it is not applicable.
Joe Casey’s aviation story began in 1990 with his first flight near Nacogdoches, TX in a Cessna 172. From lift-off, Joe knew he would have a lifetime passion flying just about anything that will leave the ground…He was completely hooked.
Along with being an FAA Designated Pilot Examiner (DPE), Joe is an ATP/CFI-AHMG and Commercial Rotorcraft/Glider Pilot in the civilian world and also a UH-60/AH-64 Pilot-in-Command/Instructor/Examiner Pilot in the US Army Reserves. His passion for the last 19 years, however, has been the PA-46 Malibu/Mirage/Matrix/Jetprop/Meridian. Has has amassed over 6,500 hours in various PA-46 airframes and believe it to be one of the finest flying machines available for the serious cross-country pilot with an eye for efficiency.
Now, Joe has flown more than 12,200 hours in just about every imaginable environment. Whether providing initial/recurrent training in the PA-46’s, TBM’s, instructing in NVG’s in a UH-60 Blackhawk, flying the King Air series of airplanes, giving tailwheel endorsements, or taking kids flying for the first time, he simply loves flying machines and the people who fly them.
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.
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.
Two pilots walk into an FBO. “Nice airplane,” Pilot 1 says to Pilot 2. “What kind of panel do you have in it?”
“I just went all glass,” Pilot 2 says. “Put in the Garmin G500 TXi, a GTN 750, and upgraded to the GFC 600 Autopilot. Even put in the Mid-Continent standby instruments. It’s a pretty sweet set up. What about you?”
“Wow, sounds like it!” Pilot 1 responds. “I went a different route. I liked all my old BendixKing instruments, so I stuck with the company. I put in a BendixKing AeroVue Touch panel, a BendixKing KSN 770 touch screen GPS, kept my KFC 225 autopilot, got the ADS-B out compliant BendixKing KT 74 transponder, and finished it off with a King AeroFlight KI 300 Digital Backup instrument.”
Wait, what? BendixKing?
Yes, my friends, BendixKing is still around.
We are all used to the latest and greatest Garmin products these days. Don’t get me wrong, Garmin and Aspen make great retro-fit products for your instrument panel, while Garmin and Avidyne are at the top of the touch-screen GPS market, but don’t forget about BendixKing. They are staying in the game too.
BendixKing announced in April the xVue Touch for experimental aircraft, with the STC for the AeroVue Touch for certified aircraft coming later this summer. The xVue and AeroVue touch are pretty nifty units, comparable in features to what Garmin is doing with the G500 TXi and G600 TXi. It will be difficult to claw back into a competitive market share with Garmin, but BendixKing might find a niche market of followers.
Let’s take a look at the unit.
BendixKing AeroVue Touch
Now, I have not used the BendixKing AeroVue Touch or the xVue Touch, only read about them. But, what I’ve read sounds pretty cool. The display has really good resolution (BendixKing brags it is the highest screen resolution available), synthetic vision that comes standard (Garmin & Aspen charge extra for synthetic vision), plus VFR Sectional Charts & IFR High and Low Enroute charts, making paper charts even more obsolete.
The display is 10.1 inches and can be easily swapped between a full screen instrument mode or a split screen setup as seen above. Apparently, BendixKing has 3-D moving maps available on the AeroVue Touch too, which is standard.
The one thing Garmin has on the BendixKing AeroVue Touch right now is engine information. The G500TXi has a full complement of engine gauges available; the AeroVue Touch doesn’t, yet. BendixKing says it’s in the works, as well as radio information and autopilot control. I’m assuming the future autopilot control software would mean you could remotely mount an autopilot controller and input all functions from the AeroVue Touch display. The nice thing about these future upgrades is all the software updates are free through BendixKing.
The sticker price for the forthcoming unit is going to be about $12,600. Garmin’s 10.5 inch G500 TXi is $16,000, while Aspen doesn’t offer anything quite that big.
BendixKing KSN 770
I’ve been keeping my eye on the BendixKing KSN 770 Touchscreen WAAS GPS for a few years now. It never really has caught on quite like the Garmin GTN 750 or the Avidyne IFD 540. BendixKing took the same route that Avidyne did in creating a hybrid touch GPS (or mini-MFD if you want to look at it that way) where a pilot can perform functions either using the touch screen or utilizing soft keys on the edges. I like the hybrid touch approach as I have been bounced around in turbulence while trying to tap something into a Garmin GTN 750 and it can prove difficult.
Similar to the AeroVue Touch, BendixKing utilized split screen technology in the KSN 770. It’s a full WAAS unit that is already certified. It’s sticker price is $14,200, compared to the Garmin GTN 750 at $17,200 and the Avidyne IFD 540 at $15,000.
Other BendixKing Gadgets
Here are some other BendixKing Gadgets both available now and in the works:
KFC 230 AeroCruz Touchscreen Digital Autopilot-2 or 3 axis options. Will be the only touchscreen digital autopilot available on the market. Also able to utilize the servos from older KFC autopilots. Should be available late fall or winter ’18.
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
The gear door and strut after the accident.
If you think about the fact that I hit the deer with the wheel, but it didn’t hit the gear door, it becomes apparent just how close the airplane was to clearing the animal completely.
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.
