LAX02LA023 · Piper PA-18-150
Piper PA-18-150 · Accident: in flight collision with object on approach
From Lodi Airport (1O3) to Herald, CA
Event
- NTSB case
- LAX02LA023
- 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-18-150
- Aircraft type
- Piper PA-18
- 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
- N9461P
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Lodi Airport (1O3), Lodi, CATo Herald, CA
- 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
- Approach · VFR go-around
- First occurrenceThe 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
- In flight collision with object
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s); Stall/mush
- 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
- Pilot in command › Go-around, delayed
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The airplane impacted trees at the departure end of the runway. The pilot reported he was practicing approaches to landings and then going around without landing. The airstrip on his ranch was 800 feet long and there was a 6-knot quartering tailwind. His third approach was too far down the runway and when he added power to go around, "The power was not there. The aircraft was mushing. I pushed the stick forward in order to get the plane to fly, but to no avail. The aircraft hit the trees at 10 [feet] above ground level." Elsewhere on the report form, in the section entitled "Mechanical Malfunction Failure" he checked the box "no."
Probable cause
The pilot's delay initiating a go-around during a downwind approach to a short runway.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX02LA023
- Event ID
- 20011113X02227
- Case number
- LAX02LA023
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: 13c00c327a70d160e651c856d03c2b4ef7ddf500db83186da2217fc9fb3f846e; retrieved 2026-09-22T11:25:35.016Z.