Mission

  • Our mission is to promote and protect San Carlos Airport and its flight operations, and to enhance the safety and spirit of general aviation through participation in local community activities.

Live View of San Carlos Airport (SQL)

San Carlos METAR

  • KSQL 210150Z 26007KT 10SM BKN047 BKN070 18/13 A3001

    A METAR describes the current weather at an airport. Click here to learn how to read a METAR.


SQL Notams

  • Click here and enter KSQL in the Locations box to read the Notices to Airmen (Notams) about San Carlos Airport.

ASOS from Half Moon Bay Airport (HAF)

Photos at SQL


Chapter

Contact

  • Email: webmaster at sancarlosairport.org
  • Our mailing address:
    San Carlos Airport Association
    P.O. Box 1183
    San Carlos, CA 94070
 

Archive for the 'Aviation Safety Articles and Tips' Category

To the General Aviation Community,

Click here: MBNMS Pilot Outreach Letter_Jul2012 for a 1-page letter (PDF format) from the superintendent of the Monterey Bay National Marine Sanctuary that highlights some current and upcoming changes that the FAA is making to the Los Angeles and San Francisco sectional and terminal area charts. The charts will display new notices about flight operations in coastal areas that may be relevant to your activities.

If you wish to verify the authenticity of this email message, feel free to contact me using the information below.

Thank you.


Scott Kathey
Federal Regulatory Coordinator
Monterey Bay National Marine Sanctuary
National Oceanic & Atmospheric Administration
U.S. Department of Commerce
99 Pacific Street, Bldg 455A
Monterey, California 93940
Phone: 831-647-4251
Website: http://montereybay.noaa.gov/

posted by Administrator3 Jul 26, 2012  07:07 PM
read (0 comments)

by Ken Steiner

Ken Steiner

Editor’s Note: Ken Steiner is the Claims Manager and Asst. Vice-President for the San Francisco office of the United States Aircraft Insurance Group (USAIG), one of the world’s largest aviation insurance companies. He has been with USAIG for over 29 years investigating all manner of aviation accidents involving aircraft from Piper Cubs to Boeing 777’s. Ken is an active pilot holding ATP and CFI certificates with over 3800 flying hours. He flies a Turbo Skylane based at San Carlos, and yes, his flying record is free of any accidents, incidents and violations!

All summer long it seemed that no matter which direction I headed, there was a permanent headwind attached to the front of the plane. If this kept up I was going to trade my airspeed indicator in for a calendar. Finally, the winds agreed to partner up with me on a flight to Truckee giving me an extra 20 knots on the tail. A “smiley face” icon lit up on the GPS ground speed display.

As I entered the pattern for runway 28, that helpful southwesterly was starting to show another personality as it became a brisk low-level crosswind. While my focus was on contending with a crosswind landing, I was not particularly mindful of the “push” I was getting from the tailwind on base leg. Sure enough it blew me well to the right of the runway 28 centerline as I was rolling out on final.

This is a pivotal and sometimes fatal moment for pilots. I knew instantly what not to do. About 4 years earlier at this very runway I had investigated the crash of a corporate Learjet that overshot the extended runway centerline while turning final from a circling instrument approach. As in my situation, the crew found themselves off to the right side on the final approach. In an attempt to get lined up, the crew made a steeply banked turn to the left. Witnesses reported the bank to be well in excess of 45 degrees. The jet stalled in the turn and slammed into the ground killing both the pilot and co-pilot. Fortunately no one else was on board and no one on the ground was injured.

Typically a plane turning base to final is already low, slow, and close to the runway. If wind or bad planning causes you to overshoot the final approach turn, there is a natural urge to want to get realigned in a hurry often by cranking in excess aileron and rudder. The increased load factor in a steep bank significantly raises the stall speed. Further, a pilot may try to arrest the increased rate of descent in a steep turn by increasing pitch attitude. The increased angle of attack causes the already shrinking stall safety margins to further erode. All of this is leading to an accelerated stall that can leave one planted firmly short of the runway. Add poor rudder control and you may even be able to perform a spin on your way down.

Ideally, proper pattern planning is the first step in avoiding this scenario. If you do find yourself off the final centerline, limit bank angles to 30 degrees and don’t use excess rudder to get realigned. Use proper elevator inputs (pitch attitude) to maintain airspeed and use power to control the rate of descent. If you can’t get back to the centerline in an orderly and stabilized manner then prepare to go-around. Don’t let the turn to final become your final turn.

posted by Administrator3 Jan 27, 2010  01:01 PM
read (0 comments)

Someone once said, “If you don’t think too good, then don’t think too much.” I can recall a few aircraft accidents that really didn’t take much thinking on anyone’s part to investigate. Sure, as an aircraft accident investigator there are certain rules about maintaining one’s objectivity, gathering factual information, and never jumping to a conclusion, but when the smoke clears sometimes you just scratch your head and say “what was this pilot thinking?” These are the kind of accidents that really aren’t accidents. All the circumstances were deliberately put in place to produce the results. It would have been an accident if the crash hadn’t resulted.

Several years ago the pilot of a twin-engine corporate jet was preparing for a flight and was unable to get one of the engines started due to a failed starter. Rather than ground the aircraft and have repairs done locally our hero, who was anxious to depart, reasoned that he could do an “air-start” once airborne to get the second engine turning. All he would have to do is take off on one-engine. The results were predictable. During the attempted single engine take-off he learned that maybe this wasn’t such a good idea. He rapidly lost control of the jet and crashed before becoming airborne. He survived, but the plane and his career were a total loss.

One of my memorable accident investigations involved an instructor and his commercial student who attempted a landing at a snow-covered mountain airport in the Sierras. This particular airport was unoccupied throughout the year so there was no information available on the runway conditions. From the air, the pilots could see wheel tracks in the snow, which obviously meant that other aircraft had landed there. What they did not know was that the tracks on the runway below were made by snowmobiles.

Upon touch down the plane came to a rather abrupt stop as it plowed through the deeper than expected snow, but was otherwise undamaged. Since they could not taxi back, the instructor and the student decided to push the plane back to beginning of the runway in order to take-off. During the first take-off attempt, the plane bogged down in the snow again this time putting a mild bend in the prop blade. Not quite ready to call it a day, they pushed the plane back and tried to take off again. Since this particular plane was not snowplow equipped and already flight impaired from the bent prop, the aircraft’s nose dug in deep enough on the take-off roll to flip the plane over on its back.

While the above stories do have an amusing quality to them, the sad part is that there are many more where these came from and some of the results are far from amusing. As pilots, we accept certain inherent risks as part of our flying and we manage those risks to make our aviating as safe as possible. When a pilot deliberately creates an unnecessary risk and steps outside the boundaries of common sense and reasonable aeronautical decision-making, he is no longer a pilot, but rather a spectator on his way to the scene of an accident.

Editor’s Note: Ken Steiner is the Claims Manager and Asst. Vice-President for the San Francisco office of the United States Aircraft Insurance Group(USAIG), one of the world’s largest aviation insurance companies. He has been with USAIG for over 28 years investigating all manner of aviationaccidents involving aircraft from Cessna 150’s to Boeing 777’s. Ken is an active pilot holding ATP and CFI certificates with over 3700 flying hours. He flies a Turbo Skylane based at San Carlos, and yes, his flying record is free of any accidents, incidents and violations!

posted by Administrator3 Jan 22, 2009  09:01 PM
read (0 comments)

It was 109 degrees on the ramp at Sacramento International. My preflight was a half-hearted walk around the plane and an oil check. I must confess my mind was more on getting the prop started to get some air circulation than it was in a detailed aircraft inspection.

At about the time I was lifting off I noticed that the air speed indicator was reading “zero”. Some errant bug probably took up residence in the pitot tube while the plane was parked overnight. I mentally kicked myself not only for my hurried pre-flight, but also for not using a pitot tube cover during my overnight stay.

