NYC04FA093

NTSB accident investigation · Mitsubishi MU-2B-36 · Pittsfield, MA · March 25, 2004

Accident · FatalField investigationFinal report
Date
March 25, 2004, 05:33 local (10:33 UTC)
Place
Pittsfield, MA
Injuries
1 fatal
Damage
Substantial damage
Phase of flight
Enroute
Aircraft
N201UVMitsubishi MU-2B-36
Weather
Visual (VMC) · Night
Status
Completed · report July 7, 2005
Report
Approved by Office Director
Parties
Mitsubishi Heavy Industries America, Inc., Honeywell Engines, Massachusetts Aeronautics Commission, FAA/AAI-100
FAA report
20040325003729A
Case key
58949

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.

On this page

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.

Sequence of events

NTSB’s coding before 2008: each occurrence and phase of flight, and the causes and factors under it. The codes are defined in NTSB’s coding manual.

In flight encounter with weatherCruise
Weather condition - icing conditions
Weather condition - clouds
Loss of control - in flightCruise
Light condition - night
Aircraft control - not maintainedPilot in commandCause
Airspeed - not maintainedPilot in command
Stall/spin - inadvertentPilot in command
In flight collision with terrain/waterDescent - uncontrolled
Terrain condition - ground

Analysis

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.

Factual narrative

History of flight

On March 25, 2004, at 0533 eastern standard time, a Mitsubishi MU-2B-36, N201UV, operated by Royal Air Freight Inc., as flight RAX747, was substantially damaged when it impacted terrain in Pittsfield, Massachusetts. The certificated airline transport pilot was fatally injured. Visual meteorological conditions prevailed at the time of the accident, and an instrument flight rules (IFR) flight plan had been filed for the flight, which originated at the Hagerstown Regional Airport (HGR), Hagerstown, Maryland. The on-demand cargo flight was destined for the Bangor International Airport (BGR), Bangor, Maine, and conducted under 14 CFR Part 135.

The Director of Operations for Royal Air Freight reported that the accident trip originated at the Oakland County International Airport (PTK), Pontiac, Michigan, about 2330, on the evening of March 24, 2004. The pilot flew from PTK to the Greater Rockford Airport (RFD), Rockford, Illinois, picked up cargo, and then flew to Hagerstown. The pilot dropped off a portion of the cargo at Hagerstown, and was en route to Bangor, Maine, when the accident occurred.

According to recorded communications provided by the Federal Aviation Administration (FAA), the pilot contacted the Elkins Flight Service Station at 0353 on the day of the accident, and filed an IFR flight plan from Hagerstown to Bangor. The specialist filed the flight plan and then asked the pilot if he was aware of turbulence and icing advisories, and mountain obscurations in New England. The pilot responded, "yeah, I got all the weather."

A review of the pilot's flight log, which was located in the airplane, revealed the pilot departed Hagerstown at 0423.

According to FAA air traffic control (ATC) transmissions, just prior to the accident, the airplane was being handled by the New York Air Route Traffic Control Center (ARTCC), flying in a northeast direction, in the vicinity of the Pittsfield Airport. All transmissions from the pilot were routine, and he did not report any problems with the airplane.

At 0530, controllers instructed the pilot to "contact boston center on ah one two three point seven five." The pilot responded, "two three seven five seven four seven so long." 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. At 0532:34, the airplane climbed 300 feet, and then descended abruptly, loosing 3,000 feet over the following 14 seconds. During the airplane's climb and abrupt descent, a groundspeed of 255 knots was maintained. Over the following 33 seconds the airplane continued to descend from 14,400 feet to an altitude of 6,700 feet, during which time the groundspeed increased slightly to 260 knots and then decreased gradually to 176 knots.

At 0533:25 the airplane initiated a climb from 6,700 feet to 7,600 feet and its groundspeed decreased from 176 knots to 125 knots. The airplane 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. One witness reported that the sound of the airplane first drew her attention to it. She described a loud grinding sound coming from the airplane, similar to "a metal I-beam going through a grinder." This sound continued for about 5-7 seconds, stopped briefly, and started again. As the sound continued, she observed the airplane spinning in a nose-high, tail low attitude, almost as if it were "hovering." She stated that the airplane began to "veer to the right," as the metallic noise stopped again. She then heard a "whining" sound coming from the airplane, as it continued to spin. She lost sight of the airplane behind trees, and then heard the impact.

