# NTSB WPR18FA201: Douglas DC3, N47HL, Burnet, TX, July 21, 2018

- Type: NTSB accident investigation
- Classification: Accident · Serious injuries · Class 2 · Field · Final report
- Date: July 21, 2018, 09:15 local (14:15 UTC)
- Place: Burnet, TX
- Coordinates: 30.737222, -98.238609 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=30.7372&lon=-98.2386&mi=10
- Phase of flight: [Takeoff](https://openairdocs.org/ntsb-phases/300) (OpenAirDocs' grouping)
- Defining event: [Takeoff: Loss of control in flight](https://openairdocs.org/ntsb-events/240)
- Highest injury: Serious injuries
- Injuries: 6 serious, 1 minor, 6 uninjured
- Status: Completed
- Report: Approved by Office Director
- Investigation class: Class 2
- NTSB office: Western Pacific Region
- Parties: Federal Aviation Administration, Commemorative Air Force
- NTSB case key (mKey): 97843
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR18FA201
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/97843/pdf
- NTSB docket: https://data.ntsb.gov/Docket?ProjectID=97843
- Page: https://openairdocs.org/ntsb/WPR18FA201

## Probable cause

The copilot's failure to maintain directional control during the initial takeoff roll and the pilot's failure to adequately monitor the copilot during the takeoff and his delayed remedial action, which resulted in the airplane briefly becoming airborne and subsequently experiencing an aerodynamic stall.

## Findings

NTSB's coded findings; those marked are part of the probable cause.

- [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Copilot (probable cause); cases with it: [Douglas DC3, 1 case](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=3021401), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md)
- [Action: delayed action](https://openairdocs.org/ntsb-findings/02041025): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Douglas DC3, 2 cases](https://openairdocs.org/ntsb-findings/02041025/cases.md?model=3021401), [All aircraft, 894 cases](https://openairdocs.org/ntsb-findings/02041025/cases.md)
- [Attention/monitoring: monitoring other person](https://openairdocs.org/ntsb-findings/02021535): Personnel issues › Psychological · Pilot (probable cause); cases with it: [Douglas DC3, 2 cases](https://openairdocs.org/ntsb-findings/02021535/cases.md?model=3021401), [All aircraft, 200 cases](https://openairdocs.org/ntsb-findings/02021535/cases.md)
- [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Douglas DC3, 1 case](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=3021401), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md)
- [Performance/control parameters: directional control](https://openairdocs.org/ntsb-findings/01062020): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Douglas DC3, 2 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md?model=3021401), [All aircraft, 3,958 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md)
- [Performance/control parameters: angle of attack](https://openairdocs.org/ntsb-findings/01062042): Aircraft › Aircraft oper/perf/capability · Capability exceeded (probable cause); cases with it: [Douglas DC3, 1 case](https://openairdocs.org/ntsb-findings/01062042/cases.md?model=3021401), [All aircraft, 990 cases](https://openairdocs.org/ntsb-findings/01062042/cases.md)

## Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event best describes what happened.

- [Takeoff: Loss of control on ground](https://openairdocs.org/ntsb-events/230); cases with it: [Douglas DC3, 2 cases](https://openairdocs.org/ntsb-events/230/sequence.md?model=3021401), [All aircraft, 4,585 cases](https://openairdocs.org/ntsb-events/230/sequence.md)
- [Takeoff: Loss of control in flight](https://openairdocs.org/ntsb-events/240) (defining event); cases with it: [Douglas DC3, 1 case](https://openairdocs.org/ntsb-events/240/sequence.md?model=3021401), [All aircraft, 5,002 cases](https://openairdocs.org/ntsb-events/240/sequence.md)
- [Takeoff: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Douglas DC3, 1 case](https://openairdocs.org/ntsb-events/470/sequence.md?model=3021401), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md)

## Analysis

According to the copilot, before takeoff, he and the pilot had briefed that the copilot would conduct the takeoff for the planned cross-country flight and be the pilot flying and that the pilot would be the pilot monitoring. The accident flight was the copilot's first takeoff in the accident airplane with it at or near its maximum gross weight. The pilot reported that he taxied the airplane onto the runway and locked the tailwheel in place and that the copilot then took over the controls. About 13 seconds after the start of the takeoff roll, the airplane veered slightly right, and the copilot counteracted with left rudder input. The airplane then swerved left, and shortly after the pilot took control of the airplane. The airplane briefly became airborne; the pilot stated that he knew the airplane was slow as he tried to ease it back over to the runway and set it back down. Subsequently, he felt the shudder “of a stall,” and the airplane rolled left and impacted the ground, the right main landing gear collapsed, and the left wing struck the ground. After the airplane came to a stop, a postimpact fire ensued. All the airplane occupants egressed through the aft left door. Postaccident examination of the airplane revealed no evidence of any mechanical malfunctions or failures with the flight controls or tailwheel. Both outboard portions of the of the aluminum shear pin within the tailwheel strut assembly were sheared off, consistent with side load forces on the tailwheel during the impact sequence. The copilot obtained his pilot-in-command type rating and his checkout for the accident airplane about 2 months and 2 weeks before the accident, respectively. The copilot had conducted two flights in the accident airplane with a unit instructor before the accident. The instructor reported that, during these flights, he noted that the copilot had directional control issues; made "lazy inputs, similar to those for small airplanes"; tended to go to the right first; and seemed to overcorrect to the left by leaving control inputs in for too long. He added that, after the checkout was completed, the copilot could take off and land without assistance; however, he had some concern about the his reaction time to a divergence of heading on the ground. Given the evidence, it is likely the copilot failed to maintain directional control during the initial takeoff roll. It is also likely that, if the pilot, who had more experience in the airplane, had monitored the copilot's takeoff more closely and taken remedial action sooner, he may have been able to correct the loss of directional control before the airplane became briefly airborne and subsequently experienced an aerodynamic stall.

## Factual narrative

The airframe and engine logbooks, including the weight and balance, were onboard the airplane at the time of the accident and were destroyed by fire; therefore, the airplane’s weight and balance at the time of the accident could not be calculated. However, the CAF unit operations officer reported that the airplane was at or near its maximum gross weight. On July 21, 2018, about 0915 central daylight time, a Douglas DC-3 airplane, N47HL, was destroyed when it was involved in an accident near Burnet, Texas. The pilot, crew chief, and four passengers sustained serious injuries; one passenger sustained minor injuries; and the copilot and five passengers were not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. Representatives from the Commemorative Air Force (CAF) reported that all of the passengers were volunteers at the CAF wing and that the intention of the flight was to travel to Oshkosh, Wisconsin, to attend an airshow. An intermediate fuel stop was planned at Sedalia Regional Airport (DMO), Sedalia, Missouri. The copilot reported that, during a discussion with the pilot before the flight, he told the pilot that his time in the airplane was low, that almost all his tailwheel time was in small airplanes. The pilot replied that “he was a 4,000-hour DC-3 pilot and that there weren't going to be any problems…if you could taxi it, you could fly it." Additionally, they briefed that the copilot would conduct the takeoff and be the pilot flying and that the pilot would be the pilot monitoring. The pilot stated that the airplane would be heavier than what the copilot was used to and that “it might be necessary to help the tail up.” He asked the copilot if he was “comfortable taking off with a heavy airplane,” and the copilot responded that he was. The copilot stated that the pilot taxied the airplane to the run-up area, where they completed all pretakeoff checks and an engine run-up. The pilot then taxied the airplane onto runway 19. Subsequently, the copilot took control of the airplane, conducted a pretakeoff brief, and initiated the takeoff sequence. After the airplane began to move, he "applied some forward pressure on the control yoke." The pilot told him that he was applying the pressure too early, so he then slightly relaxed forward pressure on the control yoke. About 10 seconds into the takeoff roll, the airplane drifted right, at which time the copilot applied left rudder input, followed shortly after by the pilot taking control of the airplane. The captain reported that, after taxiing to the runway, “he didn’t like how things looked, so he unlocked the tailwheel, let the…[airplane] roll forward 6 to 7 inches, relocked the tailwheel, and verified it was locked.” The pilot couldn’t recall whether, during the initial stages of the takeoff roll, if the airplane swerved right, but he did recall telling the copilot not “to push the tail up because it was heavy and that the airplane then swervedleft. He then yelled "right rudder" three times. Shortly thereafter, he said, “my airplane” and then took control of the airplane. As he put his hands on the control yoke, he noticed that either the tail had started to lower or that the main wheels had just lifted off the ground. He knew the airplane was slow as he tried to ease it back over to the runway and set it back down and then felt the shudder “of a stall." The airplane rolled left and impacted the ground, the right main landing gear (MLG) collapsed, and the left wing struck the ground. After the airplane came to a stop, a postimpact fire ensued. All the airplane occupants egressed through the aft left door. The crew chief, who was seated behind the pilots, reported that, during the takeoff sequence, he was concentrating on the instrument panel and heard the pilot tell the copilot not to push forward on the stick and to let the tail come up naturally. About 3 to 5 seconds later, he heard the pilot say, "I have the aircraft." He said he looked outside and could see that they were on the far-left side of the runway and that the pilot was on the controls, moving the rudder pedals and ailerons. A video recorded by a witness located on the airport’s ramp area showed that about 13 seconds after the airplane started the takeoff roll, it veered slightly right, and about 3 seconds later, it veered left. The airplane then exited the left side of the runway while turning right. The airplane briefly became airborne in a right-wing-low attitude before it rolled left. Subsequently, the left wing struck the ground, the airplane continued to yaw left as it impacted the ground, and the right MLG collapsed. Pilot The pilot reported over 4,500 hours of experience in tailwheel aircraft. The pilot last flew the DC-3 about 1 month before the accident. Copilot The copilot reported that he completed his DC-3 type rating training in May 2018, which included 8 hours in the DC-3, and 1.6 hours for a pilot-in-command (PIC) checkride. He added that, during this training, he never sat in the right seat. He recalled that the DC-3 was difficult to taxi but that he “felt that he never had issues” flying it because all the instrument approaches were standard. However, he did add that takeoffs and landings were "something you need experience with and practice with." The copilot then conducted two flights in the accident airplane with a CAF unit instructor. He stated that he felt his takeoffs and landings were very different in the accident airplane and that it was "more squirrely" than the airplane in which he had trained. The CAF unit instructor reported that the accident airplane was empty with 400 gallons of fuel onboard for their first flight and that the copilot flew the airplane from the right seat. The copilot had no issues in the air; they performed landings; and he helped the copilot through the systems, checklists, and procedures. During the second training flight, the instructor performed the first half of theflight with the copilot as the pilot flying and the second half of the flight with the copilot as the nonflying pilot. The instructor added that the copilot had issues with directional control on the ground, including that his control inputs were "lazy inputs, similar to those for small airplanes"; tended to go to the right first; and seemed to overcorrect to the left by leaving control inputs in for too long. The instructor added that the copilot's first flight in the accident airplane was not satisfactory but that he had shown gradual improvement with directional control during the second flight. He signed off the copilot because, during the second flight's debrief, the copilot's attitude was good, and his directional control of the airplane had improved. At the completion of the checkout, the instructor said that the copilot could take off and land without assistance; however, he had some concern about his reaction time to a divergence of heading on the ground. Examination of the accident site revealed that the airplane came to rest upright on a heading about 113° magnetic, about 145 ft east of the left side of runway 19, partially on the taxiway. (Figure 1) Figure 1. A photograph showing the main wreckage in relation to runway 19 and taxiway C. During examination of the runway, a skid mark consistent with the right MLG tire, was observed about 843 ft from the approach end of the runway. The mark extended from slightly right of the runway centerline toward the 1,000-ft markers and moved progressively toward the right side of the runway. Beginning about 1,106 from the approach end of the runway, the skid mark began to move progressively left, and Its angle toward the left side of the runway started increasing. A ground impression was observed left of the runway about 1,566 ft from its approach end, consistent with the right MLG exiting the left side of the runway. The impression then continued almost parallel to the runway until it reached a runway light, slightly beyond which the impression stopped. Another ground impression was observed about 2,111 ft from the approach end and extended parallel to the runway for about 200 ft, consistent with impact by the left wing. Another ground impression was observed about 2,377 ft from the approach end of the runway, which extended from the wheel skid mark toward the main wreckage, consistent with the left MLG exiting the left side of the runway. See figure 2 for a photograph showing the wheel skid mark on the runway and the ground impressions left of the runway. Figure 2. A photograph showing the left MLG wheel skid mark on the runway and the left MLG ground impressions left of the runway. Another ground impression was observed about 2,436 ft from the approach end of the runway, consistent with the right MLG. The main wreckage came to rest about 2,638 ft from the approach end of the runway. (See figure 3 for an overhead view of the left MLG wheel skid mark, right and left MLG wheel impressions, and theleft-wing impact mark locations.) Figure 3. An overhead image of the right MLG wheel skid mark, the right and left MLG ground impressions, and the left-wing impact mark locations observed at the accident site. Grass within about 200 ft of the main wreckage was burnt by postimpact fire, which consumed the fuselage from the nose cone aft to about 3 ft forward of the left cargo door. The wing center section of the fuselage was mostly consumed by fire and extended outboard to the right-wing attachment point and about 2 ft outboard of the left-wing attachment point. (See figure 4 for a photograph showing the main wreckage and postimpact fire damage.) All cables in the throttle quadrant remained attached but exhibited thermal or fire damage. The tailwheel lock engagement handle was not found. Figure 4. A photograph showing the main wreckage and postimpact damage. The tailwheel remained attached to the airframe and was oriented about 45° left of the centered position. The tailwheel locking mechanism appeared to be in the locked position. The tailwheel locking cable remained attached to the mechanism and was continuous to about the fuel tanks area. The tailwheel locking shear pin remained within the tailwheel strut assembly; however, the outboard portions of the aluminum shear pin were sheared off and located in the fuselage near the tailwheel assembly. The rudder, vertical stabilizer and left and right horizontal stabilizers and elevators remained attached via their respective mounts and were undamaged. The rudder and elevator trim tabs remained attached and appeared to be in the neutral position. Flight control continuity was established from all primary flight controls to the center section of the fuselage near the aft side of the fuel tanks and from about 2 ft forward of the fuel tanks to the control columns. No evidence was found indicating that any flight control lock had been installed. The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.

## Aircraft

- Registration: [N47HL](https://openairdocs.org/deregistered/N47HL-2020-02-03), registration cancelled 2020-02-03, S/N 27203, built 1943 (OpenAirDocs)
- Reported make and model: Douglas DC3 (B)
- Registry model: [Douglas DC3](https://openairdocs.org/model/douglas-dc3) (registry code 3021401) (OpenAirDocs)
- Registry engine: [Pratt & Whitney R-1830 series](https://openairdocs.org/engine/pratt-whitney-r-1830-series) (registry code 52020, reciprocating) (OpenAirDocs)
- Category: Airplane
- Serial number: 27203
- Year built: 1943
- Engines: Pratt & Whitney 1830 1200 horsepower reciprocating; Pratt & Whitney 1830 1200 horsepower reciprocating
- Damage: Destroyed
- Flight: Business, Part 91
- Operator: Commemorative Air Force
- Registered owner: American Airpower Heritage Flying Museum
- Airworthiness certificate: Standard, Normal
- Departed: BMQ, Burnet, TX
- Destination: DMO, Sedalia, MO
- Airport: BMQ, Burnet Muni Kate Craddock Fiel, runway 19, 5,000 × 75 ft, asphalt
- Equipment: Unknown

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 61; injuries: serious; airline transport; airplane ratings: multi-engine land, single-engine land; medical: class 2, with waivers/limitations; last flight review March 2, 2018; seat: left; restraint: lap only; flight hours: 12,500 total, 2,500 in this make and model
- Co-pilot; age 71; injuries: none; commercial, flight instructor, airline transport; airplane ratings: single-engine land, single-engine sea, multi-engine land; instrument ratings: airplane; medical: class 2, with waivers/limitations; last flight review May 4, 2018; seat: right; restraint: lap only; flight hours: 8,000 total, 17 in this make and model, 30 in the last 90 days, 10 in the last 30 days

## Weather

- Conditions: Visual (VMC), Day
- Wind: 200° at 9 knots
- Visibility: 9 statute miles
- Temperature: 84 °F, dew point 70 °F
- Altimeter: 30.07 inHg
- Observed at: KBMQ

## FAA reports on this event (1)

The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs).

- [Accident 20180721017529A](https://openairdocs.org/incident/20180721017529A), Jul 21, 2018: Douglas DC3, Burnet, TX, Destroyed. The recently type rated copilot was attempting takeoff when the captain took control and continued the attempted takeoff. The aircraft was not in control and…

## Docket (10 files)

The files NTSB released with the investigation on December 4, 2020, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=97843. 21.2 MB in all.

- Pilot/operator aircraft accident report, NTSB form 6120.1 - captain (item 1, PDF, 10 pages, 1.1 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=9384286&FileExtension=pdf&FileName=1%20Captain%206120_Redacted-Rel.pdf
- Pilot/operator aircraft accident report, NTSB form 6120.1 - co-pilot (item 2, PDF, 12 pages, 6.3 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=9384642&FileExtension=pdf&FileName=3%20Co%20Pilot%206120%20FLat_Redacted-Rel.pdf
- Record of conversations - captain (item 3, PDF, 5 pages, 242 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=9385069&FileExtension=pdf&FileName=2%20Captain%20ROC-Rel.pdf
- Record of conversations - co pilot (item 4, PDF, 5 pages, 199 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=9385217&FileExtension=pdf&FileName=5%20Co%20Pilot%20ROCs-Rel.pdf
- Record of conversation - instructor / check pilot (item 5, PDF, 4 pages, 185 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=9383651&FileExtension=pdf&FileName=6%20CAF%20Check%20Pilot%20ROCs-Rel.pdf
- Record of conversation - crew chief (item 6, PDF, 4 pages, 106 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=9385117&FileExtension=pdf&FileName=7%20Crew%20Cheif%20ROC-Rel.pdf
- Record of conversations - caf unit operations officer (item 7, PDF, 4 pages, 190 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=9384651&FileExtension=pdf&FileName=8%20Unit%20Operations%20Officer%20ROCs-Rel.pdf
- NTSB accident site examination summary report (item 8, PDF, 13 pages, 14 photos, 5.8 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=9384870&FileExtension=pdf&FileName=9%20NTSB%20accident%20site%20examination%20summary-Rel.pdf
- Photo array (item 9, PDF, 14 pages, 14 photos, 2.1 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=9394273&FileExtension=pdf&FileName=photo%20array-Rel.pdf
- Witness video (item 10, MP4, 5.0 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=11570399&FileExtension=mp4&FileName=dc3%20video%20edited%20no%20audio-Rel.mp4

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.