LAX06LA187 · Hunter Comp Air 6
Hunter Comp Air 6 · Accident: loss of engine power during initial climb
From Minden-Tahoe Airport (MEV) to an unrecorded destination
Event
- NTSB case
- LAX06LA187
- 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
Hunter Comp Air 6
- Aircraft type
- Hunter COMP AIR 6
- 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
- N6008N
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Minden-Tahoe Airport (MEV), Minden, NVTo 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
- 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
- Loss of engine power
- 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
- 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
- Fuel injection control/system › Excessive flow/output
- Pilot in command › Airspeed, not maintained
- Pilot in command › Stall, encountered
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane descended to ground impact during a forced landing following a loss of engine power during the takeoff initial climb. During the takeoff roll, the engine momentarily hesitated and made a slight "pop" sound. The engine immediately smoothed out and all the cockpit gauges displayed normal indications. After rotation, the airplane climbed to about 400 feet above ground level (agl) and the pilot initiated a turn to the crosswind leg of the traffic pattern. While the airplane was in the turn, the engine experienced a total loss of power. The pilot stated that he attempted to activate the fuel pump and restart the engine, but he was not successful. A witness observed the airplane departing from runway 34. The airplane began to make a 45-degree turn to the west and he noticed that the engine did not sound normal. The airplane appeared to be maneuvering close to the runway and was rapidly losing altitude. After making another 45-degree turn to the left, the airplane was heading south and continually losing altitude. The witness recalled that he did not hear any sound from the airplane's engine. The airplane's left wing dipped down, almost perpendicular to the ground, and then the airplane impacted the terrain. The airplane came to rest inverted. The pilot had recently purchased the airplane and he had acquired 2 hours in the same make and model. The switch for the boost pump was located on the control stick and had three positions: off, low, and high. The post accident examination revealed that the switch was in the high position. According to the previous owner, he found the switch in the high position immediately after the accident. Manual manipulation of the switch revealed that movement was very easy without discernable resistance. During the examination, investigators removed the top spark plugs, which displayed a dark, sooty coloration consistent with a rich mixture setting. Thumb compression was obtained on all six cylinders, confirming crankshaft and camshaft continuity. In addition, the magnetos and their respective ignition harnesses were tested and found to produce a spark in the proper firing order. No anomalies were noted with the engine, with the exception of the dark spark plugs.
Probable cause
a loss of engine power due to an excessively rich mixture. The underlying reasons for the overly rich mixture were not determined. Also causal was the pilot's failure to maintain an adequate airspeed while maneuvering for a forced landing, which led to a stall.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX06LA187
- Event ID
- 20060605X00681
- Case number
- LAX06LA187
- 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: 27c44fdbcd72cac689ee9e4eab5deb2840a45d82ae96ef951206a5834aae174f; retrieved 2026-09-21T08:57:37.387Z.