ERA13CA073 · Beech B19
Status Air Beech B19 · Accident: fuel exhaustion on approach
From Fort Lauderdale Executive Airport (FXE) to Fort Lauderdale Executive Airport (FXE)
Event
- NTSB case
- ERA13CA073
- 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
Beech B19
- Aircraft type
- Beechcraft 19
- 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
- N2196W
- Operator
- Status Air
- Onboard fatalities
- Unknown
- Route
- From Fort Lauderdale Executive Airport (FXE), Fort Lauderdale, FLTo Fort Lauderdale Executive Airport (FXE), Fort Lauderdale, 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 downwind
- 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 exhaustion
- 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 › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that the purpose of the flight was an orientation for two potential student pilots. The pilot said that he completed a visual inspection of the fuel tanks and that he estimated that the fuel tanks contained 10 gallons of fuel, which he determined, would have been adequate for the flight. The pilot completed two traffic patterns, and as he climbed the airplane to the downwind leg of the third pattern, the engine lost power and "surged" during the subsequent forced landing. The pilot requested an emergency landing to runway 13 but amended his request to runway 8 because the airplane was "too high." He subsequently determined the airplane was "too low" for runway 8, and the airplane touched down hard on a taxiway and skidded to a stop in the grass infield. The airplane sustained substantial damage to the cabin floor structure. Examination revealed that the airplane contained no fuel, and the pilot reported that he had exhausted his fuel supply.
Probable cause
The pilot's inadequate preflight planning, which resulted in fuel exhaustion and a total loss of engine power.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA13CA073
- Event ID
- 20121203X24219
- Case number
- ERA13CA073
- 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. 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: f1b3483efad47cf488374e0e9504e4b5bceba1c95275af33ea0a6dec567c4bbf; retrieved 2026-09-15T20:30:46.333Z.