Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

July 14, 2009 · Cessna T337 D · N21NC

Pittsburgh, PA

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
July 14, 2009
Injury Outcomes
No injuries (1 uninjured)
Location
Pittsburgh, PA
Aircraft
Cessna T337 D
Tail Number
N21NC
Operator
James H Boschma
Injuries
None
Aircraft Damage
Substantial
NTSB Number
ERA09CA402

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

NTSB Probable Cause

Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Descent/approach/glide path-Not attained/maintained - C

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

Flight

Event TypeAccident
Event Time13:20 EDT
Nearest AirportRock Airport (0nm)
Runway17
Runway Length3550 ft
Runway Width100 ft
Flight Plan FiledVFR
Flight Plan ActivatedNo
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftCessna T337 D
Tail NumberN21NC
Aircraft CategoryAir
DamageSubstantial
OperatorJames H Boschma
Operating RulePart 91
Engines2
Engine TypeReciprocating
Engine DetailsContinental · TSIO360-A · Reciprocating · 210 | Continental · TSIO360 · Reciprocating · 210
Seats4

People & Injuries

Injury SummaryNo injuries (1 uninjured)
Fatal0
Serious0
Minor0
Uninjured1
Total1
Crew 1Age 64 · Second Class · None

Conditions

ConditionsVMC
LightDaylight
Wind280° @ 4 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point0 C / 0 C
Altimeter30.15 inHg
Observation Time17:15
Weather SourceWFAC

Appendix: Source Data