ERA19TA233 · Beech 95B55 UNDESIGNAT
Beech 95B55 UNDESIGNAT · Accident: landing gear not configured
From Orlando Sanford International Airport (SFB) to Orlando Sanford International Airport (SFB)
Event
- NTSB case
- ERA19TA233
- 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 95B55 UNDESIGNAT
- Aircraft type
- Beechcraft 55
- 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
- N386Q
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Orlando Sanford International Airport (SFB), Sanford, FLTo Orlando Sanford International Airport (SFB), Sanford, FL
- Aircraft age
- About 50 years (built 1969)
- 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
- Landing · flare/touchdown
- 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
- Landing gear not configured
- 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
- Personnel issues › Action/decision
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
According to the pilot, during an approach to land he said he extended the landing gear. He said that it According to the pilot, during an approach to land, he extended the landing gear. He said that it was hard to see if the landing gear indicator light was illuminated, but he said that he observed "one green." Surveillance video showed the airplane on short final with the landing gear in the up and locked position; before touchdown, video showed the airplane’s landing flare with the landing gear stowed. During landing, the pilot heard the noise of the propellers striking the ground and pulled back on the yoke to allow the airplane to slide to a stop. Flames came from the underside of the airplane, and the airport fire department extinguished the fire.
Examination of the airplane revealed that the inboard right and left wing was substantially damaged by the fire. The airplane was raised from the runway and the landing gear was manually extended from the up and locked position. During a gear retraction and extension test, the landing gear operated normally, and no landing gear anomalies were noted that would have precluded normal operation. Given this information, it is likely that the pilot failed to extend the airplane's landing gear before touchdown on the runway.
Probable cause
The pilot's failure to extend the landing gear during landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA19TA233
- Event ID
- 20190719X40236
- Case number
- ERA19TA233
- 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: 76c93d4a3f04a303c4c9b4ec6842ea602c4148efce826cd9b723873a2b5b8a21; retrieved 2026-09-16T09:27:30.532Z.