The loss of the airspeed indicator did not concern me for this flight, but it did remind of an accident I had investigated a few years back. A high-time pilot in his Mooney was taking off from the Santa Monica Airport. Well into the take off roll he noticed that his air speed indicator was reading “zero”. Although everything else was operating normally, he got so concerned with this faulty reading that he decided to abort the take-off with insufficient pavement remaining. He sailed off the end of the runway causing the landing gear to collapse and did considerable damage to the plane. There was no reason to abandon the takeoff as the laws of aerodynamics and basic pilot skill will allow an airplane to fly just fine without an air speed indicator.

A more insidious aircraft accident occurred many years ago and involved a passenger jet airliner. The flight crew noticed that the airspeed was increasing during the climb-out. They were so concerned about exceeding the mach number speed limitations that they kept increasing pitch attitude and pulled back on the power in effort to reduce the ever increasing indicated speed. The aircraft eventually ran out of speed and stalled. The crash killed all on board. What the crew was unable to figure out was that the pitot tube had become blocked. The air trapped in the line expanded as altitude increased sending an increasingly higher, but false, indicated airspeed reading to the crew.

The point is, if you need to only remember one thing, remember to “fly the plane”. There is no reason to wreck a perfectly good aircraft by becoming fixated on one problem to the exclusion of fundamental airmanship. A clogged pitot tube is not an uncommon occurrence. I’ve had 3 of them in 37 years of flying. In warm weather months insects are usually the culprits. In the winter, ice can have the same effect. Without a speed reference, you may inadvertently exceed an aircraft’s structural limitations or sail off the end of the runway during landing if going too fast. Go too slow and you may fall out of the sky.

In VFR conditions, basic attitude flying and power management will serve you well. To train for this sort of an event, find a safe altitude somewhere and cover your airspeed indicator. Approximate an approach to landing with full flaps and approach power. Establish a pitch attitude that you are accustomed to seeing during an approach with a normal rate of descent on your VSI. Uncover the airspeed indicator and see the results. Now do the same in takeoff and cruise configurations to see how close you come to the target airspeed. Practice till you are consistent.

In IFR conditions it is more a matter of flying by the numbers and reverting to partial panel technique, but the best plan here is judicious use of pitot heat to avoid the problem in the first place. That includes function testing the pitot heat system during pre-flight before launching into the icy cotton.

If you have a GPS, you automatically have a back-up air speed indicator. Convert your normal indicated approach speed to a true airspeed and deduct the headwind. For example, let’s say your normal IAS approach speed is 70 knots, and you have calculated this to be a TAS of 75 knots. As the headwind is 10 knots, your approach speed on the GPS should be about 65 kts. Your GPS may also have a TAS display function that you can monitor. It’s just a reference so don’t forgo your attitude flying skills.

A functioning airspeed indicator is a nice instrument to have onboard, but if it quits, the plane will chug along just fine without it. All the pilot has to do is fly the plane. Hopefully the only time that your airspeed is reading zero is when you are on the ground.

Editor’s Note: Ken Steiner is the Claims Manager and Asst. Vice-President for the San Francisco office of the United States Aircraft Insurance Group (USAIG), one of the world’s largest aviation insurance companies. He has been with USAIG for over 27 years investigating all manner of aviation accidents involving aircraft from Cessna 150’s to Boeing 747’s. Ken is an active pilot holding ATP and CFI certificates with over 3500 flying hours. He flies a Turbo Skylane based at San Carlos, and yes, his flying record is free of any accidents, incidents and violations!

posted by Administrator3 Jun 28, 2008  07:06 PM
read (0 comments)

by D. Gordon Matthews, ATP, CFI-I

Click for full size image One day a few years ago, I was on an instructional IFR flight from KSJC to KSCK with a very perceptive and talented instrument student. The flight conditions were IMC with KSCK ATIS reporting a ceiling of 600 feet, sky obscured and one-mile visibility. The tops were 2500 feet, a typical central California Winter morning. As we approached Stockton, the all familiar words came crackling over the radio “Cessna 9027Hotel, turn left to 320, maintain 2000 until established, cleared for the Stockton ILS runway 29R approach, circle to runway 11L”. My student immediately and mechanically pressed the PTT switch and blurted out “Roger, turn left to 320, maintain 2000 until established, cleared for the approach, 27 Hotel”.

She then looked down at the approach plate and after, what seemed like to her, an eternity because we were in actual IFR conditions, she asked me “How do I fly this approach? The approach plate is showing a Minimum Descent Altitude not a Decision Altitude”.

I was stopped in my tracks and dumbfounded. I suddenly realized that, I didn’t know the answer to her question, I was the CFI and we were in actual IFR conditions (all simultaneously). I had flown this approach literally hundreds of times before and for some reason, unknown to me, I had never noticed that with, what turns out to be, all published “ILS, circle to land” approaches you are not given a Decision Altitude (Height) but rather a Minimum Descent Altitude. I said, very calmly, to instill confidence, as any good CFI would, “Since we aren’t going to land, let’s fly it like an ILS, straight in approach, down to the MDA and we’ll talk about it later”.

Because of a tight schedule for both of us, later didn’t come for several days, which gave me some time to research an answer. The answer, that I sought, was not easily obtained and I’m not sure I’ve got it right yet. Let’s review a bit and you will understand my dilemma.

An ILS is a precision approach with a glide slope, localizer, final approach fix (which is the glide slope intercept point, at or below the minimum glide slope intercept altitude), decision altitude (height) and a missed approach point. A non-precision approach, on the other hand, has a final approach fix, a minimum descent altitude and a missed approach point.

The glide slope and a published decision altitude (height) are only found on precision approaches, while minimum descent altitudes are only found on non-precision approaches.

According to Jeppesen’s chart glossary the DA(H) is the altitude or height on a precision approach where a decision must be made. It, further, defines the minimum descent altitude as the lowest altitude authorized on a standard instrument approach procedure, where no electronic glide slope is provided. Sounds like to me, if you’re given a decision altitude (height) you’re doing a precision approach and if you’re given a minimum descent altitude you’re doing a non-precision approach. However, let’s look a little further.

On a Jeppesen ILS approach chart, in the profile view, the precision approach flight path is traced with a solid black line, while the non-precision approach flight path (the Localizer – Glide Slope out) is traced using a dotted black line. These flight paths are the same until glide slope intercept. The precision approach then starts down along the glide slope to the DA(H) followed by the missed approach point. The non-precision approach, however, continues at the published altitude until reaching the non-precision final approach fix symbolized by the Maltese cross where it starts down to the MDA and eventually the missed approach point.

If we are given a minimum descent altitude, then we are executing a non-precision approach. We, therefore, are obligated to maintain our published or assigned altitude until we reach the non-precision final approach fix. This is, of course, well past the glide slope intercept point. We now are permitted to descend to the MDA at any reasonable rate. This rate could, initially, allow us to legally go well below the glide slope.

I conclude that, since on an “ILS, circle to land” approach we are not given a DA(H), but rather an MDA, therefore, we are executing a non-precision approach. It follows that, we can not legally start our descent at glide slope intercept and follow it down. We must maintain our altitude until the non-precision final approach fix and then start our descent. I, further conclude that, since the glide slope is one of four required parts of an ILS, this precludes the use of the term ILS to describe this approach procedure.

Therefore, there is no such thing as an “ILS, circle to land”. I think it would be much better and more accurate to call it a “localizer, circle to land” because that is what it is.

posted by Administrator3 Aug 31, 2007  01:08 PM
read (0 comments)

Weather I consider ice accumulation equivalent to an aircraft being on fire. You have to take immediate action or the consequences will be disastrous. Some pilots rely on the belief that there will be plenty of forewarning before things get serious. Perhaps, but it depends on how fast the ice is accumulating and in some cases it can be very rapid indeed. Usually there will be an increasing loss of performance i.e. loss of climb rate, decreased airspeed, an inability to maintain altitude and so forth. If corrective action is not taken you will not gently descend back to earth, but rather the plane will stall and plummet horrendously out of control. The time to act is at the first onset of ice. You will have to either descend to warmer air, climb out of it if conditions and aircraft performance permit, or do a 180 degree turn to go back to where the air is hopefully still ice-free.

