# Accident 20060913020209A: Piper PA46350P, Colorado Spring, CO, September 13, 2006

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: September 13, 2006, 15:20 local time
- Place: Colorado Spring, CO
- Airport: City Of Colorado Springs Municipal
- Damage: Substantial damage
- Phase of flight: Level Off Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 38.8161° N, 104.7008° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=38.8161&lon=-104.7008&mi=10
- Aircraft: N71DH, a cancelled registration (https://openairdocs.org/deregistered/N71DH-2024-04-30) (OpenAirDocs)
- Registry model: Piper PA 46-350P (registry code 7104620, https://openairdocs.org/model/piper-pa-46-350p) (OpenAirDocs)
- Registry engine: Lycoming TI0-540 series (registry code 41533, https://openairdocs.org/engine/lycoming-ti0-540-series) (OpenAirDocs)
- Reported make and model: PIPER PA46350P
- Reported engine: PWA PT6A34
- People aboard: 2
- Fatal injuries: 0
- NTSB investigation: [NTSB DEN06CA127](https://openairdocs.org/ntsb/DEN06CA127) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20060913020209A

## Narrative

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

(-23) PILOT CLAIMS HE WAS CLEARED FOR VISUAL THE RUNWAY WAS VACANT, IT WAS ALSO VACANT WHEN HE WAS CLEARED TO LAND. ON SHORT FINAL HE HEARD THE TOWER CLEAR A MD-80 FOR TAKEOFF IN FRONT OF HIM. HE WAS SURPRISED THAT THE MD-80 DID NOT D A ROLLING START AND THAT TOWER DID NOT ORDER HIM TO EXPEDITE FOR LANDING TRAFFIC. HE ELECTED TO CONTINUE THE APPROACH AND THOUGHT IT COULD BE SAFELY COMPLETED BEFORE THE POINT THE MD-80 ROTATED. HE UNEXPECTEDLY ENCOUNTERED SEVERE TURBULENCE FROM THE ENGINES OF THE DEPARTING JET. THE AIRCRAFT HAD A HARD LANDING THAT CAUSED STRUCTURAL DAMAGE.

## 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 DEN06CA127](https://openairdocs.org/ntsb/DEN06CA127), Sep 13, 2006: Piper PA-46T-350P (N71DH), Colo. Springs, CO, substantial damage. Probable cause: The pilot's failure to maintain control of the airplane, resulting in an inadvertent stall. Contributing factors in this accident were the jet blast encounter, and the pilot's failure to initiate a…

## Other reports on N71DH (1)

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

- [Accident 20130310003359A](https://openairdocs.org/incident/20130310003359A), Mar 10, 2013: Piper PA 46-350P (N71DH), Rogers, AR, Destroyed. On March 10 2013 at approximately 8:00 pm, the pilot stated he was on ILS approach for rw 20 at Rogers, AR. Gusting winds and turbulence were encountered. The…

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.