LAX01LA197 · Piper PA-28-180
Piper PA-28-180 · Accident: in flight collision with object while maneuvering
From O61 · Cameron Park, CA to Lodi Airport (1O3)
Event
- NTSB case
- LAX01LA197
- 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-180
- 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
- N4848L
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From O61 · Cameron Park, CATo Lodi Airport (1O3), Lodi, 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
- Maneuvering
- 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)
- 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 › Altitude/clearance, not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot was en route on a cross-country flight when the airplane collided with a tree about 12 miles from the departure airport. The pilot sustained head injuries and did not recall the circumstances leading to the accident. The accident site area is generally flat grass lands with scattered medium height trees. The first identified point of contact was a tree whose top branches were on the ground along with an outboard section of the right wing. A piece of right wing flap was near the first identified ground scar. The ground scar continued to the main wreckage, and various pieces of the airplane were in the debris field. Recorded radar data was obtained and reviewed. The departure airport had an elevation of 1,286 feet. A radar target consistent with the expected time and location of the accident flight appeared northwest of the airport on a northwest track and climbing through 1,700 feet. The target turned to the southwest, and maintained an altitude that varied between 2,300 to 2,500 feet. About 5 minutes into the flight the target track shifted left of course and began descending. The last recorded radar return occurred about 200 feet above ground level and on course for the accident site. There was no evidence of premishap catastrophic mechanical malfunction or fire. The carburetor and fuel pump contained fuel. No anomalies were found that would have precluded normal engine operation. The propeller remained attached to the crankshaft. The blades displayed leading edge gouging, torsional twisting, chordwise striations across the cambered surface, and trailing edge S-bending.
Probable cause
the pilot's failure to maintain an adequate clearance altitude from en route obstructions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX01LA197
- Event ID
- 20010607X01091
- Case number
- LAX01LA197
- 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, coordinates. 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: e95b565d008a2016c012692b37a7e8afe615e5428c2dcac84d434b9419190409; retrieved 2026-09-21T10:07:16.763Z.