LAX04FA226 · Piper PA-28R-180
Piper PA-28R-180 · Accident: loss of engine power during initial climb
From Columbia Airport (O22) to Minden-Tahoe Airport (MEV)
Event
- NTSB case
- LAX04FA226
- 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
- 2 · 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
Piper PA-28R-180
- Aircraft type
- Piper PA-28
- 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
- N7626J
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Columbia Airport (O22), Columbia, CATo Minden-Tahoe Airport (MEV), Minden, NV
- 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/mush
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Airspeed(vs), not maintained
- 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 airplane descended to ground impact in the takeoff initial climb. On the takeoff roll and initial climb from a 4,670-foot runway, witnesses heard the engine sputtering, missing, and backfiring. An additional witness on the airport reported that his attention was drawn to the runway by "snap" and "pop" sounds from the engine. When he looked toward the noise, he saw the accident airplane about midfield. It sounded to him as if the engine were running lean. The airplane lifted off the ground and appeared to climb out slowly. He then heard the engine "snap" and "pop" again, which occurred a couple of times with about 2 to 3 seconds between each cycle. The abnormal engine sounds stopped, and the airplane climbed for an additional 5 seconds before the nose pitched up about 10 degrees. The witness then saw the airplane develop a high sink rate with an increasing nose up pitch attitude. Witnesses said the airplane remained in a nose high, wings level attitude until just before it dropped behind a tree line when the right wing dropped and the airplane hit the ground. The witness estimated the airplane traveled about 3/4 down the runway where it reached its highest altitude of 50 feet above the ground. A post impact fire ensued and the cockpit and engine were thermally damaged. An airframe and engine inspection and teardown were conducted with no preimpact mechanical anomalies noted that would have precluded normal operation. Investigators were able to establish that the owner (a private pilot) was seated in the right seat, and the commercial pilot was seated in the left seat. Investigators were not able to determine who was manipulating the controls at the time of the accident. The toxicology results for the commercial pilot showed levels of marihuana in the pilot's blood that indicated recent use, likely within the 8 hours prior to the accident.
Probable cause
The loss of engine power for undetermined reason during takeoff-initial climb, and the pilot's failure to maintain sufficient airspeed to avoid a stall/mush. Factors associated with the accident are an inadvertent stall/mush, and the pilot's failure to abort the takeoff.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX04FA226
- Event ID
- 20040608X00763
- Case number
- LAX04FA226
- 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: 21ddf5062396c2aff16dbbf4f97a5ad6860e9deddb81dc383a28b887c4a419e3; retrieved 2026-09-20T18:27:37.501Z.