ERA09CA402

NTSB accident investigation · Cessna T337 · Pittsburgh, PA · July 14, 2009

Accident · No injuriesData collectionFinal report
Date
July 14, 2009, 13:20 local (17:20 UTC)
Place
Pittsburgh, PA
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N21NCCessna T337
Defining event
Landing-landing roll: Runway excursion
Weather
Visual (VMC) · Day
Status
Completed · report October 19, 2009
Report
Approved by Office Director
NTSB office
Eastern Region Aviation
Parties
FAA/FSDO
Case key
74278

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 failure to obtain the proper touchdown point during 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: descent/approach/glide pathAircraft › Aircraft oper/perf/capability · Not attained/maintainedCessna T337D: 1 caseAll aircraft: 809 casesProbable cause
Use of equip/info: aircraft controlPersonnel issues › Task performance · PilotCessna T337D: 1 caseAll 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

While on the downwind leg of the airport traffic pattern for runway 17, the pilot was advised over the airport traffic frequency that winds were favoring runway 35. The pilot elected to continue the approach to runway 17, since he could "clearly see the wind sock," which was indicating a "direct crosswind." During the landing flare, the pilot encountered an "updraft" and landed approximately "half way" down the 3,500-foot- long runway. Upon touchdown, he retracted the wing flaps, applied "very strong" pressure on the brakes, and made "shallow turns" in an attempt to stop the airplane. The airplane ran off the end of the runway, and came to rest in a ditch approximately 10 to 20 feet beyond the runway edge. A Federal Aviation Administration inspector who examined the airplane after the accident reported that it sustained substantial damage to the engine firewall, and exhibited extensive wrinkling and buckling of the fuselage, particularly at the wing roots. The pilot reported no mechanical anomalies. The nearest weather reporting station, located 12 nautical miles northwest of the accident site, reported wind direction variable between 280 degrees and 350 degrees at 7 knots at the time of the accident. The pilot stated that he should have landed on runway 35, since there were "several hills" on the approach to runway 17, and "turbulence and updrafts made speed control and altitude control difficult." In addition, runway 17 had a "downhill slope."

Factual narrative

While on the downwind leg of the airport traffic pattern for runway 17, the pilot was advised over the airport traffic frequency that winds were favoring runway 35. The pilot elected to continue the approach to runway 17, since he could "clearly see the wind sock," which was indicating a "direct crosswind." During the landing flare, the pilot encountered an "updraft" and landed approximately "half way" down the 3,500-foot long runway. Upon touchdown, he retracted the wing flaps, applied "very strong" pressure on the brakes, and made "shallow turns" in an attempt to stop the airplane. The airplane ran off the end of the runway, and came to rest in a ditch approximately 10 to 20 feet beyond the runway edge. A Federal Aviation Administration inspector who examined the airplane after the accident reported that it sustained substantial damage to the engine firewall, and exhibited extensive wrinkling and buckling of the fuselage, particularly at the wing roots. The pilot reported no mechanical anomalies. The nearest weather reporting station, located 12 nautical miles northwest of the accident site, reported wind direction variable between 280 degrees and 350 degrees at 7 knots at the time of the accident. The pilot stated that he should have landed on runway 35, since there were "several hills" on the approach to runway 17, and "turbulence and updrafts made speed control and altitude control difficult." In addition, runway 17 had a "downhill slope."

Aircraft

Registration
N21NC
Reported as
Cessna T337 (D)
Category
Airplane
Serial number
337-1022
Airframe hours
2,456
Engines
Continental TSIO360, 210 horsepower, reciprocatingContinental TSIO360-A, 210 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Operator
James H Boschma
Registered owner
Bosh Aviation LLC
Airworthiness certificate
Standard, Normal
Last inspection
Annual · July 14, 2008
Departed
3M5 · Brownsboro, AL
Destination
9GI · Pittsburgh, PA
Flight plan
VFR
Airport
9GI · Rock Airport, runway 17, 3,550 × 100 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
64
Injuries
None
Certificate
Commercial
Airplane ratings
Single-engine land, Multi-engine land
Instrument ratings
Airplane
Medical
Class 2, With waivers/limitations
Last flight review
July 4, 2009
Seat
Left
Flight hours
4,425 total · 381 in this make and model

Weather

Conditions
Visual (VMC) · Day
Wind
280° at 4 knots
Visibility
10 statute miles
Lowest ceiling
None
Altimeter
30.15 inHg
Observed at
BTP, 12 nm away

Docket · 3

The files NTSB released with the investigation on August 24, 2009, on NTSB’s docket system: statements, records, photos and specialists’ reports. 862 KB in all.