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

Piper J3C-65 accident near Durham, North Carolina, May 30, 2008

On May 30, 2008 at about 10:54 pm local time, a Piper J3C-65, registered N3544N, was substantially damaged in an accident during approach (VFR pattern final) near Durham, North Carolina (Lake Ridge Aero Park airport). It was a personal flight under general aviation rules (Part 91). 1 person was seriously injured. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot's failure to maintain clearance from trees while approaching to land.

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

What the record shows

Date
May 30, 2008 · about 10:54 pm local time
Place
Durham, North Carolina · Lake Ridge Aero Park · map
Type
Accident
Injuries
1 person was seriously injured.
Weather
visual conditions (good weather)
Aircraft
Piper J3C-65 · all J3C-65s on the register
Registration
N3544N · no longer on the register · serial 22778
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

Examination of the airplane by a Federal Aviation Administration (FAA) inspector found that the airplane had impacted the tops of trees and came to rest on a road in a steep nose down attitude, about 100-yards short of the runway. The propeller and spinner showed evidence of high speed rotation at the time of impact. All flight controls were intact. No evidence of precrash failure or malfunction of the aircraft structure, flight controls, or engine was found. The pilot stated that due to his injuries he had no "recollection of the accident and had lost all recent memories since the accident."

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

What happened, in order

  1. Collision during takeoff/land during approach (VFR pattern final) defining event

The NTSB's findings

  • cause Not determined › Not determined › (general) › (general) › Unknown/Not determined
  • Environmental issues › Physical environment › Object/animal/substance › Tree(s) › Contributed to outcome

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 1,000 hours in all
  • Medical certificate: Class 3 (without waivers/limitations)
  • Seat: frt
  • Injury: serious injuries

The aircraft

  • Airframe total time: 2,719 hours
  • Last inspection: annual inspection, March 1, 2008; 40.6 hours since
  • Maximum gross weight: 1,220 lb
  • Seats: 2
  • Landing gear: fixed
  • Engine: Continental A65-8 (piston); 0 hours total

The flight

  • Departed from: 8NC8 Durham NC at 10:34 pm
  • Destination: 8NC8 Durham NC
  • Flight plan: none

Weather at the time

  • Light: dusk
  • Wind: from 210° at 11 knots
  • Visibility: 10 statute miles
  • Sky: a few clouds at 4,500 ft
  • Temperature: 82°F (28°C), dew point 63°F (17°C)
  • Altimeter: 30.05 inHg
  • Observation at 10:51 pm from RDU, 7 miles away

Injuries

FatalSeriousMinorNone
Flight 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.