ATL91FA077 · Cessna 172D
Cessna 172D · Accident: total loss of engine power (mechanical failure) en route
From Mount Airy Surry County Airport (MWK) to Davidson County Executive Airport (EXX)
Event
- NTSB case
- ATL91FA077
- 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
- 1 · 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
Cessna 172D
- 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
- N2936U
- Operator
- Robbins, James L. · private individual
- Onboard fatalities
- Unknown
- Route
- From Mount Airy Surry County Airport (MWK), MT. AIRY, NCTo Davidson County Executive Airport (EXX), Lexington, 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
- 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
- Total 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
- Stall
- 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 › Open
- Undetermined › Airspeed, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
DURING CRUISE FLIGHT IN NIGHT, VFR CONDITIONS, THE ENGINE REPORTEDLY QUIT. DURING THE FORCED LANDING ATTEMPT, THE AIRPLANE STALLED, THEN COLLIDED WITH THE TERRAIN IN A STEEP, NOSE-DOWN ATTITUDE. POST-CRASH INVESTIGATION AND ENGINE RUN REVEALED THAT 6 OF THE 12 IGNITION HARNESS WIRE CIRCUITS WERE OPEN FROM THE MAGNETOS TO THE SPARK PLUGS. THE ENGINE WOULD RUN ON A TEST STAND, HOWEVER THREE CYLINDERS WERE COLD TO THE TOUCH AFTER THE RUN. ENGINE CONTINUITY WAS ESTABLISHED, AND THE MAGNETOS TESTED SATISFACTORILY ON A TEST BENCH. THE IGNITION HARNESS APPEARED OLD AND WORN, AND THE AIRPLANE HAD BEEN FLOWN ONLY 41 HOURS IN THE PREVIOUS 4 YEARS.
Probable cause
THE LOSS OF ENGINE POWER DUE TO OPEN CIRCUITS IN THE IGNITION WIRING HARNESS, AND THE PILOT'S FAILURE TO MAINTAIN FLYING AIRSPEED DURING THE FORCED LANDING ATTEMPT. FACTORS IN THIS ACCIDENT WERE THE DARK NIGHT LIGHTING CONDITIONS AT THE TIME OF THE ACCIDENT.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL91FA077
- Event ID
- 20001212X16719
- Case number
- ATL91FA077
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1991-04-07.
- API snapshot SHA-256: b75c06d7d21aefba7409f2f169186bee037d17295b572614dc5e1c3cd3d2aa67; retrieved 2026-09-21T01:52:15.341Z.