ERA09LA500 · Blum Matthew AVENTURA II
Blum Matthew AVENTURA II · Accident: loss of control in flight on approach
From Boca Raton, FL to Boca Raton, FL
Event
- NTSB case
- ERA09LA500
- 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
Blum Matthew AVENTURA II
- Aircraft type
- Blum Matthew AVENTURA
- 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
- N6301M
- Operator
- Matthew Blum
- Onboard fatalities
- Unknown
- Route
- From Boca Raton, FLTo Boca Raton, FL
- 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 crosswind
- Defining eventThe 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
- 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
- Aircraft › Aircraft power plant
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot had not flown the airplane for the 2 ½ months prior to the accident. The pilot departed to practice full-stop landings, and as he turned onto the crosswind leg a witness reported hearing the engine sputtering. Postaccident examination of the airplane revealed an improper assembly of both carburetors which could have caused an excessively rich fuel to air ratio. While maneuvering, the airplane stalled and impacted a road. No airframe preimpact failure or malfunction was noted, and no determination could be made as to who improperly assembled the carburetors.
Probable cause
The improper assembly of both carburetors, resulting in an excessively rich fuel to air ratio and subsequent partial loss of engine power.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA09LA500
- Event ID
- 20090908X92646
- Case number
- ERA09LA500
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: f9a8ac0d70b2ce33fd1275ec90e7b51db50bdbb79581d58fbf3f28ddf413fc11; retrieved 2026-09-13T20:27:51.033Z.