I’ll never forget one of my earlier aircraft accident investigations when a pilot flying a Cessna 210 at cruise altitude in heavy IMC radioed center that he would be returning to the airport because of ice. The plane stalled in the turn and went straight down. Result of Cessna 210 encounter with heavy icing conditions

The picture above shows what was left of the plane. It impacted like a lawn dart, sticking out from the snow-covered ground at a 90 degree angle. Three people were killed. The pilot took off where ice would be an obvious factor enroute and didn’t take corrective action until it was too late. The crash scene image has never left my mind and it weighs heavily any time that I have to make a flight in potential icing conditions.

Unlike turbine or jet engine aircraft that bleed hot air to the wings and tail for ice-protection, the average piston general aviation aircraft may, at best, be equipped with pneumatic wing boots, or a “weeping wing” system and maybe a “hot” prop. These systems offer a false sense of security and only permit an opportunity to escape icing conditions. They are not designed to fly in heavy icing conditions continuously.

Lightning Even with some wing ice-protection, an unprotected tail section can accumulate a lot of ice and cause the aircraft to stall. Don’t forget that in most general aviation aircraft the horizontal tail surfaces are aerodynamically “down-loaded” in normal flight to counterbalance the weight up at the front of the plane. If the tail stalls, the down-load is lost and the nose pitches steep down. In addition to the tail, ice can accumulate on engine air intakes and antennae causing power loss and lack of radio capability. Do you really want to deal with all this while you are flying in the wet stuff?

Besides better ice-protection systems, turbine-powered aircraft have another advantage that piston-powered aircraft do not have: Lots of excess power. Jets and turbo-prop aircraft can out-climb a lot of stuff that an ice-laden piston airplane cannot. Trying to climb at a few hundred feet per minute increases the exposure time to ice accumulation which in turn degrades performance even further. It is tempting for a pilot to expedite a climb out of icing conditions, using a “best rate” or “best angle” speed, but the increased pitch attitude in the climb may cause an increase in ice accumulation on the bottom of the wing surface as it becomes more exposed to the air stream.

In a discussion of ice, pilots rarely give due consideration to the aircraft’s windshield. Most piston aircraft defrosters are pretty useless when it comes to getting rid of windshield ice. Unless you have a true “anti-ice” (heated or chemical spray) windshield, a frozen-over windshield will have you flying blind when you break out into clear air if the temps are in the freezing range. At cruise altitude you will not see other traffic and if freezing temperatures extend to the surface, trying to find the runway and landing will be an interesting experience with your forward vision obscured.

Lightning It is beyond the scope of this article to discuss specific strategies or the legal requirements related to flight in icing conditions, but suffice it to say any possibility of an ice encounter needs to be evaluated in the preflight planning stage. At any point in your planned route, you must be able to articulate an escape plan to non-icing conditions. If you can’t do this with a reasonable degree of certainty then stay on the ground and take a cue from the advertising folk: Got Ice? Just say “No!”

Editor’s Note: Ken Steiner is the Claims Manager and Asst. Vice-President for the San Francisco office of the United States Aircraft Insurance Group (USAIG), the worlds largest aviation insurance company. He has been with USAIG for 20 years investigating all manner of aviation accidents involving aircraft from Cessna 150′s to Boeing 747′s. Ken is an active pilot holding ATP and CFI certificates with over 3500 flying hours. He flies a Cessna Turbo Skylane based at San Carlos, and yes, his flying record is free of any accidents, incidents and violations!

posted by Administrator3 Aug 30, 2007  12:08 PM
read (0 comments)

Plane “Ouch!” I muttered after turning around too quickly and banging my head on the leading edge of the wing during preflight. I haven’t even started the engine and I’m already an aviation casualty. The reality is that you don’t have to be airborne to have trouble come-a-callin’. In fact, you may be surprised at the variety of accidents that frequently occur on the ground even before we get into the airplane. Our mind-set as we meander around the familiar airport environment is far different from our focus in the air. Often our mind may drift as we become preoccupied with a pending flight or the price of Avgas. In Part I of “Grounded” we will explore the hidden dangers of the parked airplane.

Most ground-related accidents aren’t well-publicized. The smoking holes get all the press. Even a plane running out of gas and making a successful landing on a road will be “page one” news. Ground accidents may not have much pizzazz, but they can be serious and costly. It can turn an otherwise good flying day into a disaster and even a lawsuit. The examples that I present are real and are taken from my claims files.

Parked planes seem to be a magnet for airport vehicles, fuel trucks, other planes, and spaced-out pilots driving their cars. I have had more than one claim reported where the pilot was driving his own car and hit his own plane. We tend to be much more attentive driving in a supermarket parking lot where we can anticipate trouble. Oh yes, and just like in the parking lots, not everyone will stop and leave a note after hitting your plane. Sad and dangerous, but true. Even if you have only been gone from your plane for a few minutes, always do a walk-around before you get in. I have handled claims where pilots have become airborne unaware that their planes were damaged by someone on the ground who didn’t stop to leave a note.

If you are fortunate enough to have your airplane in a hangar, the odds are that you will probably be unfortunate enough at some point to come down with a case of hangar rash. Shoe-horning planes in and out of a hangar is a cumbersome task that carries with it a certainty that the plane will be damaged if 100 percent care and attentiveness is not given every time you move that plane. Are the hangar doors fully open? Is the tug or tow bar mechanically sound and properly secured to the plane? Any objects (like cars or other planes) in close proximity? Do you know how far back can you push the plane before it hits the rear hangar wall? Keep focused on the task at hand and not the flight or other distractions.

Safety FirstFailing to use chocks is a good way to get an unwanted surprise. I have handled a lot claims where unchocked airplanes have rolled away on seemingly level ground into other planes, buildings, or vehicles. The resulting damage can be awesome. Don’t deceive yourself by thinking that because you are nearby or will only be gone for a few minutes that nothing will happen. The gradient of seemingly flat ground can be deceiving and once a plane starts rolling it quickly builds a momentum that can’t be stopped by human strength alone. Even on level ground, all it takes is a well-placed breeze, prop blast, or jet thrust to set things in motion. Some pilots think that the heavy weight of larger planes will keep it from rolling – Wrong! If it has wheels it can roll and with the close quarters of parking at airports it only takes a few feet of movement to have a collision which is both costly and embarrassing. Don’t rely on parking brakes alone. Always carry a set of chocks in your plane and use them when you park.

Accidents on the ramp apply not only to airplanes, but to people as well. I have handled a number of serious injury claims (broken arms, knees, teeth, and facial injuries) that came simply from people tripping over tie down fasteners, ropes, and chains. Passengers have also received similar injuries from falling while getting in and out of aircraft, especially on low-wing planes, and as incredible as this may seem, both pilots and passengers are still departing this lifetime after close-encounters with moving propellers. Never allow anyone to board, deplane, or approach an aircraft with a running engine.

Happy planeAs comfortable as we might be in an airport environment, it is a foreign land to our non-aviation visitors. The temptation to wander about and sight-see is normal. It is your duty to supervise your guests like a mother hen and advise of them of the hazards. On the ramp make sure that you escort your guests at all times and do not let them wander off. Children and pets need special attention in this regard. Always monitor and assist passengers getting in and out of your plane.

In Part II, “Grounded – After the Engine Starts,” we will explore some of the unique and little known hazards facing a pilot during taxi operations.

Editor’s Note: Ken Steiner is the Claims Manager and Asst. Vice-President for the San Francisco office of the United States Aircraft Insurance Group (USAIG), the worlds largest aviation insurance company. He has been with USAIG for 20 years investigating all manner of aviation accidents involving aircraft from Cessna 150′s to Boeing 747′s. Ken is an active pilot holding ATP and CFI certificates with over 3500 flying hours. He flies a Cessna Turbo Skylane based at San Carlos, and yes, his flying record is free of any accidents, incidents and violations!

