CEN23LA362 · Piper PA-38-112
Piper PA-38-112 · Accident: loss of control on ground during takeoff
Event
- NTSB case
- CEN23LA362
- 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
- Event fatalities
- Unknown
- 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-38-112
- Aircraft type
- Piper PA-38
- 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
- N2351A
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- Aircraft age
- About 45 years (built 1978)
- 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
- Takeoff
- 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
- Loss of control on ground
- 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 › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot stated that prior to departure, he preflighted the airplane and found no anomalies. There no issues with his takeoff from the grass airstrip but once airborne, he felt uncomfortable to continue the flight due to hazy weather conditions. He then returned to the airstrip and landed without incident. He attempted a second takeoff with a left quartering crosswind, during which the airplane moved aggressively to the left. He applied additional right rudder control input, but the left turn increased, and the airplane impacted a cornfield about 1,000 ft down the runway. The airplane sustained substantial damage to the left- and right-wing spars and the fuselage. The pilot stated the accident could have been prevented by reducing the throttle setting or turning off the magnetos in a timely manner. Postaccident examination of the airplane revealed no mechanical anomalies that would have precluded normal operation.
Probable cause
The pilot’s failure to maintain directional control during takeoff that resulted in a runway excursion and an impact with the cornfield.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN23LA362
- Event ID
- 20230814192870
- Case number
- CEN23LA362
- 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, cause areas. 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: 31ee1a56e08032d9f97f3d572c73dcb4a40fee5eb0fec15274e56a58f8ab7ea8; retrieved 2026-09-16T18:00:13.585Z.