27 Jan 2014: BEECH C90 UNDESIGNAT — Axis Jet

27 Jan 2014: BEECH C90 UNDESIGNAT (N350WA) — Axis Jet

No fatalities • Columbia, CA, United States

Probable cause

The pilot’s unstabilized night visual approach, which resulted in a hard landing and the collapse of all three landing gear.

— NTSB Determination

Accident narrative

On January 27, 2014, about 0530 Pacific standard time (PST), a Beech C90 King Air, N350WA, experienced a hard landing at Columbia Airport (O22), Columbia, California. Axis Jet was operating the airplane under the provisions of 14 Code of Federal Regulations (CFR) Part 91. The commercial pilot and the airline transport pilot were not injured; the airplane sustained substantial damage by impact forces and the post-crash fire. The cross-country aero-medical positioning flight departed Sacramento, California, about 0500. Visual night meteorological conditions prevailed, and an instrument flight rules (IFR) flight plan had been filed.

The crew reported that the purpose of the flight was to pick up an aero-medical harvest team coordinator at O22 and fly them to San Luis Obispo, California. The crew reported no anomalies with the flight, airplane, or the approach to land at O22. The flying pilot (FP) was seated in the left seat and the non-flying co-pilot (NFP) was assisting the FP by performing the checklists and reporting speeds and other cockpit information to the FP. The NFP reported that after a turn to final approach full flaps were lowered, and that the airplane was in a "wings level, stabilized approach." The NFP also reported that on short final the gear was confirmed down for the 3rd time, and that the airspeed indicator indicated 110 knots. The pilots both described the landing as firm, and that as soon as the airplane contacted the runway they heard a loud bang followed by the airplane's belly scraping the runway. The airplane slid down the runway about 825 feet coming to rest on the left side of the runway. Both pilots observed fire on the left side of the airplane near the engine nacelle and evacuated the airplane. The airplane was subsequently consumed by the postaccident fire.

According to the Federal Aviation Administration (FAA) the crew reported after they identified the airport, activated the airport lighting system, and then canceled their instrument flight plan for a visual approach. The automated weather observation system (AWOS), reported more than 10 miles visibility, clear skies, and no wind. The temperature at the time was approximately 4 degrees Celsius with a dew point of -4 Celsius. The NFP reported that at approximately 5 miles to the airport the FP called for the 1st notch of flaps and then requested gear down on the final approach segment of the traffic pattern. Both pilots agree the landing gear was extended, and three green lights were illuminated indicating the gear was in fact down and locked. The NFP indicated that his eyes were in the cockpit calling out airspeeds, checking that the aircraft was in landing configuration, and watching the GPS unit for terrain warnings. The FP indicated that he was using the vertical approach slope indicator (VASI) initially for guidance but drifted below the glide path and did not correct back up to the glide path.

FAA investigators examined the wreckage at the accident scene. The first identified points of contact (FIPC) were three ground scars consistent with the geometry of the main landing gear and the nose wheel. The FIPC was located on the runway about 100 feet short of the displaced threshold. Broken components of the airplane landing gear were located in a debris field 175 feet to 565 feet beyond the FIPC. According to the FAA the gear was in the down and locked position at the time of the accident. Due to the postaccident fire examination of the airplane could not be performed.

Contributing factors

  • cause Descent/approach/glide path — Not attained/maintained
  • cause Pilot
  • cause Pilot
  • Effect on personnel

Conditions

Weather
VMC, vis 10sm

Loading the flight search…

What you can do on Flight Finder

  • Search flights between any two airports with live fares.
  • By aircraft — pick a plane model (e.g. Boeing 787, Airbus A350) and see every route it flies from your origin.
  • Route map — click any airport worldwide to explore its destinations, or draw a radius to find nearby airports.
  • Global aviation safety — aviation accident database, 5,200+ records since 1980, with map and rankings by aircraft and operator.
  • NTSB safety feed — recent U.S. aviation accidents and incidents from the official NTSB CAROL database, updated daily.

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.