Central Airlines Aero Commander 500 B accident
Aero Commander 500 B · Accident: landing gear not configured
From Tampa Executive Airport (VDF) to Miami-Opa Locka Executive Airport (OPF)
Event
- NTSB case
- ERA20CA148
- 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
- Charter & commuter
- 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
Aero Commander 500 B
- Aircraft type
- Aero Commander 500
- 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
- N516DT
- Operator
- Central Airlines
- Onboard fatalities
- Unknown
- Route
- From Tampa Executive Airport (VDF), Tampa, FLTo Miami-Opa Locka Executive Airport (OPF), Miami, FL
- Aircraft age
- About 55 years (built 1965)
- 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 135: Air Taxi & Commuter
- 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 · aborted after 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
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that, during the descent to final, he began the GUMPS checklist. As he turned on the fuel tanks, he picked up interference on the radios. After fixing the radio situation, he continued the checklist. During the landing flare, he noticed that the "runway sight picture" seemed lower than normal. As he noticed this, he looked at the landing gear indicator, and the landing gear warning horn simultaneously sounded, so he initiated a go-around. While climbing to traffic pattern altitude, he noticed that he had failed to extend the landing gear. He added that he had not heard or felt the airplane contact the runway before the go-around. The pilot subsequently landed without incident and noted no damage during a cursory postflight inspection. He then departed and landed at another airport. Subsequently, he performed a more thorough postflight inspection of the airplane, during which he noticed that the marker beacon antenna was shaved off and that the lower fuselage of the airplane had sustained substantial damage consistent with ground contact.
Probable cause
The pilot's failure to extend the landing gear due to distraction and his delayed go-around, which allowed the airplane to get too low and contact the runway with the landing gear retracted.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA20CA148
- Event ID
- 20200408X62348
- Case number
- ERA20CA148
- 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: ab60b48b4a01f3c81ddb9a223b12206e22ad035e376784e879af73ac297e1ba7; retrieved 2026-09-16T11:25:52.861Z.