# NTSB ERA16LA114: Cessna 182, N2861R, Gainesville, FL, February 28, 2016 - Type: NTSB accident investigation - Classification: Accident · Minor injuries · Limited investigation · Final report - Date: February 28, 2016, 12:00 local (17:00 UTC) - Place: Gainesville, FL - Coordinates: 29.698055, -82.280281 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=29.6981&lon=-82.2803&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing-landing roll: Collision during takeoff/land](https://openairdocs.org/ntsb-events/490) - Highest injury: Minor injuries - Injuries: 2 minor - Status: Completed, report June 5, 2018 - Report: Approved by Office Director - NTSB office: Eastern Region Aviation - Parties: FAA/FSDO, Continental Motors, Inc., Cessna Aircraft - NTSB case key (mKey): 92775 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA16LA114 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/92775/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=92775 - Page: https://openairdocs.org/ntsb/ERA16LA114 ## Probable cause The failure of the engine crankshaft near the Nos. 4 and 5 crankshaft journals due to oil starvation. The reason for the oil starvation could not be determined during postaccident examination. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Engine (reciprocating): recip engine power section](https://openairdocs.org/ntsb-findings/01058520): Aircraft › Aircraft power plant · Failure (probable cause); cases with it: [Cessna 182K, 1 case](https://openairdocs.org/ntsb-findings/01058520/cases.md?model=2072724), [All aircraft, 233 cases](https://openairdocs.org/ntsb-findings/01058520/cases.md) - [Not determined](https://openairdocs.org/ntsb-findings/05000000): Not determined › Not determined · Unknown/Not determined (probable cause); cases with it: [Cessna 182K, 3 cases](https://openairdocs.org/ntsb-findings/05000000/cases.md?model=2072724), [All aircraft, 2,247 cases](https://openairdocs.org/ntsb-findings/05000000/cases.md) - [Fluids: oil](https://openairdocs.org/ntsb-findings/01071020): Aircraft › Fluids/misc hardware · Fluid level (probable cause); cases with it: [Cessna 182K, 1 case](https://openairdocs.org/ntsb-findings/01071020/cases.md?model=2072724), [All aircraft, 174 cases](https://openairdocs.org/ntsb-findings/01071020/cases.md) - [Object/animal/substance: tree(s)](https://openairdocs.org/ntsb-findings/03022020): Environmental issues › Physical environment · Contributed to outcome; cases with it: [Cessna 182K, 1 case](https://openairdocs.org/ntsb-findings/03022020/cases.md?model=2072724), [All aircraft, 933 cases](https://openairdocs.org/ntsb-findings/03022020/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Approach: Loss of engine power (total)](https://openairdocs.org/ntsb-events/341); cases with it: [Cessna 182K, 3 cases](https://openairdocs.org/ntsb-events/341/sequence.md?model=2072724), [All aircraft, 3,820 cases](https://openairdocs.org/ntsb-events/341/sequence.md) - [Emergency descent: Off-field or emergency landing](https://openairdocs.org/ntsb-events/440); cases with it: [Cessna 182K, 3 cases](https://openairdocs.org/ntsb-events/440/sequence.md?model=2072724), [All aircraft, 3,365 cases](https://openairdocs.org/ntsb-events/440/sequence.md) - [Landing-landing roll: Collision during takeoff/land](https://openairdocs.org/ntsb-events/490) (defining event); cases with it: [Cessna 182K, 2 cases](https://openairdocs.org/ntsb-events/490/sequence.md?model=2072724), [All aircraft, 1,309 cases](https://openairdocs.org/ntsb-events/490/sequence.md) - [Landing-landing roll: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Cessna 182K, 6 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=2072724), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis The commercial pilot stated that, before takeoff, he conducted a preflight inspection of the airplane and added 1 quart of oil to make a total of 8 quarts of oil in the airplane; the engine runup was normal. He further stated that the approximate 2-hour flight was uneventful until after he was cleared to land, when the engine began to run "rough." He enriched the mixture and reduced power, but the engine began shaking, oil sprayed onto the windshield, and then the engine lost total power. He declared an emergency and conducted a forced landing on a road, during which the left wing impacted a tree. An examination of the engine revealed that the crankshaft's Nos. 4 and 5 connecting rod journals exhibited discoloration and heat damage, consistent with oil starvation, and that the rods had separated from the crankcases at their respective journals. The main bearing support mating surfaces were intact and exhibited no signs of fretting, bearing movement, or bearing rotation. The oil galleys and passages in the crankshaft and engine case halves were clear and unrestricted. Although an unmeasured quantity of oil was noted in the engine's oil sump, due to the damage of the sump and crankcase, the quantity of oil in the engine before the accident could not be determined. ## Factual narrative On February 28, 2016, about 1200 eastern standard time, a Cessna 182K, N2816R, experienced a total loss of engine power and performed a forced landing to a road near Gainesville, Florida. The commercial pilot and passenger incurred minor injuries. Visual meteorological conditions prevailed, and an instrument flight rules flight plan was filed for the flight, which originated at Fort Lauderdale Executive Airport (FXE), Fort Lauderdale, Florida, around 1000. The airplane was owned and operated by the pilot. The personal cross-country flight was conducted under the provisions of 14 Code of Federal Regulations Part 91 and had an intended destination of Gainesville Regional Airport (GNV), Gainesville, Florida. According to the pilot, he performed a preflight inspection, added 1 quart of oil to the engine, which totaled 8 quarts of oil, and then performed an engine run up with no anomalies noted. The takeoff, climb, and beginning of the descent phase of flight were "uneventful." The pilot was cleared to land on runway 7 when the engine began to run "rough." He unsuccessfully attempted to alleviate the rough engine noise by enriching the mixture and then reducing the power. The engine began shaking, oil sprayed onto the windscreen of the airplane, and then the engine experienced a total loss of power. The pilot declared an emergency, and elected to land on a road. After touching down on the paved surface, the left wing of the airplane impacted a palm tree and the airplane stopped on the road. A postaccident examination of the airplane revealed that the wings and fuselage were substantially damaged. In addition, the engine cowling was removed to facilitate an engine examination, and a hole was noted in the top of the crankcase in the vicinity of the No. 4 cylinder. In addition, the No. 4 cylinder connecting rod was located on the top of the engine. The engine was retained for further examination. According to Federal Aviation Administration (FAA) records, the airplane was manufactured in 1967, and registered to the pilot/owner in 2014. It was equipped with a Continental Motors IO-550 D series, 300-hp engine, which was installed in February 2000 in accordance with a supplemental type certificate. According to the pilot, the engine had accumulated 2,135 total hours of time in service since the time of rebuild in 1999, and had approximately 130 flight hours since the most recent annual inspection, which was completed on November 3, 2015. The most recent oil change occurred approximately 32 flight hours prior to the accident. Engine manufacturer guidance recommended that the time-based overhaul of the engine occur at 1,700 flight hours or every 12 years. The engine was examined at the manufacturer's facility under NTSB oversight. Examination of the cylinders revealed normal operating signatures and combustion deposits. The intake and exhaust valve faces and seats exhibited full seat contact signatures, and the intake and exhaust valve guides exhibitednormal wear and operating signatures. The intake and exhaust rocker arms and shafts also exhibited normal operating signatures. All piston heads exhibited normal combustion deposits. The Nos. 4 and 5 pistons exhibited impact damage and the No. 4 piston was fractured. Disassembly of the engine revealed the Nos. 4 and 5 connecting rods had separated from the crankshaft at their respective journals. The Nos. 4 and 5 journals exhibited discoloration and heat damage, consistent with oil starvation. The oil galleys and passages in the crankshaft were clear and unrestricted. The engine oil sump was removed from the engine and the forward section exhibited impact damage. In addition, an unmeasured amount of oil and metal particles were noted inside the oil sump. The oil filter remained attached to the engine and was removed. It was disassembled and metal particles were noted in the filter. The crankcase exhibited exterior damage concentrated at the No. 4 cylinder. Cylinder bays Nos. 4 and 5 were mechanically damaged, with portions of the crankcase missing above the No. 4 cylinder. The main bearing support mating surfaces were intact, exhibited no signs of fretting, and exhibited no signs of bearing movement or rotation. The oil galleys and passages in the left and right crankcase halves were intact, clear, and unrestricted. The airplane was equipped with a JPI engine data monitor that was capable of recording engine performance data. The engine data monitor was removed and successfully downloaded at the NTSB's Vehicle Recorder Division in Washington, D.C. The data parameters that were recorded for the accident flight included, fuel flow, exhaust gas temperature, cylinder head temperature, oil temperature, fuel used, battery voltage, and outside air temperature. According to the data, the flight was uneventful until about 1156, when the oil temperature began a steady increase. In the 4 minutes that followed, oil temperature continued to rise and peaked at 202 degrees F prior to the end of the data. According to the engine instruments in the cockpit, the DO NOT EXCEED oil temperature was 225 degrees F. Below 225 degrees F was the normal oil temperature operating range. ## Aircraft - Registration: [N2861R](https://openairdocs.org/deregistered/N2861R-2018-03-13), registration cancelled 2018-03-13, S/N 18258461, built 1967 (OpenAirDocs) - Reported make and model: CESSNA 182 (K) - Registry model: [Cessna 182K](https://openairdocs.org/model/cessna-182k) (registry code 2072724) (OpenAirDocs) - Registry engine: [Continental O-470 series](https://openairdocs.org/engine/continental-o-470-series) (registry code 17026, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 18258461 - Year built: 1967 - Airframe hours: 2139 - Engines: CONT MOTOR IO-550 Series 300 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Last inspection: Annual, November 3, 2015, 130 hours before - Departed: FXE, FORT LAUDERDALE, FL - Destination: GNV, Gainesville, FL - Flight plan: IFR - Airport: GNV, Gainesville Rgnl - Equipment: Electronic flight bag or handheld device, Auto-pilot, ADS-B, Handheld GPS, Onboard weather, Stall warning system ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 61; injuries: minor; private, foreign, commercial; airplane ratings: single-engine land, single-engine sea, multi-engine land; instrument ratings: airplane; medical: class 3, without waivers/limitations; last flight review October 6, 2015; seat: left; restraint: 4-point; flight hours: 1,900 total, 800 in this make and model, 1,500 as pilot in command, 130 in the last 90 days, 40 in the last 30 days, 4 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: calm - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 64 °F, dew point 28 °F - Altimeter: 30.29 inHg - Observed at: KGNV ## 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 20160228021069A](https://openairdocs.org/incident/20160228021069A), Feb 28, 2016: Cessna 182K, Gainesville, FL, Substantial damage. While on approach passing thru 2000 feet for landing on runway 07 at gnv airport the engine began to run 'rough'. The pilot enrichened the mixture with no help… ## Other investigations on N2861R (1) 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. - [NTSB DEN04CA066](https://openairdocs.org/ntsb/DEN04CA066), Apr 21, 2004: Cessna 182K (N2861R), Durango, CO, substantial damage. Probable cause: the pilot's inadequate in-flight planning and decision making. Contributing factors include the crosswind and the crosswind component exceeded. ## Docket (11 files) The files NTSB released with the investigation on March 5, 2018, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=92775. 10.4 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 1.7 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40460546&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF - Pilot's Statement (item 2, .PDF, 548 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40460547&FileExtension=.PDF&FileName=Pilot%27s%20Statement-Master.PDF - Flight Log (item 3, .PDF, 150 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40460548&FileExtension=.PDF&FileName=Flight%20Log-Master.PDF - Engine Maintenance Logbook (item 4, .PDF, 3.3 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40460549&FileExtension=.PDF&FileName=Engine%20Maintenance%20Logbook-Master.PDF - Engine Data Monitor Data Plot (item 5, .PDF, 336 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40460550&FileExtension=.PDF&FileName=Engine%20Data%20Monitor%20Data%20Plot-Master.PDF - Engine Data Monitor Tabular Data (item 6, .CSV, 149 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40460551&FileExtension=.csv&FileName=Engine%20Data%20Monitor%20Tabular%20Data-Master.csv - NTSB Engine Examination Report (item 7, .PDF, 2.8 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40460552&FileExtension=.PDF&FileName=NTSB%20Engine%20Examination%20Report-Master.PDF - Statement of Party Representatives to NTSB Investigation (item 8, .PDF, 512 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40460553&FileExtension=.PDF&FileName=Statement%20of%20Party%20Representatives%20to%20NTSB%20Investigation-Master.PDF - Photo Array (item 9, .PDF, 2 photos, 846 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40460554&FileExtension=.PDF&FileName=Photo%20Array-Master.PDF - Evidence Control Form (item 10, .PDF, 79 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40460555&FileExtension=.PDF&FileName=Evidence%20Control%20Form-Master.PDF - Release of Aircraft Wreckage, NTSB Form 6120.15 (item 11, .PDF, 36 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40460677&FileExtension=.PDF&FileName=Release%20of%20Aircraft%20Wreckage,%20NTSB%20Form%206120.15-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.