FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN11FA133 · Piper PA-46-310P

30 Dec 2010 · Milaca, MN, United States

Teemark Piper PA-46-310P · Accident en route

From Aitkin Municipal Airport Steve Kurtz Field (AIT) to Beaumont Municipal Airport (BMT)

Report a problem

Event

NTSB case
CEN11FA133
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
Instrument Meteorological Cond

Piper PA-46-310P

Aircraft type
Piper PA-46
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
N9103N
Operator
Teemark
Onboard fatalities
Unknown
Route
From Aitkin Municipal Airport Steve Kurtz Field (AIT), Aitkin, MNTo Beaumont Municipal Airport (BMT), Beaumont, TX
Aircraft age
Not recorded
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
En route · climb to cruise
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
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 oper/perf/capability
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

About 20 minutes after departing on a cross-country flight, the pilot acknowledged the air traffic controller’s clearance to climb to 17,000 feet mean sea level (msl). Radar data indicated that the airplane reached a maximum altitude of 16,800 feet msl. The airplane then entered a right descending turn followed by a left descending turn. While in the left turn, the pilot informed the controller, “I lost my autopilot; I’m in an unusual attitude.” The pilot stated this same information two more times in response to transmissions by the controller. The pilot’s last transmission was that he was busy trying to recover the airplane. Witnesses heard the airplane flying overhead for several minutes, but they could not see it due to the low ceiling.

A postaccident examination of the airplane did not reveal any preaccident mechanical malfunctions or failures with the engine that would have precluded normal operation. Examination of the autopilot system revealed a loose screw inside the pitch servo housing. The screw was one of two that secured the high wattage resistor to the solenoid housing. Observed corrosion within the screw threads was consistent with the threads not being engaged in a nut or other internally threaded feature. No mechanical damage or arcing was visible on the screw. The operational impact of the loose screw is unknown.

The pilot’s instrument flying proficiency could not be determined. According to log records, the pilot last flew 4.5 months before the accident. The airplane was in instrument meteorological conditions when the pilot stated that he was trying to recover from the unusual attitude. The pilot did not follow prescribed procedures for an autopilot malfunction. Weather data indicates that the airplane most likely encountered turbulence and icing conditions during the flight; however, the airplane was equipped with an ice protection system. Although ethanol was found during the toxicology tests, the levels varied greatly among the tissue/fluid samples. The investigation was unable to determine if the presence of ethanol was from ingestion or from postmortem production or contamination. The detected level of diphenhydramine, an over-the-counter sedating antihistamine used to treat allergies, was above therapeutic levels and likely contributed to the pilot’s inability to recover from the unusual attitude.

Probable cause

The pilot did not recover from an unusual attitude while operating in instrument meteorological conditions following a disconnect of the autopilot system for undetermined reasons. Contributing to the accident were the pilot’s lack of recent flight experience and impairment due to diphenhydramine.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN11FA133
Event ID
20101230X40808
Case number
CEN11FA133
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. 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: 8308ff3adc3bc669562394db7ae304df9b60a71a77fd1d4acdb30f95ef2a383a; retrieved 2026-09-13T21:12:04.821Z.