M and M Aviation Aero Commander 500-B accident
Aero Commander 500-B · Accident: partial loss of engine power (mechanical failure) en route
From Dallas Love Field (DAL) to OKC Will Rogers World Airport (OKC)
Event
- NTSB case
- FTW97LA258
- 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
- N802TC
- Operator
- M & M Aviation
- Onboard fatalities
- Unknown
- Route
- From Dallas Love Field (DAL)To OKC Will Rogers World Airport (OKC), Oklahoma City, OK
- 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 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
- En route · climb to 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
- Partial loss of engine power (mechanical failure)
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Wire, transmission; Tree(s)
- 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 › Emergency procedure, not followed
- Pilot in command › Gear retraction, not performed
- Pilot in command › Propeller feathering, not performed
- Pilot in command › Raising of flaps, not performed
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
On the dark early morning departure from Dallas Love Field, the pilot rated passenger was occupying the left seat. During climb out the pilot-in-command realized there was some kind of problem because they were not gaining any altitude, so he 'applied 1/4 flaps to try and gain some altitude.' The airspeed at that time was about 105 knots. He then retracted the flaps because his airspeed had deteriorated to about 90 knots and the aircraft was not gaining altitude. 'Both engines appeared to be developing power, RPM 2,300 Manifold Pressure 26 inches with fuel flow, however he thought the right engine acted as if it were operating only on one mag.' The pilot rated passenger did not notice any problems with the engines until after the airplane struck the first power line and then the right engine began making sounds like it was 'cutting out.' Examination of the aircraft wreckage revealed that both main landing gear were down and the nose landing gear was within the aircraft's crushed nose. The right main landing gear up lock was fractured. The landing gear control lever was found half way between the up and down position, the flap control lever was in the full down position, and the throttle, propeller and mixture control levers were full forward. Examination of the flap actuator revealed it to be fully extended and the exposed actuating rod was measured at 3 inches. According to the aircraft manufacturer, this would equate to the flaps being fully extended. Examination of the right engine revealed the right magneto's ignition lead cover plate was separated from the magneto. The magneto on the right engine was changed by the pilot the day prior at Tulsa, Oklahoma. Cracks were found in cylinders #1 and #4 of the right engine in the vicinity of their intake ports. The cracks were 2 inches in length with black deposits. It appeared that the intake ports had been modified. Performance data indicates the airplane's single engine rate-of-climb was approximately 289 feet per minute with an indicated airspeed of 108 miles per hour. To attain this rate of climb the aircraft's flight manual states that you must 'use maximum continuous power on operating engine (full throttle, 2,575 RPM) leaned to best power fuel flow, cowl flaps as required to control engine temperature within limits, landing gear up, flaps up. Inoperative engine feathered, cowl flaps closed. Climb at best rate of climb speed.'
Probable cause
The pilot-in-command's failure to follow emergency procedures to reduce drag and maintain best climb airspeed. Factors were the partial loss of engine power due to the cracks in the #1 and #4 cylinders as the result of an unapproved modification of their intake ports, the separation of the magneto lead plate due to its improper installation by the pilot-in-command, the dark night light conditions and the lack of suitable terrain for the forced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW97LA258
- Event ID
- 20001208X08374
- Case number
- FTW97LA258
- 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: 527d95c8ab3509580805318d2b2b9b3c39384e5b321d938c5822680a7ac705c6; retrieved 2026-09-18T17:29:19.628Z.