A second witness observed the airplane from his second-floor apartment about 1-1/2 miles from the accident site. He stated that he could hear the airplane before he could see it, due to an overcast cloud layer, at an altitude of about 1,500 feet. The witness described the sound as a loud "howling" sound, similar to a pair of motorcycles. The sound was synchronized and continuous, with no interruption. When the witness observed the airplane "break out of the clouds," it was spinning in a counter-clockwise direction, with about a 10-degree nose-down attitude. As the witness observed the airplane spin, he also heard the sound of the engines get louder and quieter with each rotation. The witness reported that the airplane continued to spin until it impacted the ground.

A third witness observed the airplane pass over his house in a south to north direction, in a "flat spin." According to the witness, as the airplane continued to travel to the north, he heard the sound of the engines "throttling up, then throttling down, as if the pilot were trying to recover."

A fourth witness reported hearing a loud noise overhead, and looked up to see the airplane in a "flat spin." The witness reported that the engines were "very loud," and the airplane continued to spin until it impacted the ground.

Personnel information

The pilot held an airline transport pilot certificate, and was type-rated in the Learjet. He also held a flight instructor certificate, with ratings for airplane single and multi-engine land, instrument airplane. His most recent FAA first-class medical certificate was issued on January 29, 2004, at which time he reported 6,500 hours of total flight experience.

According to the Director of Operations at Royal Air Freight, the pilot was hired in April 1998, and began flying the MU-2 in May 1998. Since that time, he had accumulated more than 2,000 hours in the MU-2. He received his type rating in the Learjet on January 23, 2001, and at the time of the accident was routinely flying both the Learjet and the MU-2. In the 90 days prior to the accident, the pilot had accumulated 142 hours in the MU-2. In the week prior to the accident, the pilot logged about 4.4 hours in the MU-2, and 10.1 hours in the Learjet.

The pilot's total duty time during the week prior to the accident included: a 4.4 hour trip in the MU-2 on March 22, 2004, followed by a 10.1-hour trip in the Learjet, originating at 1330 on March 23, 2004, and ending at 0400 on March 24, 2004. The pilot was off-duty from 0400 until 2330 on March 24, 2004, at which time the accident trip commenced.

Aircraft information

Review of the airplane logbooks revealed the airplane was maintained in accordance with an FAA Approved Aircraft Inspection Program (AAIP). The last AAIP 125-hour inspection was performed on the airplane on February 12, 2004, at an aircraft time of 13,419.9 total flight hours. No mechanical anomalies were noted in the logbooks.

Meteorological information

A Safety Board meteorologist conducted a review of weather conditions at the time of the accident. According to the meteorologist's Factual Report, weather charts and recorded data indicated that a dissipating warm front was present in the vicinity of the accident site, and another defined warm front was moving across Ohio, West Virginia, and Maryland, into New England. The northeast section of the National Weather Service (NWS) Radar Summary Chart, issued at 0418 depicted an area of light-to-moderate intensity echoes in the vicinity of the accident site. No NWS Radar Summary Chart was available for 0500, and 0600; however, the radar summary chart issued at 0717, depicted several areas of 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

Aircraft

Registration
N201UV
Reported as
Mitsubishi MU-2B-36
Category
Airplane
Serial number
680
Airframe hours
13,420
Engines
Garrett-AiResearch TPE331-10-511, 900 horsepower, turbo propGarrett-AiResearch TPE331-10-511, 900 horsepower, turbo prop
Damage
Substantial damage
Fire
On-Ground
Flight
Part 135
Registered owner
Royal Air Freight Inc
Airworthiness certificate
Standard, Normal
Last inspection
AAIP · February 12, 2004
Departed
HGR · Hagerstown, MD
Destination
BGR · Bangor, ME
Flight plan
IFR

Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

Flight crew

As NTSB recorded them. NTSB leaves out names.

Role
Pilot
Age
33
Injuries
Fatal
Certificates
Airline transport, Flight instructor
Airplane ratings
Multi-engine land, Single-engine land
Instrument ratings
Airplane
Medical
Class 1, Valid Medical--w/ waivers/lim
Seat
Left
Toxicology
Performed
Flight hours
6,500 total · 2,000 in this make and model

Weather

Conditions
Visual (VMC) · Night
Wind
Variable at 6 knots
Visibility
10 statute miles
Lowest ceiling
5,000 ft overcast
Temperature
41 °F, dew point 34 °F
Altimeter
30.47 inHg
Observed at
PSF

FAA reports on this event · 1

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.