# Accident 20040724018749A: Beech 58P, Fort Collins, CO, July 24, 2004

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: July 24, 2004, 12:06 local time
- Place: Fort Collins, CO
- Damage: Destroyed
- Phase of flight: Climb
- Operating rules: General operating rules (Part 91)
- Location: 40.5331° N, 105.0208° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=40.5331&lon=-105.0208&mi=10
- Aircraft: N69CL, a cancelled registration (https://openairdocs.org/deregistered/N69CL-2006-07-07) (OpenAirDocs)
- Registry model: Beech 58P (registry code 1152744, https://openairdocs.org/model/beech-58p) (OpenAirDocs)
- Registry engine: Continental TSIO-520 series (registry code 17040, https://openairdocs.org/engine/continental-tsio-520-series) (OpenAirDocs)
- Reported make and model: BEECH 58P
- Reported engine: CONT TSIO520WB
- People aboard: 3
- Fatal injuries: 3
- Pilot flight hours: 1,398 total, 172 in this make and model, 46 in the last 90 days
- NTSB investigation: [NTSB DEN04FA109](https://openairdocs.org/ntsb/DEN04FA109) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20040724018749A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

(-23) ON JULY 24, 2004 AT APPROXIMATELY 12:05 PM, N69CL A BEECH BARON 58P IMPACTED THE GROUND AT THE INTERSECTION OF CARRICK ROAD AND STONEHAVEN DRIVE FORT COLLINS, COLORADO APPROXIMATELY FIVE MILES NORTH OF FORT COLLINS/LOVELAND AIRPORT (FNL) ON 355 DEGREES. THE AIRCRAFT IMPACTED FLAT WITH A HEADING OF 322 DEGREES AND WAS DESTROYED ON IMPACT WITH A POST CRASH FIRE. ALL THREE PERSONS ON BOARD RECEIVED FATAL INJURIES. THE AIRCRAFT WAS BEING OPERATED UNDER 14CFR PART 91 IN IMC CONDITIONS UNDER A IFR FLIGHT PLAN FNL TO OMA. A TOTAL OF THIRTEEN WITNESS STATEMENTS WERE OBTAINED FROM LOCAL LAW ENFORCEMENT. SUMMARY OF THE STATEMENTS DESCRIBE THE ENGINES MAKING ERRATIC NOISES, EMERGES FROM THE CLOUDS IN A FLAT SPIN (ONE STATES IN A COUNTERCLOCKWISE ROTATION OF THREE TO FOUR ROTATIONS, PRIOR TO IMPACT) AND THE ELEVATOR IN A FULL UP POSITION. WRECKAGE WAS CONTAINED IN A SMALL AREA WITH ONE RIGHT PROPELLER BLADE BEING THROWN SIXTY TO EIGHTY FEET. THE PILOT HELD A PRIVATE CERTIFICATE WITH SEL, MEL AND INSTRUMENT RATINGS. AN INTERVIEW WITH THE CFI WHO ADMINISTERED A REFRESHER ON JULY 23, 2004, STATED THAT THE N69CL HAD NO ABNORMALITIES DURING THE 3.1 HOUR FLIGHT.

## The NTSB's investigation of this event (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB DEN04FA109](https://openairdocs.org/ntsb/DEN04FA109), Jul 24, 2004: Beech 58P (N69CL), Fort Collins, CO, destroyed, 3 fatal. Probable cause: the loss of engine power for undetermined reasons, and the pilot's failure to maintain adequate airspeed which resulted in a stall/spin. Clouds and the pilot's diverted attention were contributing…

## Other reports on N69CL (3)

Matched to the same aircraft by N-number and date.

- [Incident 20000505017859I](https://openairdocs.org/incident/20000505017859I), May 5, 2000: Beech 58P (N69CL), Winston Salem, NC, Minor damage. (-23)Aircraft landed gear up due to mechanical problems with the gear system, no injuries, minor damage to aircraft.
- [Incident 19960124006539I](https://openairdocs.org/incident/19960124006539I), Jan 24, 1996: Beech 58P (N69CL), Raleigh-Durham, NC. Narrative: aircraft was attempting a visual approach to rdu on rwy 32. The aircraft touched down approximately 1/3 of the length of the runway. The pilot…
- [Incident 19920827039629I](https://openairdocs.org/incident/19920827039629I), Aug 27, 1992: Beech 58P (N69CL), Roanoke Rapids, NC. Oil streaming from nose area from right engine. Engine feathered. Found right front cylinder was broken.

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.