DFW07CA209 · Piper PA-31-350
Ameriflight Piper PA-31-350 · Accident: wheels up landing
From Hutchinson County Airport (BGD) to Perry Lefors Field (PPA)
Event
- NTSB case
- DFW07CA209
- 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
- Instrument Meteorological Cond
Piper PA-31-350
- Aircraft type
- Piper PA-31
- 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
- N45014
- Operator
- Ameriflight
- Onboard fatalities
- Unknown
- Route
- From Hutchinson County Airport (BGD), Borger, TXTo Perry Lefors Field (PPA), Pampa, TX
- 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
- Landing · flare/touchdown
- 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
- Wheels up landing
- 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 › Wheels up landing, inadvertent
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
During the landing flare in a twin-engine airplane, the 1,391-hour commercial pilot heard the landing gear warning horn. The pilot stated that he added engine power to initiate a go-around as he extended the landing gear. The airplane's propellers struck the runway and the airplane skidded approximately 650-feet down the runway before coming to a stop on the runway. The pilot egressed, uninjured, through the left cabin door. The throttles were found in the "full forward" position and the landing gear selector handle was found in the "down" position. The inboard main gear doors were found in the retracted position indicating that gear sequencing had not started when the airplane touched-down on the runway. Company policy directed the pilot to extend the landing gear prior to descending below 1,000-feet above ground level on approach.
Probable cause
The pilot's failure to extend the landing gear prior to landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DFW07CA209
- Event ID
- 20071126X01837
- Case number
- DFW07CA209
- 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: 4c2a9e6d7f6d971f3a406348eb44f5fa291064edc5a6fcedb838738c0a331bf5; retrieved 2026-09-22T03:23:43.969Z.