MIA06LA062 · Cessna 180
Cessna 180 · Accident: total loss of engine power (non-mechanical) on approach
From M33 · Gallatin, TN to Pilot Country Airport (X05)
Event
- NTSB case
- MIA06LA062
- 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
- 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 180
- Aircraft type
- Cessna 180
- 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
- N9138C
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From M33 · Gallatin, TNTo Pilot Country Airport (X05), Brooksville, FL
- 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
- 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; 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
- 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 pilot stated that he had topped off the airplane's fuel tanks in Gallatin, Tennessee, and he had 60 gallons of fuel onboard. He departed at 0625 central daylight time, climbed to 9,000 feet, and the flight's duration was 3 hours 30 minutes. He said he leaned the fuel mixture, observing fuel flows of about 10.5 to 11gallons per hour on his JPI analyzer, and that the quantity of fuel remaining never was less than 20 gallons. Upon reaching his destination airport he said he over-flew the airport to observe the winds, and then flew 6 miles south, twice circling his friend's house, and then returned to land. During the approach, while turning to base he applied 30 degrees of flaps, at which time the engine ceased operating. He said obstacles included trees and utility wires, and during the glide, after avoiding the trees, he selected 40 degrees of flaps in an attempt to balloon over the wires, and the airplane stalled and descended impacting the ground. During the pilot's report of the accident to the NTSB he stated that there were no mechanical failures or malfunctions to the airplane or any of its systems. A witness stated that he saw the accident airplane on downwind, rocking its wings, and he saw it on final approach and as it came over the trees. He said the propeller had stopped rotating, and as he continued watching, it appeared as if the pilot was trying to stretch the glide. He said he saw the airplane stall and descend, impacting the ground a short distance from the runway. On the day of the accident, an FAA inspector responded to the scene of the accident and found no evidence of fuel spillage at the scene. When the airplane was checked, the inspector found about 2 gallons of fuel in the left tank, and no fuel in the right tank. On March 10, 2006, an FAA licensed mechanic, under the supervision of the FAA inspector, conducted a detailed examination of the airplane's airframe and engine, and no anomalies were noted. The accident airplane was equipped with a Texas Skyways Incorporated conversion O-520 -U/TS engine. On July 17, 2007, a technician at Texas Skyways stated to the NTSB that Texas Skyways did not publish endurance documentation for their conversions because of the various models of engines they modified, and their variability in fuel consumption. He further stated that from his experience, climb to cruise fuel consumption for the O-520 U/TS engine, at a rate of climb of about 1,000 feet per minute, at full power, without leaning for changes in altitude would yield a fuel consumption of about 23 gallons per hour. He further stated that with leaning the mixture, and with other climb related adjustments, the average fuel consumption during the climb should be about 18 gallons per hour. At an altitude of 9,000 feet, the technician also estimated that the airplane should consume about 14 gallons per hour, while in cruise flight. In addition, the technician also said that JPI endurance data was consistent with the exhaust and cylinder head temperatures noted.
Probable cause
An in-flight loss of fuel for undetermined reasons which resulted in fuel exhaustion, a forced landing and damage to the airplane during the landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA06LA062
- Event ID
- 20060316X00310
- Case number
- MIA06LA062
- 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: 74564ceabbade140d9cfb73c65b8314b4dcd5d3be421aa94512a5de135e830ba; retrieved 2026-09-21T08:59:50.584Z.