CEN09LA173

NTSB accident investigation · Piper PA-31T · Pueblo, CO · February 23, 2009

Accident · No injuriesLimited investigationFinal report
Date
February 23, 2009, 16:44 local (23:44 UTC)
Place
Pueblo, CO
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N171AFPiper PA-31T
Defining event
Landing-flare/touchdown: Abnormal runway contact
Weather
Visual (VMC) · Day
Status
Completed · report June 22, 2009
Report
Approved by Office Director
NTSB office
Central Region
Parties
FAA Flight Standards District Office
FAA report
20090223001479A
Case key
73384

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.

On this page

Probable cause

The pilot's improper flare and recovery from a bounced landing.

Findings · 2

NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.

Performance/control parameters: landing flareAircraft › Aircraft oper/perf/capability · Incorrect use/operationPiper PA-31T: 1 caseAll aircraft: 1,285 casesProbable cause
Use of equip/info: aircraft controlPersonnel issues › Task performance · PilotPiper PA-31T: 4 casesAll aircraft: 9,295 casesProbable cause

Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.

Analysis

The pilot said that while en route, he obtained Automatic Terminal Information Alpha that reported moderate to strong westerly and gusting winds. A Low-Level Wind Shear advisory was also in effect. He maneuvered the airplane for an extended right base to runway 26R and configured the airplane for landing. Due to the reported winds and advisory, he elected to approach 5 to 10 knots faster, or approximately 135 to 140 knots indicated airspeed. The approach and descent were normal, and he made several power changes to maintain airspeed and rates of descent consistent with the reported wind conditions. As he flared for landing, he thought that he saw something on the runway. There was a sudden loss of lift, and he adjusted the pitch slightly up to compensate. The touchdown was "unusually hard" and the airplane bounced. The airplane then became hard to control in the pitch and yaw axes, porpoising "violently" 4 or 5 times before he was able to keep it on the ground and exit the runway. Postaccident inspection revealed that the right wing was buckled, some engine mounts were broken, the cowling was wrinkled, and the engine was drooping from its mounts. Airport personnel drove the length of the runway but found no debris.

Factual narrative

On February 23, 2009 at 1644 mountain standard time, a Piper PA-31T, N171AF, registered to and operated by Aero Oro LLC and piloted by an airline transport pilot, was substantially damaged when the right propeller struck the runway and the airplane began porpoising before landing hard at Pueblo Memorial Airport (PUB), Pueblo, Colorado. Visual meteorological conditions prevailed at the time of the accident. The positioning flight was being conducted under the provisions of Title 14 Code of Federal Regulations (CFR) Part 91 without a flight plan. The pilot, the sole occupant aboard, was not injured. The positioning flight originated at Colorado Springs, Colorado, approximately 1620, and was en route to PUB. The pilot said that while en route, he obtained ATIS (Automatic Terminal Information) Information Alpha that reported moderate to strong westerly and gusty winds. A Low Level Wind Sheer (LLWS) Advisory was also in effect. He maneuvered the airplane for an extended right base to runway 26R, and configured the airplane for landing. Due to the reported winds and advisory, he elected to approach 5 to 10 knots faster, or approximately 135 to 140 KIAS (knots indicated airspeed). The approach and decent were "normal," and he made several power changes to maintain airspeed and rates of decent consistent with the reported wind conditions. As he flared for landing, he thought he saw something on the runway. There was a sudden loss of lift, and he adjusted the pitch slightly up to compensate. The touchdown was "unusually hard" and the airplane bounced. The airplane then became hard to control in the pitch and yaw axes, porpoising "violently" 4 or 5 times before he was able to keep it on the ground and exit the runway. Post-accident inspection revealed the right wing was buckled, some engine mounts were broken, the cowling was wrinkled, and the engine was drooping from its mounts. Airport personnel drove the length of the runway but found no debris.

Aircraft

Registration
N171AF
Reported as
Piper PA-31T
Category
Airplane
Serial number
31T-7920089
Airframe hours
6,249
Engine
Pratt & Whitney PT6A-28, 620 horsepower, turbo prop
Damage
Substantial damage
Flight
Positioning · Part 91
Operator
Aero Oro LLC
Registered owner
Aero Oro LLC
Airworthiness certificate
Standard, Normal
Last inspection
100 hour · September 29, 2008 · 100 hours before
Departed
COS · Colo. Springs, CO
Destination
PUB · Pueblo, CO
Airport
PUB · Pueblo Memorial, runway 26R, 10,496 × 150 ft, asphalt

Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

Flight crew

As NTSB recorded them. NTSB leaves out names.

Role
Pilot
Age
62
Injuries
None
Certificates
Flight engineer, Military, Commercial, Airline transport
Airplane ratings
Multi-engine land, Single-engine land
Instrument ratings
Helicopter, Airplane
Medical
Class 1, Without waivers/limitations
Last flight review
June 13, 2008
Seat
Left
Flight hours
14,387 total · 105 in this make and model · 3,500 as pilot in command · 30 in the last 90 days · 20 in the last 30 days · 7 in the last 24 hours

Weather

Conditions
Visual (VMC) · Day
Wind
300° at 17 knots, gusting 25
Visibility
10 statute miles
Lowest ceiling
11,000 ft broken
Temperature
68 °F, dew point 30 °F
Altimeter
29.95 inHg
Observed at
PUB

FAA reports on this event · 1

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.