posted by Administrator3 Aug 30, 2007  09:08 AM
read (0 comments)

Ramp view at San Carlos Airport

You would think that taxiing an aircraft is a relatively low risk proposition. We follow painted lines. We move at slow speeds. Ground traffic is often controlled by ATC. We have signs, rules, radios, and space to maneuver and yet this seemingly innocuous phase of aircraft operation results in numerous avoidable, expensive and embarrassing accidents. In fact, the odds of having an airplane accident during a ground operation are far greater than accidents due to airborne-related events. As I had mentioned in Part I of “Grounded”, part of the problem is that aircraft accidents on the ground are not well publicized and many pilots are unaware of the potential for trouble.

Cessna 421 with part of wing missing!

Just recently, I investigated a typical needless ground accident. A pilot had taxied his twin engine airplane to the run-up area, but had to hold on the taxiway as the run-up area was full. A Cessna 172 behind the twin became impatient and tried to cut in front of the twin. In doing so, the left wing of the 172 over-lapped the right wing of the twin. The 172′s wing got chopped up by the twin’s propeller. In spite of the considerable damage, it could have been worse had the 172′s gas tank ruptured causing a fuel spill and fire. All this because of one pilot’s impatience and bad judgment.

Of course we can read about this and say “I would never do anything like that”. Maybe so, but even if we avoid the obvious, accidents can occur when we are subject to distraction and inattention. Taxiing an aircraft is a seemingly undemanding task. It is easy to let our thoughts wander while moving on a spacious ramp. We are not “on guard” as there is no perceived danger. Some of us are even fiddling with avionics, charts, or checklists when we should be keeping our mind and eyes on the road.

About two years ago I had just landed at a large uncontrolled field and was taxiing on the main parallel taxiway toward the ramp. As I was approaching an intersection, a Piper Cub came darting out from an arterial taxiway completely oblivious to my presence and was headed towards the same intersection. Having just enough knowledge of Physics 101, to realize that two aircraft could not occupy the same space at the same time I stopped my plane about a 100 yards from the intersection. Even though I had already stopped well clear of the intersection, the sight of another airplane was enough to startle the Cub pilot into making a panic stop, not a good thing to do in a tail dragger.

Piper Cub up on its nose!
In disbelief I watched as the Cub went over on its nose with the tail up in the air and the propeller trying to screw itself into the ground. To make matters worse, the pilot (of considerable girth) was stuck in the snug cockpit of the up-ended aircraft and fuel was pouring out of the wing tanks toward the hot engine and exhaust. I radioed the unicom for assistance and went over and helped extricate the Cub pilot out of the plane. Fortunately, there was no fire. Just a bent prop and bent ego.

A point of importance. The Cub pilot was no novice. He was an experienced, professional pilot who had a momentary lapse of attention as to where he was and what he was doing. As in the first example with the 172, the consequences could have been fatal if a fire had broken out. Don’t be lulled into feeling safe and secure because you are on the ground. When you are taxiing an aircraft, your level of attention and focus should be no less than when you are airborne.

Never play the “I think I can make it” game when trying to maneuver around aircraft on the ground, especially when parking. You either can or can’t clear it. If there is any doubt, shut it down and take a look. Don’t feel embarrassed if you have to get out the old tow bar or have someone help you push the plane if you find yourself in a tight spot. It is a far better decision than causing damage to two planes: your plane and the plane you hit. Also, don’t abdicate your judgment to well-meaning passengers, and passersby that are helping to guide you or reassure you that you will pass clear of a particular obstacle. Stay alert. I have even handled a number of claims involving pilots who were blindly following the direction of line people when they hit another aircraft or obstacle. As much as they would like to blame the line person, the Pilot-In-Command is still responsible for the safe operation of his aircraft. Never be lulled into a false sense of security just because you are following a painted line on the ground. It is not an insurance policy that will prevent you from hitting another parked plane, building, or other structure such as a utility pole. Scan for hazards as you do in flight and watch your wing tips.

Hazards while taxiing are not just limited to other aircraft. Taxiing over dips and depressions on the ground can cause a prop strike. Extra caution is needed on unpaved surfaces. Sometimes depressions will be camouflaged by standing water so as to look like an innocuous puddle. I handled one such prop-strike claim at SQL after a heavy rain had covered an otherwise well-marked, but recessed storm drain. When a nose gear enters even a small depression, the strut compresses which can bring prop clearance down to nil. Speaking of airport storm drains, be careful when taxiing over drains, grates and manhole covers. I have handled claims where these gave way under the weight of light planes causing prop strikes and serious airframe damage.

One of the most demanding aspects of taxiing can be trying to stay oriented at an unfamiliar airport. Anyone who has been to LGB (Long Beach) knows how intimidating an airport can be on the ground. Add in darkness or other forms of limited visibility at an unfamiliar or complex airport and you could find yourself wandering into trouble. Inadvertent runway incursions can and have had fatal results. Get ground-orientated as part of the preflight. Study the airport diagram, monitor the taxi signs and markings and never hesitate to ask ground control for “progressive taxi” either to or from the runway. If you become disorientated, stop where you are and figure it out. Don’t proceed blindly.

We’ve covered a lot of “ground” in this two-part series. You shouldn’t feel that the accident boogey-man is lurking in the shadows every time you get near a plane, but you need to be aware of some of the lesser known, but all too common potential traps for the unwary. Just use a little heads-up airmanship and you won’t be “grounded.”

Editor’s Note: Ken Steiner is the Claims Manager and Asst. Vice-President for the San Francisco office of the United States Aircraft Insurance Group (USAIG), the worlds largest aviation insurance company. He has been with USAIG for 20 years investigating all manner of aviation accidents involving aircraft from Cessna 150′s to Boeing 747′s. Ken is an active pilot holding ATP and CFI certificates with over 3500 flying hours. He flies a Cessna Turbo Skylane based at San Carlos, and yes, his flying record is free of any accidents, incidents and violations!

posted by Administrator3 Aug 29, 2007  12:08 PM
read (0 comments)

It is easy to feel relatively secure in dealing with known aviation risks.  We can plan for potential hazards such as bad weather or systems failures and then apply an alternate course of action to insure the safe outcome of a flight.  The prospect of a mid-air collision, on the other hand, bothers most pilots since it is a scenario that is real, but seemingly unpredictable and one that we may not be able to control.  We worry that we could be broad-sided out of the sky even while exercising all due caution and vigilance.  Indeed, there are few pilots out there who have not at one time or another had to take an evasive maneuver to avoid another aircraft in close proximity.

Mid-air collisions are seldom a single random event which involve two aircraft that simply run into each other.  Like other accidents, midair collisions have a causal chain.  That is to say that independent circumstances set the stage for the accident that is yet to come.  I have investigated a number of aircraft mid-air collisions over the years and in each situation there are identifiable links in the chain which allowed the accident to take place.  Let’s take a look at a few examples in the briefest of terms.  We are not focusing on the accident, but the contributing factors.  Most of these accidents happened over 15 years ago and all involved fatalities.

A Piper climbing out of Long Beach collides with a DC-9 on approach to Los Angeles international.  Factors: The pilot of the Warrior was relatively new to the area.  For unknown reasons his transponder was found to be in the “standby” position.  He was not in communication with ATC and he had entered Class B airspace without clearance when he hit the DC-9.

A Piper in-bound to the Oakland airport was on a 45 degree entry to runway 27 right and collided with a Cessna which had just taken off from runway 33 on a straight out departure.  Factors: The airport tower radar was out of service.  The tower failed to provide adequate warnings to each aircraft.   The use of runway 33 for takeoff and 27 for landing increased the collision conflict risk.

A Mooney had just pulled on to runway 12 at the Half Moon Bay airport and was on the take-off roll when it collided with a Cessna just about to touch down on runway 12.  Factors: Uncontrolled airport.  The Mooney did not communicate his departure on the unicom.  It was also determined that the pilot of the Mooney did not have a current medical certificate or biennial flight review.

