FTW99LA070 · Cessna 180J
Cessna 180J · Accident: loss of engine power en route
From TX (no airport) to an unrecorded destination
Event
- NTSB case
- FTW99LA070
- 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
- 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 180J
- 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
- N52170
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From TX (no airport)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
- 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
- Loss of engine power
- 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 as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
At departure the right fuel tank was empty, the left fuel tank contained 17 gallons, and the fuel selector was positioned to the 'BOTH' position for takeoff. After takeoff, the pilot selected the left fuel tank. Within 2 to 3 minutes after takeoff, the engine began to 'run rough and sputter.' Emergency checklist procedures did not restore engine power. Power lines crossed the approach path for the runway selected for the forced landing. The airspeed decreased as the airplane cleared the power lines and the airplane landed 'hard' on the runway. Flight control continuity was confirmed. There was continuity of fuel flow throughout the fuel system. No physical evidence of fuel leakage was found. Engine continuity was confirmed and no discrepancies were found that would prevent engine operation. The carburetor was flow tested and disassembled. No fuel flow test variations or discrepancies were noted that would prevent operation of the carburetor.
Probable cause
The loss of engine power due to an undetermined reason. A factor was the power lines crossing the final approach path.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW99LA070
- Event ID
- 20001204X00060
- Case number
- FTW99LA070
- 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: 46d9f242ce260c0b2d48cecb2a787a155e2dc83ae575bbd33e57faac17658845; retrieved 2026-09-22T15:57:53.008Z.