NYC89FA032 · Mooney M20K
Mooney M20K · Accident: uncontrolled altitude deviation en route
From Worcester Regional Airport (ORH) to Igor I Sikorsky Memorial Airport (BDR)
Event
- NTSB case
- NYC89FA032
- 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
- 1 · 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
- Instrument Meteorological Cond
Mooney M20K
- Aircraft type
- Mooney M20
- 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
- N1170Z
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Worcester Regional Airport (ORH), Worcester, MATo Igor I Sikorsky Memorial Airport (BDR), Bridgeport, CT
- 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
- 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
- Destroyed
Cause areas
- Pilot in command › Spatial disorientation
Approximate · Estimated position: the centre of Holden, MA, the place the record names. Not the accident site.
NTSB narrative
THE ACFT MADE A NIGHT INSTRUMENT DEPARTURE WITH A MAXIMUM ASSIGNED ALTITUDE OF 4,000 FT. THE PLT FAILED TO FOLLOW HIS DEPARTURE INSTRUCTIONS CONCERNING ROUTING. HE CLIMBED TO 4,600 FT AND WHEN QUERIED, SAID HE WAS HAVING AUTOPILOT PROBLEMS. A FEW MINUTES LATER, THE ACFT DISAPPEARED FROM RADAR. THE ACFT IMPACTED A LINE OF TREES AT A HIGH SPEED AND WAS EXTENSIVELY BROKEN UP. THE WRECKAGE WAS SCATTERED OVER 450 FT. THE AUTOPILOT PROBLEM WAS NOT IDENTIFIED DUE TO THE EXTENT OF IMPACT DAMAGE; HOWEVER, NO PROBLEM WAS NOTED WITH THE AIRFRAME OR ENGINE. THE PLT WAS CURRENT WITH INSTRUMENTS, BUT NOT FOR NIGHT FLIGHT. THE ACFT PITOT STATIC SYSTEM AND TRANSPONDER WERE BOTH OUT OF INSPECTION.
Probable cause
INFLIGHT LOSS OF CONTROL DUE TO SPATIAL DISORIENTATION AND CONTACT WITH TREES PRIOR TO REGAINING CONTROL AFTER THE PILOT EXPERIENCED AN UNKNOWN PROBLEM WITH THE AUTOPILOT. CONTRIBUTING WAS THE LACK OF RECENT NIGHT EXPERIENCE.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC89FA032
- Event ID
- 20001213X27333
- Case number
- NYC89FA032
- 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: 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: 635b3445fe37c432b8b2444dcfa6737af0553a0a95cd46328c819dc596aa8b2c; retrieved 2026-09-21T03:29:16.258Z.