FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA09CA402 · Cessna T337 D

14 Jul 2009 · Pittsburgh, PA, United States

Cessna T337 D · Accident: runway excursion during landing

From Moontown Airport (3M5) to 9GI · Pittsburgh, PA

Report a problem

Event

NTSB case
ERA09CA402
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

Cessna T337 D

Aircraft type
Cessna 337
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
N21NC
Operator
James H Boschma · private individual
Onboard fatalities
Unknown
Route
From Moontown Airport (3M5), Brownsboro, ALTo 9GI · Pittsburgh, PA
Aircraft age
Not recorded
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
Landing · landing roll
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

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Task performance

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

NTSB 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."

Probable cause

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

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA09CA402
Event ID
20090714X95017
Case number
ERA09CA402
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: e696d6d6bfdacddb9ec0794d6dd0169113ce534405ba8ace7eda3981595b1fc4; retrieved 2026-09-15T11:51:41.817Z.