17 Feb 2013: CESSNA 195

17 Feb 2013: CESSNA 195 (N4426C) — Unknown operator

No fatalities • Austin, TX, United States

Probable cause

The pilot's use of an excessive taxi speed, which resulted in the airplane overrunning the end of the unlit taxiway after the failure of the right wing landing light.

— NTSB Determination

Accident narrative

On February 16, 2013, about 2145 central standard time, a Cessna model 195 airplane, N4426C, was substantially damaged while taxiing at the Austin Executive Airport (EDC), Austin, Texas. The private pilot and passenger were not injured. The airplane was registered to and operated by the pilot, under the provisions of 14 Code of Federal Regulations Part 91, without a flight plan. Night visual meteorological conditions prevailed for the personal flight. The flight had the intended destination of Gillespie County Airport (T82), Fredericksburg, Texas.The pilot reported that the accident occurred as he was taxiing on the unlit taxiway that paralleled runway 13-31. As the airplane approached the end of the taxiway, adjacent to the runway 13 threshold, the right wing landing light became inoperable, significantly reducing the pilot's forward visibility in the dark night conditions. The pilot cycled the right wing landing light switch as he applied wheel brakes; however, the light did not illuminate. The pilot stated that he was unable to stop the airplane before it departed the end of the taxiway and traveled down an embankment. He did not recall seeing any reflective markers identifying the end of the taxiway. Although the airplane was equipped with two landing lights, one on each wing, the pilot reported that he avoided using both lights simultaneously during taxi operations because such use rapidly depletes the battery charge at the lower engine power settings required to taxi.

According to information provided by the EDC airport manager, the unlit taxiway that serviced runway 13-31 was marked with blue reflective posts that were 24-inches tall. These blue reflective posts were spaced at 31-foot intervals along the taxiway edges only. The end of the taxiway was identified by red reflectors that were installed at ground level. Additionally, an airport survey plot indicated that there was a 16-foot descending embankment, specified to have a 3:1 graded slope, located immediately adjacent to the northwest end of the taxiway and the runway 13 threshold. The use of reflective posts to identify the taxiway and the descending embankment were not identified in the Federal Aviation Administration (FAA) Airport Facility Directory.

According to the FAA Airplane Flying Handbook, the requirements for safe taxi operations include the ability to recognize potential hazards in time to avoid them, as well as the ability to stop or turn where and when desired. The handbook further stipulates that taxi speeds should be slow enough that the airplane can be stopped promptly and "without undue reliance on the brakes."

At 2155, the airport's automated surface observing system reported: wind 210 degrees true at 4 knots, visibility 10 miles, sky clear, temperature 8 degrees Celsius, dew point -3 degrees Celsius, and an altimeter setting 30.24 inches of mercury.

The United States Naval Observatory reported that sunset and end of civil twilight at the airport on the night of the accident occurred at 1820 and 1844, respectively. At 2145, the waxing crescent moon was visible to the west of airport, located about 36 degrees above the horizon, with about 44 percent of the moon's visible disk illuminated. The moonset occurred about 3 hours after the accident at 0046.

In response to the accident, the airport authority agreed to purchase additional blue reflective posts to more adequately mark the limits of the unlit taxiway. Additionally, the FAA agreed to amend its Airport Facility Directory to reflect that the taxiway edges were marked by reflector posts and that the northwest end of runway 13-31 and parallel taxiway had a 16-foot descending embankment beginning at the end of the pavement.

Contributing factors

  • factor Exterior lighting — Failure
  • cause Incorrect use/operation
  • cause Pilot
  • Effect on operation

Conditions

Weather
VMC, wind 210/04kt, 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.