FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX07LA020 · Aero Commander 112

23 Oct 2006 · Chino, CA, United States

Aero Commander 112 · Accident: partial loss of engine power (non-mechanical) during initial climb

From Chino Airport (CNO) to Chino Airport (CNO)

Report a problem

Event

NTSB case
LAX07LA020
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

Aero Commander 112

Aircraft type
Aero Commander 112
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
N1022J
Operator
Unknown
Onboard fatalities
Unknown
Route
From Chino Airport (CNO), Chino, CATo Chino Airport (CNO)
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
Initial climb
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
Partial 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 starvation
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

  • Fluid, fuel › Starvation
  • Fuel system, vent › Blocked(partial)

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

During the takeoff climb the engine began to run rough, and was not producing enough power to sustain flight. The certified flight instructor (CFI) reported that there was no remaining runway when the engine began to lose power, and he made a forced landing in an open field. An annual inspection had been completed on the airplane 14 days prior to the accident, and this was the first flight since the inspection. During the annual inspection, the fuel system had been inspected. The inspection included de-fueling the fuel tanks to seal the wing leading edge rivets. The fuel tanks were serviced, and no leaks were observed. An inspection checklist for the fuel system identified various items for inspection at the 50 and 100-hour inspections. During the 50-hour inspection, the drain valves, vent lines and vents, filler cap, anti-siphoning valves, and fuel system placards are examined. In the 100-hour inspection, the internal tank inspection, gages, transmitters, fuel line fittings, vent lines, and vents, and the fuel vent line drain assembly beneath the fuselage is removed and cleaned. Following the annual inspection, the airplane sat on the ramp for 2 weeks before the accident flight. On the accident flight, the CFI stated that he and the owner/passenger did a thorough preflight with no discrepancies noted. According to the flight manual, during the preflight inspection, the pilot is to check that both the left and right wing fuel tank vents are unobstructed. The postaccident airframe inspection revealed that the left and right wings' fuel vent lines were clogged with dirt at each end, and their associated unions were also packed with dirt. The vent lines and unions were removed and shipped to the Safety Board's materials laboratory for further inspection. The fuel vent lines were found intermittently clogged with dirt at multiple locations along the length of the lines. The vent lines were cut open and the dirt removed for examination. Insect carcasses were found in the vent lines. According to the airframe manufacturer, there are three fuel vent lines; one at each wing, and one located on the belly of the airplane. If both the main fuel vent lines (left and right wings) become clogged, the belly fuel vent line would not be able to compensate for the clogged vent lines, and fuel flow to the engine would be restricted.

Probable cause

A loss of engine power during the initial climb after takeoff due to blocked fuel vent lines that resulted in fuel starvation. Contributing to the accident was an inadequate preflight inspection by the pilot-in-command (CFI).

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX07LA020
Event ID
20061101X01600
Case number
LAX07LA020
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: d2cc53318abd6e3795068a3c727a60a43288241926b5a291fbbbe4c0350528e6; retrieved 2026-09-21T08:53:22.533Z.