IAD04FA021

The pilot was finishing his third round-trip, Part 135 cargo flight. The first round trip began the previous evening, about 2150, and the approach back to the origination airport resulted in a landing on runway 15R at 2305. The second approach back to the origination airport resulted in a landing on runway 28 at 0230. Prior to the third approach back to the airport, the pilot was cleared for, and acknowledged a visual approach to runway 33R twice, at 0720, and at 0721. However, instead of proceeding to the runway, the airplane flew north of it, on a westerly track consistent with a modified downwind to runway 15L. During the westerly track, the airplane descended to 700 feet. Just prior to an abeam position for runway 15L, the airplane made a "sharp" left turn back toward the southeast, and descended into the ground. Witnesses reported the airplane's movements as "swaying motions as if it were going to bank left, then right, and back left again," and "the nose...pointing up more than anything...but doing a corkscrew motion." Other witnesses reported the "wings straight up and down," and "wings vertical." Tower controllers also noted the airplane to be "low and tight," and "in an unusually nose high attitude close to the ground. It then "banked left and appeared to stall and then crashed." A post-flight examination of the wreckage revealed no evidence of mechanical malfunction. The pilot, who reported 6,800 hours of flight time, had also flown multiple round trips the previous two evenings. He had checked into a hotel at 0745, the morning prior to the accident flight, checked out at 1956, the same day, and reported for work about 1 hour before the first flight began.

History of flight

On May 14, 2004, at 0724 eastern daylight time, a Mitsubishi MU-2B-60, N755AF, operating as Epps Air Service flight 101, was destroyed when it impacted trees and terrain in Ferndale, Maryland, while approaching Baltimore-Washington International Airport (BWI), Baltimore, Maryland. The certificated airline transport pilot was fatally injured. Visual metrological conditions prevailed for the flight that had been operating on an instrument flight rules flight plan from Philadelphia International Airport (PHL), Philadelphia, Pennsylvania. The non-scheduled cargo flight was operating under 14 CFR Part 135.

A review of the Federal Aviation Administration (FAA) Air Traffic Control accident package revealed that the airplane departed Philadelphia International Airport, runway 08, at 0658, and the pilot contacted the Philadelphia South Departure controller at 0659. At 0702, the pilot was told to contact a Philadelphia South Arrival controller, and at 0711, he was told to contact a Potomac Approach Control controller. The controller accepted the airplane 47 miles northeast of Baltimore-Washington, at 8,000 feet. On initial contact, the pilot advised that he had ATIS information x-ray. The controller issued the current Baltimore altimeter setting, and told the pilot to expect a visual approach to runway 33R.

At 0713, the pilot was cleared to descend to and maintain 4,000 feet, and at 0714, he was cleared to proceed direct to the airport.

At 0717, the pilot was instructed to change to a Baltimore-Washington International Final South radio frequency, and 4 seconds later, he did so.

At 0718, the pilot reported the airport in sight, and the controller cleared him to descend to and maintain 2,500 feet.

At 0720, the pilot was advised of traffic at 12 o'clock, 2 1/2 miles, at 2,000 feet. The pilot reported the traffic in sight, and was instructed to maintain visual separation, then cleared for a visual approach to runway 33R.

At 0721, the pilot acknowledged the clearance and read back the assigned runway, then was advised to contact Baltimore Tower.

At 0721:37, the pilot stated: "baltimore tower epps one oh one with you three three right."

At 0721:43, the tower (local) controller responded: "epps one oh one runway three three right, cleared to land, wind calm."

At 0721:47, the pilot responded: "cleared to land three three right one oh one."

At 0723:22, the controller stated: "epps one oh one, traffic's a dash eight to depart," and the pilot responded, "one oh one."

At 0724:09, the controller stated: "epps, epps one oh one."

There were no further transmissions from the pilot.

Radar returns revealed that the airplane was on a westerly track, north of the airport, that bypassed the approach end of runway 33R, consistent with a modified downwind for runway 15L. Along that track, the airplane descended to 700 feet. Just prior to an abeam position for runway 15L, the airplane began a left turn back toward the southeast. The last radar return occurred in the approximate position of the wreckage site, with the airplane at an indicated altitude of 200 feet.