A Cessna 172 and a Cessna 152 collided near Morgan Hill, California.  Factors: Each aircraft was on an instrument training flight with a student under the hood and an instructor in the right seat.  Both aircraft were operating without the benefit of ATC radar advisories in a corridor of busy airspace.

Each of the above respective “Factors” relate a measure of increased risk that were a fundamental part of the collision.  Playing armchair quarterback for a moment, put yourself in the position of each pilot.  What could have you done on each of these flights to minimize the risk, break-up the causal chain and prevent a tragic outcome? Some are obvious, some are not, but the point is that these accidents did not happen out of the blue and were preventable tragedies.

In the above accidents the weather was excellent VFR, the collisions took place below 5000 feet AGL and they occurred within 5 miles of an airport.  These underlying conditions often prevail during mid-air collisions.  There is no mystery here.  The airspace below 5000′ and in the vicinity of an airport brings together the greatest confluence of transitioning aircraft and the collision risk simply increases through statistical probability due to higher numbers of potential targets.  Pilots are also at much higher workload levels down low than in cruise flight and may not be giving the requisite attention to scanning for traffic.

Good VFR conditions tend to increase the volume of flight activity and can also bring a measure of pilot complacency given the relatively relaxed structure of the VFR operating environment.  The wild card contributing to the threat are pilots who disregard the rules, use non-standard pattern entry or departure procedures and don’t communicate their position or intentions especially at uncontrolled fields..  Even controllers can make mistakes so never hesitate to question them if you have any doubt or uncertainty regarding their communications.

Even if one pilot is mostly to blame by setting the stage for a collision, it will be of little comfort to the other pilot given the often fatal outcome.  Consider that there is always someone out there who is constructing their own causal chain towards a mid-air collision.  Basically they are an accident waiting for a place to happen, but it takes two to create the big bang.  By anticipating this threat and by actively using the collision avoidance skills that you were taught early on you need not be a part of their future.

Editor’s Note: Ken Steiner is the Claims Manager and Asst. Vice-President for the San Francisco office of the United States Aircraft Insurance Group (USAIG), one of the world’s largest aviation insurance companies. He has been with USAIG for over 27 years investigating all manner of aviation accidents involving aircraft from Cessna 150′s to Boeing 747′s. Ken is an active pilot holding ATP and CFI certificates with over 3500 flying hours. He flies a Turbo Skylane based at San Carlos, and yes, his flying record is free of any accidents, incidents and violations!

posted by Administrator3 Aug 29, 2007  09:08 AM
read (0 comments)

It was a beautiful summer’s day as the pilot and his family were flying back in the late afternoon after visiting friends in Sacramento. Over Concord the pilot could see that the marine cloud layer was blanketing the Bay Area with the coastal stratus just touching the tops of the East Bay hills. He thought he could see under the clouds over to the Bay side, but it was really just an illusion of light bouncing off the clouds and maybe some wishful thinking on his part. No matter, he knew the area well and would just stay below the clouds to get home.

Clouds over hillsAs he approached the hills he had to descend little by little to keep from entering the scud. To stay under the clouds he descended below the ridgelines and was now flying through the passes. A feeling of unease started to creep in. At this low altitude all the familiar landmarks melted into the homogeneous terrain and he wasn’t quite sure of where he was or where he should be going. He turned to avoid entering the clouds blocking his path, but had little room to maneuver. In an instant the windshield turned a solid gray-white causing a complete loss of orientation as to which way to go. Seconds later there was a loud “blaam” followed by eternal silence.

It is a tragic scenario that plays over and over again. This is the most common type of fatal accident that I investigate in the Western States and it occurs all too often in our area where we have an abundance of coastal stratus and hills. It happens to both instrument and non-instrument rated pilots alike. Scud running is one of the most dangerous flying activities you can undertake because, as with the pilot above, it can seem like a fairly benign idea to begin with, but may turn out to be a lethal one-way trap.

Radio towersWhat constitutes scud running? Well, even undefined you pretty much know it when you are doing it (and you usually don’t feel good about it). I tend to think that anytime you have less than a 1000 feet of altitude between the ground and the base of the clouds you are running short of VFR maneuvering room. Even when the terrain is flat, surface elevations and cloud bases will vary over distance and may shrink your safety margins quickly. Other lethal hazards associated with scud running include hitting obstructions such as utility structures or wires. Even without obstructions, spatial disorientation from an inadvertent cloud encounter can cause a non instrument pilot to lose control of the aircraft.

Like walking into quicksand, the danger may not be apparent until it is too late to retreat. The solution is easy: Don’t go there. Don’t even think about it. If low clouds block your path don’t be tempted to sneak under. Light can play funny tricks and tempt you with false illusions of clearing in the distance. See if you can circumnavigate a safe route even if takes a bit longer.
If you are qualified, current, and equipped for instrument flight, make the effort to request an IFR clearance. If not, then land and consider your options to either wait it out, rent a car, or spend the night. Tomorrow is another day and it is better than the alternative.

Editor’s Note: Ken Steiner is the Claims Manager and Assistant Vice-President for the San Francisco office of the United States Aircraft Insurance Group (USAIG), the worlds largest aviation insurance company. He has been with USAIG for over 20 years investigating all manner of aviation accidents involving aircraft from Cessna 150′s to Boeing 747′s. Ken is an active pilot holding ATP and CFI certificates with over 3500 flying hours. He flies a Cessna Turbo Skylane based at San Carlos, and yes, his flying record is free of any accidents, incidents and violations!

posted by Administrator3 Aug 28, 2007  11:08 AM
read (0 comments)

Last week while flying back to the Bay Area, the topic for this article came to me in a flash. Well, actually several flashes. Over on the west side of the San Francisco peninsula nature was putting on one of its most dazzling shows. Brilliant bolts of lightning arced across the sky. I didn’t have to look at my Stormscope to know where the bad stuff was. Luckily, I could enjoy this dramatic scene from a safe and respectful distance. The less fortunate were reporting some pretty rough rides to ATC.

The early Vikings believed that lightning came from Thor striking his hammer on an anvil as he rode his chariot across the clouds. There is an alternative belief for the non-Vikings among us that lightning occurs when negative and positive electric charges in the atmosphere start to separate due to the shears associated with thunderstorm development. An accumulation of negative charges in clouds will eventually discharge towards a positive charge such as the earth or other clouds.

LightningThis discharge is basically an electrical spark in which the flash lasts about half-a-second and the heat can be up to five times the temperature of the sun. The noise you hear (thunder) is the compression of the super-heated air around the bolt as it slices through the atmosphere. By the way, lightning strikes occur about 100 times per second on our planet. One study suggested aircraft lightning strikes occur approximately once per every 1000 flight hours.

The good news is that lightning is a relatively rare factor in fatal aircraft accidents, but it certainly is a potential hazard. Between 1959 and 1988 there were 9 fatal airline accidents attributable to lightning strikes. On December 8, 1963, a Pan American Boeing 707 sustained a lighting strike near Elkton, Maryland, which ignited a fire on the right wing. The wing separated and 81 people were killed. On February 8, 1988, a Metroliner was hit by lightning near Mulheim, Germany, causing the electrical system to fail while IFR. During an uncontrolled descent, a wing broke off resulting in 21 fatalities.

Lightning strike exit burn on elevator trim tab of a Lear jet
Lightning strike exit burn on elevator trim tab of a Lear jet

Normally, when lightning strikes an aircraft, the metal airframe provides a conductive path for the electricity to travel through it and dissipate back into the atmosphere. Composite structures incorporate a metallic mesh to provide the necessary conductive path. Lightning often strikes the front of an aircraft first. The physical evidence of a lightning strike is usually in the form of some small electrical pitting or arcing marks which are often found on nose cones, prop spinners, cowl inlets and leading edges. Similar small burn marks are found where the lightning exits the airframe at control surface trailing edges, trim tabs, and tail cones.

