King Schools Updates Check Ride Guidance

FltPlan Go

ByHank Gibson August 10, 2016August 27, 2016

I am an iPad user, but I have an Android phone.  I had been using a junky aviation weather app that just gave meters and TAFs, but seemed to have been programmed in a foreign language (un-decoded TAFs notwithstanding).  I wanted something more robust, but didn’t see the need to pay for a Garmin Pilot subscription since Foreflight on my iPad was my main EFB (Electronic Flight Bag) I use in the airplane.

When I upgraded my phone, I decided I had to find something better.  I have a WIFI only iPad, so I utilize my phone to take quick glances at weather reports or when I want to see the radar without having to tether my iPad to my phone.  The app I had wasn’t cutting it.

That’s when I found FltPlan Go.  We are all familiar with FltPlan.com.  It’s what a lot of corporate pilots use to file flight plans.  I’ve used it some, but there is a large amount of data it needs to set up an airplane. Since I already have all the airplanes I need in Foreflight, I don’t use it that much since I didn’t want to do the setup.  It is rather handy as it spits out flight logs and has a lot of pre-loaded performance numbers for different makes and models.

FltPlan Go is FltPlan.com‘s app.  It is very user friendly, easy to use, and, most importantly, free!  You can get METARs, TAFs, NOTAMs, Airport Diagrams, approach plates, full weather reports for airports including radar, maps, and a whole lot more.  As far as I can tell, it is a full fledged EFB.  I haven’t really scratched the surface on all the features in using mine, but it is quite robust from the little bit of poking around I’ve done.

I’m still a Foreflight guy, but if you want something else or you have an Android phone and don’t want to pay for Garmin Pilot or WingXPro, check out FltPlan Go.  It’s a winner.

3 Tips to Better Landings

ByHank Gibson December 21, 2017December 21, 2017

In my 3,000+ hours of flight training, I have developed some tips and tricks to help people fly better.  With teaching landings, I have 3 specific tips that will make smoother landings every time, guaranteed.

A Good Pattern

A wise flight instructor whom I would love to give credit to (but don’t know who it is!) once said that a good landing starts off with a good traffic pattern.  So true!  A good landing all begins with the setup.  This is true for a VFR rectangular traffic pattern or an IFR instrument approach.  Flying the proper speeds and being at the proper AGL altitudes helps immensely in making a good landing. Being at 600 feet AGL on a 1/2 mile final (or the alternative of 60 feet off the ground on a mile final!) makes it hard to make a good landing.

Proper Use & Understanding of Pitch and Power

Once flaps are used in the pattern, the plane is now on the back side of the power curve (or in the region of reverse command).  Power is now being used to control the plane’s rate of descent while pitch is being used to control airspeed.  The key is, both pitch and power work together, so if the pilot changes the power, he’ll also need to change the pitch and vice versa.

The common mistake I see here is when the airplane gets low on final, the pilot tends to (quite naturally) pitch up.  All this does is bleed off airspeed and cause the airplane to sink faster.  The proper input would be to add power, then adjust the pitch for airspeed.

Look Down the Runway

Now that we have gotten to the point of the round-out and touchdown, it’s the most important part.  The best thing the pilot can do to make the best landing possible, is to look at the trees at the end of the runway.  When I worked with college students, I told them to find the owl in the trees at the end of the runway.

The tendency is to stare at the pavement (or concrete) the whole way down to the landing.  When a pilot’s eyes are fixated on the ground, this destroys his depth perception and causes a level off too low to the runway, resulting in a 3 point landing and/or a bounce.

By looking at the trees at the end of the runway, this gives the pilot much better depth perception and allows him to properly judge where to level off the airplane.

The question now is when should the pilot start looking at the trees?  My recommendation is crossing the threshold of the runway.  For some, it works better to start looking at the trees when turning final.  Others, right before the level off.  Regardless, find that owl!

Oh, Deer (Part 1)

ByAndrew Robinson March 7, 2017April 5, 2017

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!

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.

Cirrus CAPS Pull in Arkansas

ByHank Gibson December 9, 2015December 21, 2015

Cirrus CAPS pull #55 took place at the beginning of November over Fayatteville, AR.  From initial reports, it appears a clamp broke on the oil cooler, causing a loss of oil pressure.  It does not appear that the engine immediately quit, but an annunciator alerted the pilot that the engine was losing oil pressure.  At this point, it appears the pilot elected to do an emergency descent to an airport below him, but ended up not timing it right, missing the airport and pulling the parachute.

As an experienced Cirrus flight instructor, there appears to be some suspect decision making in handling this operation.  I teach in a Cirrus that if an oil light comes on, given that a pilot has some altitude to work with, it is a better option to physically shut the engine down, leaving control of the situation in the pilot’s hands.  This way, the pilot knows when the engine is stopping and is prepared for it, instead of the engine acting erratically and causing problems on the descent.

