MIA02FA044

The flight was cleared for the ILS approach to runway 5R. The flight was at mid runway, at 2,100 feet, heading 049 degrees, at a speed of 163 knots, when the pilot stated "...missed approach." He was instructed to maintain 2,000, and to fly runway heading. Radar showed N41003 started a right turn, was flying away from the airport/VOR, descending. At a point 0.57 miles from the airport/VOR, the flight had descended to 1,500 feet, was turning right, and increasing speed. The flight had descended 400 feet, and had traveled about 0.32 miles in 10 seconds. When radio and radar contact were lost, the flight was 2.35 miles from the airport/VOR, level at 1,600 feet, on a heading of 123 degrees, and at a speed of 169 knots. The published decision height (DH) was 620 feet mean sea level (msl). The published minimum visibility was 1/2 mile. The published Missed Approach in use at the time of the accident was; "Climb to 1,000 [feet], then climbing right turn to 2,500 [feet] via heading 130 degrees, and RDU R-087 [087 degree radial] to ZEBUL Int [intersection] and hold." A witness stated that the aircraft was flying low, power seemed to be in a cruise configuration, and maintaining the same sound up until the crash. The reported weather at the time was: Winds 050 at 5 knots, visibility 1/2 statute mile, obscuration fog and drizzle, ceiling overcast 100, temperature and dew point 11 C, altimeter 30.30 in HG. At the time of the accident the pilot had 10 total flight hours in this make and model airplane; 33 total night flight hours; and 59 total instrument flight hours.

History of flight

On December 12, 2001, about 1904 eastern standard time, a Piper PA-46-350P, N41003, operated by M&M Aero LLC, as a Title 14 CFR Part 91 business flight impacted with a private home in a residential area about 2 miles southeast of the Raleigh/Durham International (RDU) Airport, Raleigh, North Carolina. Instrument meteorological conditions prevailed. An instrument flight rules (IFR) flight plan was filed. The airplane was destroyed. The private rated-pilot and two passengers were fatally injured. There were no injuries on the ground. The flight had originated from the Dothan, Alabama Airport, at 1648 (1548 central standard time).

