LAX96LA211 · Bellanca 17-30A
Bellanca 17-30A · Accident: loss of control on ground/water during landing
From Prescott Regional Airport - Ernest A. Love Field (PRC) to Fallbrook Community Airpark (L18)
Event
- NTSB case
- LAX96LA211
- 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
Bellanca 17-30A
- Aircraft type
- Bellanca 17
- 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
- N23MB
- Operator
- Frank B. Harriman · private individual
- Onboard fatalities
- Unknown
- Route
- From Prescott Regional Airport - Ernest A. Love Field (PRC), Prescott, AZTo Fallbrook Community Airpark (L18), 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
- Landing · landing roll
- 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
- Loss of control on ground/water
- 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 › Directional control, not maintained
- Pilot in command › Proper touchdown point, not attained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot and his passenger were returning from a cross-country flight and landed on runway 18. A brief rain and hail squall reached the airport at the time of their arrival. The pilot landed long, and the aircraft touched down on the nosewheel first, then bounced three times. The aircraft departed the left side of the 2,160-foot-long runway. The pilot did not get a preflight weather briefing nor file a flight plan. He stated that a television station reported clear weather and unlimited visibility, but possible clouds by late evening near the coast. The wind was from the southwest at 10 to 15 knots.
Probable cause
failure of the pilot to attain the proper touchdown point on the runway, and his failure to maintain directional control of the airplane. Factors relating to the accident were: the excessive airspeed on final approach, and the short and wet condition of the runway.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX96LA211
- Event ID
- 20001208X05822
- Case number
- LAX96LA211
- 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: 5dbfee923e568c0a065964dfbe31654865c210e56dbaeceb6a8e4a348966b409; retrieved 2026-09-22T22:27:20.199Z.