NYC89FA093 · Piper PA-31-350
Falcon Flight Center Piper PA-31-350 · Accident: uncontrolled altitude deviation en route
From Hartford Brainard Airport (HFD) to Atlantic City International Airport (ACY)
Event
- NTSB case
- NYC89FA093
- 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
- 0 · all aircraft and ground
- Ground fatalities
- 0
- 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
- Visual Meteorological Cond
Piper PA-31-350
- Aircraft type
- Piper PA-31
- 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
- N40978
- Operator
- Falcon Flight Center
- Onboard fatalities
- Unknown
- Route
- From Hartford Brainard Airport (HFD), Hartford, CTTo Atlantic City International Airport (ACY), Atlantic City, NJ
- 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 · cruise
- First occurrenceThe 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
- Uncontrolled altitude deviation
- 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
- Pilot in command › Aircraft control, not maintained
- Pilot in command › Airspeed, not maintained
- Pilot in command › Design stress limits of aircraft, exceeded
Approximate · Estimated position: the centre of Toms River, NJ, the place the record names. Not the accident site.
NTSB narrative
THE ACFT WAS CRUISING AT 8500 FT WHEN IT EXPERIENCED AN INFLT LOSS OF CONTROL. THE PLT SAID THE AUTOPILOT PITCH TRIM RAN AWAY NOSE DOWN & HE WAS UNABLE TO DISCONNECT THE AUTOPILOT PRIOR TO THE LOSS OF CONTROL. EXAM OF THE ACFT SHOWED THE LEFT ELEVATOR HORN WAS BENT DOWN & THE RIGHT ELEVATOR HORN WAS BROKEN OFF. THE AUTOPILOT WAS EXAMINED & ALL DISCONNECTS EXCEPT FOR THE ACCELEROMETER TEST FUNCTIONED PROPERLY. THE PITCH TRIM BOARD WAS FOUND IMPROPERLY INSTALLED IN THE AUTO PILOT & DID NOT MAKE CONNECTION. WITH THE ALTITUDE HOLD ENGAGED, THE AUTOPILOT WOULD HOLD THE ELEVATOR POSITION AT TIME OF ENGAGEMENT & TRIM TO KEEP THE FORCES NEUTRAL. IF THE AIRCRAFT SLOWED, IT WOULD LOSE ALTITUDE & TRIM NOSE UP. RADAR DATA SHOWED THE ACFT STARTED TO SLOW, THEN DESCENDED FROM 8500 TO 8300 FT, THEN CLIMBED TO 8900 FT. THE ACFT THEN CAME DOWN VERY RAPIDLY TO 1700 FT PRIOR TO A RECOVERY. RPRTDLY, THE PLT DID NOT TEST THE AUTOPLT BEFORE TAKEOFF. .
Probable cause
FAILURE OF THE PILOT TO MAINTAIN AIRSPEED AND CONTROL OF THE AIRCRAFT, AND HIS EXCEEDING THE DESIGN STRESS LIMITS OF THE AIRCRAFT. FACTORS RELATED TO THE ACCIDENT WERE: AUTOPLT MALFUNCTION DUE TO IMPROPER INSTALLATION BY MAINTENANCE PERSONNEL AND THE PILOT'S FAILURE TO PREFLIGHT THE AUTOPILOT BEFORE USING IT IN FLIGHT.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC89FA093
- Event ID
- 20001213X27977
- Case number
- NYC89FA093
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1989-03-02.
- API snapshot SHA-256: 8d3d05a1409f414c6dcf4c4dd4ea308f65f4b723587aa7f569f25e94fd58eba9; retrieved 2026-09-23T07:50:37.857Z.