FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN22FA208 · Piper PA-32-260

22 May 2022 · Broomfield, CO, United States

Piper PA-32-260 · Accident during initial climb

From Erie Municipal Airport (EIK) to Erie Municipal Airport (EIK)

Report a problem

Event

NTSB case
CEN22FA208
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-32-260

Aircraft type
Piper PA-32
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
N85CT
Operator
Unknown
Onboard fatalities
Unknown
Route
From Erie Municipal Airport (EIK), Erie, COTo Erie Municipal Airport (EIK), Erie, CO
Aircraft age
About 56 years (built 1966)
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
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
Unknown or undetermined
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 power plant
  • Personnel issues › Action/decision

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

NTSB narrative

The pilot and pilot-rated passenger conducted a personal flight that included troubleshooting an avionics issue. Following an extended taxi of longer than 1 hour, the airplane departed with a longer-than-normal ground roll and made a shallower-than-normal climb out. About ½ mile past the departure end of the runway, the airplane turned left and descended toward a road, which was a flight profile that was consistent with a forced landing attempt. The airplane impacted the road and then a large tree, which separated the engine and cockpit area from the fuselage, resulting in substantial damage. Postaccident examination of the airframe and engine did not reveal any indication of a mechanical failure or malfunction that would have precluded normal operation. Recorded data indicated engine performance during the accident takeoff was significantly lower than a previous takeoff. The engine power increased very slowly on the accident takeoff roll and fuel flow was about 45% less than the previous takeoff. The reason for the lower fuel flow during the accident takeoff could not be conclusively determined. However, one possibility was that the pilot(s) leaned the mixture during the extended ground operations of more than 1 hour and subsequently forgot to enrich the mixture before takeoff. A second possibility for the lower fuel flow was carburetor ice. The weather conditions at the time of the accident were conducive to serious carburetor icing at glide power. Carburetor ice can affect the fuel flow by disturbing the venturi effect in the carburetor throat that draws fuel into the cylinders. The result is lower fuel flows. Toxicology testing of the pilot did not identify any tested-for substances. The pilot-rated passenger’s toxicology indicated use of a number of substances; however, indications were limited to the urine and it is unlikely they were contributory to the accident. The slow acceleration and extended ground roll due to the degraded engine performance necessitated an abort that was not accomplished by the pilots. Since a purpose of the flight was troubleshooting an avionics issue, it is possible that the pilots were distracted by the avionics issue during the takeoff roll. This distraction could have led to inattention to ensuring that the fuel flow/engine performance was adequate during the takeoff roll and to abort the takeoff.

Probable cause

The pilot’s failure to abort the takeoff due to degraded engine performance. Contributing to the accident was the reduced performance of the engine, the reason for which could not be determined.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN22FA208
Event ID
20220522105113
Case number
CEN22FA208
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, coordinates, cause areas. 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: 7b7e8eb1d68708e23326561d480a8200c631e833a7aae02724168178679f6994; retrieved 2026-09-15T07:44:39.245Z.