# Incident 20061203029389I: Piper PA46350P, Atlanta, GA, December 3, 2006

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: December 3, 2006, 12:30 local time
- Place: Atlanta, GA
- Damage: Minor damage
- Phase of flight: Normal Cruise
- Operating rules: General operating rules (Part 91)
- Location: 33.7548° N, 84.3902° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=33.7548&lon=-84.3902&mi=10
- Aircraft: N46PT, registered now (https://openairdocs.org/aircraft/N46PT) (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
- People aboard: 2
- Fatal injuries: 0
- Pilot flight hours: 2,700 total, 1,000 in this make and model, 30 in the last 90 days
- NTSB investigation: [NTSB CHI07LA035](https://openairdocs.org/ntsb/CHI07LA035) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20061203029389I

## Narrative

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

(-23) ON DECEMBER 3, 2006, AT APPROX. 1230 EST, PIPER AIRCRAFT PA-46-350P, REGISTRATION NUMBER N46PT WHILE ENROUTE FROM FT MYERS, PAGE AIRPORT (KFMY) TO INDIANAPOLIS METROPOLITAN AIRPORT (KUMP) WITH THE OWNER/PILOT IN COMMAND AND 1 PASSENGER ABOARD EXPERIENCED AN INADVERTENT AUTOPILOT DISCONNECT AND IN FLIGHT UPSET. THE AIRCRAFT WAS AT FL 200 WHEN THE UPSET OCCURRED AND THE PILOT WAS ABLE TO REGAIN CONTROL AT FL 190. THE AIRCRAFT WAS ABLE TO CONTINUE TO THE DESTINATION AND LANDED UNEVENTFULLY. ON DECEMBER 08, 2006, THE OWNER/PILOT CALLED THE INDIANAPOLIS FSDO DUTY PERSON AND NOTIFIED THE INCIDENT.

## 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 CHI07LA035](https://openairdocs.org/ntsb/CHI07LA035), Dec 3, 2006: Piper PA 46-350P (N46PT), Atlanta, GA, substantial damage. Probable cause: The exceedance of airplane design stress limits when the pilot did not maintain aircraft control after his attention was diverted to the right side attitude indicator during cruise flight. An…

## Other reports on N46PT (2)

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

- [Incident 20100425032779I](https://openairdocs.org/incident/20100425032779I), Apr 25, 2010: Piper PA 46-350P (N46PT), Owensboro, KY, Minor damage. Pilot reports that during cruise flight, 15000 ft., 188 KTS TAS, 27 degree f. OAT, the cockpit left side window broke and the aircraft depressurized. All other…
- [Incident 20000512027809I](https://openairdocs.org/incident/20000512027809I), May 12, 2000: Piper PA46350P (N46PT), Indianapolis, IN, Minor damage. (-23)A/c N46PT was landing on runway 15 at Indianapolis metro airport. The pilot says he saw three green landing gear lights and then continued to complete 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.