MIA98LA244 · Aero Commander S2R
Aero Commander S2R · Accident: loss of engine power while maneuvering
Event
- NTSB case
- MIA98LA244
- 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
- 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 S2R
- Aircraft type
- Aero Commander S2
- 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
- N3652X
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- 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 137: Agricultural
- 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
- Maneuvering
- 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 engine power
- 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
- 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
- Ignition system, ignition harness › Chafed
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot stated that he was approximately three miles west of the airstrip when the engine lost all power. He stated, '...I was 600 to 700 feet AGL., I first pushed the throttle to full power position then started pumping the wobble pump and got no response.' The pilot stated that he began looking for an area to land, he picked out an area between two trees. According to the pilot during the landing, the airplane went between two trees and the wings were sheared then he impacted the ground. The engine was examined November, 1998. The FAA inspector's report showed that the following was found, '...wiring to magnetos had shielding completely chaffed from [the] wires and bare wires were present where it passed through the firewall of the aircraft...non aircraft wiring and splices were installed in the aircraft...suspect magnetos were grounded in flight.'
Probable cause
a loss of engine power due to a chaffed ignition wires, resulting in a forced landing and subsequent impact with trees.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA98LA244
- Event ID
- 20001211X11130
- Case number
- MIA98LA244
- 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: 4140ffffb3383f2c286b790f2d52dbe86d766713725521a040f3b56167585049; retrieved 2026-09-22T16:51:27.062Z.