MIA00FA260 · Beech B-95
Beech B-95 · Accident: loss of control in flight while maneuvering
From ORMC Trauma Center Heliport (3FD1) to FL
Event
- NTSB case
- MIA00FA260
- 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
- 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 B-95
- Aircraft type
- Beechcraft B-95
- 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
- N3WT
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From ORMC Trauma Center Heliport (3FD1), Odessa, FLTo 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
- Maneuvering
- 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
- 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(vmc), 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
The accident aircraft was found in a field after an emergency locator transmitter beacon had made an alert of a possible accident having occurred. At about 1225, a witness, who had also been a student pilot, was in a housing development near where the accident aircraft was found, and he said that he had observed an aircraft maneuvering at a low altitude, just above the tree line. He said he saw the aircraft enter a steep bank, and start a dive with its left wing down. According to the witness, the aircraft then went below the tree line, and he waited for signs of an impact, such as noise or smoke, but did not hear or see anything. He said he then assumed that the pilot might have recovered enough to set the aircraft down in the field. He said the aircraft had descended as an eagle would, had it been attacking a small animal. FAA Tampa Approach radar information showed that the accident aircraft had been at 300 feet at 1221:44, and it had climbed to a maximum altitude of 1,100 feet at 1223:35. At 1224:21, radar information showed the aircraft at 700 feet, prior to all radar information being lost. The accident occurred during daylight hours, in visual meteorological condition, and examination of the accident aircraft did not reveal any preexisting failure or malfunction to the aircraft or any of its systems. The accident aircraft propeller signatures that were found were consistent with the left propeller having been feathered, and the right propeller rotating upon impact.
Probable cause
the pilot's failure to maintain Vmc, which resulted in a loss of control, and collision with the ground. Contributing to the accident was the pilot's decision to feather a propeller powered by an operational engine, while at a low altitude.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA00FA260
- Event ID
- 20001212X22029
- Case number
- MIA00FA260
- 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: c561b24e2a5e88d13c5dc4e2e09fe5cc947a24bf97c35c15bb8c936f21f1990f; retrieved 2026-09-20T20:52:49.738Z.