# Accident 20000813040789A: Beech A36, Sloatsburg, NY, August 13, 2000

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: August 13, 2000, 18:20 local time
- Place: Sloatsburg, NY
- Damage: Substantial damage
- Phase of flight: Normal Cruise
- Operating rules: General operating rules (Part 91)
- Location: 41.1606° N, 74.1895° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=41.1606&lon=-74.1895&mi=10
- Aircraft: N100XH, registered now (https://openairdocs.org/aircraft/N100XH) (OpenAirDocs)
- Registry model: Raytheon A36 (registry code 7150001, https://openairdocs.org/model/raytheon-a36) (OpenAirDocs)
- Registry engine: Continental IO-550 series (registry code 17042, https://openairdocs.org/engine/continental-io-550-series) (OpenAirDocs)
- Reported make and model: BEECH A36
- Reported engine: CONT IO550*
- People aboard: 1
- Fatal injuries: 0
- Pilot flight hours: 22,445 total, 1,100 in this make and model, 50 in the last 90 days
- NTSB investigation: [NTSB NYC00LA270](https://openairdocs.org/ntsb/NYC00LA270) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20000813040789A

## Narrative

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

(.4) THE PILOT REPORTED THAT WHILE FLYING IN IMC, HE WAS HAVING DIFFICULTY WITH THE AUTOPILOT. SPECIFICALLY, HE WAS HAVING PROBLEMS HOLDING ASSIGNED HEADINGS, AND ENGAGING THE AUTOPILOT. THE AIRPLANE THEN BEGAN A RAPID DESCENT, BUT THE PILOT WAS ABLE TO RECOVER ONCE IN VMC. PRIOR TO THE ACCIDENT FLIGHT, THE PILOT EXPERIENCED DIFFICULTY WITH ANOTHER AIRPLANE. IN THAT AIRPLANE, WITH A DIFFERENT MODEL AUTOPILOT, HE LOST CONTROL WHILE LANDING. ACCORDING TO REPRESENTATIVES FROM THE AIRPLANE AND AUTOPILOT MANUFACTURERS, THE PILOT AND OWNER COMPLAINED ABOUT AUTOPILOT PROBLEMS IN THE PAST. HOWEVER, ON AT LEAST TWO OCCASIONS PRIOR TO THE ACCIDENT FLIGHT, THE OWNER OR PILOT OF THE AIRPLANE HAD BEEN OPERATING THE AUTOPILOT WHILE THE AIRPLANE WAS OUTSIDE THE SPECIFICATIONS FOR SAFE AUTOPILOT OPERATION. PRIOR TO THE ACCIDENT, THREE SEPARATE TEST FLIGHTS DID NOT REVEAL ANY MALFUNCTIONS. AFTER THE ACCIDENT, THE PILOT STATED THAT HE MIGHT HAVE DEPARTED WITH THE AUTOPILOT IN THE SLAVED NAV HEADING DISENGAGED MODE. SUBSEQUENTLY, DATA RETRIEVED FROM THE AUTOPILOT DID NOT INDICATE ANY MALFUNCTIONS.                                                                                                         (-23) FAA FLIGHT STANDARDS BECAME AWARE OF THIS ACCIDENT BY VIRTUE OF A HOTLINE COMPLAINT THAT HAD BEEN FILED BY THE OWNER OF THE AIRCRAFT, ^PRIVACY DATA OMITTED^ ALLEGED THAT THE MANUFACTURER OF THE AUTOPILOT (HONEYWELL) WAS RESPONSIBLE FOR THE DAMAGE TO HIS AIRCRAFT WHICH RESULTED FROM AN UNCOMMANDED PITCH DAMAGE WHICH CAUSED AN UNCONTROLLED DESCENT. INVESTIGATION DETERMINED THAT THE PILOT, MR. NORMAND PAULHUS, WAS ON AN INSTRUMENT FLIGHT RULES CLEARANCE AND WAS ALLEGEDLY EXPERIENCING DIFFICULTIES IN MANAGING THE AUTOPILOT. ACCORDING TO MR. PAULHUS, THE AIRCRAFT SUDDENLY PITCHED DOWN AND COMMENDED AN UNCONTROLLED DESCENT. THE PILOT STATED THAT HE FINALLY REGAINED CONTROL WHEN HE ENTERED VISUAL CONDITIONS AND WAS ABLE TO REFERENCE THE GROUND. THE AIRCRAFT RECEIVED SIGNIFICANT DAMAGE FROM WHAT APPEARS TO HAVE BEEN IN-FLIGHT STRESS AS A RESULT OF EXCEEDING DESIGN LIMITS OF THE AIRCRAFT. POST-EVENT TESTING OF THE AIRCRAFT AND FLIGHT CONTROL SYSTEM WAS CONDUCTED WITH MR. PAULHUS ONCE AGAAIN OPERATING THE AUTOPILOT. WHILE MFGR'S REPS COULD FIND NO APPARENT CAUSE FOR THE UNCONTROLLED DESCENT IT WAS OBSERVED THAT DURING THE POST-EVENT FLIGHT TEST MR. PAULHUS FAILED TO FOLLOW             THE PRESCRIBED PROCEDURES.

## 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 NYC00LA270](https://openairdocs.org/ntsb/NYC00LA270), Aug 13, 2000: Beech A36 (N100XH), Sloatsburg, NY, substantial damage. Probable cause: The pilot's failure to maintain aircraft control. A factor was the pilot's diverted attention.

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.