FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA10CA265 · Piper PA-24-260B

8 May 2010 · Carrollton, GA, United States

Piper PA-24-260B · Accident: landing area undershoot

From West Georgia Regional Airport / O V Gray Field (CTJ) to West Georgia Regional Airport / O V Gray Field (CTJ)

Report a problem

Event

NTSB case
ERA10CA265
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-24-260B

Aircraft type
Piper PA-24
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
N9231P
Operator
Unknown
Onboard fatalities
Unknown
Route
From West Georgia Regional Airport / O V Gray Field (CTJ), Carrollton, GATo West Georgia Regional Airport / O V Gray Field (CTJ), Carrollton, GA
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
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

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Action/decision

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

NTSB narrative

The pilot had just purchased a share in the airplane and was receiving a checkout with a certified flight instructor for insurance purposes. While practicing a landing with a simulated engine failure, the airplane landed about 90 feet short of the runway pavement. As the airplane proceeded forward, the nosewheel struck the runway edge, collapsing the nose gear. The pilot initiated a go-around and, on the second landing attempt and with no nosewheel, the airplane skidded to a stop, substantially damaging the engine firewall. The pilot reported there were no mechanical problems with the airplane. According to the pilot the firewall damage was likely sustained as the landing gear crossed the edge of the runway pavement. The pilot also noted that the majority of his flight experience has been in high-wing aircraft, where it is easier to see the main gear and runway.

Probable cause

The pilot's improper touchdown point during landing. Contributing to the accident was the certificated flight instructor's lack of remedial action.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA10CA265
Event ID
20100514X20928
Case number
ERA10CA265
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: 2397990ac611a027ff4859f62f92ddca4f4ab3208b87eadae083439627d1eddf; retrieved 2026-09-15T14:05:25.437Z.