ERA23LA119 · Beech A23 A
Beech A23 A · Accident: fuel starvation en route
From Florida Keys Marathon International Airport (MTH) to an unrecorded destination
Event
- NTSB case
- ERA23LA119
- 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
Beech A23 A
- Aircraft type
- Beechcraft 23
- 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
- N16TH
- Operator
- Mosquera Daniel
- Onboard fatalities
- Unknown
- Route
- From Florida Keys Marathon International Airport (MTH), Marathon, FLTo not recorded
- Aircraft age
- About 57 years (built 1966)
- 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
- En route
- 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
- Fuel starvation
- 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 › Fluids/miscellaneous hardware
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to the pilot, he was on a local flight at an altitude of 1,000 ft when he noticed the engine starting to lose power. The pilot said he switched fuel tanks, but engine power was not regained. The pilot conducted an emergency landing on a road and the airplane collided with a bus and then a pole. Postaccident examination of the airplane revealed that the fuel tanks were intact, and that the left fuel only contained a residual amount of fuel, while about 10 gallons of fuel remained in the right fuel tank. An engine test run was then attempted at the accident site, and the engine ran normally using the right fuel tank but did not run consistently with the left fuel tank selected. Based on this information, it is likely that the pilot mismanaged the airplane’s fuel supply and starved the engine of fuel, which resulted in the total loss of engine power and subsequent forced landing.
Probable cause
The pilot’s mismanagement of fuel supply, which resulted in fuel starvation.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA23LA119
- Event ID
- 20230130106648
- Case number
- ERA23LA119
- 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, cause areas. 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: 540431332dedb29fe34b3dfa802e669ad19ba58089aba0a039dba6c840a879d1; retrieved 2026-09-16T17:17:13.580Z.