WPR11LA025 · Piper PA-28-236
Piper PA-28-236 · Accident: loss of engine power (partial) en route
From Truckee Tahoe Airport (TRK) to Borrego Valley Airport (L08)
Event
- NTSB case
- WPR11LA025
- 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
- Instrument Meteorological Cond
Piper PA-28-236
- 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
- N228KK
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Truckee Tahoe Airport (TRK), Truckee, CATo Borrego Valley Airport (L08), Borrego Valley, CA
- 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
- 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
- Loss of engine power (partial)
- 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
- Tree(s)
- 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
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that, while the airplane was level at 15,000 feet in instrument meteorological conditions, he failed to apply carburetor heat to the engine. After several minutes, the engine began losing power, and the airplane was not able to sustain flight. During the descent for a forced landing in mountainous terrain, the airplane descended below the cloud base about 2,000 feet above the ground, and the pilot observed a road and a clearing. During the landing rollout, the airplane impacted trees, which severed its wings. Icing probability charts indicated that carburetor ice was probable under the atmospheric conditions in which the airplane had been flying. The pilot reported that if he had applied the carburetor heat during flight, the accident likely would not have occurred.
Probable cause
The pilot’s failure to use carburetor heat while cruising in carburetor icing conditions, which resulted in a loss of engine power.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR11LA025
- Event ID
- 20101023X94911
- Case number
- WPR11LA025
- 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: 2d029ae3652438857e96e3a4ccdbaf23d2d646c9dc65ec6443c98deb97c8e47e; retrieved 2026-09-15T15:30:48.850Z.