At 1358, central standard time (CST), the pilot contacted the Anniston AFSS (Automated Flight Service Station), Flight Data position to file an IFR flight plan, and received a standard weather briefing from Dothan, to RDU. The pilot estimated the time en route to be about 2 hours 15 minutes, and 7 hours of fuel on board. The pilot was told there was an AIRMET (Airman's Meteorological Information Network) for IFR across the entire route, and "low IFR" basically the current condition at Dothan. He was told that the RDU forecast was; "…winds [at] zero six zero [060 degrees] at three, half a mile fog overcast two hundred with occasional two miles mist overcast eight hundred...valid till twelve hundred Zulu [0800]." He was told that RDU was expecting "...half a mile fog and overcast two hundred...about a forty percent probability it may go to 2 miles with mist overcast 800." The specialist said, "...I'll be real honest with you I doubt you'll see that...I don't believe your going to get that break." The pilot asked the specialist for an alternate airport, something that was VFR [visual flight rules]. He was told there was nothing in Georgia or the Carolinas; maybe there was something in northeast Tennessee or Virginia. The pilot said, he wanted something with an ILS (instrument landing system), and decided on Tri City, Tennessee. The pilot was then given the following PIREP (pilot reports); 20 miles southwest of Raleigh at 4,000 feet a Beech Baron reported IMC (instrument metrological conditions) at 400 feet, light rain and turbulence. The briefing ended at 1404: 19 CST.

After takeoff and climb to altitude, the flight was transferred through several sectors and proceeded without incident until 1844, when the pilot of N41003 reported on the Raleigh East Arrival Radar (E-AR) frequency, level at 9,100 feet, heading 028 degrees, and reducing speed to 191 knots. The pilot of N41003 was advised to expect the ILS Runway 5R.

At 1849:38, the E-AR controller instructed the pilot of N41003 to fly heading 070, join the runway 5R localizer, and maintain 6,000 feet. The initial read back was incorrect, the altitude was restated, and the second read back was correct.

At 1853:59, the controllers conducted a position relief briefing between E-AR and the Raleigh West Final Radar (W-FR). W-FR opened and assumed appropriate airspace and traffic.

At 1854:48, the pilot of N41003 was instructed by the W-FR controller to keep "his speed up," and asked by the control what speed he was indicating. The pilot answered "approximately 190 knots." The pilot reported passing through 5,600 feet, for 3,000 feet.

At 1855:26, the flight joined the Runway 5R localizer on an 18.75 mile final, at a speed of 195 knots, and descended through 5,200 feet.

At 1857:25, the W-FR controller issued the pilot of N41003, an ILS Runway 5R clearance, which instructed him to maintain at least 170 knots until the Final Approach Fix. The pilot responded, "...we'll try it sir." Radar showed that the flight was on the localizer, on a 12.5-mile final, below the glide slope, descending through 3,700 feet, and at a speed of 185 knots.

The pilot of N41003 contacted the Raleigh Local Control East (LC-E), when the flight was at 3,000 feet. He was issued a clearance to land, and told that the RVR (runway visual range) roll out was 4,000 feet. The pilot acknowledged.

At 1859:12, radar showed N41003 was on the localizer, on glide path, on a 7.25 mile final, at an altitude of 2,900 feet, and reducing speed to 167 knots. At 1859:44, the flight was at the Final Approach Fix (5.8 miles from the runway threshold), on the localizer, above the glide slope, at an altitude of 2,900 feet, and reducing speed to 148 knots. At 1900:47, on the localizer, on the glide slope, on a 3.5 mile final, at an altitude of 2,900 feet, and reducing speed to 124 knots. At 1901:35, the flight began a descent out of 2,900, was on localizer, above glide slope, 1.9 from the runway threshold, at 119 knots.

At 1902:17, N41003 was at the runway threshold, descending to 2,200 feet, on a heading of 052 degrees, increasing speed to 159 knots.

At 1902:30, responding to the LC-E controller's inquiry, the pilot of N41003 stated "...going around, missed approach," the LC-E controller instructed the pilot of N41003 to maintain 2,000, and to fly runway heading. The pilot's read back was correct. At this time radar data showed N41003 was mid runway, level 2,100, heading 049, at 163 knots.

Radar showed that at 1902:55, N41003 started a right turn, on the RDU VOR (Very High Frequency Omni-directional radio-range) 360-degree radial, 0.25 miles from the VOR, descending to 1,900, turning 076 degrees, and reducing speed to 118 knots.

At 1903:05, the LC-E controller attempted to verify the heading of N41003, and there was no response. Radar data showed N41003 was on the RDU VOR 083 radial, 0.57 miles from the VOR, descending to 1,500, turning 122 degrees, and increasing speed to 154 knots.

Radar data showed that the flight had descended 400 feet in 10 seconds, which calculated to 2,400 feet-per-minute rate of descent, and had traveled about 0.32 miles in 10 seconds.

At 1903:18 the pilot of N41003 was responding to the second LC-E controller's attempt, and the pilot's last radio transmission stated he was "turning back to a heading 050." Radar showed that N41003 was level at 1,600 feet, In a right turn, increasing speed to 166 knots. The LC-E controller instructed the pilot of N41003 to fly a heading 120 degrees, maintain 2,000 feet, and did not get a response.

At 1903:37, the Raleigh Tower Supervisor notified Raleigh South Departure Radar (S-DR) of N41003's go around, missed approach instructions, and lost radio contact.

Radar contact was lost at 1903:47, and N41003 last known radar position was 117 degrees from the RDU VOR, at 2.35 miles, level at 1,600 feet, on a heading of 123 degrees, at a speed of 169 knots.

ATC initiated emergency notifications, air traffic operations were suspended at RDU, and at 1908:40, the Wake County Emergency Services confirmed N41003 had crashed on the east side of Umstead Park.

A witness who lived near the accident site, and who was a private pilot with an instrument rating, stated that he heard the aircraft flying low near his home. The power seemed to be in a cruise configuration, maintaining the same sound up until the crash.

Personnel information

The pilot held an FAA private pilot certificate, with airplane single engine land, instrument airplane last issued on September 25, 2001. He held an FAA class 3 medical certificate issued on June 22, 2001, with limitations; "available glasses for near vision." The pilot last received a biennial flight review, as required by 14 CFR Part 61, on September 25, 2001, the same day he received his instrument rating. The pilot's personal flight logbooks revealed, he had accumulated a total of 926 total flight hours, in all aircraft; 10 total flight hours in this make and model airplane; 33 total night flight hours; and 59 total instrument flight hours. A Certificate of Completion was found in the pilot records from a company called ATM, and stated that the pilot "...has satisfactorily completed 28 hour Piper Malibu Mirage ground and flight initial co