MIA04FA128 · Cessna R182
MC Aviation Cessna R182 · Accident: loss of engine power during takeoff
From Peter Prince Field (2R4) to 2R4
Event
- NTSB case
- MIA04FA128
- 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
- Visual Meteorological Cond
Cessna R182
- Aircraft type
- Cessna 182
- 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
- N5157T
- Operator
- MC Aviation
- Onboard fatalities
- Unknown
- Route
- From Peter Prince Field (2R4), Milton, FLTo 2R4
- 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
- Takeoff · roll/run
- 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
- Stall
- 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 › Aborted takeoff, not performed
- Pilot in command › Airspeed(vs), not maintained
- Pilot in command › Operation with known deficiencies in equipment
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
During a checkout flight by a certified flight instructor (CFI) with the operator in the accident airplane the day before, an excessive (200 rpm) decrease was noted when checking the right magneto. Maintenance cleaned the spark plugs, performed an engine run-up, and returned the airplane to service. The pilot passed the check out flight and was provided the airplane. The CFI reportedly advised the pilot that if there was any maintenance problem to have the airplane worked on and the maintenance cost would be deducted. The day before the accident the pilot flew the airplane to Milton, Florida, and landed uneventfully where the airplane remained overnight. No maintenance was performed or requested, and no fuel was purchased. The pilot and three passengers boarded the airplane for a local flight and three witnesses, one of whom is an A & P mechanic, reported hearing the pilot having trouble starting the engine. The engine ran rough after starting, and the airplane was taxied to the approach end of runway 36 where the pilot performed an engine run-up. Several witnesses including the A & P mechanic reported hearing a discrepancy during the magneto check. The pilot was heard increasing the engine rpm while at the engine run-up area. During the takeoff roll one witness reported that the engine was, "making sounds as if it was not developing power." Several witnesses noted the airplane did not become airborne until approximately 3/4 down the 3,700 foot-long runway, or approximately 2,828 feet down the runway. Conservative takeoff distances for ground roll and distance to clear a 50 foot obstacle per the airplane "Information Manual" were 910 and 1,745 feet, respectively. The airplane began climbing to an estimated height of 100 feet, and the landing gear was noted to retract. One witness reported the airplane flew over her position and the engine was heard to be running rough. A pilot who was flying in the area at the time observed the airplane turn onto the downwind leg, stall, then pitch straight down. The airplane crashed in the side yard of a residence located approximately .30 nautical mile and 303 degrees from the departure end of runway 36. Examination of the flight controls and power section of the engine revealed no evidence of preimpact failure or malfunction. The ignition harness was impact damaged which precluded testing. Examination of the heat damaged magneto revealed the left capacitor was shorted to ground consistent with heat damage, while the right capacitor was functional. Heat damaged components were replaced, the magneto was placed on a test bench and operated with no discrepancies noted. Examination of the impact and heat damaged carburetor revealed the accelerator pump piston seal was badly worn exposing most of the sealing spring; the worn seal would reportedly not result in increased fuel flow. The as found setting of the economizer would result in a leaner fuel/air ratio. Rust was noted in the drain cavity below the float bowl, on the inner portion of the carburetor bowl drain plug, and a small amount of debris was noted in the main bowl chamber. Documents provided by the operator indicate a discrepancy related to excessive rpm decrease during a magneto check on August 27, 2004. The spark plugs were removed, cleaned, rotated, and reinstalled.
Probable cause
The pilots operation of the airplane with known deficiencies in the equipment based on witness statements describing an excessive rpm drop and rough running engine after starting, during the engine run-up, and after becoming airborne, his failure to abort the takeoff after an excessive takeoff roll, and his failure to maintain airspeed resulting in an inadvertent stall, uncontrolled descent, and in-flight collision with terrain. A factor in the accident was the loss of engine power due to undetermined reasons.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA04FA128
- Event ID
- 20040929X01515
- Case number
- MIA04FA128
- 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: 703d52672d7e3a1335e50305c847bbccd41566bb795c48da4d38a2ba2db3fc31; retrieved 2026-09-20T18:20:00.377Z.