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

Douglas DC-3 accident near Charlotte, North Carolina, September 26, 2000

On September 26, 2000 at about 10:35 am local time, a Douglas DC-3, registered N12907, was substantially damaged in an accident near Charlotte, North Carolina (Charlotte Douglas airport). It was a positioning flight under general aviation rules (Part 91). No one was hurt; 2 people were on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

the right main brake locked after touchdown causing the airplane to yaw and depart the runway, resulting in the landing gear collapsing.

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

What the record shows

Date
September 26, 2000 · about 10:35 am local time
Place
Charlotte, North Carolina · Charlotte Douglas · map
Type
Accident
Injuries
No one was hurt; 2 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Douglas DC-3 · all DC-3s on the register
Registration
N12907 · no longer on the register · serial 27187
Damage
Substantial damage
Flight
Positioning flight · general aviation rules (Part 91)

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

After an approach to runway 5, and touched down at 85 knots, the airplane yawed right, exited the runway, the right main landing gear collapsed, and the airplane nosed over. Examination of the airplane revealed that a right main wheel brake had locked up, and the landing gear had collapsed. Inspection of the right main landing gear assembly and all associated components could not provide any determination as to what caused the main wheel brake to lockup. The brake assembly was broken down into its component parts and inspected. No evidence of malfunction could be detected. No contamination of the hydraulic fluid was evident.

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: 10,500 hours in all; 7,500 in this make and model; 201 in the last 90 days; 101 in the last 30 days; 9,500 as pilot in command
  • Medical certificate: Class 2 (valid medical--no waivers/lim.)
  • Seat: left

The aircraft

  • Airframe total time: 17,425 hours
  • Last inspection: approved inspection programme, September 23, 2000; 14 hours since
  • Maximum gross weight: 26,900 lb
  • Seats: 3
  • Landing gear: retractable
  • Engine: P&W 1830-92 (piston); 0 hours total

The flight

  • Departed from: 6W4 Anderson NC at 9:45 am
  • Destination: CLT
  • Flight plan: IFR
  • Runway 5, 7,502 ft by 150 ft
  • A second pilot was aboard

Weather at the time

  • Light: night, bright
  • Wind: from 200° at 6 knots
  • Visibility: 10 statute miles
  • Sky: overcast at 800 ft; clear
  • Temperature: 55°F (13°C), dew point 54°F (12°C)
  • Altimeter: 29.00 inHg
  • Observation at 10:45 am from CLT

Injuries

FatalSeriousMinorNone
Crew2

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.