MIA00FA117 · Cessna 177RG
Cessna 177RG · Accident: total loss of engine power (non-mechanical) on approach
From Jim Hamilton L.B. Owens Airport (CUB) to an unrecorded destination
Event
- NTSB case
- MIA00FA117
- 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 177RG
- Aircraft type
- Cessna 177
- 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
- N1556H
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Jim Hamilton L.B. Owens Airport (CUB)To 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 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
- Approach · VFR pattern turn to base
- 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 (non-mechanical)
- 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
- Fuel exhaustion; 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
- Destroyed
Cause areas
- Pilot in command › Preflight planning/preparation, inadequate
- Pilot in command › Refueling, not performed
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to the PIC, substantiated by the widow of the passenger/pilot, the airplane fuel tanks were topped off at Orangeburg Municipal Airport, Orangeburg, South Carolina, on March 19, 2000. The PIC further stated that he flew directly home to Columbia Downtown Airport, parked, and tied down for a total fuel burn time of about 30 minutes. On March 22, 2000, the airplane took off from Columbia Downtown Airport, the PIC having radioed his intention to stay in the traffic pattern, and sustained an engine stoppage as the airplane approached the abeam position for its first landing. The airplane collided with the terrain and revealed no evidence of onboard fuel at the crash site. The engine underwent a factory test cell run, and it was unsatisfactory until factory fuel injector nozzles were substituted, at which time the engine met factory specifications. Subsequent disassembly examination of the fuel system components revealed contamination in the fuel injector servo. The fuel quantity indication system underwent factory testing and revealed the right tank system was operating erratically, which appeared to be a precrash condition.
Probable cause
The PIC's inadequate planning and preparation resulting in refueling not being performed and the subsequent fuel exhaustion and forced landing into trees. A factor in the accident was the erratic operation of the right fuel tank quantity indicating system.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA00FA117
- Event ID
- 20001212X20688
- Case number
- MIA00FA117
- 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: 6db319092a3d38b305258183493da7eae4693d4eadf0b25cb7cdb6eda561c80e; retrieved 2026-09-20T21:23:41.640Z.