The U.S. aircraft register, updated daily
Accidents · NTSB ATL04LA097 · Final report

Amateur-built Lancair Legacy accident near Oakland, Tennessee, April 23, 2004

On April 23, 2004 at about 2:59 pm local time, a amateur-built Lancair Legacy, registered N511WD, was destroyed in an accident near Oakland, Tennessee. It was a personal flight under general aviation rules (Part 91). 1 person was killed. The weather was instrument conditions (cloud, fog or low visibility).

The NTSB's probable cause their words, unchanged

The pilot loss control of the airplane when he continued flight into known thunderstorm and convective activity. A factor is insufficient information provided by ATC personnel.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
April 23, 2004 · about 2:59 pm local time
Place
Oakland, Tennessee · map
Type
Accident
Injuries
1 person was killed.
Weather
instrument conditions (cloud, fog or low visibility)
Aircraft
Amateur-built Lancair Legacy
Registration
N511WD · no longer on the register · serial L2K-147
Damage
Destroyed
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

The pilot received an abbreviated preflight briefing from an FAA Automated Flight Service Station. The pilot informed the briefer that he knew about the weather along his planned route of flight and that he wanted to know about the thunderstorm activity. At the completion of the briefing the pilot informed the briefer that he was going to take a look. The pilot contacted Memphis Approach Control level at 6,000 feet. The controller asked the pilot for his heading and the pilot stated 356-degrees. The controller then asked the pilot if he wanted to continue on that heading or turn east bound to go-around the weather. The pilot stated, "I'd like to avoid the weather" The controller acknowledged the pilot's request and instructed him to turn right to a heading of 060-degrees. The pilot informed the controller, "The route straight ahead as far as I can see looks VMC I'd like to be sure on that but I appreciate your input." The controller replied, "All right - stay on course and let me know if that weather starts to become a problem for you." The pilot acknowledged the controller. The controller informed the pilot that he was going to run into a 10-mile band of showers that was crossing his flight path, but did not provide any information on the intensity of the echoes. The controller stated that the quickest way through the weather was on a heading of 330-degrees. The pilot stated, "alright sir we'll go to three thirty and we'll slow down a little bit." A short time later the controller informed the pilot that it appeared the airplane was encountering some up drafts. The controller informed the pilot there were no targets around his altitude, and he should be out of the weather in about 10 miles. The pilot acknowledged the transmission. The controller made a radio call in the blind stating that radar contact was lost 30 miles northeast of Memphis. He further stated, if you can hear, suggest a heading of northwest bound to get through the weather. You are in an area of level four and level five thunderstorms. No communication was received from the pilot. Review of radar data revealed the airplane started a descending right turn at 09:58:54 and the last radar beacon code was at 09:59:12. No primary radar targets were depicted in the accident area. Federal Aviation Administration (FAA) Order 7110.65, "Air Traffic Control," contains guidance to controllers on the supply of radar-observed weather information to pilots. a. Issue pertinent information on observed/reported weather or chaff areas. Provide radar navigational guidance and/or approve deviations around weather or chaff areas when requested by the pilot. 1. Issue weather and chaff information by defining the area of coverage in terms of azimuth (by referring to the 12-hour clock) and distance from the aircraft or by indicating the general width of the area and the area of coverage in terms of fixes or distance and direction from fixes. 2. Issue the level of echo intensity when that information is available.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

Pilot

  • Certificate: commercial pilot
  • Ratings: multi-engine land; single-engine land; instrument: airplane
  • Flight time: 3,000 hours in all; 105 in this make and model
  • Medical certificate: Class 3 (valid medical--w/ waivers/lim.)
  • Seat: unk
  • Injury: fatal

The aircraft

  • Airframe total time: 130 hours
  • Last inspection: annual inspection, September 1, 2003
  • Maximum gross weight: 1,493 lb
  • Seats: 2
  • Landing gear: retractable
  • Engine: Continental IO-550-N (piston); 0 hours total

The flight

  • Departed from: 66Y Diamondhead MS at 1:40 pm
  • Destination: ALN Alton IL
  • Flight plan: IFR

Weather at the time

  • Light: daylight
  • Wind: from 360° at 10 knots
  • Visibility: 4 statute miles
  • Sky: broken clouds at 2,400 ft; scat at 600 ft
  • Temperature: 66°F (19°C), dew point 64°F (18°C)
  • Altimeter: 30.06 inHg
  • Observation at 2:50 pm from NQA, 16 miles away

Injuries

FatalSeriousMinorNone
Crew1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.