FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Flight RAX747 · Mitsubishi MU-2B-36

25 Mar 2004 · Pittsfield, MA, United States

Mitsubishi MU-2B-36 · Accident: in flight encounter with weather en route

From Hagerstown Regional Richard A Henson Field (HGR) to Bangor International Airport (BGR)

Report a problem

Event

NTSB case
NYC04FA093
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
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
Charter & commuter
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

Mitsubishi MU-2B-36

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
N201UV
Operator
Unknown
Onboard fatalities
Unknown
Route
From Hagerstown Regional Richard A Henson Field (HGR), Hagerstown, MDTo Bangor International Airport (BGR), Bangor, ME
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 135: Air Taxi & Commuter
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
In flight encounter with weather
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Stall/spin
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

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

Approximately 3 minutes prior to the accident, the airplane was flying in a northeast direction, at 17,100 feet, and was instructed by air traffic controllers to contact Boston Center. He acknowledged the instruction, and no further transmissions were received from the pilot. Radar data indicated the airplane continued level at 17,100 feet on a northeasterly heading, and maintained a groundspeed of 255 knots, for approximately 2 minutes after the last transmission. The airplane then climbed 300 feet, and descended abruptly, loosing 10,700 feet during the next 46 seconds, while maintaining an approximate groundspeed of 255 knots. The airplane then initiated a climb from 6,700 feet to 7,600 feet, maintained an altitude of 7,600 feet for 4 seconds, and then entered a continuous descent until the last radar contact 17 seconds later, at an altitude of 2,400 feet. Several witnesses observed the airplane prior to it impacting the ground. All of the witness described the airplane in a "flat spin" with the engines running prior to impact. Examination of recorded weather data revealed several areas of light-to-moderate precipitation echoes in the vicinity of the accident site. The maximum echo tops were depicted ranging from 14,000 to 25,000 feet, with tops near 17,000 feet in the immediate vicinity of the accident site. Recorded radar images depicted the airplane traveling through an area of lower echoes for approximately 5-minutes immediately prior to the accident. AIRMET Zulu was current for icing conditions from the freezing level to 22,000 feet over the route of flight and the accident site. Four PIREPs were also issued indicating light-to-moderate rime to mixed icing in the clouds from the freezing level to 16,000 feet. Cloud tops were reported from 16,000 to 17,000 feet by two aircraft. Examination of the airplane and engines revealed no pre-impact mechanical anomalies. Additionally, examination of the cockpit overhead switch panel indicated propeller de-ice, engine intake heat, windshield anti-ice, and wing de-ice were all in the 'off' position. According to the pilot's toxicology test results, pseudoephedrine and diphenhydramine was detected in the pilot's urine. Diphenhydramine was not detected in the blood.

Probable cause

The pilot's loss of aircraft control for undetermined reasons, which resulted in an inadvertent stall/spin and subsequent impact with the ground.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC04FA093
Event ID
20040402X00418
Case number
NYC04FA093
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, coordinates. 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: fd716358cc50b1ee0efb8edf0fcb01f48a90ce66ebe32be02a9fb3bf8910b13f; retrieved 2026-09-18T13:00:59.599Z.