FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI08CA036 · Piper PA-30

13 Oct 2007 · Lonoke, AR, United States

Piper PA-30 · Accident: hard landing

From North Little Rock Municipal Airport (ORK) to Country Air Estates Airport (1AR9)

Report a problem

Event

NTSB case
CHI08CA036
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-30

Aircraft type
Piper PA-30
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
N8635Y
Operator
Unknown
Onboard fatalities
Unknown
Route
From North Little Rock Municipal Airport (ORK), N Little Rock, ARTo Country Air Estates Airport (1AR9), Lonoke, AR
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
First occurrenceThe 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
Hard landing
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

  • Pilot in command › Flare, misjudged

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The pilot inadvertently executed a hard landing on runway 18 (3,800 feet by 100 feet, turf). The pilot stated that he landed short in order to avoid back taxiing and to minimize delays for other aircraft. The pilot stated he "landed hard and struck the left prop on the ground." He subsequently taxied safely to parking. A post accident inspection revealed damage to the left wing inboard of the engine, and to the left side of the fuselage under the pilot's side window. The pilot reported no failures or malfunctions related to the aircraft prior to the accident.

Probable cause

The pilot's misjudgment of the landing flare resulting in a hard landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI08CA036
Event ID
20080104X00018
Case number
CHI08CA036
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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, coordinates. 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: 717a137948338a15f6dcec16eceb851619bee22e8902116ce0e5fab31b78acd7; retrieved 2026-09-22T03:20:47.786Z.