LAX98LA099 · Sweet-House RD MUSTANG 2 RD MUSTANG
Sweet-House RD MUSTANG 2 RD MUSTANG · Accident: loss of control in flight during landing
From Madera Municipal Airport (MAE) to an unrecorded destination
Event
- NTSB case
- LAX98LA099
- 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
Sweet-House RD MUSTANG 2 RD MUSTANG
- Aircraft type
- Sweet House RD MUSTANG 2
- 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
- N546SH
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Madera Municipal Airport (MAE)To not recorded
- 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 · flare/touchdown
- 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 in flight
- 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 maintained
- Pilot in command › Directional control, not maintained
- Pilot in command › Stall/mush, encountered
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that he was on approach to runway 30. As he initiated the flare, he felt the airplane bleed off airspeed quicker than anticipated and realized that 'the aircraft was quickly starting to stall.' The pilot stated that he knew that he was too high and applied power to arrest the stall but the left wing dropped and seemed to start flying again when power was applied. The pilot then attempted to abort the landing and execute a go-around but the aircraft veered to the left off the runway. The left wingtip contacted the ground, followed by the engine and right wing. The right wing broke off at the wing splice point and the aircraft nosed over and came to rest inverted. The pilot reported that at the time of the accident he had logged only 1 hour in this type of aircraft.
Probable cause
The failure of the pilot to maintain adequate airspeed during the approach, which resulted in a stall. An additional cause was the pilot's failure to maintain directional control during the attempted go around. A factor in this accident is the pilot's lack of total experience in aircraft type.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX98LA099
- Event ID
- 20001211X09704
- Case number
- LAX98LA099
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1998-03-02.
- API snapshot SHA-256: 673aad4be51a481965e20f22b0e5b06aa6846d129a4be66547e40f52c90bda06; retrieved 2026-09-22T18:00:19.592Z.