MIA02GA137 · Cessna 172S
Cessna 172S · Accident: loss of engine power while maneuvering
From Northeastern Regional Airport (KEDE) to Northeastern Regional Airport (KEDE)
Event
- NTSB case
- MIA02GA137
- 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
- 3 · 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
- Government
- 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 172S
- Aircraft type
- Cessna 172
- 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
- N928CP
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Northeastern Regional Airport (KEDE), Edenton, NCTo Northeastern Regional Airport (KEDE), Edenton, NC
- 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
- Public Aircraft
- 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
- 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 › Airspeed, not maintained
- Reason for occurrence undetermined
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The flight departed about 1300 with a pilot, co-pilot, and observer (law enforcement officer) on-board for a marijuana eradication flight operated by the Civil Air Patrol. The airplane had been operated earlier that day in the morning and afternoon orbiting throughout areas of the county between witness reported altitudes of between 300 and 500 feet agl on the same type of mission by the same pilot. After departure on the accident flight, the flight continued the aerial observation and according to one witness, on the last pass, the airplane was observed in a large clockwise orbit noticeably lower than the 300 to 500 feet agl previously observed. A sputtering noise was heard by one witness, and another stated there was no engine sound at all just before she observed the aircraft depart normal upright flight. From an altitude of about 120 to 150 feet agl, she saw the aircraft simultaneously nose over vertically and commence a right half roll into the terrain. The airplane came to rest inverted in a field containing cotton crops. One EMT who was on-scene within minutes of the accident reported observing a finger sized stream of fuel leaking from the left wing root area; the leakage lasted an estimated 15-20 minutes. Other personnel on scene stated they did not smell a strong odor of fuel after arriving within minutes of the crash. There was no evidence of leakage from the right fuel tank; the header tank was impact damaged. The fuel selector was found positioned to the "both" position. No evidence of preimpact failure or malfunction of the flight controls for roll, pitch, and yaw was noted, and no evidence of preimpact mechanical failure/malfunction of the engine, magnetos, or mechanical fuel pump was noted. The flaps were extended 10 degrees. Bench testing of the impact damaged fuel injection servo as received revealed it flowed greater than specified service limits. The impact damaged mixture control shaft was replaced, the unit was flow tested and found to flow within limits at all ranges above idle. Examination of the flow divider revealed the cover had the same safety wire pattern as the pattern used during manufacturing; bench testing of the unit revealed it operated at 2.0 psi; no contamination was noted following disassembly, and the spring was not failed. Fuel consumption calculations indicate that an estimated 15 gallons of fuel should have been on-board at the time of the accident.
Probable cause
The loss of power for undetermined reasons, and the pilot's failure to maintain airspeed.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA02GA137
- Event ID
- 20020723X01185
- Case number
- MIA02GA137
- 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: 51da8cc0c00896828a0193d9278fff96d3e555ff19c7f3f1641718c52811e0d3; retrieved 2026-09-18T14:35:44.962Z.