After checking the engine gauges and shutting the engine down, a pilot should establish best glide first, not nose down and descend at a high rate trying to make an airport.  Best glide gives the pilot many more options and a lot more altitude to work with, further allowing him/her to plan how to make an airport directly underneath the airplane.

To pontificate, it seems that if the pilot had adjusted the plane to best glide, instead of performing an emergency descent, there is the possibility that Drake Field would have been reachable, the chute would not have been needed, and the driver of the truck would not have had to visit the hospital.  Hindsight is 20-20, but this may be an overall training and decision making issue that may need further emphasis.

The initial NTSB report as well as a link to the CBS story is below.

http://www.cbsnews.com/live/video/pilot-forced-to-deploy-emergency-parachute-in-arkansas/

NTSB Identification: CEN16LA026
14 CFR Part 91: General Aviation
Accident occurred Tuesday, November 03, 2015 in Fayetteville, AR
Aircraft: CIRRUS DESIGN CORP SR22T, registration: N857SW
Injuries: 3 Minor, 1 Uninjured.
This is preliminary information, subject to change, and may contain errors. Any errors in this report will be corrected when the final report has been completed. NTSB investigators may not have traveled in support of this investigation and used data provided by various sources to prepare this aircraft accident report.
On November 3, 2015, at 0950 central standard time, a Cirrus SR22T airplane, N857SW, descended under the canopy of the cirrus airframe parachute system (CAPS) and landed on a road in Fayetteville, Arkansas. The pilot, pilot rated passenger and one person on the ground received minor injuries. One passenger in the back right seat was uninjured. The airplane was substantially damaged. The airplane was registered to WG Aviation LLC, Rogers, Arkansas, and operated by a private individual under the provisions of 14 Code of Federal Regulations Part 91 as a personal flight. Visual meteorological conditions prevailed at the time of the accident and an instrument flight rules (IFR) flight plan was filed. The flight departed from the Bentonville Municipal Airport (VBT), Bentonville, Arkansas, at 0934 and was en route to the Waco Regional Airport (ACT), Waco, Texas.

According to the pilot, after departure from ACT he leveled off around 10,000 ft mean sea level (MSL) and was in “VFR on top” conditions. The pilot noticed that the crew alerting system (CAS) flashed a yellow caution light for oil pressure; the engine was still producing power. The pilot notified air traffic control (ATC) of the issue and received vectors to the nearest airport, Drake Field Airport (FYV), Fayetteville, Arkansas. The pilot descended and maneuvered toward FYV as the CAS indicated a red warning light for oil pressure, which had dropped below 10 psi. The engine was producing inconsistent power as the airplane descended to 3,300 ft and FYV was still not in sight due to cloud coverage. The pilot was unable to maintain altitude and the airplane’s stall warning horned sounded. The pilot deployed the Cirrus airframe parachute system (CAPS) and descended to the ground. During the landing the airplane collided with a truck and then came to rest on a four lane road.

At 0953, the weather observation at FYV reported wind from 190 at 9 knots, gusting to 17 knots, 10 miles visibility, clear sky, temperature 61° F, dew point 57° F, and altimeter setting 30.11 inches of mercury.

An initial postaccident examination was conducted on November 4, 2015, in Fayetteville. Engine oil was observed on the underside of the fuselage. The oil cooler cross fitting was broken and oil was observed in the engine compartment.

The airplane’s recoverable data module and three data cards were removed and sent to the NTSB Vehicle Recorders Laboratory for download.

The airplane has been retained for further examination.

AOPA’s Emergency In Person Seminar

ByHank Gibson December 18, 2015

Courtesy AOPA.org

We spend time training for them, but real-world emergencies are rare enough that it’s easy to get complacent. They don’t always happen to “other pilots,” though, and preparation can make a big difference when things don’t go as planned:
• What if you lose 500 rpm during takeoff, but the engine is running smoothly?
• What if the ammeter drops to zero during a flight in IMC?
• What if your left aileron develops a strong vibration in flight?
Our new seminar is full of expert tips on handling those “up here, but wishing you were down there” scenarios. We focus on how to keep abnormal situations from becoming full-blown emergencies, offer advice on keeping critical problems under control, and give our best advice on off-airport landings.

Find an AOPA Emergency Seminar near you!

• Monday January 11, 2016-The Woodlands Waterway, 7pm-9pm
  • 1601 Lake Robbins Drive, The Woodlands, TX 77380
• Tuesday January 12, 2016-Wyndham Houston West, 7pm-9pm
  • 14703 Park Row Blvd., Houston, TX 77079
• Wednesday January 13, 2016, Holiday Inn San Antonio Airport, 7pm-9pm
  • 77 NE Loop 410, San Antonio, TX 78216
• Thursday January 14, 2016, Omni Austin Hotel at Southwark, 7pm-9pm
  • 4140 Governor’s Row, Austin, TX 78744