FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN24LA132 · Pietenpol AIRCAMPER

6 Mar 2024 · Lockhart, TX, United States

Pietenpol AIRCAMPER · Accident: loss of control in flight during takeoff

From Lockhart Municipal Airport (50R) to an unrecorded destination

Report a problem

Event

NTSB case
CEN24LA132
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
0
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

Pietenpol AIRCAMPER

Aircraft type
Pietenpol AIRCAMPER
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
N7710J
Operator
Unknown
Onboard fatalities
Unknown
Route
From Lockhart Municipal Airport (50R), Lockhart, TXTo not recorded
Aircraft age
About 12 years (built 2012)
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 in flight
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
  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Task performance

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

NTSB narrative

The pilot reported that, shortly after takeoff from runway 18, the airplane moved laterally to the left. The pilot tried to correct by inputting right rudder and right aileron. The left wing rose abruptly, and the airplane crossed to the right side of the runway. The airplane lost lift and landed in the grass on the right side of the runway. The pilot attempted to stop, but the airplane slid into a drainage ditch. The airplane sustained substantial damage to the left wing. The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation. The pilot reported swirling wind contributed to the loss of control. The reported wind at an airport 10 miles northwest was 150° at 6 kts.

Probable cause

The pilot’s failure to maintain control during after takeoff.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN24LA132
Event ID
20240311193913
Case number
CEN24LA132
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: 6ccecb5deb532c6095177e6c970c11266774d4dfd9fcd9d7df23d888f8eded84; retrieved 2026-09-16T18:34:51.792Z.