FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN15LA149 · Piper PA 32RT-300T

20 Feb 2015 · Lubbock, TX, United States

Piper PA 32RT-300T · Accident: runway excursion during takeoff

From Town & Country Airpark (F82) to Fort Worth Spinks Airport (FWS)

Report a problem

Event

NTSB case
CEN15LA149
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Piper PA 32RT-300T

Aircraft type
Piper PA-32
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N22267
Operator
Unknown
Onboard fatalities
Unknown
Route
From Town & Country Airpark (F82), Lubbock, TXTo Fort Worth Spinks Airport (FWS), Fort Worth, TX
Aircraft age
About 37 years (built 1978)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Takeoff · rejected takeoff
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Runway excursion
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Personnel issues › Action/decision

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The private pilot was conducting a short-field takeoff from the private, 3,500-ft-long paved runway. He reported that, upon reaching 80 knots indicated airspeed, he applied aft control yoke pressure to rotate; however, the airplane did not respond to his control input. The pilot attempted to rotate a second time using both hands on the yoke, but the airplane still did not rotate, and he aborted the takeoff as the airplane crossed the runway midpoint. The pilot was unable to stop the airplane before it overran the end of the runway into a plowed field, where the landing gear collapsed.

Postaccident examination did not identify any flight control system anomalies that would have precluded normal airplane operation; however, testing of the airplane's airspeed indicator revealed that it consistently read 5 knots higher than the calibrated test equipment. Consequently, the pilot likely attempted to rotate at an actual airspeed that was 5 knots lower than intended. The pilot and his passenger both reported that, shortly before takeoff, they heard someone broadcast on the airport frequency that the local surface wind was from the west-southwest at 4 knots with 14 knots gusts; however, a postaccident review of available weather data indicated the prevailing surface wind was likely from the west-northwest between 9 to 15 knots with gusts as high as 23 knots. Wind from this direction would have resulted in tailwind component of 4-8 knots, which would have increased the airplane's takeoff distance and the ground speed required to achieve liftoff. It is likely that the combination of the inaccurate airspeed indication and the tailwind component during takeoff resulted in the airplane's inability to achieve a normal takeoff rotation at the expected point on the runway.

Probable cause

The pilot's delayed decision to abort the takeoff after the airplane did not lift off as expected due to an inaccurate airspeed indication and tailwind condition, which resulted in a subsequent runway overrun.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN15LA149
Event ID
20150220X72637
Case number
CEN15LA149
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 0f94bd5476d54de4864fa6330c9a659ed529317b1a3cf0319e97170e830d4b5a; retrieved 2026-09-16T02:05:51.738Z.