WPR22LA320 · Cessna 152
Cessna 152 · Accident: collision during takeoff/landing
From Lodi Airport (1O3) to an unrecorded destination
Event
- NTSB case
- WPR22LA320
- 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
Cessna 152
- Aircraft type
- Cessna 152
- 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
- N49430
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Lodi Airport (1O3), Lodi, CATo not recorded
- Aircraft age
- About 44 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
- Collision during takeoff/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
- Personnel issues › Action/decision
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
During a discovery flight, the passenger asked the instructor if they could land at a private airstrip near his residence. The instructor was not familiar with this particular airstrip, nor had he consulted the airplane’s performance charts to determine if a safe landing and takeoff could be completed, but he still agreed to land. After landing to the west, the instructor turned the airplane around to depart to the east, as the wind appeared calm. He performed a short-field takeoff and observed the engine speed advance as the airplane began to move down the runway. When the airplane was about midfield, the instructor noticed that both his digital and analog airspeed indicators displayed 0 knots. Shortly after making this observation, after the airplane had traveled about 3/4 of the total length of the 1,300-ft-long runway, he decided to abort the landing. The airplane subsequently collided with a fence at the end of the runway and trees beyond the runway edge. A postaccident examination of the airplane did not reveal any preimpact mechanical anomalies with the airframe or engine that could have precluded normal operation. Examination of the pitot/static system did not indicate any failures or blockages. Performance computations indicated that the airplane had the required performance to complete the takeoff from a paved, level runway; however, the departure runway was composed of dirt, which the takeoff performance chart did not account for. Performance charts also indicated that the airplane did not have the distance necessary to stop when the instructor aborted the takeoff to avoid impacting the fence at the end of the runway. Therefore, the instructor’s delayed decision to abort the takeoff resulted in a collision with a fence and a tree. His decision to land at the unfamiliar airstrip without determining whether the airplane’s performance capabilities were adequate to perform a safe takeoff and landing contributed to the accident.
Probable cause
The flight instructor’s delayed decision to abort the takeoff, which resulted in impact with a fence and a tree. Contributing to the accident was the instructor’s decision to land at the unfamiliar airstrip without determining whether it was within the airplane’s performance capabilities.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR22LA320
- Event ID
- 20220829105823
- Case number
- WPR22LA320
- 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, coordinates, 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: 1a0b264d745d4a66fa52a2342c91427ea53cb71d3af428c2a41778ddd01b8cc4; retrieved 2026-09-16T15:49:55.548Z.