CEN10CA237 · Piper PA-28-140
Piper PA-28-140 · Accident: abnormal runway contact during landing
From Sugar Land Regional Airport (KSGR) to KEYQ · Houston, TX
Event
- NTSB case
- CEN10CA237
- 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-28-140
- 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
- N4397T
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Sugar Land Regional Airport (KSGR), Sugar Land, TXTo KEYQ · Houston, TX
- 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
According to a telephone conversation and subsequent written statement submitted by the pilot, during the night landing roll on runway 27 (3,455 feet by 40 feet, asphalt), the pilot was not able to stop the airplane. The airplane impacted a fence and vegetation at the departure end of the runway. The pilot stated that the runway surface was wet at the time of the landing. According to a statement provided to the Federal Aviation Administration (FAA) by the pilot, the airplane touched down adjacent the fuel pumps on the ramp. An examination of the airplane revealed that the left and right wings sustained substantial damage to several ribs and the spars. The fuselage and firewall were wrinkled. An examination of the airplane and its systems, conducted by an FAA airworthiness inspector, revealed no anomalies. Rain was recorded six hours prior to the accident; however, no rain was recorded just prior to the accident. Examination of the pilot's flight records revealed that he was not current for passenger carriage at night.
Probable cause
The pilot's failure to attain the proper touchdown point which resulted in an overrun.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN10CA237
- Event ID
- 20100427X22650
- Case number
- CEN10CA237
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2010-04-30.
- API snapshot SHA-256: 09ef0240b4e32844428638816abc8c13a7e4e15481b705bd716a900c90a5224f; retrieved 2026-09-15T13:55:33.147Z.