FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN12CA671 · Piper PA-28R-200

29 Aug 2012 · Goldsby, OK, United States

University of Oklahoma Piper PA-28R-200 · Accident: landing area undershoot

From University of Oklahoma Westheimer Airport (OUN) to David Jay Perry Airport (1K4)

Report a problem

Event

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

Piper PA-28R-200

Aircraft type
Piper PA-28
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
N7602C
Onboard fatalities
Unknown
Route
From University of Oklahoma Westheimer Airport (OUN), Norman, OKTo David Jay Perry Airport (1K4), Goldsby, OK
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
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
Landing area undershoot
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

  • Personnel issues › Action/decision

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

NTSB narrative

The commercial pilot was taking a practical test to become a flight instructor and was demonstrating a simulated short field landing over a simulated 50-foot obstacle. The commercial pilot reported that he had planned to touch down on or within 100 feet past the numbers painted on the runway. The painted numbers were 60 feet long and about 18 feet from the approach end of the runway. The airplane touched down short of the intended landing spot, and the right main landing gear struck the edge of the runway surface, causing a loud “bang” that both the commercial pilot and the pilot examiner reported hearing. A postflight examination showed that the hard landing caused substantial damage to the right wing when three wing ribs separated from the spar web and partially penetrated through the upper skin. The commercial pilot added that the accident could have been avoided if he had picked a touchdown spot further away from the approach end of the runway.

Probable cause

The commercial pilot did not attain the proper touchdown point during the landing, which resulted in a premature touchdown and an impact with the edge of the runway surface.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN12CA671
Event ID
20121011X71031
Case number
CEN12CA671
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: b23d12c890d21390c25f390dc528a9f2eea26b3e0032011a5eee2a8cae3c7d28; retrieved 2026-09-15T20:08:37.507Z.