# NTSB ERA14LA072: Cessna 182T, N963CP, Burlington, NC, December 17, 2013 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: December 16, 2013, 21:15 local (Dec 17, 2013, 02:15 UTC) - Place: Burlington, NC - Coordinates: 36.048889, -79.474166 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=36.0489&lon=-79.4742&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: No injuries - Injuries: 2 uninjured - Status: Completed, report March 17, 2015 - Report: Approved by Office Director - NTSB office: Eastern Region Aviation - Parties: FAA/FSDO - NTSB case key (mKey): 88559 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA14LA072 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/88559/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=88559 - Page: https://openairdocs.org/ntsb/ERA14LA072 ## Probable cause A loss of airplane control during takeoff for reasons that could not be determined due to the postaccident condition of the elevator control system. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Performance/control parameters: pitch control](https://openairdocs.org/ntsb-findings/01062022): Aircraft › Aircraft oper/perf/capability · Attain/maintain not possible (probable cause); cases with it: [Cessna 182T, 2 cases](https://openairdocs.org/ntsb-findings/01062022/cases.md?model=2072703), [All aircraft, 526 cases](https://openairdocs.org/ntsb-findings/01062022/cases.md) - [Not determined](https://openairdocs.org/ntsb-findings/05000000): Not determined › Not determined · Unknown/Not determined (probable cause); cases with it: [Cessna 182T, 2 cases](https://openairdocs.org/ntsb-findings/05000000/cases.md?model=2072703), [All aircraft, 2,247 cases](https://openairdocs.org/ntsb-findings/05000000/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Takeoff: Unknown or undetermined](https://openairdocs.org/ntsb-events/000); cases with it: [Cessna 182T, 2 cases](https://openairdocs.org/ntsb-events/000/sequence.md?model=2072703), [All aircraft, 1,703 cases](https://openairdocs.org/ntsb-events/000/sequence.md) - [Takeoff: Loss of control in flight](https://openairdocs.org/ntsb-events/240) (defining event); cases with it: [Cessna 182T, 11 cases](https://openairdocs.org/ntsb-events/240/sequence.md?model=2072703), [All aircraft, 5,002 cases](https://openairdocs.org/ntsb-events/240/sequence.md) - [Emergency descent: Off-field or emergency landing](https://openairdocs.org/ntsb-events/440); cases with it: [Cessna 182T, 2 cases](https://openairdocs.org/ntsb-events/440/sequence.md?model=2072703), [All aircraft, 3,365 cases](https://openairdocs.org/ntsb-events/440/sequence.md) - [Landing-landing roll: Runway excursion](https://openairdocs.org/ntsb-events/300); cases with it: [Cessna 182T, 10 cases](https://openairdocs.org/ntsb-events/300/sequence.md?model=2072703), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md) - [Landing-landing roll: Landing area undershoot](https://openairdocs.org/ntsb-events/370); cases with it: [Cessna 182T, 1 case](https://openairdocs.org/ntsb-events/370/sequence.md?model=2072703), [All aircraft, 201 cases](https://openairdocs.org/ntsb-events/370/sequence.md) ## Analysis The pilot reported that he was practicing night takeoffs and landings. He completed two takeoffs and landings without incident; however, during the third takeoff, as the airplane was climbing to between about 10 and 20 ft above ground level, it stopped climbing, and the pilot felt increased resistance on the elevator control. The airplane did not respond to elevator control inputs, and it subsequently pitched nose down and descended. The airplane touched down before departing the left side of the runway. The nose gear collapsed, and the airplane sustained substantial damage to the firewall and nose section. The pilot reported that the airplane had a recent history of elevator trim issues, which included difficulty controlling the elevator. The elevator trim jackscrew had been removed, inspected, and reinstalled about 1 week before the accident, and the airplane had since been operated about 7 hours. Examination of the airplane, including the elevator control system, did not reveal any preimpact mechanical malfunctions that would have precluded normal operation; however, impact damage precluded the ability to conduct a complete functional check of the elevator control system. ## Factual narrative On December 16, 2013, about 2115 eastern standard time, a Cessna 182T, N963CP, operated by the Civil Air Patrol (CAP), was substantially damaged during takeoff from the Burlington-Alamance Regional Airport, Burlington, North Carolina. The private pilot and a passenger were not injured. Night visual meteorological conditions prevailed and no flight plan had been filed for the personal flight that was conducted under the provisions of 14 Code of Federal Regulations Part 91.The pilot reported that he was practicing night takeoffs and landings from runway 6, a 6,405-foot-long, 100-foot-wide, asphalt runway. He completed two takeoffs and landings without incident; however, during the third takeoff, as the airplane reached an altitude of about 10 to 20 feet above the ground, it stopped climbing, and the pilot felt increased resistance on the elevator control. The airplane did not respond to elevator control inputs, pitched nose-down, and descended. The airplane touched back down onto the runway before departing the left side and rolling onto the grass. The nose gear collapsed and the airplane sustained substantial damage to the firewall and nose section. The pilot further reported that the airplane had a recent history of elevator trim issues, which included difficulty controlling the elevator, and had undergone maintenance related to the elevator system during the week prior to the accident. Examination of the airplane by a Federal Aviation Administration inspector did not reveal any preimpact mechanical malfunctions which would have precluded normal operation. The elevator trim was observed in the normal takeoff position and the flaps were retracted. Utilizing the elevator trim wheel, the trim was exercised through its complete range of travel. Elevator control cable continuity was confirmed from the yoke to the elevator control surface; however, the inspector noted the cables were loose with rub marks visible on the frame. Upon further inspection, impact damage was noted on the forward underside of the airframe and both pulleys underneath the rudder pedals which guide the respective up and down elevator cables were damaged. The airplane was manufactured in 2007 and had been operated for about 1,700 total hours at the time of the accident. Review of maintenance records revealed that on December 9, 2013, maintenance was performed on the airplane which included removal, and inspection of the elevator trim jackscrew. The airplane had been operated for about 7 hours since it was returned to service, and about 70 hours since its most recent annual inspection, which was performed on August 29, 2013. As of the date of this report, additional postaccident inspections by CAP maintenance personnel did not reveal any preaccident failures or conditions which would have restricted elevator flight control movement. The pilot reported 165 hours of total flight experience, which included about 23 hours in the same make and model as the accident airplane, and about12 hours logged as night flight experience. The pilot's previous night currency flights were performed on September 13, 2013. ## Aircraft - Registration: [N963CP](https://openairdocs.org/aircraft/N963CP), registered now, S/N 18281973, built 2007 (OpenAirDocs) - Reported make and model: CESSNA 182T - Registry model: [Cessna 182T](https://openairdocs.org/model/cessna-182t) (registry code 2072703) (OpenAirDocs) - Registry engine: [Lycoming IO-540-AB1A5](https://openairdocs.org/engine/lycoming-io-540-ab1a5) (registry code 41808, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 18281973 - Year built: 2007 - Airframe hours: 1703 - Engines: LYCOMING IO-540-AB1A5 230 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Civil Air Patrol - Registered owner: Civil Air Patrol - Airworthiness certificate: Standard, Normal - Last inspection: Annual, August 29, 2013, 69 hours before - Departed: BUY, Burlington, NC - Destination: BUY, Burlington, NC - Airport: BUY, Burlington-Alamance Regional, runway 06, 6,405 × 100 ft, asphalt - Equipment: Stall warning system ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 56; injuries: none; private; airplane ratings: single-engine land; medical: class 3, without waivers/limitations; last flight review December 15, 2013; seat: left; restraint: 3-point; flight hours: 165 total, 23 in this make and model, 81 as pilot in command, 9 in the last 90 days, 2 in the last 30 days, 2 in the last 24 hours ## Weather - Conditions: Visual (VMC), Night - Wind: calm - Visibility: 10 statute miles - Temperature: 41 °F, dew point 34 °F - Altimeter: 30.10 inHg - Icing: Unknown - Turbulence: Unknown - Observed at: BUY ## 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 20131216023949A](https://openairdocs.org/incident/20131216023949A), Dec 16, 2013: Cessna 182T, Burlington, NC, Substantial damage. On December 16, 2013, at approximately 21:00 EST, the pilot was performing night currency take offs and landings. On the 3rd takeoff of the night the pilot was… ## Docket (9 files) The files NTSB released with the investigation on January 28, 2015, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=88559. 5.6 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 2.0 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40421803&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF - FAA Inspector Statement (item 2, .PDF, 18 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40421804&FileExtension=.PDF&FileName=FAA%20Inspector%20Statement-Redacted.PDF - Aircraft Bill of Sale (Accident Airplane) (item 3, .PDF, 215 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40421805&FileExtension=.PDF&FileName=Aircraft%20Bill%20of%20Sale%20(Accident%20Airplane)-Redacted.PDF - Aircraft Airworthiness Certificate (item 4, .PDF, 133 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40421806&FileExtension=.PDF&FileName=Aircraft%20Airworthiness%20Certificate-Redacted.PDF - Maintenance Records Excerpts (item 5, .PDF, 232 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40421807&FileExtension=.PDF&FileName=Maintenance%20Records%20Excerpts-Redacted.PDF - Airport Weather Observations (item 6, .PDF, 101 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40421808&FileExtension=.PDF&FileName=Airport%20Weather%20Observations-Master.PDF - Photo 1 – Airplane as it came to rest (item 7, .PDF, 134 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40421809&FileExtension=.PDF&FileName=Photo%201%20%E2%80%93%20Airplane%20as%20it%20came%20to%20rest-Master.PDF - Photo 2 – Airplane Hour Meter (item 8, .PDF, 118 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40421810&FileExtension=.PDF&FileName=Photo%202%20%E2%80%93%20Airplane%20Hour%20Meter-Master.PDF - Photo 3 – Damage in vicinity of elevator pulley and cable (item 9, .PDF, 2.7 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40421811&FileExtension=.PDF&FileName=Photo%203%20%E2%80%93%20Damage%20in%20vicinity%20of%20elevator%20pulley%20and%20cable-Master.PDF 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.