While the external arcing marks are usually a minor cosmetic concern, the energy of a lightning strike can instantly fry electronic equipment causing the pilot to lose instrumentation and avionics, which is a bad thing to happen when traversing a thunderstorm under IFR conditions. I know of one pilot flying a Cessna 210 who had this happen and he lost control of the aircraft. He barely recovered in time. I have also seen radar dishes look like black cast-iron frying pans after a lightning strike.

Besides the electronics, another concern about a bolt of lighting traveling through an aircraft is the destructive potential to bearing surfaces. Bearing surfaces are typically designed for applications where frictional contact is to be kept to a minimum. A lightning strike may cause electrical pitting on these bearing surfaces essentially destroying them. A strike on other surfaces such as propeller blades may compromise structural integrity requiring a complete replacement depending on the manufacture’s criteria. Usually manufacturers provide lightning strike inspection procedures for their airplanes and components.

Under the worst circumstances, a lightning strike can penetrate the fuel system and ignite fuel vapors causing an aircraft to explode or burn as in the case of the earlier mentioned 707 accident. I investigated an accident involving a Piper Arrow that did ignite and explode in the air while traveling through convective activity. Due to the extensive destruction of the plane we could not conclusively state that lightning caused the explosion, but it seemed a logical possibility given the surrounding circumstances. Most planes are designed to prevent this situation, but a mechanical or structural deficiency could allow it to happen.

No TrespassingConsider that lightning is really just an unusually bright “No Trespassing” sign for aviators. You can often see and avoid it way in advance if you are VFR and, if IFR, it is easily detected if you have a Stormscope or Strikefinder on board. Lightning is trying to tell you that this is a place where you are not welcome. With in its boundaries you will meet the rest of the family: hail, heavy rain showers, and killer turbulence. Lightning won’t be a problem if you know enough to stay away from thunderstorms. If you don’t know enough to stay away from thunderstorms, than kindly put your pilot’s license back in the cereal box from where it came from. Enjoy the fireworks, but do it from a safe distance.

Editor’s Note: Ken Steiner is the Claims Manager and Assistant Vice-President for the San Francisco office of the United States Aircraft Insurance Group (USAIG), the worlds largest aviation insurance company. He has been with USAIG for over 20 years investigating all manner of aviation accidents involving aircraft from Cessna 150′s to Boeing 747′s. Ken is an active pilot holding ATP and CFI certificates with over 3000 flying hours. He flies a Cessna Turbo-182 based at San Carlos, and yes, his flying record is free of any accidents, incidents and violations!

posted by Administrator3 Aug 20, 2007  11:08 AM
read (0 comments)

Crop DusterLast week I planned a flight from San Carlos to a crop duster airstrip in the southern end of the San Joaquin Valley.  The weather forecast seemed pretty consistent on my route with occasional rain showers and cloud bases ranging from 3000 to 5000 feet thanks to an active area of low pressure.  I departed IFR to get out of the area, but by the time I got over to the San Joaquin Valley the weather was decent VFR and I cancelled my instrument flight plan and was proceeding comfortably below the clouds at 3500 feet.              

Wall of CloudsAbout 50 miles from my destination, I noticed what could only be described as wall of clouds blocking my route that seemed to extend up from the ground to the bases of the clouds above me.  I could not circum navigate around it and because there was no instrument approach at my intended destination there was little point in trying to get an instrument clearance.  I opted to call it day and headed back to the barn.

The next day I learned that a Cessna 210 had been in the same area about an hour before me and had broken up in flight.   The three on board were killed.  The preliminary information indicates that the pilot was not instrument rated and likely lost control of the plane during an inadvertent encounter with IFR conditions.  I could identify with the pilot’s predicament, but not with the tragic outcome.

There are thousands of NTSB fatal aircraft accident reports which contain the familiar words “pilot failed to maintain VFR” as part of the probable cause findings.   A catch-all phrase to be sure, but one that often reflects the prologue of non-instrument pilots who encounter IMC conditions.  Keep in mind that we are talking about situations where the IMC encounter occurs at sufficient altitude with no obstructions nearby and the pilot loses control of an otherwise airworthy aircraft.   Low-level scud running, on the other hand will shorten the life expectancy of both instrument and non-instrument rated pilots alike as they fly, often under complete control, into unforgiving terra firma.

As part of our certification all pilots are required to maintain control of an aircraft by reference to the instruments.  Unfortunately, it is a skill seldom kept proficient by most non-instrumented rated pilots.  In reality it is essential to be able to control an aircraft by instrument reference not only for inadvertent cloud encounters, but also for flying under conditions of night or low visibility when there may be no outside horizon to reference.  The ability to integrate the use of both instrument and outside visual flight references makes one a much more precise, smoother, and safer pilot.

Instrument PanelIf you ever find yourself in a position of inadvertently losing outside visual reference your initial objective is to focus on the instruments to maintain a straight and level flight attitude (obstacle clearance permitting) and ignore any false sense of motion that could lead to spatial disorientation.   The attitude indicator will be your best friend here.  You will also have to fight the feelings of anxiety and fear that come with this situation especially if there is turbulence.  Just because you are in the clag, the laws of aerodynamics have not been repealed and your plane will fly just the same.   You will just have to work a little harder and keep your cool.

Use trim to stabilize pitch attitude and apply small, gentle control inputs while keeping your eyes on the instrument panel to maintain straight and level.   A properly trimmed aircraft will fly itself.  Better yet, use the autopilot if you have one.  Just make sure that you thoroughly understand how to use it.   Get help from ATC if you can, but don’t lose control of the plane while fiddling with the radios.  When you get settled you will need to either do a gentle 180-degree turn back to clear skies or climb or descend if cloud bases or tops permit.

Why is it so important to focus on straight and level flight?  A loss of control under IMC typically occurs when the pilot isn’t paying attention or starts succumbing to spatial disorientation and the aircraft starts to bank.  As the wing drops down the aircraft also starts to descend picking up speed.   A pilot will react by pulling back on the yoke without first leveling the wings.  This aggravates the situation by increasing the bank angle, descent rate, air speed and wing loading.  This is often referred to as the “graveyard spiral.”  Speeds can quickly exceed structural limits causing the aircraft to break up as the pilot tries to pull out of it.  If you find yourself in this situation level the wings, reduce power, and slow the aircraft as best you can before gently pulling out of the dive.  Keep it straight and the plane won’t break.

Plane about to enter IFR conditionsIdeally the best course of action is not to be in a position where you have to “cancel VFR,” but stuff happens and it is best to be prepared as you would for any potential emergency through recurrent training.  With an instructor on board, a cloud encounter can easily be simulated in VFR conditions by putting on the hood and practicing an exit strategy by doing turns, climbs, and descents with and without the use of an autopilot.   The session should also include unusual attitude recoveries and how to obtain assistance from ATC.  This is simple stuff at which all pilots should be proficient.   Remember that a plane doesn’t care if it is in clear air or clouds; it flies pretty much the same.  As in most things in life, attitude is what counts.

Ken Steiner Editor’s Note: Ken Steiner is the Claims Manager and Asst. Vice-President for the San Francisco office of the United States Aircraft Insurance Group (USAIG), one of the world’s largest aviation insurance companies. He has been with USAIG for over 27 years investigating all manner of aviation accidents involving aircraft from Cessna 150’s to Boeing 747’s. Ken is an active pilot holding ATP and CFI certificates with over 3500 flying hours. He flies a Turbo Skylane based at San Carlos, and yes, his flying record is free of any accidents, incidents and violations!

posted by Administrator3 Aug 20, 2007  09:08 AM
read (0 comments)

One of my early claims involved a pilot who was flying his recently purchased Beech Bonanza and could not get the landing gear to extend. He conscientiously tried everything he could think of to extend the gear, but finally resigned himself to the fact that he was going to have to make a gear-up landing. He methodically burned off as much fuel as possible, asked for the emergency equipment to stand-by and made as smooth a touch down as possible with the wheels retracted. All in all a successful outcome except for the belly and prop damage. Shortly after the incident the pilot was interviewed by the FAA who asked the pilot if he was able to rotate the emergency extension hand crank located behind the pilot’s seat to extend the gear. The pilot replied “What hand crank?”

