The U.S. aircraft register, updated daily
Accidents · NTSB ERA14LA149 · Final report

Piper Aircraft INC PA-46-500TP accident near Alabaster, Alabama, February 23, 2014

On February 23, 2014, a 2007 Piper Aircraft INC PA-46-500TP, registered N3061J, was substantially damaged in an accident during takeoff near Alabaster, Alabama (Shelby County Airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 5 people were on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot’s delay in aborting the takeoff following the loss of directional control early in the takeoff roll due to a deflated left main landing gear tire.

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

What the record shows

Date
February 23, 2014
Place
Alabaster, Alabama · Shelby County Airport · map
Type
Accident
Injuries
No one was hurt; 5 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Piper Aircraft INC PA-46-500TP, built 2007
Registration
N3061J · no longer on the register · serial 4697322
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, while taxiing the airplane onto the runway with the flaps extended for takeoff, he applied power and then began the takeoff roll. While the airplane was at 60 knots and on the runway centerline, he noticed a sudden pulling to the left and "excessive vibration." He applied full right rudder for about 1 to 2 seconds with no effect. Unable to regain directional control, he reduced power, placed the propeller to the "beta" position, and pulled on the control yoke while applying full brakes and right rudder input. Runway marks indicated that the airplane began veering left about 1,000 ft down the runway, continued off the left side of the runway, and then remained in the grass for about 500 ft. The airplane then travelled back onto the runway, began veering left again, and then continued off the left side of the runway into the grass, turned right, travelled back onto the runway again, and then came to rest upright about 2,761 ft from the approach end of the runway. Both main landing gear tires were found deflated, and the tube of the left main tire was found in numerous pieces. Examination of the airplane about 10 days after the accident revealed that the nose landing gear tire was inflated to 55 pounds per square inch (psi); the minimum specification is 70 psi. Given witness statements indicating that they heard takeoff power being applied up to the point of the second runway excursion and the distance between the location of the first point of loss of directional control and the resting position of the airplane (about 1,761 ft), it is likely that the pilot did not abort the takeoff until after the second runway excursion. If the pilot had aborted the takeoff immediately after the first runway excursion, it is likely that the airframe would not have been damaged. The pilot's report of the airplane pulling left and vibrating early in the takeoff roll is consistent with a deflated left main landing gear tire.

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 takeoff defining event
  2. Runway excursion during takeoff (rejected takeoff)

The NTSB's findings

  • cause Personnel issues › Action/decision › Info processing/decision › (general) › Pilot
  • cause Personnel issues › Action/decision › Action › Delayed action › Pilot
  • cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Directional control › Not attained/maintained
  • cause Aircraft › Aircraft systems › Landing gear system › Tire casing › Not specified

Pilot

  • Certificate: private
  • Ratings: single-engine land; instrument: airplane
  • Flight time: 1,074 hours in all; 173 in this make and model; 47 in the last 90 days; 12 in the last 30 days; 1,074 as pilot in command
  • Last flight review: February 14, 2014
  • Medical certificate: Class 3 (without waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 867.3 hours
  • Last inspection: annual inspection, November 22, 2013; 65 hours since
  • Maximum gross weight: 5,092 lb
  • Landing gear: retractable
  • Engine: P&W Canada PT6A-42A (turboprop); 669 hours total
  • Operator: Jb Piper Meridian LLC

The flight

  • Departed from: EET Alabaster AL
  • Destination: BFM Mobile AL
  • Flight plan: IFR
  • Runway 16, 5,000 ft by 75 ft

Weather at the time

  • Light: not reported
  • Wind: from 150° at 3 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 63°F (17°C), dew point 23°F (-5°C)
  • Altimeter: 30.04 inHg
  • Observation at 11:53 pm from EET

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers4

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

10 documents, released by the NTSB on December 31, 2014. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.