The U.S. aircraft register, updated daily · Carbon Free Flight by 2050
Accidents · NTSB CEN10CA490 · Final report

Piper PA-46-310P accident near Austin, Texas, August 20, 2010

On August 20, 2010 at about 10:15 pm local time, a Piper PA-46-310P, registered N106LB, was substantially damaged in an accident during landing (landing roll) near Austin, Texas (Lakeway airport). It was a personal flight under general aviation rules (Part 91). 1 person was seriously injured; 1 other was unhurt. The weather was visual conditions (good weather).

Preview. This page is not yet listed for search engines.

The NTSB's probable cause their words, unchanged

The pilot's failure to maintain a stabilized approach, which resulted in a loss of control on landing with a tailwind.

Source: NTSB aviation accident database, copy made October 4, 2026. Docket and reports at the NTSB.

What the record shows

Date
August 20, 2010 · about 10:15 pm local time
Place
Austin, Texas · Lakeway · map
Type
Accident
Injuries
1 person was seriously injured; 1 other was unhurt.
Weather
visual conditions (good weather)
Aircraft
Piper PA-46-310P · all PA-46-310Ps on the register
Registration
N106LB · registry record · serial 46-8508093
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

The pilot reported that he was distracted by his passenger, who was seated in the back of the airplane. He landed with an 18 knot tailwind and, after being unable to slow the airplane, attempted to abort the landing by abruptly applying full engine power. He advanced the throttle too fast and the engine power did not respond. He realized that he had flooded the engine and maneuvered the airplane away from approaching obstacles at the end of the runway. The airplane continued off the runway and crossed a ditch on to a golf course before coming to a stop; it sustained structural damage to the left wing. The pilot reported that there were no preimpact mechanical deficiencies with the airplane.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Loss of control on ground during landing (landing roll) defining event

The NTSB's findings

  • cause Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 330 hours in all; 130 in this make and model
  • Medical certificate: Class 3

The aircraft

  • Seats: 6
  • Landing gear: fixed
  • Engine: Cont Motor TSIO-520 SER (piston); 0 hours total
  • Operator: Lhbg Aviation LLC

The flight

  • Departed from: LIT Little Rock AR
  • Destination: 3R9 Austin TX
  • Flight plan: not recorded
  • Runway 34

Weather at the time

  • Light: daylight
  • Temperature: 0°F (-18°C), dew point 0°F (-18°C)

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.

About this page

Everything above comes from the NTSB's public accident database: the narrative, probable cause and findings are the NTSB's own words, and the coded tables behind its report (pilot, aircraft, flight, weather, injuries, sequence of events) are written out in plain English. Pilots' ages, home towns and medical details are left out on purpose. The documents and photographs are the NTSB's docket, the folder of records gathered during the investigation, shown as the NTSB released them (the NTSB redacts some personal details first) and listed under the NTSB's own titles. This site's own text never names pilots, passengers or anyone else involved. A preliminary report describes what is known soon after the event and can change; the final report, with the probable cause, usually follows one to two years later and this page is refreshed when it does. Case number CEN10CA490.