LAX92LA404 · Lanceair 235
Lanceair 235 · Accident: in flight collision with object on approach
From 3O7 to 3O7
Event
- NTSB case
- LAX92LA404
- 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
- 1 · 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
Lanceair 235
- Aircraft type
- Lanceair 235
- 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
- N25EH
- Operator
- Earl R. Heldt · private individual
- Onboard fatalities
- Unknown
- Route
- From 3O7To 3O7
- 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 pattern final
- 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
- Guy wire
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Altitude, inadequate
- Pilot in command › Planned approach, poor
Approximate · Estimated position: the centre of Hollister, CA, the place the record names. Not the accident site.
NTSB narrative
ACCORDING TO WITNESSES, THE AIRPLANE WAS MAKING A LANDING APPROACH LESS THAN A MILE FROM THE AIRPORT WHEN IT STRUCK A GUY WIRE AT A HEIGHT OF ABOUT 30 FEET ABOVE THE GROUND. THE AIRPLANE WENT INTO AN UNCONTROLLED DESCENT UNTIL IT STRUCK THE GROUND. THE WITNESSES REPORTED HEARING THE AIRPLANE'S ENGINE RUNNING AT A 'HIGH SPEED' AFTER THE AIRPLANE COLLIDED WITH THE WIRE. THE AIRPLANE WAS EXAMINED ON-SCENE BY AN FAA AVIATION SAFETY INSPECTOR. HE ATTRIBUTED ALL NOTED DAMAGE TO THE AIRPLANE TO IMPACT FORCES SUSTAINED DURING THE ACCIDENT SEQUENCE AND REPORTED NO PREIMPACT MECHANICAL MALFUNCTIONS.
Probable cause
THE PILOT PERFORMING THE FINAL SEGMENT OF A VISUAL APPROACH AT TOO LOW OF AN ALTITUDE RESULTING IN AN INFLIGHT COLLISION WITH A GUY WIRE.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX92LA404
- Event ID
- 20001211X15737
- Case number
- LAX92LA404
- 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: 24f2d76e72f030afb55da1893e56af5739b5bdea9ec398b29ed19328e6d5a0e6; retrieved 2026-09-21T00:54:43.562Z.