Oops!

Its hard to know whether to laugh or cry when you hear a story like this, but it is really only a variation on a continuing theme of pilots causing great bodily harm to their retractable gear aircraft. Yes we have all heard the expression there are “those who have and those who will” when it comes to the predictability of a gear up event. I personally don’t share this philosophy. There are plenty of RG pilots out there who will roll steadily back to their tie down through out their flying career. So what about those that don’t?

Gear-up landingWhen a gear-up landing is reported to my office I try to tread lightly when I interview the pilot. I know that he has already sustained an ego bruising. Most pilots are up front and honest about what happened. Some assert that a mechanical failure is the responsible culprit. A good investigation will disclose the truth and while mechanical problems occasionally contribute to a gear collapse or extension failure, most problems are, well, let me put it this way: “We have met the enemy and he is us.”

Inexperienced pilots transitioning to retractable gear aircraft have their own set of problems in adapting to faster and more complex aircraft, but remembering to raise and lower the gear is not one of them. It is the more experienced and complacent aviators among us who are the most likely to join the “those who have” club. I have handled gear-up claims involving pilots with over 20,000 hours and a wallet full of flying credentials. The average gear-upper I deal with has about 1500 hours or more total time and about 500 hours RG time. The incidents occur in all variety of aircraft from light single engine planes to heavy jets.

Even with gear warning horns, pilots can find new and creative ways to turn their planes into leg-less birds. Anyone who relies on a gear warning horn to save them, probably believes in the tooth fairy as well. The rigging of the gear warning horn seems to be universally set to go off at a power setting somewhere between engine idle and shutdown. Not very helpful for most of us carrying power on final. I did have one pilot of a gear-up landing report to me that his gear horn went off prior to touchdown. Unfortunately, at the time he thought it was the stall warning horn so he ignored it. In another instance an instructor giving instruction in a twin engine aircraft pulled the power back on one engine to simulate a single engine workload. With the throttle pulled back, the gear warning horn kept blaring so he pulled the gear system circuit breaker to silence it which also disables the gear motor. Want to guess the results?

There's trouble ahead!Automatic landing extension systems, such as on a Piper Arrow work great except for those unfortunates who come in faster than the gear activation speed or forgot that they had switched to the over-ride mode. Also, it is very hard to develop any kind of consistent habit pattern when sometimes you lower the gear manually and sometimes you let “Otto” do it. In any airplane your job doesn’t end just because you place the gear switch in the “down” position. You have to verify that the swing cycle is complete and that all three gear are locked into position. I have had claims where a pilot moved the lever or switch to “down” not realizing that the gear circuit breaker popped or the motor jammed only to have the partially extended gear collapse on landing. Also, be alert that sometimes things get out of rig and a gear motor may not shut off. The result can be a burned out gear motor and possible fire hazard from an overheated motor. My rule is to keep your hand on the gear control until the up or down cycle is complete and do not move your hand until you have verified gear extension or retraction from all means available which includes: lights and/or mechanical indicators, visual confirmation if you can see them, the sounds of the gear locking into place, and the sound of the gear motor shutting off.

Another variety of gear-up accidents involves planes that make a normal landing only to have the gear fold during the roll-out because the pilot reached for the wrong lever at the wrong time. This was a common occurrence among pilots who switched between flying older retractable Beechcraft planes which had the non-standard placement of the gear switch on the right side and the flap switch to the left and then flying other planes with the opposite configuration. Out of habit they go to retract the flaps only to find that the gear switch is now occupying that particular piece of panel real estate and go for a slide on the pavement. This type of event happens even for those who fly the same plane on a regular basis. The moral of the story is don’t touch anything without verifying what it is and preferably not until you are off the active runway at a complete stop. When you touch a switch it may help to remember that a gear switch is round to represent a wheel and a flap switch often is shaped in flap-like form.

Another gear-up landingThe gear can also retract before you even get airborne. I had a claim where a passenger’s knee accidentally bumped a gear handle that had a weak detent causing the wheels to fold. What’s that you say? What about the squat switch to prevent ground retractions? You might as well put it under your pillow along with the gear warning horn while waiting for the tooth fairy to come along. They just don’t work. Either they are out of rig to begin with or the gear will fold as soon as wheel weight is unloaded during taxi or take-off. Speaking of take-off, always establish a positive rate-of-climb before retracting the gear especially in density altitude situations. I have handled a number of claims where the plane never really got out of ground effect and settled down on its belly because the landing gear was retracted prematurely. A prop hitting the pavement at take-off power is an ugly sight to behold.

Making the wheels of an aircraft go up or down is as simple as flipping a light switch. You can train any non-aviator to do it with a few minutes of instruction, but to do it right and accident-free over a lifetime of aviating requires establishing consistent and methodical habit patterns. It starts with a comprehensive knowledge of the landing gear system of the plane you fly including the appropriate V speeds and emergency or abnormal procedures. Gear extension and verification should be done as part of the pre-landing check list while outside the airport traffic area. A GUMP check (gas, undercarriage, mixture, prop/ pumps/ pressurization) works well for many. Double check gear extension on the first pattern leg while you complete the landing checklist. A final check should be done at 500 feet AGL on final and say out loud every time, “Gear down and verified!” which will serve as a habit pattern reinforcement on both a conscious and sub-conscious level. Once on the ground, avoid touching switches or retracting flaps during the roll out. If the flaps must be retracted, make sure it feels like a flap lever before moving it.

If anything unusual occurs prior to landing such as unexpected traffic, mechanical glitches, non-standard instructions from ATC, unscheduled go-arounds, and so forth, you have entered a “distraction mode.” Your habit patterns have been disrupted and you are vulnerable to forgetting tasks which are normally accomplished as part of your routine. After giving the distraction the requisite attention, get back to flying the plane with the recognition that you were distracted and do the check list dance one more time. It may save you from having to walk back to the tie-down.

Editor’s Note: Ken Steiner is the Claims Manager and Asst. Vice-President for the San Francisco office of the United States Aircraft Insurance Group (USAIG), the worlds largest aviation insurance company. He has been with USAIG for 20 years investigating all manner of aviation accidents involving aircraft from Cessna 150′s to Boeing 747′s. Ken is an active pilot holding ATP and CFI certificates with over 3500 flying hours. He flies a Cessna Turbo Skylane based at San Carlos, and yes, his flying record is free of any accidents, incidents and violations!

posted by Administrator3 Jul 31, 2007  12:07 PM
read (0 comments)

Crossing the majestic Sierras on one of my rare weekend pleasure flights, thoughts of work started to creep in. Though all was serene in this perfect sky, I couldn’t help, but wonder how many of my fellow aviators would experience a less than an enjoyable ending to their weekend sojourn.

On Monday morning at work, the computer spit out the answer with clinical detachment. The FAA Office of Accident Investigation reported 36 accidents over the 2-day weekend, which included 6 fatal crashes. Not at all an unusual figure, perhaps even low for a summer weekend. Also, these were just the reported accidents. It is likely that there were several more accidents that never made it to the official records since not all accidents are, or have to be, reported.

So what went wrong? Just the usual, that occurs over and over again ever since Wilbur and Orville broke the surly bonds. Here are a few random excerpts in brief from the report:

AIRCRAFT LANDED GEAR UP ON RUNWAY 13R, BROWNSVILLE, TX

WHILE TAXIING OFF THE RUNWAY, WAS STRUCK BY ANOTHER ACFT

ACFT IMPACTED POWERLINE WHICH WRAPPED AROUND THE LANDING GEAR AND PROPELLER FORCING ACFT TO THE GROUND, MITCHELL, SD

ACFT ATTEMPTED TO LAND AND HIT TREELINE AND CRASHED 200-500 YARDS SW OF GALION AIRPORT, FOUR PERSONS ON BOARD, TWO WERE FATALLY INJURED, TWO SUSTAINED SERIOUS INJURIES,

