# NTSB ERA09CA402: Cessna T337, N21NC, Pittsburgh, PA, July 14, 2009

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Data collection · Final report
- Date: July 14, 2009, 13:20 local (17:20 UTC)
- Place: Pittsburgh, PA
- Coordinates: 40.603332, -79.82611 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=40.6033&lon=-79.8261&mi=10
- Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping)
- Defining event: [Landing-landing roll: Runway excursion](https://openairdocs.org/ntsb-events/300)
- Highest injury: No injuries
- Injuries: 1 uninjured
- Status: Completed, report October 19, 2009
- Report: Approved by Office Director
- NTSB office: Eastern Region Aviation
- Parties: FAA/FSDO
- NTSB case key (mKey): 74278
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA09CA402
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/74278/pdf
- NTSB docket: https://data.ntsb.gov/Docket?ProjectID=74278
- Page: https://openairdocs.org/ntsb/ERA09CA402

## Probable cause

The pilot's failure to obtain the proper touchdown point during landing.

## Findings

NTSB's coded findings; those marked are part of the probable cause.

- [Performance/control parameters: descent/approach/glide path](https://openairdocs.org/ntsb-findings/01062040): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Cessna T337D, 1 case](https://openairdocs.org/ntsb-findings/01062040/cases.md?model=2075719), [All aircraft, 809 cases](https://openairdocs.org/ntsb-findings/01062040/cases.md)
- [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Cessna T337D, 1 case](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=2075719), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md)

## Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event best describes what happened.

- [Landing-flare/touchdown: Landing area overshoot](https://openairdocs.org/ntsb-events/380); cases with it: [Cessna T337D, 1 case](https://openairdocs.org/ntsb-events/380/sequence.md?model=2075719), [All aircraft, 400 cases](https://openairdocs.org/ntsb-events/380/sequence.md)
- [Landing-landing roll: Runway excursion](https://openairdocs.org/ntsb-events/300) (defining event); cases with it: [Cessna T337D, 1 case](https://openairdocs.org/ntsb-events/300/sequence.md?model=2075719), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md)
- [Landing-landing roll: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Cessna T337D, 2 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=2075719), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md)

## 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](https://openairdocs.org/deregistered/N21NC-2010-02-11), registration cancelled 2010-02-11, S/N 337-1022, built 1968 (OpenAirDocs)
- Reported make and model: CESSNA T337 (D)
- Registry model: [Cessna T337D](https://openairdocs.org/model/cessna-t337d) (registry code 2075719) (OpenAirDocs)
- Registry engine: [Continental IO-360 series](https://openairdocs.org/engine/continental-io-360-series) (registry code 17025, reciprocating) (OpenAirDocs)
- Category: Airplane
- Serial number: 337-1022
- Airframe hours: 2456
- Engines: CONTINENTAL TSIO360 210 horsepower reciprocating; CONTINENTAL 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

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 64; injuries: none; 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 files)

The files NTSB released with the investigation on August 24, 2009, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=74278. 862 KB in all.

- Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 711 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40316388&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF
- FAA Inspector Interview - Memorandum for Record (item 2, .PDF, 38 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40316629&FileExtension=.PDF&FileName=FAA%20Inspector%20Interview%20-%20Memorandum%20for%20Record-Redacted.PDF
- Weather Reports and Records (item 3, .PDF, 113 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40316387&FileExtension=.PDF&FileName=Weather%20Reports%20and%20Records-Master.PDF

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.