DEN07CA035 · Piper PA-28-180
Piper PA-28-180 · Accident: loss of engine power on approach
From 00V · Falcon, CO to 00V · Falcon, CO
Event
- NTSB case
- DEN07CA035
- 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
Piper PA-28-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
- N6487J
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From 00V · Falcon, COTo 00V · Falcon, CO
- 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 turn to base
- 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
- 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
No findings designated as a cause are recorded in the NTSB data yet.
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
According to the pilot, he was established on a base leg for runway 15 when the engine lost power. The pilot lined up with an adjacent road and continued for a forced landing. The pilot stated that prior to the landing he checked his carburetor heat, mixture, throttle, and magnetos in attempt to troubleshoot the power loss. He stated that he observed car lights and "swerved into [the] tree." The airplane became lodged in the tree, resulting in substantial damage. An examination of the engine and related systems revealed no anomalies. The routine aviation weather report reported, temperature minus 01 degrees Celsius (C); dewpoint, minus 05 degrees C. According to the carburetor icing probability chart conditions were conducive for "serious icing at glide power" and "serious icing at cruise power."
Probable cause
loss of power due to carburetor icing. Contributing factors were weather conditions conducive to carburetor icing, unsuitable terrain available on which to make a forced landing and the tree.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DEN07CA035
- Event ID
- 20070117X00059
- Case number
- DEN07CA035
- 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: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2006-12-08.
- API snapshot SHA-256: 5871192966cc6c78b4e64c0a391b8a086ed5b88169227a39132b20af095fdd5a; retrieved 2026-09-21T18:38:52.546Z.