FTW83FA299 · Aero Commander 680-F
Aero Commander 680-F · Accident: loss of control in flight on approach
From Dallas Love Field (DAL) to Wichita Dwight D. Eisenhower National Airport (ICT)
Narrative check · The NTSB narrative appears to contradict this record's operator. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- FTW83FA299
- 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
- 2 · 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
Aero Commander 680-F
- Aircraft type
- Aero Commander 680
- 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
- N6139X
- Operator
- 12 Narrative disagrees
- Onboard fatalities
- Unknown
- Route
- From Dallas Love Field (DAL), Dallas, TXTo Wichita Dwight D. Eisenhower National Airport (ICT), Wichita, KS
- 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 go-around
- 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
- Destroyed
Cause areas
- Pilot in command › Reason for occurrence undetermined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE ACFT CRASHED AFTER STARTING A GO-AROUND OR ABORTED LANDING AT NORMAL OK. THE ACFT WAS ON A X-COUNTRY FROM DALLAS TO WICHITA. THERE WAS NO RADIO COMMUNICATION WITH THE ACFT AFTER IT WAS CLEARED TO LAND. THE APPROACH LOOKED OK BUT ON SHORT FINAL THE ACFT SUDDENLY TURNED RIGHT, LEVELED THEN ENTERED A STEEP CLIMBING RIGHT TURN AND CONTINUE TO ROLL UNTIL INVERTED THEN PITCHED NOSE DOWN UNTIL CRASHING. THE PLT IN THE RIGHT SEAT HAD REPORTEDLY WORKED LATE THE NIGHT BEFORE INSTALLING WHAT APPEARED TO BE AN AUX FUEL SYSTEM IN THE CABIN. THE ACFT HAD JUST BEEN SOLD AND THE IDENTITY AND LOCATION OF THE OWNER WAS NOT ESTABLISHED. NO ONE CLAIMED THE WRECKAGE. EVIDENCE REVEALED THAT BOTH PROPELLERS WERE ROTATING AT HIGH RPM AT IMPACT. THE FIRE AFTER IMPACT BURNED MOST INTENSELY AND PERSISTANTLY IN THE CENTER OF THE CABIN WHERE THE REMAINS OF WHAT APPEARED TO BE AN AUX FUEL SYSTEM WERE FOUND. NO PRE-IMPACT MALFUNCTONS OR FAILURES WERE FOUND.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record FTW83FA299
- Event ID
- 20001214X43327
- Case number
- FTW83FA299
- 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. 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: a110f0cdeff3a410fcd17f113433cb46ff2910116b2c942324dd1072d21bd0a1; retrieved 2026-09-21T06:34:32.977Z.