AIRCRAFT HIT TREES WHILE LANDING AT A PRIVATE STRIP, ONE PERSON ON BOARD WAS FATALLY INJURED

ACFT STALLED ON TAKEOFF AND CRASHED JUST OFF THE AIRPORT, OTHER CIRCUMSTANCES ARE UNKNOWN, OSHKOSH, WI

WHILE EN ROUTE, THE ENGINE LOST POWER. PILOT MADE AN EMERGENCY LANDING ON A DIRT ROAD IN THE DESERT, 42 NW OF ALPINE, TX

It would be wrong to draw any conclusions just from these brief excerpts, but they are a newsflash reminder that not all of us are having a good flying day. As a pilot, the single most important way you can avoid becoming an accident statistic is to take heed of the accidents of others. For example, you may have noticed that two of the above serious accidents involved planes hitting trees during the approach. Perhaps if either pilot had recently read about someone having a similar accident, it might have altered their course of action and we wouldn’t be reading about them now.

Aside from being a dedicated chicken, 25 years of investigating aircraft accidents have made it impossible for me not to fly without the "Ghosts of Accidents Past" riding along. This is a good thing. If am tempted to scud-run through a mountain pass or play tag with Mr. Ice, the "Ghosts" are there to remind me of the penalties for not succeeding. It suddenly becomes very easy to make the right decision. Even if your job doesn’t involve investigating aircraft accidents for a living, you can still develop your own helpful ghosts by learning from the mistakes of others to avoid similar misfortune.

You might want to start on-line with http://www.ntsb.gov/ or http://www.faa.gov/ for a review of current and past accident investigations. The Air Safety Foundation section of the AOPA web site, http://www.aopa.org/, is also an excellent resource. In particular I would suggest checking out the Nall Report. This provides a comprehensive review and statistical analysis of general aviation accident trends on a yearly basis. It is an eye-opening read for any pilot. One of the best monthly subscription periodicals, in my opinion, is Aviation Safety. This is an easy to read and highly informative magazine profiling interesting accidents and safety of flight issues.

NTSB Logo
NTSB
FAA Logo
FAA
AOPA Logo
AOPA

When studying an accident put yourself in the pilot’s place and identify what went wrong and what you would have done to change the outcome. The more you do this, the more you will elevate your own decision making and judgment skills and become a safer pilot in the process. Drawing upon the hard-earned lessons of others and not wanting to travel that same road just may keep you out of the headlines. Simple as that.

Ken Steiner Editor’s Note: Ken Steiner is the Claims Manager and Assistant Vice-President for the San Francisco office of the United States Aircraft Insurance Group (USAIG), one of the world’s largest aviation insurance companies. He has been with USAIG for over 25 years investigating all manner of aviation accidents involving aircraft from Cessna 150′s to Boeing 747′s. Ken is an active pilot holding ATP and CFI certificates with over 3000 flying hours. He flies a Cessna Turbo-182 based at San Carlos, and yes, his flying record is free of any accidents, incidents and violations!

posted by Administrator3 Aug 31, 2006  01:08 PM
read (0 comments)

Many years ago, I was flying a single-engine plane at night across some very remote and hostile mountainous terrain when the engine started to run rough. It was so subtle at first that I thought it was "automatic rough" caused by an over-active imagination when being in the wrong place at the wrong time. No, this was real and I knew that if the engine went south so would I. That sinking, quivering feeling that you get in the pit of your stomach knowing that your very existence is on the line is something you never forget. Needless to say the outcome was favorable, but I vowed never to fly at night again across rough terrain on one engine or otherwise put myself in a position where options were not an option.

Night approach

The risks associated with night flight aren’t just limited to the above scenario. Other hazards exist which are much less apparent, but just as deadly. Last year I investigated three fatal accidents that had one common thread: They all occurred at night. The circumstances were distinctive, but night was a key element and the outcomes might have been different if the flights had taken place during daylight hours.

The first accident took place on a crystal clear, moonless night at a remote desert airport. Although visibility was otherwise excellent, witnesses described conditions as pitch black with no visible horizon. The 2000-hour, instrument-rated pilot took off from a lighted runway. Within half-a-mile of the runway departure end, the aircraft went in to a 90 degree left bank. The left wing tip struck the ground causing the aircraft to cartwheel resulting in the destruction of the aircraft and two fatalities.

This is a classic example of a "black hole" accident where the pilot is lulled into a sense of complacency because the weather is excellent, but visual references are limited or non-existent. The mind-set is VFR (visual flight rules) when, in the blink of an eye, instrument skills are required as soon as the plane lifts off and the runway lights disappear from view. About 15 years ago there was a nearly identical accident after a night departure from the Harris Ranch airport, also with an instrument-rated pilot aboard. If you have never experienced a "black hole" departure, the Mariposa Airport, to the east of Modesto, is a good place to learn (with a qualified, night-current instructor aboard). Be prepared for an instant transition to flight-by-instrument reference upon departing at night.

These "black hole" type of accidents can occur not only during takeoff, but also while maneuvering to land. A distant point of light in an otherwise dark area can induce rapid spatial disorientation if, for example, a star in the sky is incorrectly interpreted to be a light on the ground. If the pilot of an aircraft in a bank attempts to roll out believing that the light on the ground is a star or vice-versa the aircraft will be headed towards an inverted position. Not a good thing. I know of two aircraft that were lost in this manner both of which had airline transport pilots onboard.

The next accident involves a relatively inexperienced non-instrument rated pilot departing from a coastal airport at night. Again, conditions were very dark with the only local weather available from the airport’s ASOS (Airport Surface Observation System) which was correctly reporting clear skies over the airport. What the pilot didn’t know and couldn’t see was that a coastal fog layer was moving onshore just approaching the airport perimeter. After takeoff the pilot realized that he was encountering the clouds at about 500 feet above ground level and attempted to return to the airport. With darkness being a continuing factor, he lost altitude awareness and hit the ground resulting in one fatality and a serious injury. Had this been daylight, the weather hazard and his height above the ground would have been apparent. Weather can be very difficult to see at night and reports in many areas are sporadic and can cause a pilot to unexpectedly require the sudden need for instrument skills.

While the previous accident discusses a low-time pilot encountering instrument meteorological conditions during a night departure, this next accident provides an interesting contrast to the last one in that it involves a highly experienced pilot encountering instrument conditions during a night landing. The flight was VFR to an uncontrolled field with no instrument approach. Upon arrival a shallow ground fog was over the airport, but the pilot could see the runway lights from overhead. During the approach the pilot lost sight of the runway upon entering the ground fog and crashed into a ditch just a few hundred yards from the runway threshold resulting in one fatality and one serious injury. While one could argue that the outcome might have been the same during daylight, the sight of the runway lights illuminating the airport through the fog created an illusion that conditions were not that bad and likely induced the pilot to attempt the approach.

The above are all cautionary tales to keep in mind. These pilots were not acting recklessly or imprudently, but encountered conditions in which they were quickly caught off guard. Night flying can be an enjoyable aspect of the aviating experience, but it also brings with it certain risks and hazards not associated with flight during daylight hours. While you need not be instrument rated to legally fly VFR at night (although in Canada you need an instrument ticket to fly at night) you should be instrument proficient and prepared to fly by reference to the instruments when outside visual references are unexpectedly impaired.

Remember that a successful night flight is one where you see the light of day.

Editor’s Note: Ken Steiner is the Claims Manager and Asst. Vice-President for the San Francisco office of the United States Aircraft Insurance Group (USAIG), the worlds largest aviation insurance company. He has been with USAIG for 20 years investigating all manner of aviation accidents involving aircraft from Cessna 150′s to Boeing 747′s. Ken is an active pilot holding ATP and CFI certificates with over 3500 flying hours. He flies a Cessna Turbo Skylane based at San Carlos, and yes, his flying record is free of any accidents, incidents and violations!

posted by Administrator3 Aug 31, 2005  02:08 PM
read (0 comments)