FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN11LA089 · Cessna 180

2 Dec 2010 · Omaha, NE, United States

Cessna 180 · Accident: system/component malfunction/failure (non-power) on approach

From Philip Airport (PHP) to Eppley Airfield (OMA)

Report a problem

Event

NTSB case
CEN11LA089
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
N3246D
Onboard fatalities
Unknown
Route
From Philip Airport (PHP), Philip, SDTo Eppley Airfield (OMA), Omaha, NE
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 final
Defining eventThe 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
System/component malfunction/failure (non-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

  • Aircraft › Aircraft systems

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

During the landing approach and 1/2-mile from the runway, the engine lost power. During the ensuing forced landing, the airplane impacted a tree and terrain. During postaccident functional testing of the engine, it lost power when the throttle was moved quickly from a low power setting to a high power setting, and became more pronounced as the engine got warmer. The carburetor was removed from the engine and a visual inspection was conducted. A roughness was felt in the accelerator pump while manually moving the control at the carburetor, and very little fuel flow came from the accelerator pump. The carburetor was disassembled and all check valves, ports and vents, the venturi, nozzle bleed holes, carburetor bowl vent channels, and float assembly were cleaned. After reassembly, a much higher fuel output was achieved. The carburetor and accelerator pump were reinstalled on the engine, and all functional checks were normal.

Probable cause

A loss of engine power due to a stuck check valve in the carburetor acceleration pump, resulting in an improper fuel mixture when the pilot attempted to add power.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN11LA089
Event ID
20101202X94844
Case number
CEN11LA089
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 3d004f9348f2f660ed2ac90b01cb584f08e0ad8e0d82da85ae2f06aec9dfb13e; retrieved 2026-09-15T15:36:00.501Z.