LAX02LA190 · Bellanca 17-30A
Bellanca 17-30A · Accident: in flight collision with terrain/water during initial climb
From Fallon Municipal Airport (FLX) to Lake Havasu City Airport (HII)
Event
- NTSB case
- LAX02LA190
- 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
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
- N8249R
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Fallon Municipal Airport (FLX), Fallon, NVTo Lake Havasu City Airport (HII), LAKE HAVASU, AZ
- 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
- Initial climb
- 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 terrain/water
- 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
- 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 › Airspeed, not attained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane settled into the ground on a taxiway during the takeoff initial climb. After the pilot raised the flaps during takeoff, the airplane did not seem to climb. He lowered the nose to gain airspeed; however, due to his proximity to the ground, he had to raise the nose again to reestablish a climb. He repeated the cycle of raising and lowering the nose as he turned back to the airfield. The stall warning horn was sounding during this sequence. The airplane touched down hard on the taxiway, continued through a median, crossed over the runway, and came to rest in the sand. The airplane departed with full fuel and was at or near gross weight. The density altitude was 4,647 feet msl.
Probable cause
the pilot's failure to attain an adequate takeoff airspeed, which resulted in a stall/mush. The high gross weight and density altitude were contributing factors.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX02LA190
- Event ID
- 20020614X00888
- Case number
- LAX02LA190
- 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: df0c7e2c61b4999b496cfcbbbd1c1b8128fbdf481c53330743792a08fe343aa0; retrieved 2026-09-21T09:38:36.806Z.