# Accident 20050216003009A: Cessna 560CESSNA, Pueblo, CO, February 16, 2005

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: February 16, 2005, 09:13 local time
- Place: Pueblo, CO
- Airport: Pueblo Memorial Airport
- Damage: Destroyed
- Phase of flight: Approach
- Operating rules: General operating rules (Part 91)
- Location: 38.2869° N, 104.3925° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=38.2869&lon=-104.3925&mi=10
- Aircraft: N500AT, a cancelled registration (https://openairdocs.org/deregistered/N500AT-2007-02-15) (OpenAirDocs)
- Registry model: Cessna 560 (registry code 2076750, https://openairdocs.org/model/cessna-560) (OpenAirDocs)
- Registry engine: Pratt & Whitney Canada JT15D 5 series (registry code 52113, https://openairdocs.org/engine/pratt-whitney-canada-jt15d-5-series) (OpenAirDocs)
- Reported make and model: CESSNA 560CESSNA
- Reported engine: PWC JT15*
- People aboard: 8
- Fatal injuries: 8
- Pilot flight hours: 8,700 total, 0 in this make and model, 0 in the last 90 days
- NTSB investigation: [NTSB DCA05MA037](https://openairdocs.org/ntsb/DCA05MA037) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20050216003009A

## Narrative

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

(-23) THE AIRCRAFT CRASHED DURING AN INSTRUMENT APPROACH TO PUEBLO AIRPORT. ICING WAS FORECAST AND REPORTED BY OTHER AIRCRAFT IN THE AREA NEAR THE TIME OF THE ACCIDENT.

## 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 DCA05MA037](https://openairdocs.org/ntsb/DCA05MA037), Feb 16, 2005: Cessna 560 (N500AT), Pueblo, CO, destroyed, 8 fatal. Probable cause: the flight crew's failure to effectively monitor and maintain airspeed and comply with procedures for deice boot activation on the approach, which caused an aerodynamic stall from which they did not…

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.