Several witnesses noticed the airplane just prior to the accident. One stated that it was "flying abnormally," and initially thought it was a stunt plane. He noticed it making "swaying motions as if it were going to bank left, then right, and back left again." As the airplane neared a tree line, its "nose flipped up and back."

Another witness was standing outside when he noticed the airplane flying "very low" near a high school. It "all of a sudden made a very sharp bank to the left," then "began tilting right, then left, and finally completely back to left over a 180-degree bank, and directly into the ground."

A third witness, who recognized the airplane, saw it "banking hard to the left, then the right, then the left, back and forth. It was never inverted or level, but always out of control. The nose was pointing up more than anything, but it was, however, doing a corkscrew motion. I lost it behind a row of trees with the nose way up, maybe 60 degrees, and the wings vertical."

A fourth witness reported seeing the wings "straight up and down," while other witnesses reported the airplane "at about a 45-degree angle, then rolled to the opposite angle," "pitch and roll violently," "falling tail over nose," "wings were straight up and down," and "seemed to tip to the left with a sharp turn."

Four controllers in the tower provided written statements. The tower supervisor stated that he saw the airplane enter a "midfield downwind" for runway 33R. The airplane appeared to be "low and tight." As the supervisor "questioned his approach, [the airplane] banked left and appeared to stall and then crashed."

The local controller stated that she cleared the airplane to land on runway 33R. She then called the pilot about a DH-8 to depart before his arrival, and the pilot acknowledged the transmission. The local controller was next alerted to the airplane when the tower supervisor "showed concern over the erratic handling of the aircraft." She then saw the airplane close to the ground.

Another controller wrote that he was alerted to the airplane by the tower supervisor's "concern over the unusual approach of [the] aircraft. Looking toward the location, I observed an aircraft in an unusually nose high attitude close to the ground."

The fourth controller, who was working the clearance delivery position, heard the tower supervisor say, "What's this guy doing?" He looked out, and saw "an aircraft in an unusual attitude. The aircraft seemed to spiral to the ground and then I saw a plume of smoke."

The accident occurred during daylight hours, in the vicinity of 39 degrees, 11.205 minutes north latitude, 76 degrees, 39.026 minutes west longitude.

Personnel information

The pilot held an airplane transport pilot certificate with a CL-600 type rating. On his latest application for an FAA first class medical certificate, issued May 7, 2004, the pilot reported 6,800 hours of total flight time.

According to company records, the pilot's latest FAR Part 135 proficiency check was completed on February 9, 2004.

Company records also revealed that the pilot had flown the accident airplane the evenings of May 11th-12th, and May 12th-13th, as well as the evening of May13th-14th.

The pilot's duty time, starting on the evening of May 11th, was from 2000 until 0500, when he logged 3.1 hours of flight time from PHL-BWI-PHL-BWI-PHL-BWI-PHL.

The pilot's duty time, starting on the evening of May 12th, was from 2330 until 0800, when he logged 2.1 hours, including 1.6 hours of night time, from BWI-PHL-BWI-PHL-BWI.

The pilot's intended routing, starting on the evening of May 13th, was BWI-PHL-BWI-PHL-BWI-PHL-BWI.

A Safety Board air traffic control specialist reviewed the pilot's earlier arrivals at BWI. According to the specialist, during the first arrival, the pilot contacted the tower controller about 20 nautical miles east of the airport, and was cleared to land on runway 15R. The pilot asked the controller when the "short runway" was expected to open, and the controller indicated it would be about 0600. The pilot then landed on runway 15R at 2305.

During the second arrival, the pilot also contacted the tower controller about 20 nautical miles east of the airport, "with you for runway one zero and is two eight available?" The pilot was subsequently cleared to, and landed on runway 28 at 0230.

A receipt from a hotel close to Baltimore-Washington Airport revealed that the pilot checked in on May 13th, at 0745, and checked out that same day at 1956.

According to the company's director of operations, the pilot would have normally arrived at work about 1 hour prior to his first flight, and his first reported taxi-out time was about 2150.

Aircraft information

According to aircraf