ANC06LA026 · Extra Flugzeugbau 300S
Extra Flugzeugbau 300S · Accident: loss of control in flight on approach
From Reid-Hillview Airport of Santa Clara County (KRHV) to Metz Airport (3CA7)
Event
- NTSB case
- ANC06LA026
- 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
- 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
Extra Flugzeugbau 300S
- Aircraft type
- Extra 300
- 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
- N124X
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Reid-Hillview Airport of Santa Clara County (KRHV), San Jose, CATo Metz Airport (3CA7), Greenfield, 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
- Approach · VFR pattern base
- 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(vs), 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
At the conclusion of a Title 14, CFR Part 91 flight, the commercial certificated pilot was landing an experimental/exhibition airplane at a rural airport after performing about 20 minutes of aerobatic flight in a nearby aerobatic practice area. Witnesses reported that the airplane appeared to fly a left (southeast) downwind pattern, paralleling the runway. Near the approach end of the runway, the airplane made a right turn of about 45 degrees, away from the runway, then made a steep left turn, toward the runway. The airplane was then observed to level the wings and descend toward the ground with about a 10 degree nose-down attitude. The airplane collided with the ground in what witnesses described as a flat, level attitude with a high vertical velocity. The airplane bounced and struck the ground a second time, coming to rest within about 50 feet of the initial impact point, and about 15 degrees to the right of the runway heading. The airplane came to rest about 100 feet to the right, and about 850 feet past the approach end of the runway. Inspection of the airplane disclosed no evidence of any preimpact mechanical anomalies.
Probable cause
The pilot's failure to maintain adequate airspeed during the base leg to final approach phase of a VFR landing pattern, which resulted in an inadvertent stall and an uncontrolled descent. A factor contributing to the accident was the inadvertent stall/mush.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ANC06LA026
- Event ID
- 20060323X00338
- Case number
- ANC06LA026
- 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: 4725d8072296680bd8bc210f6f5df2fc8e2a875148e73424bcf3404b4201e124; retrieved 2026-09-20T17:28:52.083Z.