BFO92FA094 · Mitsubishi MU-2B-40
Mitsubishi MU-2B-40 · Accident: loss of control in flight en route
From Concord Municipal Airport (CON) to Utica, NY
Event
- NTSB case
- BFO92FA094
- 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
- 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
- Unknown
Mitsubishi MU-2B-40
- Aircraft type
- Mitsubishi MU-2
- 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
- N220MA
- Operator
- Richard R. Hough · private individual
- Onboard fatalities
- Unknown
- Route
- From Concord Municipal Airport (CON), Concord, NHTo Utica, NY
- 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
- Loss of control in flight
- 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
- Reason for occurrence undetermined
Approximate · Estimated position: the centre of Concord, NH, the place the record names. Not the accident site.
NTSB narrative
THE 74 YEAR OLD PILOT AND HIS WIFE WERE ON A TRIP TO ATTEND A FUNERAL. A WITNESS, WHO HEARD THE AIRPLANE OVERHEAD, REPORTED THAT IT SOUNDED LOW AND AT LEAST ONE ENGINE WAS OPERATING. HE REPORTED THAT WHEN HE LOOKED UP, THE AIRPLANE WAS IN A DIVE, SPINNING SLOWLY; HOWEVER, THE AIRPLANE DID NOT MAKE A COMPLETE REVOLUTION. RADAR DATA SHOWED THE AIRPLANE IN A LEFT DESCENDING TURN AT APPROXIMATELY 2000 FEET PER MINUTE. THE AIRPLANE IMPACTED THE GROUND ABOUT 3 MILES WEST OF THE AIRPORT IN A NEAR VERTICAL DESCENT, AND MUCH OF THE FORWARD SECTION HAD PENETRATED THE GROUND. THERE WAS A POST-CRASH FIRE. EXAMINATION OF THE AIRPLANE AND VARIOUS ACTUATORS CONFIRMED THAT THE LANDING GEAR WAS RETRACTED, FLAPS WERE EXTENDED 5 DEGREES, ELEVATOR AND AILERON TRIM WERE NEUTRAL, AND THE RUDDER WAS POSITIONED 3 DEGREES LEFT. EXAMINATION OF THE ENGINE CONFIRMED INTERNAL/ROTATIONAL DAMAGE.
Probable cause
LOSS OF CONTROL DURING FLIGHT FOR UNDETERMINED REASON(S).
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record BFO92FA094
- Event ID
- 20001211X15054
- Case number
- BFO92FA094
- 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: a4a889fccafa268ce2f7c9cc35e5f2111aecfb71d5ffee529623c04da4aeae8f; retrieved 2026-09-21T01:03:03.782Z.