FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN13CA434 · David W Oakes RV-7A

25 Jul 2013 · Charlottesville, IN, United States

David W Oakes RV-7A · Accident: abnormal runway contact during landing

From Shelbyville Municipal Airport (KGEZ) to Oakes Field (66IN)

Report a problem

Event

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

David W Oakes RV-7A

Aircraft type
David W Oakes RV-7
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
N1243A
Onboard fatalities
Unknown
Route
From Shelbyville Municipal Airport (KGEZ), Shelbyville, INTo Oakes Field (66IN), Charlottesville, IN
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 · flare/touchdown
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
Abnormal runway contact
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 › Task performance

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

NTSB narrative

While in the traffic pattern to land on a turf strip, the pilot noted that he was below a normal pattern altitude. During the final approach leg, the pilot had to add power to ensure the airplane would make the runway surface. Once the airplane made the end of the runway, the pilot pulled the throttle to idle and the airplane descended. The nosewheel touched first and bent aft. The airplane bounced and then landed hard. The nose of the airplane contacted the ground and the airplane flipped over, coming to rest in the inverted position. The pilot reported that there were no mechanical malfunctions or failure prior to the accident. Examination of the airplane revealed substantial damage to the vertical stabilizer and rudder.

Probable cause

The improper landing attitude which damaged the nosewheel and a resulted in a hard landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN13CA434
Event ID
20130725X44200
Case number
CEN13CA434
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: bec19aa0eb417f7a7d334ce526db5d2fafb65e6acea40549f3712f347b961adc; retrieved 2026-09-15T22:19:03.780Z.