DFW07FA004 · Aero Commander 690A
Aero Commander 690A · Accident: airframe, component or system failure en route
From Wiley Post Airport (PWA) to Orlando Executive Airport (ORL)
Event
- NTSB case
- DFW07FA004
- 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
- 4 · 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
Aero Commander 690A
- Aircraft type
- Aero Commander 690
- 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
- N55JS
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Wiley Post Airport (PWA), Oklahoma City, OKTo Orlando Executive Airport (ORL), Orlando, 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
- En route · cruise
- 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
- Airframe, component or system failure
- 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 › Design stress limits of aircraft, exceeded
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
Approximately 37 minutes after departing on a 928-nautical mile cross-country flight under instrument flight rules, the twin-engine turboprop airplane experienced an in-flight break-up after encountering moderate turbulence while in cruise flight at the assigned altitude of FL230. In the moments preceding the break-up, the airplane had been flying approximately 15 to 20 knots above the placarded maximum airspeed for operations in moderate turbulence. The airplane was found to be approximately 1,038 pounds over the maximum takeoff weight listed in the airplane's type certificate data sheet (TCDS). The last radar returns indicated that the airplane performed a 180-degree left turn while descending at a rate of approximately 13,500 feet per minute. There were no reported eyewitnesses to the accident. The wreckage was located the next day in densely wooded terrain. The wreckage was scattered over an area approximately three miles long by one mile wide. An examination of the airframe revealed that the airplane's design limits had been exceeded, and that the examined fractures were due to overload failure.
Probable cause
The pilot's failure to reduce airspeed while operating in an area of moderate turbulence, resulting in an in-flight break up. Contributing factors were the pilot's decision to exceed the maximum takeoff weight, and the prevailing turbulence.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DFW07FA004
- Event ID
- 20061024X01554
- Case number
- DFW07FA004
- 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: edecfd1cfc92edf99303baa9d8c4c1bdf034593b01821ba0c938cdcc21c054d7; retrieved 2026-09-20T17:01:38.921Z.